stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 8 Jul 2019 08:23:32 +0200	[thread overview]
Message-ID: <20190708062332.GA28690@kroah.com> (raw)
In-Reply-To: <1562565301017.49476@alliedtelesis.co.nz>

On Mon, Jul 08, 2019 at 05:55:00AM +0000, Joshua Scott wrote:
> Hi,
> 
> I do not think this patch alone will work on 4.14.
> 
> An earlier pair of patches which implements the
> "marvell,armada-38x-uart" quirk is present on the other kernel
> versions, but I do see it as far back as 4.14.
> 
> The following two patches are the ones which add support for that compatible string:
> 
> 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

But, this patch says:
	Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for armada-xp-98dx3236")
and that commit showed up in 4.12.

If that is not the case, fine, I'll drop this, otherwise I just have to
go off of what is given to me :)

thanks,

greg k-h

  reply	other threads:[~2019-07-08  6:23 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 [this message]
2019-07-08 22:06     ` Joshua Scott
2019-07-10  7:48       ` gregkh

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=20190708062332.GA28690@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).