From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Greg Ungerer <gerg@uclinux.org>,
stable@vger.kernel.org, gregory.clement@free-electrons.com,
jason@lakedaemon.net, andrew@lunn.ch,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mvebu: pass the coherency availability information at init time
Date: Thu, 11 Jun 2015 07:51:29 -0700 [thread overview]
Message-ID: <20150611145129.GA3777@kroah.com> (raw)
In-Reply-To: <20150611092549.2276beb8@free-electrons.com>
On Thu, Jun 11, 2015 at 09:25:49AM +0200, Thomas Petazzoni wrote:
> Greg, Greg,
>
> On Thu, 11 Jun 2015 14:04:18 +1000, Greg Ungerer wrote:
>
> > > Why? What's wrong with taking the exact specific upstream patches
> > > instead?
> >
> > The exact patch mentioned below ("5686a1e5aa4") will not apply.
> > Too much of the code around it has changed. This does the same
> > thing in the same away taking into account the changes around it.
>
> As the original author of 5686a1e5aa4 ("bus: mvebu: pass the coherency
> availability information at init time"), I can confirm that it will
> clearly not apply as is on 3.10. What Greg Ungerer is proposing here is
> a backport of 5686a1e5aa4 to 3.10.
What about 3.14-stable?
And if this is just a simple backport, that should have been stated
here.
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-11 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 3:19 [PATCH] ARM: mvebu: pass the coherency availability information at init time gerg
2015-06-11 3:45 ` Greg KH
2015-06-11 4:04 ` Greg Ungerer
2015-06-11 7:25 ` Thomas Petazzoni
2015-06-11 14:51 ` Greg KH [this message]
2015-06-11 15:14 ` Thomas Petazzoni
2015-06-12 1:19 ` Greg Ungerer
2015-06-30 0:31 ` Greg KH
2015-06-30 13:09 ` Greg Ungerer
2015-06-30 16:48 ` Greg KH
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=20150611145129.GA3777@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew@lunn.ch \
--cc=gerg@uclinux.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).