From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] i2c: at91: add support to FIFOs and alternative command
Date: Wed, 3 Jun 2015 00:36:28 +0900 [thread overview]
Message-ID: <20150602153622.GB2661@katana> (raw)
In-Reply-To: <20150602152647.GA2806@odux.rfo.atmel.com>
> If you send a new version, could you add stable in Cc to patch 3/6:
No need to send a new version just because of an additional ack. I can
apply that. However...
> Cc: stable at vger.kernel.org #3.10 and later
> If not, Wolfram could you do it please?
The problem with 3/6 is that it seems to depend on 1/6 which is a
cleanup patch. If cleaning up is not essential for the bugfix, the
latter should be done first. To avoid exactly this problem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150603/7f8670ee/attachment.sig>
next prev parent reply other threads:[~2015-06-02 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:18 [PATCH v3 0/6] i2c: at91: add support to FIFOs and alternative command Cyrille Pitchen
2015-06-02 13:18 ` [PATCH v3 1/6] i2c: at91: use BIT() macro to define register bits Cyrille Pitchen
2015-06-02 13:18 ` [PATCH v3 2/6] i2c: at91: update documentation for DT bindings Cyrille Pitchen
2015-06-02 13:18 ` [PATCH v3 3/6] i2c: at91: fix a race condition when using the DMA controller Cyrille Pitchen
2015-06-02 13:18 ` [PATCH v3 4/6] i2c: at91: add support for new alternative command mode Cyrille Pitchen
2015-06-02 13:18 ` [PATCH v3 5/6] i2c: at91: print hardware version Cyrille Pitchen
2015-06-02 14:37 ` Sergei Shtylyov
2015-06-02 13:18 ` [PATCH v3 6/6] i2c: at91: add support to FIFOs Cyrille Pitchen
2015-06-02 15:26 ` [PATCH v3 0/6] i2c: at91: add support to FIFOs and alternative command Ludovic Desroches
2015-06-02 15:36 ` Wolfram Sang [this message]
2015-06-02 15:52 ` Ludovic Desroches
2015-06-02 15:58 ` Wolfram Sang
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=20150602153622.GB2661@katana \
--to=wsa@the-dreams.de \
--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