public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: u-boot@lists.denx.de
Subject: [PATCH 4/5] ds414: Auto-populate env if appropriate
Date: Thu, 4 Mar 2021 14:20:05 +0100	[thread overview]
Message-ID: <20210304132005.GM22016@orbyte.nwl.cc> (raw)
In-Reply-To: <326825c5-93f0-2a3d-43c7-301bfaa4e17e@denx.de>

On Thu, Mar 04, 2021 at 02:06:01PM +0100, Stefan Roese wrote:
> On 03.03.21 01:55, Phil Sutter wrote:
> > Define a misc_init_r() which calls "syno populate_env" if the
> > environment seems incomplete (or default), indicated by missing
> > "ethaddr" variable. With this in place, no random MAC address fallback
> > is needed anymore.
> > 
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > ---
> >   board/Synology/ds414/cmd_syno.c |  2 +-
> >   board/Synology/ds414/ds414.c    | 13 +++++++++++++
> >   configs/ds414_defconfig         |  4 +---
> >   3 files changed, 15 insertions(+), 4 deletions(-)
> > 
> > diff --git a/board/Synology/ds414/cmd_syno.c b/board/Synology/ds414/cmd_syno.c
> > index a120c3123ffb3..07bb395da3acc 100644
> > --- a/board/Synology/ds414/cmd_syno.c
> > +++ b/board/Synology/ds414/cmd_syno.c
> > @@ -22,7 +22,7 @@
> >   #define SYNO_CHKSUM_TAG		"CHK="
> >   
> >   
> > -static int do_syno_populate(int argc, char *const argv[])
> > +int do_syno_populate(int argc, char *const argv[])
> >   {
> >   	unsigned int bus = CONFIG_SF_DEFAULT_BUS;
> >   	unsigned int cs = CONFIG_SF_DEFAULT_CS;
> > diff --git a/board/Synology/ds414/ds414.c b/board/Synology/ds414/ds414.c
> > index 9c4ce670ddfbd..c2469d6665255 100644
> > --- a/board/Synology/ds414/ds414.c
> > +++ b/board/Synology/ds414/ds414.c
> > @@ -179,6 +179,19 @@ int board_init(void)
> >   	return 0;
> >   }
> >   
> > +#ifndef CONFIG_SPL_BUILD
> > +int do_syno_populate(int argc, char *const argv[]);
> 
> I suspect that this prototype in a C file will trigger at least a
> checkpatch warning?

What is checkpatch? ;)
Mea culpa, sometimes past me's dirty hacks slip my review. I'll go find
a checkpatch-compliant way.

Thanks, Phil

  reply	other threads:[~2021-03-04 13:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  0:55 [PATCH 0/5] Synology DS414 integration mini-review Phil Sutter
2021-03-03  0:55 ` [PATCH 1/5] ds414: Add a Kconfig defining some strings Phil Sutter
2021-03-04 13:00   ` Stefan Roese
2021-03-03  0:55 ` [PATCH 2/5] configs: ds414: Enable XHCI_PCI by default Phil Sutter
2021-03-04 13:00   ` Stefan Roese
2021-03-04 13:11     ` Phil Sutter
2021-03-05 20:03   ` [PATCH v2 " Phil Sutter
2021-03-06  8:15     ` Stefan Roese
2021-03-07 20:58       ` Phil Sutter
2021-03-08  6:34         ` Stefan Roese
2021-03-07 21:21     ` [PATCH v3 " Phil Sutter
2021-03-08  6:34       ` Stefan Roese
2021-03-03  0:55 ` [PATCH 3/5] board/Synology: Unify legacy kernel support Phil Sutter
2021-03-04 13:03   ` Stefan Roese
2021-03-04 13:11     ` Phil Sutter
2021-03-05 20:04   ` [PATCH v2 " Phil Sutter
2021-03-07 21:22     ` [PATCH v3 " Phil Sutter
2021-03-08  6:36       ` Stefan Roese
2021-03-03  0:55 ` [PATCH 4/5] ds414: Auto-populate env if appropriate Phil Sutter
2021-03-04 13:06   ` Stefan Roese
2021-03-04 13:20     ` Phil Sutter [this message]
2021-03-04 13:22       ` Stefan Roese
2021-03-05 20:05   ` [PATCH v2 " Phil Sutter
2021-03-03  0:55 ` [PATCH 5/5] ds414: Add sample u-boot update command Phil Sutter
2021-03-04 13:09   ` Stefan Roese
2021-03-04 13:28     ` Phil Sutter
2021-03-04 13:34       ` Stefan Roese
2021-03-04 13:56         ` Phil Sutter
2021-03-05 20:05   ` [PATCH v2 " Phil Sutter
2021-04-08  8:52 ` [PATCH 0/5] Synology DS414 integration mini-review Stefan Roese

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=20210304132005.GM22016@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --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