All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charalampos Mitrodimas <charmitro@posteo.net>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: tmgross@umich.edu,  andrew@lunn.ch,  hkallweit1@gmail.com,
	linux@armlinux.org.uk,  davem@davemloft.net,
	 edumazet@google.com, kuba@kernel.org,  pabeni@redhat.com,
	 netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: qt2025: Fix hardware revision check comment
Date: Wed, 19 Feb 2025 13:14:16 +0000	[thread overview]
Message-ID: <87zfiiyt3r.fsf@posteo.net> (raw)
In-Reply-To: <20250219.100200.440798533601878204.fujita.tomonori@gmail.com>

FUJITA Tomonori <fujita.tomonori@gmail.com> writes:

> On Mon, 17 Feb 2025 23:53:50 +0000
> Charalampos Mitrodimas <charmitro@posteo.net> wrote:
>
>> Correct the hardware revision check comment in the QT2025 driver. The
>> revision value was documented as 0x3b instead of the correct 0xb3,
>> which matches the actual comparison logic in the code.
>> 
>> Signed-off-by: Charalampos Mitrodimas <charmitro@posteo.net>
>> ---
>>  drivers/net/phy/qt2025.rs | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/drivers/net/phy/qt2025.rs b/drivers/net/phy/qt2025.rs
>> index 1ab065798175b4f54c5f2fd6c871ba2942c48bf1..7e754d5d71544c6d6b6a6d90416a5a130ba76108 100644
>> --- a/drivers/net/phy/qt2025.rs
>> +++ b/drivers/net/phy/qt2025.rs
>> @@ -41,7 +41,7 @@ impl Driver for PhyQT2025 {
>>  
>>      fn probe(dev: &mut phy::Device) -> Result<()> {
>>          // Check the hardware revision code.
>> -        // Only 0x3b works with this driver and firmware.
>> +        // Only 0xb3 works with this driver and firmware.
>>          let hw_rev = dev.read(C45::new(Mmd::PMAPMD, 0xd001))?;
>>          if (hw_rev >> 8) != 0xb3 {
>>              return Err(code::ENODEV);
>
> Oops,
>
> Reviewed-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> Given that this patch is expected to be merged via netdev, you might
> need to resend with a proper subject:
>
> https://elixir.bootlin.com/linux/v6.13/source/Documentation/process/maintainer-netdev.rst

Hi Fujita,

Very helpful; didn't think to check the Networking subsystem workflow
docs.

Thanks,
C. Mitrodimas

>
> Thanks,

      parent reply	other threads:[~2025-02-19 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 23:53 [PATCH] net: phy: qt2025: Fix hardware revision check comment Charalampos Mitrodimas
2025-02-19  1:02 ` FUJITA Tomonori
2025-02-19 13:00   ` Andrew Lunn
2025-02-19 13:08     ` Charalampos Mitrodimas
2025-02-19 13:14   ` Charalampos Mitrodimas [this message]

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=87zfiiyt3r.fsf@posteo.net \
    --to=charmitro@posteo.net \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fujita.tomonori@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.