All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thomas Kupper <thomas.kupper@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 1/1] amd-xgbe: fix active cable determination
Date: Thu, 10 Nov 2022 17:11:01 -0800	[thread overview]
Message-ID: <20221110171101.6dce660c@kernel.org> (raw)
In-Reply-To: <aa6ad8c7-5df9-9569-2849-ee601b862645@gmail.com>

On Fri, 11 Nov 2022 00:00:38 +0100 Thomas Kupper wrote:
> >> I apologise, after reading through all the guidelines I forgot that it
> >> was on top of the latest linux-kernel instead of net.
> >>
> >> Regarding the 'Fixes' tag: active cables don't works for at least since
> >> kernel v5.15, to what commit would you suggest do I refer to?  
> > Which exact sub-version of 5.15 ? Looking at the history of the file
> > commit 09c5f6bf11ac988743 seems like a candidate but you'd need to
> > double check based on what you know, or just revert and see if that
> > fixes your problem (to confirm that's the culprit).  
> 
> Checking with git blame shows that in commit abf0a1c2b26ad from 
> 2016-11-10 the whole if, else if ... clause plus a lot more was 
> introduced. And since then the handling of the active cables was 
> missing. The check (for the passive cable) got moved up in the commit 
> you mentioned.
> 
> I would then use 'Fixes: abf0a1c2b26ad ...', right?

Yup, sounds like it! Make sure you use the exact format from here
https://www.kernel.org/doc/html/v4.12/process/submitting-patches.html#describe-your-changes
don't wrap the line, and don't separate the tags with empty lines.
The Fixes tags are used by automated backport machinery so we need
exact format to be followed.

> And sent pretty much the same mail as the first time, with Tom and
> Raju CCed? And Patchwork will realise that?

You can throw in v2 into the subject tag to avoid any confusion:
[PATCH new v2] and that's it, yes :)

      reply	other threads:[~2022-11-11  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 21:03 [PATCH net 1/1] amd-xgbe: fix active cable determination Thomas Kupper
2022-11-10 21:57 ` Jakub Kicinski
     [not found]   ` <fcf6ad3b-8dde-a926-1b6e-e2810040d7c8@gmail.com>
     [not found]     ` <20221110143558.793dd6bf@kernel.org>
2022-11-10 23:00       ` Thomas Kupper
2022-11-11  1:11         ` Jakub Kicinski [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=20221110171101.6dce660c@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.kupper@gmail.com \
    /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.