All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] dm: core: add functions to get memory-mapped I/O addresses
Date: Mon, 30 Apr 2018 17:12:42 -0600	[thread overview]
Message-ID: <CAPnjgZ1Q7oWe3smFU0mOqD1r_N6A6cHmCNfd39EfH9L8NB8-gw@mail.gmail.com> (raw)
In-Reply-To: <20180429195654.709-1-daniel.schwierzeck@gmail.com>

On 29 April 2018 at 13:56, Daniel Schwierzeck
<daniel.schwierzeck@gmail.com> wrote:
> From: Álvaro Fernández Rojas <noltari@gmail.com>
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> Reviewed-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
> Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
>
> ---
> This replaces/updates patch 01/17 from patch series
> https://patchwork.ozlabs.org/cover/889542/. The update fixes
> some issues with Sandbox and adds unit-tests. The remaining patches
> from the patch series can be applied as-is when this patch has been
> committed.
>
> Changes in v3:
> - replace ioremap() with map_physmem()
> - add unit tests
> - fix checkpatch.pl warnings
>
> Changes in v2:
> - new patch
>
>  drivers/core/fdtaddr.c | 15 +++++++++++++++
>  drivers/core/read.c    | 15 +++++++++++++++
>  include/dm/fdtaddr.h   | 22 ++++++++++++++++++++++
>  include/dm/read.h      | 32 ++++++++++++++++++++++++++++++++
>  test/dm/test-fdt.c     | 42 ++++++++++++++++++++++++++++++++++++++++++
>  5 files changed, 126 insertions(+)

Reviewed-by: Simon Glass <sjg@chromium.org>

  reply	other threads:[~2018-04-30 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 19:56 [U-Boot] [PATCH v3] dm: core: add functions to get memory-mapped I/O addresses Daniel Schwierzeck
2018-04-30 23:12 ` Simon Glass [this message]
2018-05-06 19:34 ` Daniel Schwierzeck

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=CAPnjgZ1Q7oWe3smFU0mOqD1r_N6A6cHmCNfd39EfH9L8NB8-gw@mail.gmail.com \
    --to=sjg@chromium.org \
    --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.