mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] commands: add config option for dfu command
Date: Fri, 10 Jan 2025 09:27:41 +0100	[thread overview]
Message-ID: <Z4DZ_YNBp4NuLSyY@pengutronix.de> (raw)
In-Reply-To: <e4af3816-0f89-402a-8d4f-25c477dc62ee@pengutronix.de>

On Thu, Jan 09, 2025 at 10:10:42AM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
> 
> On 09.01.25 08:44, Sascha Hauer wrote:
> > Add an extra config option for the dfu command to avoid building it in
> > non interactive builds which leads to linker errors.
> > 
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> >  commands/Kconfig  | 6 ++++++
> >  commands/Makefile | 2 +-
> >  2 files changed, 7 insertions(+), 1 deletion(-)
> > 
> > diff --git a/commands/Kconfig b/commands/Kconfig
> > index 67116ec9fc..a30299abf6 100644
> > --- a/commands/Kconfig
> > +++ b/commands/Kconfig
> > @@ -2172,6 +2172,12 @@ config CMD_USBGADGET
> >  	depends on USB_GADGET
> >  	prompt "usbgadget"
> >  
> > +config CMD_DFU
> > +	bool
> > +	depends on USB_GADGET_DFU
> > +	default y
> 
> Let's use the occasion and make it not enabled by default?
> 
> > +	prompt "dfu"
> 
> Please add a help text pointing out usbgdaget and mentioning that
> the downside of using dfu (blocks shell).

Did that while applying.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-01-10  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  7:44 Sascha Hauer
2025-01-09  9:10 ` Ahmad Fatoum
2025-01-10  8:27   ` Sascha Hauer [this message]
2025-01-10  8:23 ` Sascha Hauer

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=Z4DZ_YNBp4NuLSyY@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox