public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Eugen.Hristev at microchip.com <Eugen.Hristev@microchip.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 00/10] spi: Add Atmel QuadSPI driver
Date: Mon, 8 Jul 2019 11:40:23 +0000	[thread overview]
Message-ID: <e8a1f014-d9bb-07e0-d55a-2f94a67abfe1@microchip.com> (raw)
In-Reply-To: <CAMty3ZC=DaMoS6bKLx=QuH78-tX2xwDezpF=PmF0_jXzocqPJw@mail.gmail.com>



On 29.06.2019 17:55, Jagan Teki wrote:

> Hi Eugen,
> 
> On Tue, Jun 25, 2019 at 9:10 PM Jagan Teki <jagan@amarulasolutions.com> wrote:
>>
>> On Tue, Jun 25, 2019 at 5:05 PM <Eugen.Hristev@microchip.com> wrote:
>>>
>>> Hello Jagan,
>>>
>>> I can only take these patches through u-boot-atmel tree if you
>>> Ack/Review them.
>>> Otherwise you can consider taking them through u-boot-spi ?
>>
>> I would need a look on the new version, once ie fine I can pick via
>> spi tree. if possible please assign me on the patchwork, thanks.
> 
> I have marked my comments,  you can make the decision accordingly. By
> the way I assigned them to you as well, thanks.
> 
> Jagan.
> 

Applied patches 2-10 to u-boot-atmel/next
Dropped patch 1 (dt-bindings) as advised by Jagan.
Will be queued for 2019.10 merge window.

Thanks Tudor and Jagan !

Eugen

      reply	other threads:[~2019-07-08 11:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  8:51 [U-Boot] [PATCH v5 00/10] spi: Add Atmel QuadSPI driver Tudor.Ambarus at microchip.com
2019-06-18  8:51 ` [U-Boot] [PATCH v5 01/10] dt-bindings: spi: add bindings for Atmel QSPI driver Tudor.Ambarus at microchip.com
2019-06-29 14:53   ` Jagan Teki
2019-06-18  8:51 ` [U-Boot] [PATCH v5 02/10] spi: Add Atmel QuadSPI driver Tudor.Ambarus at microchip.com
2019-06-29 14:38   ` Jagan Teki
2019-06-18  8:51 ` [U-Boot] [PATCH v5 03/10] configs: sama5d2_xplained: enable qspi controller and flashes Tudor.Ambarus at microchip.com
2019-06-29 14:39   ` Jagan Teki
2019-06-18  8:51 ` [U-Boot] [PATCH v5 04/10] configs: sama5d27_som1_ek: " Tudor.Ambarus at microchip.com
2019-06-29 14:40   ` Jagan Teki
2019-06-18  8:51 ` [U-Boot] [PATCH v5 05/10] ARM: dts: at91: sama5d2_xplained: fix QSPI0 node Tudor.Ambarus at microchip.com
2019-06-29 14:46   ` Jagan Teki
2019-06-18  8:52 ` [U-Boot] [PATCH v5 06/10] ARM: at91: sama5: add common environment for QSPI Tudor.Ambarus at microchip.com
2019-06-18  8:52 ` [U-Boot] [PATCH v5 07/10] configs: sama5d2_xplained: add qspiflash_defconfig Tudor.Ambarus at microchip.com
2019-06-29 14:48   ` Jagan Teki
2019-06-18  8:52 ` [U-Boot] [PATCH v5 08/10] configs: sama5d27_som1_ek: " Tudor.Ambarus at microchip.com
2019-06-29 14:49   ` Jagan Teki
2019-06-18  8:52 ` [U-Boot] [PATCH v5 09/10] configs: sama5d27_som1_ek: qspi: use common memory layout Tudor.Ambarus at microchip.com
2019-06-18  8:52 ` [U-Boot] [PATCH v5 10/10] configs: sama5d2_xplained: add support QSPI flash boot Tudor.Ambarus at microchip.com
2019-06-25 11:35 ` [U-Boot] [PATCH v5 00/10] spi: Add Atmel QuadSPI driver Eugen.Hristev at microchip.com
2019-06-25 15:40   ` Jagan Teki
2019-06-29 14:55     ` Jagan Teki
2019-07-08 11:40       ` Eugen.Hristev at microchip.com [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=e8a1f014-d9bb-07e0-d55a-2f94a67abfe1@microchip.com \
    --to=eugen.hristev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox