On Mon, Aug 21, 2023 at 03:09:22PM -0400, Matthew Howell wrote:
> On Mon, 21 Aug 2023, Greg KH wrote:
>
> > ⚠Caution: External email. Exercise extreme caution with links or attachments.⚠
> >
> >
> > On Mon, Aug 21, 2023 at 12:06:17PM -0400, Matthew Howell wrote:
> > > From: Matthew Howell <matthew.howell@xxxxxxxxxxxx>
> > >
> > > These Sealevel 7xxxC IDs are no longer needed because we (Sealevel) will
> > > be releasing the cards with the standard Exar hardware IDs. This is due
> > > to the selected IDs causing unexpected behaviors on some Windows systems.
> > >
> > > Reverts: 14ee78d ("Add support for Sealevel 7xxxC serial cards")
> >
> > If this is a real "revert", then perhaps just do that revert instead?
>
> I will try that if that is preferable.
It is please.
> > Also, as per our documentation, you need a sha1 a bit longer than that
> > :)
>
> Sorry, I thought I had seen them referenced as 7 characters in other
> posts. Will fix when I resubmit.
>
> >
> > And "Reverts:" isn't a valid tag, perhaps "Fixes:"?
> >
> > And meta-note, your patch series was not linked together, how did you
> > send them?
>
> I used Alpine.
> Sorry for the hassle...but could you clarify how they should be linked? Do
> you mean I should have sent the second patch as a reply to this one?
Yes. That way our tools automatically pick it up as a patch series.
> I didn't see any specifics about patch linking in the documentation so I
> am not/was not clear on the intended or 'best practice' way of linking
> patches.
git send-email does it automatically for you, or you have to do it
manually if you don't use that, sorry.
thanks,
greg k-h
