public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Ian Lartey <ian@opensource.wolfsonmicro.com>,
	Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Stable <stable@kernel.org>
Subject: Re: [PATCH] mfd/wm831x-irq: Convert to new irq_chip functions and fix build failure
Date: Fri, 10 Dec 2010 08:55:51 +0100	[thread overview]
Message-ID: <201012100855.51446.PeterHuewe@gmx.de> (raw)
In-Reply-To: <12ABA93B-6923-4AF7-BF34-E070BE72A8E2@opensource.wolfsonmicro.com>

Am Freitag 10 Dezember 2010, 02:09:00 schrieb Mark Brown:
> > Cc: Stable <stable@kernel.org>
> 
> Why are you CCing to stable? This API was only introduced in 2.6.37 which
> is still in -rc and attempting to backport to stable releases would cause
> those releases to fail to build.

The driver obviously fails since October 30 in linus tree [1], that's why I 
thought it might still have gone into .36
If not I'm sorry about the cc.

Seems like I got a little confused about that - sorry.
I'm doing this only in my leisure time and tracking the whole lkml and 
subprojects is quite a lot ;) 
I'm doing my usual checks with git, but sometimes things slip.

It seems the right thing for me to drop that patch at this time, since there 
is some actual development going on here. 
(I just don't like build failures in Linus' tree ;)

But I'd like to add that there are still many other drivers, especially in 
mtd, which still break - but mark already seems to have them on his list.


Peter

References:
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/3423418/
[2] http://kisskb.ellerman.id.au/kisskb/buildresult/3607680/






      parent reply	other threads:[~2010-12-10  7:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 23:34 [PATCH] mfd/wm831x-irq: Convert to new irq_chip functions and fix build failure Peter Huewe
     [not found] ` <12ABA93B-6923-4AF7-BF34-E070BE72A8E2@opensource.wolfsonmicro.com>
2010-12-10  1:39   ` Thomas Gleixner
2010-12-10  5:07     ` Paul Mundt
2010-12-10 12:14       ` Mark Brown
2010-12-10 15:43         ` Paul Mundt
2010-12-10 17:01           ` Paul Mundt
2010-12-10 17:32             ` Mark Brown
2010-12-10 17:24           ` Mark Brown
2010-12-10 17:48             ` Paul Mundt
2010-12-10 18:24               ` Mark Brown
2010-12-11  1:59                 ` Paul Mundt
2010-12-20  0:29                   ` Samuel Ortiz
2010-12-10  7:55   ` Peter Hüwe [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=201012100855.51446.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=ian@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox