From: Jagan Teki <jteki@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 77/77] x86: Drop using spi_flash_dm_ops
Date: Wed, 17 Feb 2016 14:39:29 +0530 [thread overview]
Message-ID: <56C438C9.8040206@openedev.com> (raw)
In-Reply-To: <CAEUhbmU31qTObNWF=Dfeb68DR2xadBp0Afs1iYbEtzO39Tg5VA@mail.gmail.com>
Hi Bin,
On Wednesday 17 February 2016 02:37 PM, Bin Meng wrote:
> Hi Jagan,
>
> On Wed, Feb 17, 2016 at 4:27 PM, Jagan Teki <jteki@openedev.com> wrote:
>> spi_flash_erase_dm
>> spi_flash_write_dm
>>
>> These spi_flash_dm_ops never no longer available on new
>> spi-nor changes, so use spi_flash_erase/write ops with
>> mtd uclass changes.
>>
>> Cc: Simon Glass <sjg@chromium.org>
>> Cc: Bin Meng <bmeng.cn@gmail.com>
>> Signed-off-by: Jagan Teki <jteki@openedev.com>
>> ---
>> Changes for v7:
>> - newly added patch
>>
>> This patch is on top of spi-nor core changes, will send this
>> again with the series.
>
> Yes, you need squash this patch somewhere in the middle of your whole
> series, otherwise buildman will complain.
Sure I will do that and send the patch.
thanks!
--
Jagan
prev parent reply other threads:[~2016-02-17 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:27 [U-Boot] [PATCH v7 77/77] x86: Drop using spi_flash_dm_ops Jagan Teki
2016-02-17 9:07 ` Bin Meng
2016-02-17 9:09 ` Jagan Teki [this message]
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=56C438C9.8040206@openedev.com \
--to=jteki@openedev.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