All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Greg Ungerer <gerg@uclinux.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	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: Mon, 29 Jun 2015 17:31:05 -0700	[thread overview]
Message-ID: <20150630003105.GF6430@kroah.com> (raw)
In-Reply-To: <557A33AF.9030101@uclinux.org>

On Fri, Jun 12, 2015 at 11:19:43AM +1000, Greg Ungerer wrote:
> On 12/06/15 00:51, Greg KH wrote:
> > 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?
> 
> As Thomas pointed out, yes. Due to file movements and other changes
> neither this patch (for 3.10.y) or the original commit 5686a1e5aa4
> apply cleanly to 3.14.y.
> 
> How do you want to handle that for 3.14.y?

I need a backport for 3.14.y as well.

And I need a signed-off-by: from the subsystem maintainers that this
backport is acceptable, as it's so different from what is in Linus's
tree, before I can take it.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: pass the coherency availability information at init time
Date: Mon, 29 Jun 2015 17:31:05 -0700	[thread overview]
Message-ID: <20150630003105.GF6430@kroah.com> (raw)
In-Reply-To: <557A33AF.9030101@uclinux.org>

On Fri, Jun 12, 2015 at 11:19:43AM +1000, Greg Ungerer wrote:
> On 12/06/15 00:51, Greg KH wrote:
> > 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?
> 
> As Thomas pointed out, yes. Due to file movements and other changes
> neither this patch (for 3.10.y) or the original commit 5686a1e5aa4
> apply cleanly to 3.14.y.
> 
> How do you want to handle that for 3.14.y?

I need a backport for 3.14.y as well.

And I need a signed-off-by: from the subsystem maintainers that this
backport is acceptable, as it's so different from what is in Linus's
tree, before I can take it.

thanks,

greg k-h

  reply	other threads:[~2015-06-30  0:31 UTC|newest]

Thread overview: 21+ 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:19 ` gerg at uclinux.org
2015-06-11  3:45 ` Greg KH
2015-06-11  3:45   ` Greg KH
2015-06-11  4:04   ` Greg Ungerer
2015-06-11  4:04     ` Greg Ungerer
2015-06-11  7:25     ` Thomas Petazzoni
2015-06-11  7:25       ` Thomas Petazzoni
2015-06-11 14:51       ` Greg KH
2015-06-11 14:51         ` Greg KH
2015-06-11 15:14         ` Thomas Petazzoni
2015-06-11 15:14           ` Thomas Petazzoni
2015-06-12  1:19         ` Greg Ungerer
2015-06-12  1:19           ` Greg Ungerer
2015-06-30  0:31           ` Greg KH [this message]
2015-06-30  0:31             ` Greg KH
2015-06-30 13:09             ` Greg Ungerer
2015-06-30 13:09               ` Greg Ungerer
2015-06-30 16:48               ` Greg KH
2015-06-30 16:48                 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2015-06-09  1:35 gerg at uclinux.org

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=20150630003105.GF6430@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.