All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] dm: core: Add dev_read_bytes()
Date: Tue, 16 Apr 2019 10:06:57 +0200	[thread overview]
Message-ID: <20190416080657.GB10907@ulmo> (raw)
In-Reply-To: <CANr=Z=aaaeYev5E_YCdfsg36mtFq978tZ5k4g4s=DSnB2kY_gw@mail.gmail.com>

On Mon, Apr 15, 2019 at 09:21:45PM +0000, Joe Hershberger wrote:
> On Mon, Apr 15, 2019 at 4:11 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > From: Thierry Reding <treding@nvidia.com>
> >
> > This function can be used to read a binary property into a buffer. One
> > example where this is needed is to read a MAC address from device tree.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> 
> Is there a reason dev_read_u8_array_ptr is insuffient?

No, it's perfectly suitable, I just hadn't seen it.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190416/c8e64ee6/attachment.sig>

      reply	other threads:[~2019-04-16  8:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15  9:10 [U-Boot] [PATCH 1/3] dm: core: Add dev_read_bytes() Thierry Reding
2019-04-15  9:10 ` [U-Boot] [PATCH 2/3] net: eth-uclass: Write MAC address to hardware after probe Thierry Reding
2019-04-15 21:24   ` Joe Hershberger
2019-04-16  8:21     ` Thierry Reding
2019-04-15  9:10 ` [U-Boot] [PATCH 3/3] net: eth-uclass: Support device tree MAC addresses Thierry Reding
2019-04-15 21:26   ` Joe Hershberger
2019-04-15 21:21 ` [U-Boot] [PATCH 1/3] dm: core: Add dev_read_bytes() Joe Hershberger
2019-04-16  8:06   ` Thierry Reding [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=20190416080657.GB10907@ulmo \
    --to=thierry.reding@gmail.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.