From: "Yeounsu Moon" <yyyynoom@gmail.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] net: dlink: fix multicast stats being counted incorrectly
Date: Sun, 24 Aug 2025 01:33:11 +0900 [thread overview]
Message-ID: <DC9Y9ZQA78BC.34TLXL2P7VT3T@gmail.com> (raw)
In-Reply-To: <8f47407c-fb5b-4805-a95f-ca15d6eb7838@lunn.ch>
On Sat Aug 23, 2025 at 12:15 AM KST, Andrew Lunn wrote:
> The hash for fixes tends to be shorter than that.
>
> Fixes: 3401299a1b9e ("de6*/dl2k/sundance: Move the D-Link drivers")
>
> If you add this to your .git/config
>
> [pretty]
> fixes = Fixes: %h (\"%s\")
>
> You can do
>
> git log --pretty=fixes 3401299a1b9e747cbf7de2cc0c8f6376c3cbe565
> Fixes: 3401299a1b9e ("de6*/dl2k/sundance: Move the D-Link drivers")
>
Thanks for pointing that out.
> This problem actually goes back further:
>
> git blame 3401299a1b9e~1 drivers/net/dl2k.c
>
> shows it was broken in the first commit in git.
>
> So the correct Fixes: tag is:
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>
Regarding the Fixes: tag, I have one question. You suggested
1da177e4c3f4 ("Linux-2.6.12-rc2"), which is indeed the first commit in
the current git history. However, the actual code change seems to go
back further, and I found it in the history.git repository.
In such cases, should the Fixes: tag refer to the first commit in the
mailine git tree, or to the actual commit in history.git where the bug
originated?
next prev parent reply other threads:[~2025-08-23 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 12:02 Yeounsu Moon
2025-08-22 15:15 ` Andrew Lunn
2025-08-23 16:33 ` Yeounsu Moon [this message]
2025-08-23 17:21 ` Andrew Lunn
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=DC9Y9ZQA78BC.34TLXL2P7VT3T@gmail.com \
--to=yyyynoom@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®