[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYpEreHKdUyfcANA9kTRAjVbLbpJkBJCq1Q_pAeOKcdxw@mail.gmail.com>
Date: Fri, 17 May 2013 10:25:10 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Fabio Baltieri <fabio.baltieri@...aro.org>
Cc: Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...aro.org>, Arnd Bergmann <arnd@...db.de>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s
On Fri, May 17, 2013 at 9:51 AM, Fabio Baltieri
<fabio.baltieri@...aro.org> wrote:
> Hello Samuel,
(...)
> The last two:
>
> mfd: ab8500-sysctrl: Set sysctrl_dev during probe
> mfd: ab8500-sysctrl: Let sysctrl driver work without pdata
>
> are actually fixes for bugs introduced in this merge window that
> inhibited the ab8500-sysctl driver as a consequence. Would you
> reconsider pulling just those?
A good way to make sure that patches fixing regressions are applied
to the -rc series is to indicate in the commit message or even the
heading that it fixes a regression.
I usually try to begin such commits with the text:
this patch fixes a regression caused by change 018745435
"foo: fix bar"...
Then copying in some crash dump text never hurts :-)
It makes it very easy for us as subsystem maintainers to pick
regression fixes.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists