public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>,
	u-boot@lists.denx.de,
	Mattijs Korpershoek <mkorpershoek@kernel.org>
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
	Marek Vasut <marex@denx.de>,
	Andrew Goodbody <andrew.goodbody@linaro.org>,
	Kory Maincent <kory.maincent@bootlin.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Christian Marangi <ansuelsmth@gmail.com>,
	Dinesh Maniyam <dinesh.maniyam@altera.com>,
	Heiko Schocher <hs@nabladev.com>,
	"Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>
Subject: Re: [PATCH v3 5/6] usb: musb-new: Relative ctrl_mod address parsing
Date: Fri, 16 Jan 2026 09:41:28 +0100	[thread overview]
Message-ID: <87ikd2dk5j.fsf@kernel.org> (raw)
In-Reply-To: <20260114-topic-musb-probing-v2026-01-v3-5-ebb8d990b9df@baylibre.com>

Hi Markus,

Thank you for the patch.

On Wed, Jan 14, 2026 at 09:33, "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com> wrote:

> For the upstream DT the ctrl_mod node is using a relative register
> address which is not translated by the current code.
>
> Make address parsing understand relative addresses.
>
> Signed-off-by: Markus Schneider-Pargmann (TI.com) <msp@baylibre.com>

I already reviewed this in v1 and the patch did not change in v3:
https://lore.kernel.org/all/87v7hdzge3.fsf@kernel.org/#t

Can you please explain why you have dropped my Reviewed-by?

Anyways, putting it back so that b4 picks it up.

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>


> ---
>  drivers/usb/musb-new/ti-musb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>

  reply	other threads:[~2026-01-16  8:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14  8:33 [PATCH v3 0/6] dm: core: Support same compatible in host/gadget musb drivers Markus Schneider-Pargmann (TI.com)
2026-01-14  8:33 ` [PATCH v3 1/6] dm: core: lists_bind_fdt: Remove unused variable Markus Schneider-Pargmann (TI.com)
2026-01-16  8:22   ` Mattijs Korpershoek
2026-01-14  8:33 ` [PATCH v3 2/6] dm: core: lists_bind_fdt: Replace found variable Markus Schneider-Pargmann (TI.com)
2026-01-16  8:23   ` Mattijs Korpershoek
2026-01-14  8:33 ` [PATCH v3 3/6] dm: core: Support multiple drivers with same compatibles Markus Schneider-Pargmann (TI.com)
2026-01-16 10:50   ` Mattijs Korpershoek
2026-01-21 16:45     ` Maniyam, Dinesh
2026-01-21 17:00       ` Markus Schneider-Pargmann
2026-01-23 11:24         ` Maniyam, Dinesh
2026-01-14  8:33 ` [PATCH v3 4/6] test: dm: Add compatible multimatch test Markus Schneider-Pargmann (TI.com)
2026-01-16  8:35   ` Mattijs Korpershoek
2026-01-14  8:33 ` [PATCH v3 5/6] usb: musb-new: Relative ctrl_mod address parsing Markus Schneider-Pargmann (TI.com)
2026-01-16  8:41   ` Mattijs Korpershoek [this message]
2026-01-16 10:14     ` Markus Schneider-Pargmann
2026-01-14  8:33 ` [PATCH v3 6/6] usb: musb-new: Add compatibles for ti,musb-am33xx Markus Schneider-Pargmann (TI.com)
2026-01-16  8:44   ` Mattijs Korpershoek

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=87ikd2dk5j.fsf@kernel.org \
    --to=mkorpershoek@kernel.org \
    --cc=andrew.goodbody@linaro.org \
    --cc=ansuelsmth@gmail.com \
    --cc=clamor95@gmail.com \
    --cc=dinesh.maniyam@altera.com \
    --cc=hs@nabladev.com \
    --cc=kory.maincent@bootlin.com \
    --cc=marex@denx.de \
    --cc=msp@baylibre.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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