From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: dwoods@mellanox.com, jh80.chung@samsung.com,
ulf.hansson@linaro.org, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] mmc: dw_mmc: Use device_property_read instead of" was seriously submitted to be applied to the 4.12-stable tree?
Date: Tue, 8 Aug 2017 07:51:55 -0700 [thread overview]
Message-ID: <20170808145155.GA17739@kroah.com> (raw)
In-Reply-To: <028d1845-16f5-1fa7-ab64-1df661962305@mellanox.com>
On Tue, Aug 08, 2017 at 10:29:24AM -0400, Chris Metcalf wrote:
> On 8/7/2017 5:01 PM, Greg KH wrote:
> > On Mon, Aug 07, 2017 at 12:51:38PM -0700, Greg KH wrote:
> > > Ok, I've applied this for 4.12 and 4.9 trees, let's see what
> > > breaks...
> > Ok, 4.9 breaks badly, can you provide working backports of the two
> > patches for that kernel tree please?
>
> Sure. There were some additional of_property_*() calls added since
> 4.9, so the patches failed to apply cleanly. I'll reply to the two "FAILED"
> emails with properly backported versions.
>
> Note that you will have to apply commit e44bb0cbdc88 ("device
> property: Make dev_fwnode() public") as well to allow the code to
> compile, since it uses dev_fwnode.
Yes, that patch is in the tree now.
thanks,
greg k-h
prev parent reply other threads:[~2017-08-08 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 23:32 WTF: patch "[PATCH] mmc: dw_mmc: Use device_property_read instead of" was seriously submitted to be applied to the 4.12-stable tree? gregkh
2017-07-25 1:22 ` Chris Metcalf
2017-07-25 14:48 ` Greg KH
2017-07-25 15:55 ` Chris Metcalf
2017-07-28 13:52 ` Chris Metcalf
2017-07-28 23:30 ` Greg KH
2017-07-29 2:02 ` Chris Metcalf
2017-08-07 19:51 ` Greg KH
2017-08-07 21:01 ` Greg KH
2017-08-08 14:29 ` Chris Metcalf
2017-08-08 14:51 ` 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=20170808145155.GA17739@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cmetcalf@mellanox.com \
--cc=dwoods@mellanox.com \
--cc=jh80.chung@samsung.com \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.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).