From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL RESEND] pxa for v3.20
Date: Tue, 27 Jan 2015 05:42:44 +0100 [thread overview]
Message-ID: <87lhkoq1ff.fsf@free.fr> (raw)
In-Reply-To: 20150127021733.GB22154@quad.lixom.net
Olof Johansson <olof@lixom.net> writes:
> I had already merged, but it looks like you broke viper and zeus. Both of them
> still refer to PXA_ISA_IRQ().
>
> Can you send an incremental patch for that? Or if you prefer that we drop this
> branch for now while you sort it out that's OK too -- your preference.
I'll send an incremental patch.
I'm really frustrated my bot didn't catch that, I suppose yours caught it by
building viper_defconfig ...
> Yeah we normally scale this by educating downstream maintainers. checkpatch is
> useful in many cases but making it do everything is hard.
Yeah, but humans do forget, even educated ... I'll be carefull as much as I can,
but I knew the rule and yet this slipped through.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-01-27 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 19:01 [GIT PULL RESEND] pxa for v3.20 Robert Jarzmik
2015-01-23 21:54 ` Olof Johansson
2015-01-24 14:18 ` Robert Jarzmik
2015-01-27 2:17 ` Olof Johansson
2015-01-27 4:42 ` Robert Jarzmik [this message]
2015-01-27 4:45 ` Olof Johansson
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=87lhkoq1ff.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--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).