From: Josua Mayer <josua@solid-run.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v2 0/4] phy: phy-can-transceiver: Ad-hoc cleanups and refactoring
Date: Mon, 27 Apr 2026 13:41:43 +0000 [thread overview]
Message-ID: <5d4c3c95-cbe1-4439-8036-b014264ce8c2@solid-run.com> (raw)
In-Reply-To: <ae9l4n8wocbVegcJ@ashevche-desk.local>
Am 27.04.26 um 15:34 schrieb Andy Shevchenko:
> On Mon, Apr 27, 2026 at 11:09:48AM +0000, Josua Mayer wrote:
>> Am 14.04.26 um 20:43 schrieb Andy Shevchenko:
>>> On Tue, Mar 17, 2026 at 09:27:26PM +0100, Andy Shevchenko wrote:
>>>> The driver does two things that need to be addressed:
>>>> - includes subject to remove gpio.h
>>>> - checks for error code from device property APIs when it can be done in
>>>> a robust way
>>>>
>>>> This series addresses the above and adds a couple of additional refactoring.
>>> Any comments on this? Doesn't look like it being applied so far...
>> For unknown reason your patch-set did not arrive in my inbox.
>> Perhaps it went missing for others, too?
> Are you in the MAINTAINERS for this part of the kernel?
> The CAN NETWORK DRIVERS and GENERIC PHY FRAMEWORK do not list your name.
Correct. I touched can phy once related to mux only.
> If you think of mail delivery in general, it's delivered at least to the ML
> https://lore.kernel.org/all/20260317203001.2108568-1-andriy.shevchenko@linux.intel.com/
>
> TBH I don't know what to answer to your question as I don't know your expectations and
> how it should be fulfilled taking into account my above question...
Changelog v2:
- Cc'ed to Ulf and Josua due to above
This is why I expected it in my inbox.
Usually in this situation I blame my provider.
>
> But thanks for the reviewing! I will address the commit message in v3.
Great!
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-04-27 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 20:27 [PATCH v2 0/4] phy: phy-can-transceiver: Ad-hoc cleanups and refactoring Andy Shevchenko
2026-03-17 20:27 ` [PATCH v2 1/4] phy: phy-can-transceiver: Convert to use device property API Andy Shevchenko
2026-04-27 11:26 ` Josua Mayer
2026-03-17 20:27 ` [PATCH v2 2/4] phy: phy-can-transceiver: Move OF ID table closer to their user Andy Shevchenko
2026-03-17 20:27 ` [PATCH v2 3/4] phy: phy-can-transceiver: Don't check for specific errors when parsing properties Andy Shevchenko
2026-03-17 20:27 ` [PATCH v2 4/4] phy: phy-can-transceiver: Drop unused include Andy Shevchenko
2026-04-27 11:05 ` Josua Mayer
2026-04-14 18:43 ` [PATCH v2 0/4] phy: phy-can-transceiver: Ad-hoc cleanups and refactoring Andy Shevchenko
2026-04-27 11:09 ` Josua Mayer
2026-04-27 13:34 ` Andy Shevchenko
2026-04-27 13:41 ` Josua Mayer [this message]
2026-04-27 15:26 ` Andy Shevchenko
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=5d4c3c95-cbe1-4439-8036-b014264ce8c2@solid-run.com \
--to=josua@solid-run.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=neil.armstrong@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.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