From: Udit Agarwal <udit.agarwal@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/1] Set environment location to ENVL_NOWHERE with CONFIG_ENV_IS_NOWHERE.
Date: Mon, 22 Apr 2019 13:15:38 +0000 [thread overview]
Message-ID: <VI1PR04MB3983CC4B5BB3D44C52ECFB749E220@VI1PR04MB3983.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR0402MB3854D5C17C058527171F764D97430@VI1PR0402MB3854.eurprd04.prod.outlook.com>
Hi,
arch/arm/cpu/armv8/fsl-layerscape/cpu.c uses ENVL_NOWHERE to initialize the env_loc enum variable.
Shall the ENVL_NOWHERE be replaced with ENV_NOWHERE in commit message.
Regards
Udit Agarwal
> -----Original Message-----
> From: Prabhakar Kushwaha
> Sent: Friday, March 22, 2019 4:32 PM
> To: Udit Agarwal <udit.agarwal@nxp.com>; u-boot at lists.denx.de
> Cc: Ruchika Gupta <ruchika.gupta@nxp.com>; Jaiprakash Singh
> <jaiprakash.singh@nxp.com>; Arun Pathak <arun.pathak@nxp.com>
> Subject: RE: [PATCH v2 1/1] Set environment location to ENVL_NOWHERE with
> CONFIG_ENV_IS_NOWHERE.
>
>
> > -----Original Message-----
> > From: Udit Agarwal
> > Sent: Thursday, March 7, 2019 2:55 PM
> > To: u-boot at lists.denx.de
> > Cc: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>; Ruchika Gupta
> > <ruchika.gupta@nxp.com>; Jaiprakash Singh <jaiprakash.singh@nxp.com>;
> > Arun Pathak <arun.pathak@nxp.com>; Udit Agarwal <udit.agarwal@nxp.com>
> > Subject: [PATCH v2 1/1] Set environment location to ENVL_NOWHERE with
> > CONFIG_ENV_IS_NOWHERE.
> >
> > ENVL_NOWHERE is dependent on CONFIG_ENV_IS_NOWHERE and not on
> > CONFIG_CHAIN_OF_TRUST so return ENVL_NOWHERE when
> > CONFIG_ENV_IS_NOWHERE is enabled
> >
> > Signed-off-by: Udit Agarwal <udit.agarwal@nxp.com>
> > ---
>
> S /ENVL /ENV
>
> --pk
prev parent reply other threads:[~2019-04-22 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 9:24 [U-Boot] [PATCH v2 1/1] Set environment location to ENVL_NOWHERE with CONFIG_ENV_IS_NOWHERE Udit Agarwal
2019-03-22 11:01 ` Prabhakar Kushwaha
2019-04-22 13:15 ` Udit Agarwal [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=VI1PR04MB3983CC4B5BB3D44C52ECFB749E220@VI1PR04MB3983.eurprd04.prod.outlook.com \
--to=udit.agarwal@nxp.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.