From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>, poky@yoctoproject.org
Subject: Re: [PATCH v2] u-boot: enable dhcp for MPC8315 board
Date: Wed, 07 Jun 2017 13:32:28 +0100 [thread overview]
Message-ID: <1496838748.6630.214.camel@linuxfoundation.org> (raw)
In-Reply-To: <1496838489-25242-1-git-send-email-ed.bartosh@linux.intel.com>
On Wed, 2017-06-07 at 15:28 +0300, Ed Bartosh wrote:
> Getting ip address from DHCP server is much more convenient
> than setting static ip. It allows to configure u-boot in
> more generic way and to avoid hardcoding static ip in
> u-boot configuration.
>
> Enabled dhcp client functionality for Yocto reference
> hardware MPC8315E-RDB.
>
> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> ---
> meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-DHCP.patch | 12
> ++++++++++++
> meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc | 4
> +++-
> 2 files changed, 15 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-bsp/u-boot/files/MPC8315ERDB-enable-
> DHCP.patch
These files are in OE-Core, not meta-yocto but you sent them to the
poky list?
Cheers,
Richard
next prev parent reply other threads:[~2017-06-07 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 12:05 [PATCH] u-boot: enable dhcp for MPC8315 board Ed Bartosh
2017-06-07 12:12 ` Burton, Ross
2017-06-07 12:28 ` [PATCH v2] " Ed Bartosh
2017-06-07 12:32 ` Richard Purdie [this message]
2017-06-08 0:43 ` Tom Rini
2018-05-04 2:01 ` [poky] " Trevor Woerner
2018-05-04 2:03 ` Tom Rini
2017-06-07 12:33 ` Ed Bartosh
2017-06-07 12:29 ` Ed Bartosh
2017-06-07 12:31 ` ✗ patchtest: failure for u-boot: enable dhcp for MPC8315 board (rev2) Patchwork
2017-06-07 13:21 ` [PATCH v3] u-boot: enable dhcp for MPC8315 board Ed Bartosh
2017-06-07 13:24 ` [PATCH v4] " Ed Bartosh
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=1496838748.6630.214.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ed.bartosh@linux.intel.com \
--cc=poky@yoctoproject.org \
/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.