On Mon, 18 Sep 2023, Greg KH wrote: > On Thu, Sep 14, 2023 at 03:51:26PM -0400, Matthew Howell wrote: > > On Thu, 14 Sep 2023, Andy Shevchenko wrote: > > > On Thu, Sep 14, 2023 at 08:28:47AM -0400, Matthew Howell wrote: > > > > From: Matthew Howell <matthew.howell@xxxxxxxxxxxx> > > > > > > > > Hardware ID of Sealevel 7xxxC cards changed prior to release. This has rendered 14ee78d5932a redundant. > > > > > > Too long line. > > > > > > > Revert "serial: exar: Add support for Sealevel 7xxxC serial cards" > > > > > > > > This reverts commit 14ee78d5932afeb710c8305196a676a715bfdea8. > > > > > > > > Link: https://lore.kernel.org/all/72b3e74e-ced6-784c-01e0-8a851326a203@xxxxxxxxxxxx/T/ > > > > Fixes: 14ee78d5932a ("Add support for Sealevel 7xxxC serial cards") > > > > Signed-off-by: Matthew Howell <matthew.howell@xxxxxxxxxxxx> > > > > > > The patch 1 and patch 2 have not been linked via email, so mail archives and > > > mail clients do not see this as a thread. I suggest to use `git send-email` for > > > patches. With --thread option (which I believe should be default) it chains > > > the mails it sends. > > > > I have not seen any way to setup git send-mail with this email as git > > send-email seems to lack OAUTH2. If you can set it up with OAUTH2 & O365 > > I have not been able to find any documentation or guides on how to do > > this. > > If you are using mutt, just respond to the first patch with the second > one. Otherwise our tools really don't like dis-joined patch series and > I have to dig them out by hand :( I understand. I've been doing that (but in Alpine), it just seems like it failed to thread on the most recent submissions for some reason, but I'm not sure why. I will take a look at the headers next time before sending the reply to make sure it is adding the in-reply-to header correctly. > I'll do so for this one, but in the future, please fix up. > > thanks, > > greg k-h >
