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: Mon, 18 Sep 2023 11:26:15 +0300 [thread overview]
Message-ID: <ZQgJp0AkHBvYH+es@smile.fi.intel.com> (raw)
In-Reply-To: <15c38a1b-65ed-54db-c973-0ae995e201d4@sealevel.com>
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@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.
>
> 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.
We have O365 at the company, but git send-email works transparently. Perhaps
you have to talk to the IT in yours.
For reading messages we are using email-oauth2-proxy python script (you may
find it on GitHub), it can also be configured for SMTP (in my case only IMAP is
in use).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-09-18 8:27 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
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 [this message]
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=ZQgJp0AkHBvYH+es@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox