public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Boris BREZILLON <boris.brezillon@free-electrons.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Olof Johansson <olof@lixom.net>,
	arm@kernel.org, romain.izard.pro@gmail.com,
	Wenyou Yang <wenyou.yang@atmel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: fixes for 4.6 #1
Date: Tue, 10 May 2016 11:30:31 +0200	[thread overview]
Message-ID: <5465950.OCrl9K6RLM@wuerfel> (raw)
In-Reply-To: <1462865249-28552-1-git-send-email-nicolas.ferre@atmel.com>

On Tuesday 10 May 2016 09:27:29 Nicolas Ferre wrote:
> Here is a late fix for AT91. Sorry to have figure it out so late in the
> development cycle but we had to confirm it was an error with the documentation
> of two products.
> So, as the compatibility string is in since 4.6-rc1 and that the previous one
> works okay, it's a good opportunity to switch back to the one that works without
> introducing a intermediary bug.
> The revert on driver code and the removal of the useless additional
> compatibility string will be queued for 4.7 through NAND/MTD.

Thanks, pulled into the fixes. I ended up taking the text above as the
commit log for the merge, as it was more descriptive than the shorter
version you had in the tag.

	Arnd

  reply	other threads:[~2016-05-10  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10  7:27 [GIT PULL] at91: fixes for 4.6 #1 Nicolas Ferre
2016-05-10  9:30 ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-22 16:46 Nicolas Ferre

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=5465950.OCrl9K6RLM@wuerfel \
    --to=arnd@arndb.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.com \
    --cc=romain.izard.pro@gmail.com \
    --cc=wenyou.yang@atmel.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