From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Joshua Scott <Joshua.Scott@alliedtelesis.co.nz>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node" has been added to the 4.14-stable tree
Date: Wed, 10 Jul 2019 09:48:50 +0200 [thread overview]
Message-ID: <20190710074850.GA5186@kroah.com> (raw)
In-Reply-To: <1562623610543.71373@alliedtelesis.co.nz>
On Mon, Jul 08, 2019 at 10:06:50PM +0000, Joshua Scott wrote:
> Hi Greg,
>
> 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236") is the patch
> which introduces the armada-xp-98dx3236, and contains the device-tree entry for the driver that does
> not behave correctly with this SoC.
>
> However, the driver quirk that implements the fix does not exist until the two patches I mentioned :
> b7639b0b15dd serial: 8250_dw: Limit dw8250_tx_wait_empty quirk to armada-38x devices
> 914eaf935ec7 serial: 8250_dw: Allow TX FIFO to drain before writing to UART_LCR
>
> Before then, there is no "marvell,armada-38x-uart".
>
> The current patch being delivered only changes the .dts to make use of the quirk. This won't work
> if it's being delivered to a branch that does not have the above two patches. I had a look at linux-4.14.y
> on kernel.org, and did not see the two patches there.
Ok, thanks, I've deleted it from the queueu now.
greg k-h
prev parent reply other threads:[~2019-07-10 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <156231715780108@kroah.com>
2019-07-08 5:55 ` Patch "ARM: dts: armada-xp-98dx3236: Switch to armada-38x-uart serial node" has been added to the 4.14-stable tree Joshua Scott
2019-07-08 6:23 ` gregkh
2019-07-08 22:06 ` Joshua Scott
2019-07-10 7:48 ` gregkh [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=20190710074850.GA5186@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Joshua.Scott@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).