From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 2/2] spi: Add Cadence QSPI controller Kconfig entry
Date: Mon, 30 Mar 2015 15:50:16 +0200 [thread overview]
Message-ID: <201503301550.16635.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RS10d+GwK7KQg2UbP=dsSTZ_W=R=gZJ4FwvsURhh5r8zg@mail.gmail.com>
On Monday, March 30, 2015 at 02:16:05 PM, Jagan Teki wrote:
> On 6 March 2015 at 12:22, Stefan Roese <sr@denx.de> wrote:
> > On 05.03.2015 21:51, Marek Vasut wrote:
> >> Add Cadence QSPI controller Kconfig entry.
> >>
> >> Signed-off-by: Marek Vasut <marex@denx.de>
> >> Cc: Chin Liang See <clsee@opensource.altera.com>
> >> Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> >> Cc: Jagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
> >> Cc: Pavel Machek <pavel@denx.de>
> >> Cc: Simon Glass <sjg@chromium.org>
> >> Cc: Stefan Roese <sr@denx.de>
> >> Cc: Tom Rini <trini@konsulko.com>
> >> Cc: Vince Bridgers <vbridger@opensource.altera.com>
> >
> > Acked-by: Stefan Roese <sr@denx.de>
>
> Shall I pick these two on my tree (-spi)?
Either that or I can send PR via SoCFPGA tree. Either way is OK.
The patches are now sitting in u-boot-socfpga/topic/spi-kconfig
so I can just send that out ...
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-03-30 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 20:51 [U-Boot] [PATCH V2 1/2] spi: Add Designware SPI controller Kconfig entry Marek Vasut
2015-03-05 20:51 ` [U-Boot] [PATCH V2 2/2] spi: Add Cadence QSPI " Marek Vasut
2015-03-05 21:46 ` Simon Glass
2015-03-05 21:51 ` Marek Vasut
2015-03-05 21:53 ` Simon Glass
2015-03-30 13:53 ` Marek Vasut
2015-03-30 14:07 ` Jagan Teki
2015-03-30 14:14 ` Marek Vasut
2015-03-06 6:52 ` Stefan Roese
2015-03-30 12:16 ` Jagan Teki
2015-03-30 13:50 ` Marek Vasut [this message]
2015-03-05 21:46 ` [U-Boot] [PATCH V2 1/2] spi: Add Designware SPI " Simon Glass
2015-03-06 6:51 ` Stefan Roese
2015-03-06 10:47 ` Pavel Machek
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=201503301550.16635.marex@denx.de \
--to=marex@denx.de \
--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