From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] Fix lubbock and mainstone interrupts
Date: Sun, 26 Apr 2015 11:31:13 +0200 [thread overview]
Message-ID: <87pp6rkzha.fsf@belgarion.home> (raw)
In-Reply-To: <7247485.mMzWTjWY84@wuerfel> (Arnd Bergmann's message of "Sun, 26 Apr 2015 00:20:58 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Saturday 25 April 2015 23:13:20 Robert Jarzmik wrote:
>> This serie was submitted to the lak list, then migrated to mfd drivers, to end
>> up again here. There was no change since last submission. Let's hope this is the
>> last spin and that these platform will be fixed at last.
>>
>
> Should these be marked 'Cc: stable at vger.kernel.org'?
I can do this. I thought that 3 patches of 100+ lines, and the fact that these
boards were broken since october 2011 would prevent this serie from reaching the
stable branch.
Well, I'll resubmit with this information, and after comments stage it to my
fixes branch. Let's see what stable tree people will do.
> Can you also add a 'Fixes' tag with the commit that introduced the problem?
Sure.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-04-26 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 21:13 [PATCH v5 0/3] Fix lubbock and mainstone interrupts Robert Jarzmik
2015-04-25 21:13 ` [PATCH v5 1/3] ARM: pxa: pxa_cplds: add lubbock and mainstone IO Robert Jarzmik
2015-04-26 19:10 ` Paul Bolle
2015-04-26 19:38 ` Robert Jarzmik
2015-04-25 21:13 ` [PATCH v5 2/3] ARM: pxa: mainstone: use new pxa_cplds driver Robert Jarzmik
2015-04-25 21:13 ` [PATCH v5 3/3] ARM: pxa: lubbock: " Robert Jarzmik
2015-04-25 22:20 ` [PATCH v5 0/3] Fix lubbock and mainstone interrupts Arnd Bergmann
2015-04-26 9:31 ` Robert Jarzmik [this message]
2015-04-27 9:16 ` Arnd Bergmann
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=87pp6rkzha.fsf@belgarion.home \
--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