From: Thomas Gleixner <tglx@linutronix.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, hpa@zytor.com,
peterz@infradead.org, linuxppc-dev@lists.ozlabs.org,
shangw@linux.vnet.ibm.com, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:irq/core] powerpc: eeh: Fixup the brown paperbag fallout of the "cleanup"
Date: Wed, 5 Mar 2014 00:29:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1403050027560.18573@ionos.tec.linutronix.de> (raw)
In-Reply-To: <1393975112.10727.103.camel@pasglop>
On Wed, 5 Mar 2014, Benjamin Herrenschmidt wrote:
> On Tue, 2014-03-04 at 15:15 -0800, tip-bot for Thomas Gleixner wrote:
> > Commit-ID: 57310c3c99eb6fab2ecbd63aa3f7c323341ca77e
> > Gitweb: http://git.kernel.org/tip/57310c3c99eb6fab2ecbd63aa3f7c323341ca77e
> > Author: Thomas Gleixner <tglx@linutronix.de>
> > AuthorDate: Wed, 5 Mar 2014 00:06:11 +0100
> > Committer: Thomas Gleixner <tglx@linutronix.de>
> > CommitDate: Wed, 5 Mar 2014 00:13:33 +0100
> >
> > powerpc: eeh: Fixup the brown paperbag fallout of the "cleanup"
> >
> > Commit b8a9a11b9 (powerpc: eeh: Kill another abuse of irq_desc) is
> > missing some brackets .....
> >
> > It's not a good idea to write patches in grumpy mode and then forget
> > to at least compile test them or rely on the few eyeballs discussing
> > that patch to spot it.....
>
> Ouch :-)
>
> Next time you have a series like that, if you want I'll throw it at my
> build tester.
You simply could have been less lazy and picked up the whole ppc
related stuff instead of ignoring it....
Thanks,
tglx
prev parent reply other threads:[~2014-03-04 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-57310c3c99eb6fab2ecbd63aa3f7c323341ca77e@git.kernel.org>
2014-03-04 23:18 ` Benjamin Herrenschmidt
2014-03-04 23:29 ` Thomas Gleixner [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=alpine.DEB.2.02.1403050027560.18573@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=benh@kernel.crashing.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=shangw@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®