From: Greg KH <gregkh@linuxfoundation.org>
To: Cameron Williams <cang1@live.co.uk>
Cc: stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "tty: 8250: Add support for Intashield IX cards" has been added to the 5.10-stable tree
Date: Mon, 6 Nov 2023 14:02:17 +0100 [thread overview]
Message-ID: <2023110652-probe-unvented-312e@gregkh> (raw)
In-Reply-To: <DU0PR02MB7899088E4076359C07F436F0C4AAA@DU0PR02MB7899.eurprd02.prod.outlook.com>
On Mon, Nov 06, 2023 at 12:56:23PM +0000, Cameron Williams wrote:
> On Mon, Nov 06, 2023 at 01:18:36PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > tty: 8250: Add support for Intashield IX cards
> >
> > to the 5.10-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > tty-8250-add-support-for-intashield-ix-cards.patch
> > and it can be found in the queue-5.10 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> I don't think this patch should be in 5.10-stable. It's using the
> pbn_oxsemi_x_15625000 configuration which isn't available in the version
> of the driver (it's actually pbn_oxsemi_x_3906250 in this version).
> The rest of the patches to be merged look OK for this branch (as they are
> all using the generic configuration rather than Oxsemi).
Yes, it broke the build and I dropped it right after it, my scripts
committed it before I could build-test it.
thanks for the quick response!
greg k-h
prev parent reply other threads:[~2023-11-06 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2023110636-sandfish-thickness-bdc1@gregkh>
2023-11-06 12:56 ` Patch "tty: 8250: Add support for Intashield IX cards" has been added to the 5.10-stable tree Cameron Williams
2023-11-06 13:02 ` Greg KH [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=2023110652-probe-unvented-312e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cang1@live.co.uk \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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