All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH 4/9] ks2_evm: Switch to DM_SPL, SPL_OF_CONTROL
Date: Thu, 11 Jun 2020 14:16:47 +0530	[thread overview]
Message-ID: <CAMty3ZBt4i-LXqpgKEhm2N1NQ3gmLdzqDhJrMg-8xwtP7hwk1Q@mail.gmail.com> (raw)
In-Reply-To: <20200526080430.118262-5-jagan@amarulasolutions.com>

On Tue, May 26, 2020 at 1:34 PM Jagan Teki <jagan@amarulasolutions.com> wrote:
>
> This would make SPL build to DM_SPL, SPL_OF_CONTROL.
>
> Build fine with but not tested.
>
> Cc: Vitaly Andrianov <vitalya@ti.com>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---

Applied to u-boot-spi/master

  reply	other threads:[~2020-06-11  8:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  8:04 [PATCH 0/9] spi: dm-convert and cleanups Jagan Teki
2020-05-26  8:04 ` [PATCH 1/9] spi Drop spi_init() Jagan Teki
2020-05-27 18:21   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 2/9] spi: Kconfig: Drop redundant CF_SPI definition Jagan Teki
2020-05-27 18:22   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 3/9] spi: Kconfig: Move MSCC_BB_SPI, FSL_QSPI into DM_SPI Jagan Teki
2020-05-27 18:22   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 4/9] ks2_evm: Switch to DM_SPL, SPL_OF_CONTROL Jagan Teki
2020-06-11  8:46   ` Jagan Teki [this message]
2020-05-26  8:04 ` [PATCH 5/9] spi: davinci: Drop non-dm code Jagan Teki
2020-05-28  0:30   ` Adam Ford
2020-06-11  8:47   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 6/9] spi: mxs: Drop nondm code Jagan Teki
2020-06-11  8:38   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 7/9] spi: mxs: Code cleanup Jagan Teki
2020-06-11  8:39   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 8/9] spi: Zap SOFT_SPI (non-dm) Jagan Teki
2020-05-31 14:07   ` Simon Glass
2020-06-11  8:40   ` Jagan Teki
2020-05-26  8:04 ` [PATCH 9/9] doc: driver-model: Update SPI migration status Jagan Teki
2020-05-31 14:07   ` Simon Glass

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=CAMty3ZBt4i-LXqpgKEhm2N1NQ3gmLdzqDhJrMg-8xwtP7hwk1Q@mail.gmail.com \
    --to=jagan@amarulasolutions.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.