From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Matthew Howell <matthew.howell@sealevel.com>
Cc: gregkh@linuxfoundation.org, jeff.baldwin@sealevel.com,
james.olson@sealevel.com, ryan.wenglarz@sealevel.com,
darren.beeson@sealevel.com, linux-serial@vger.kernel.org,
ilpo.jarvinen@linux.intel.com
Subject: Re: [PATCH V5 1/2] serial: exar: Revert "serial: exar: Add support for Sealevel 7xxxC serial cards"
Date: Thu, 14 Sep 2023 22:04:07 +0300 [thread overview]
Message-ID: <ZQNZJwJoad0EkIYL@smile.fi.intel.com> (raw)
In-Reply-To: <a804d136-4865-f528-6434-68a7358d7606@sealevel.com>
On Thu, Sep 14, 2023 at 08:28:47AM -0400, Matthew Howell wrote:
> From: Matthew Howell <matthew.howell@sealevel.com>
>
> 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@sealevel.com/T/
> Fixes: 14ee78d5932a ("Add support for Sealevel 7xxxC serial cards")
> Signed-off-by: Matthew Howell <matthew.howell@sealevel.com>
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.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-09-14 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 12:28 [PATCH V5 1/2] serial: exar: Revert "serial: exar: Add support for Sealevel 7xxxC serial cards" Matthew Howell
2023-09-14 19:04 ` Andy Shevchenko [this message]
2023-09-14 19:51 ` Matthew Howell
2023-09-18 7:30 ` Greg KH
2023-09-18 14:51 ` Matthew Howell
2023-09-18 8:26 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZQNZJwJoad0EkIYL@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=darren.beeson@sealevel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.olson@sealevel.com \
--cc=jeff.baldwin@sealevel.com \
--cc=linux-serial@vger.kernel.org \
--cc=matthew.howell@sealevel.com \
--cc=ryan.wenglarz@sealevel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.