From: fabio.baltieri@linaro.org (Fabio Baltieri)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] MFD: Fixes due for the v3.10 -rc:s
Date: Fri, 17 May 2013 10:33:54 +0200 [thread overview]
Message-ID: <20130517083354.GA32133@balto.lan> (raw)
In-Reply-To: <CACRpkdYpEreHKdUyfcANA9kTRAjVbLbpJkBJCq1Q_pAeOKcdxw@mail.gmail.com>
On Fri, May 17, 2013 at 10:25:10AM +0200, Linus Walleij wrote:
> On Fri, May 17, 2013 at 9:51 AM, Fabio Baltieri
> <fabio.baltieri@linaro.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.
Right, I actually pointed to the culprit commit (applied during the
merge window) in the message, but I'll try to be more direct next time.
I also agree on the crash dump, but unfortunately this one was failing
silently. :-)
Thanks for the tip!
Fabio
--
Fabio Baltieri
next prev parent reply other threads:[~2013-05-17 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:19 [GIT PULL] MFD: Fixes due for the v3.10 -rc:s Lee Jones
2013-05-15 9:04 ` [GIT PULL v2] " Lee Jones
2013-05-16 22:43 ` Samuel Ortiz
2013-05-17 7:51 ` Fabio Baltieri
2013-05-17 8:25 ` Linus Walleij
2013-05-17 8:33 ` Fabio Baltieri [this message]
2013-05-21 8:56 ` Samuel Ortiz
2013-05-21 9:12 ` Fabio Baltieri
2013-05-21 21:58 ` Samuel Ortiz
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=20130517083354.GA32133@balto.lan \
--to=fabio.baltieri@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).