All of lore.kernel.org
 help / color / mirror / Atom feed
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DaVinci fixes for v3.11
Date: Mon, 19 Aug 2013 09:32:45 -0700	[thread overview]
Message-ID: <87mwodk5ea.fsf@kernel.org> (raw)
In-Reply-To: <5211CC26.7050702@ti.com> (Sekhar Nori's message of "Mon, 19 Aug 2013 13:11:26 +0530")

Hi Sekhar,

Sekhar Nori <nsekhar@ti.com> writes:

>> The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:
>> 
>>   Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)
>> 
>> are available in the git repository at:
>> 
>>   git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-fixes-for-v3.11
>> 
>> for you to fetch changes up to de30e316d38b0837fe4c09b43f1b52c8e230c44e:
>> 
>>   ARM: davinci: nand: specify ecc strength (2013-08-16 15:12:20 +0530)
>> 
>> ----------------------------------------------------------------
>> This pull request includes a patch for
>> making NAND flash work on multiple DaVinci
>> boards. The NAND probe was failing because
>> ecc strength was not specified while using
>> hardware ecc algorithm.

Note that our current fixes branch is based on -rc4, and since it
doesn't look like this fix is in -next, I've rebased it onto our fixes
branch.

IOW, rebased to -rc4, and applied to fixes.

In general, we prefer fixes based on older -rcs (at least not newer than
the current fixes branch) unless there is a dependency on a newer -rc.

Thanks,

Kevin

  reply	other threads:[~2013-08-19 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5211C957.4090902@ti.com>
2013-08-19  7:41 ` [GIT PULL] DaVinci fixes for v3.11 Sekhar Nori
2013-08-19 16:32   ` Kevin Hilman [this message]
2013-08-20  4:12     ` Sekhar Nori

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=87mwodk5ea.fsf@kernel.org \
    --to=khilman@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.