public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] sf: add missing Atmel at25df321 spi flash support
Date: Sat, 12 Oct 2013 09:20:57 +0800	[thread overview]
Message-ID: <5258A3F9.10406@atmel.com> (raw)
In-Reply-To: <52575333.30009@atmel.com>

Hi Jagan,
   Cc Tom.

On 10/11/2013 09:24, Bo Shen wrote:
> Hi Jagan,
>
> On 10/10/2013 22:14, Jagan Teki wrote:
>> Thanks for this.
>>
>> On Thu, Oct 10, 2013 at 10:37 AM, Bo Shen <voice.shen@atmel.com> wrote:
>>> As the spi flash transfer to multiple parts, it is forgot to add
>>> Atmel AT25DF321 spi flash support, which broken several Atmel EK
>>> boards which this chip. So, add it
>>>
>>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>>> ---
>>>   drivers/mtd/spi/sf_probe.c |    1 +
>>>   1 file changed, 1 insertion(+)

If this patch not applied before release at Oct 14, it will make a 
regression for several Atmel EK boards boot from spi flash.

Would you please pick it before release?

Best Regards,
Bo Shen

  reply	other threads:[~2013-10-12  1:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  5:07 [U-Boot] [PATCH 1/3] sf: add missing Atmel at25df321 spi flash support Bo Shen
2013-10-10  5:07 ` [U-Boot] [PATCH 2/3] sf: change indentation in <sf_probe.c> Bo Shen
2013-10-10 16:43   ` Jagan Teki
2013-10-10  5:07 ` [U-Boot] [PATCH 3/3] sf: using the same license header format Bo Shen
2013-10-10 16:42   ` Jagan Teki
2013-10-10 16:46     ` Tom Rini
2013-10-10 17:13       ` Jagan Teki
2013-10-10 21:39     ` Wolfgang Denk
     [not found] ` <CAD6G_RSJbaQz4pqHwxt6Y0Z7iBm_W4DQ_MQ0zJHZGKBnDd4z=A@mail.gmail.com>
2013-10-11  1:24   ` [U-Boot] [PATCH 1/3] sf: add missing Atmel at25df321 spi flash support Bo Shen
2013-10-12  1:20     ` Bo Shen [this message]
2013-10-14  8:14       ` Jagan Teki
2013-10-14  8:32         ` Bo Shen

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=5258A3F9.10406@atmel.com \
    --to=voice.shen@atmel.com \
    --cc=u-boot@lists.denx.de \
    /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