From: Marek Vasut <marex@denx.de>
To: Xavier Drudis Ferran <xdrudis@tinet.cat>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Simon Glass <sjg@chromium.org>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Suneel Garapati <suneelglinux@gmail.com>,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [SPAM] Re: [PATCH] cmd: usb: Prevent reset in usb tree/info command
Date: Wed, 21 Jun 2023 01:08:32 +0200 [thread overview]
Message-ID: <bfa43f70-4e42-94cc-df97-54aa9e013921@denx.de> (raw)
In-Reply-To: <ZJGC4lOvMLI4ZqD7@xdrudis.tinet.cat>
On 6/20/23 12:43, Xavier Drudis Ferran wrote:
> El Tue, Jun 20, 2023 at 11:49:36AM +0200, Marek Vasut deia:
>>
>> Default, see:
>> $ git grep CONFIG_BOOTCOMMAND configs/
>>
>
> I'm lost.
>
> I called default what Kconfig used as default.
> You seem to call default what's in board specific config files.
> Whatever. Fix the wording in the commit message if you like.
All I am really asking for is minimal test case.
That is all I was asking for since the very beginning.
So to answer my own question, this is the minimal test case:
=> usb reset ; bootflow scan ; usb info
Can you please add it to the commit message, collect RB from Simon, add
Reviewed-by: Marek Vasut <marex@denx.de>
Tested-by: Marek Vasut <marex@denx.de>
And send V2 so I can pick it for this release ?
Thank you
next prev parent reply other threads:[~2023-06-20 23:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZJAqKxrO7qa8r6Kq@xdrudis.tinet.cat>
2023-06-19 21:49 ` [PATCH] cmd: usb: Prevent reset in usb tree/info command Marek Vasut
2023-06-20 9:17 ` Xavier Drudis Ferran
2023-06-20 9:49 ` Marek Vasut
2023-06-20 10:43 ` [SPAM] " Xavier Drudis Ferran
2023-06-20 23:08 ` Marek Vasut [this message]
2023-06-05 15:20 Xavier Drudis Ferran
2023-06-07 22:05 ` Marek Vasut
2023-06-08 7:39 ` Xavier Drudis Ferran
2023-06-09 1:20 ` Marek Vasut
[not found] ` <ZILsTOaXliizQjiH@xdrudis.tinet.cat>
2023-06-09 18:52 ` [SPAM] " Xavier Drudis Ferran
2023-06-11 12:29 ` Marek Vasut
2023-06-12 21:17 ` Simon Glass
2023-06-13 6:42 ` Xavier Drudis Ferran
2023-06-13 6:52 ` Xavier Drudis Ferran
2023-06-13 14:58 ` Simon Glass
2023-06-13 16:04 ` Xavier Drudis Ferran
2023-06-13 20:12 ` Simon Glass
2023-06-14 8:40 ` Xavier Drudis Ferran
2023-06-20 10:03 ` Simon Glass
2023-06-20 11:20 ` Xavier Drudis Ferran
2023-06-20 14:36 ` Simon Glass
2023-06-20 0:50 ` Marek Vasut
2023-06-20 7:03 ` Xavier Drudis Ferran
2023-06-20 9:13 ` Marek Vasut
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=bfa43f70-4e42-94cc-df97-54aa9e013921@denx.de \
--to=marex@denx.de \
--cc=bmeng.cn@gmail.com \
--cc=lukma@denx.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=suneelglinux@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=xdrudis@tinet.cat \
/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