All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Gerlando Falauto <gerlando.falauto@keymile.com>,
	linux-kernel@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	Andrew Lunn <andrew@lunn.ch>,
	Russell King <linux@arm.linux.org.uk>,
	Ben Dooks <ben-linux@fluff.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@linaro.org>,
	Simon Guinot <sguinot@lacie.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3b 0/9] refactoring for mask_cache
Date: Tue, 26 Mar 2013 13:47:25 -0700	[thread overview]
Message-ID: <20130326204725.GA4521@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1303262136350.22263@ionos>

On Tue, Mar 26, 2013 at 09:37:53PM +0100, Thomas Gleixner wrote:
> On Thu, 21 Mar 2013, Greg KH wrote:
> 
> > On Thu, Mar 21, 2013 at 06:12:02PM +0100, Gerlando Falauto wrote:
> > > This patchset addresses a regression found with the Orion GPIO controller
> > > when both Edge- and Level- based interrupts are requested within the same
> > > GPIO chip. The regression was introduced by e59347a
> > > "arm: orion: Use generic irq chip"
> > > 
> > > thereby affecting all kernel releases since 3.0.x.
> > 
> > <formletter>
> > 
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> > for how to do this properly.
> > 
> > </formletter>
> 
> Aside of that it would be less intrusive for the stable series to
> revert the offending commit(s), if that is possible.

If it is reverted in Linus's tree, yes, I can do that.  But if so,
please just tag that revert with the Cc: stable marking and then I can
pick it up properly.

Otherwise, no, I can't revert something that isn't already fixed in
upstream first.

thanks,

greg k-h

  reply	other threads:[~2013-03-26 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1363885931-20571-1-git-send-email-gerlando.falauto@keymile.com>
2013-03-21 21:57 ` [PATCH v3b 0/9] refactoring for mask_cache Greg KH
2013-03-26 20:37   ` Thomas Gleixner
2013-03-26 20:47     ` Greg KH [this message]
2013-03-26 20:54       ` Thomas Gleixner
2013-04-10 20:38         ` Greg KH
     [not found] ` <1363885931-20571-4-git-send-email-gerlando.falauto@keymile.com>
2013-03-27 12:57   ` [PATCH v3 3/9] gpio: mvebu: convert to usage of *pmask_cache within irq_chip_type Linus Walleij
     [not found] ` <1363885931-20571-9-git-send-email-gerlando.falauto@keymile.com>
2013-03-27 12:58   ` [PATCH v3b 8/9] orion-gpio: enable IRQ_GC_SEPARATE_MASK_REGISTERS Linus Walleij
     [not found] ` <1363885931-20571-10-git-send-email-gerlando.falauto@keymile.com>
2013-03-27 12:58   ` [PATCH v3b 9/9] gpio: mvebu: " Linus Walleij
2013-04-18 14:01 ` [PATCH v3b 0/9] refactoring for mask_cache Gerlando Falauto

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=20130326204725.GA4521@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=ben-linux@fluff.org \
    --cc=gerlando.falauto@keymile.com \
    --cc=grant.likely@secretlab.ca \
    --cc=jason@lakedaemon.net \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ralf@linux-mips.org \
    --cc=sguinot@lacie.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.