public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Joe Hershberger <joe.hershberger@ni.com>
Subject: Re: [PATCH 2/2] env: Couple networking-related variable flags to CONFIG_NET
Date: Fri, 3 Feb 2023 13:23:53 -0500	[thread overview]
Message-ID: <Y91ROXVd3kQrAXfs@bill-the-cat> (raw)
In-Reply-To: <c6bd489e0171a292014177e3afba3e79e7f3ea25.1675426972.git.jan.kiszka@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

On Fri, Feb 03, 2023 at 01:22:52PM +0100, Jan Kiszka wrote:

> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Boards may set networking variables programmatically, thus may have
> CONFIG_NET on but CONFIG_CMD_NET off. The IOT2050 is an example.
> 
> CC: Joe Hershberger <joe.hershberger@ni.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-02-03 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 12:22 [PATCH 0/2] env: Enhancements for establishing variable protection Jan Kiszka
2023-02-03 12:22 ` [PATCH 1/2] env: Complete generic support for writable list Jan Kiszka
2023-02-07  4:02   ` Simon Glass
2023-02-07  5:49     ` Jan Kiszka
2023-02-07 13:38       ` Simon Glass
2023-02-10 18:44   ` Tom Rini
2023-02-03 12:22 ` [PATCH 2/2] env: Couple networking-related variable flags to CONFIG_NET Jan Kiszka
2023-02-03 18:23   ` Tom Rini [this message]
2023-02-10 18:44   ` Tom Rini

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=Y91ROXVd3kQrAXfs@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=jan.kiszka@siemens.com \
    --cc=joe.hershberger@ni.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox