From: Marek Vasut <marek.vasut@mailbox.org>
To: Mehmet Fide <mehmet.fide@gmail.com>,
Marek Vasut <marek.vasut+usb@mailbox.org>,
Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
u-boot@lists.u-boot-project.org,
Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: Re: [PATCH v2 0/4] usb: ehci-vf: take the register bases from the device tree
Date: Fri, 21 Aug 2026 02:29:12 +0200 [thread overview]
Message-ID: <2cb90777-c31d-43f7-aa6a-b11b7dea9f4f@mailbox.org> (raw)
In-Reply-To: <20260820071511.1036506-1-mehmet.fide@gmail.com>
On 8/20/26 9:15 AM, Mehmet Fide wrote:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> Review of v1 asked for three things and they are all here.
Can you please respond to the feedback before sending new versions of
patches daily, and please consider whether or not the feedback applies
to other parts of the patches too (e.g. whether you have to handle
ENOSYS or other return values all over the place). Thank you
next prev parent reply other threads:[~2026-08-21 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 7:15 [PATCH v2 0/4] usb: ehci-vf: take the register bases from the device tree Mehmet Fide
2026-08-20 7:15 ` [PATCH v2 1/4] usb: ehci-vf: remove the code path for a build without DM_USB Mehmet Fide
2026-08-20 7:15 ` [PATCH v2 2/4] usb: ehci-vf: drop the empty bind hook Mehmet Fide
2026-08-20 7:15 ` [PATCH v2 3/4] dm: core: add ofnode_get_alias_seq() Mehmet Fide
2026-08-20 7:15 ` [PATCH v2 4/4] usb: ehci-vf: take the register bases from the device tree Mehmet Fide
2026-08-21 0:29 ` Marek Vasut [this message]
2026-08-21 5:56 ` [PATCH v2 0/4] " Mehmet Fide
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=2cb90777-c31d-43f7-aa6a-b11b7dea9f4f@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=marek.vasut+usb@mailbox.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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