From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] mtd: spi: export functions to sf_internal.h
Date: Thu, 17 Jan 2019 13:13:42 +0100 [thread overview]
Message-ID: <20190117121340.si7nd3gtzocre4sj@soft-dev3.microsemi.net> (raw)
In-Reply-To: <341ddd93-4a7e-d98d-772c-1f8b0624e1a4@gmail.com>
Hi Daniel,
The 01/16/2019 15:07, Daniel Schwierzeck wrote:
>
>
> Am 16.01.19 um 13:07 schrieb Horatiu Vultur:
> > Expose the following functions: clean_bar, write_bar, spi_flash_std_write,
> > spi_flash_std_erase and spi_flash_std_probe to sf_internal.h to be able to
> > reuse them.
> >
> > Cc: Jagan Teki <jagan@amarulasolutions.com>
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> > ---
> > drivers/mtd/spi/sf_internal.h | 8 ++++++++
> > drivers/mtd/spi/sf_probe.c | 8 ++++----
> > drivers/mtd/spi/spi_flash.c | 4 ++--
> > 3 files changed, 14 insertions(+), 6 deletions(-)
> >
>
> maybe you should wait with this series as there is on-going work to
> import spi-nor from Linux [1]
>
> [1] https://lists.denx.de/pipermail/u-boot/2018-December/350565.html
>
That is perfectly fine for me, I will submit another patch after the
spi-nor series is accepted. Thank you.
> --
> - Daniel
--
/Horatiu
next prev parent reply other threads:[~2019-01-17 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:07 [U-Boot] [PATCH 0/3] mtd: spi: Add MSCC SPI flash driver Horatiu Vultur
2019-01-16 12:07 ` [U-Boot] [PATCH 1/3] mtd: spi: export functions to sf_internal.h Horatiu Vultur
2019-01-16 14:07 ` Daniel Schwierzeck
2019-01-17 12:13 ` Horatiu Vultur [this message]
2019-01-16 12:07 ` [U-Boot] [PATCH 2/3] mtd: spi: add MSCC SPI flash driver Horatiu Vultur
2019-01-16 12:07 ` [U-Boot] [PATCH 3/3] mips: mscc: use MSCC SPI flash driver for Luton Horatiu Vultur
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=20190117121340.si7nd3gtzocre4sj@soft-dev3.microsemi.net \
--to=horatiu.vultur@microchip.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 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.