From: Jakub Kicinski <kuba@kernel.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Eric Dumazet <edumazet@google.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Qianqiang Liu <qianqiang.liu@163.com>,
Chris Snook <chris.snook@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
kernel@collabora.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: ethernet: ag71xx: Remove dead code
Date: Thu, 12 Sep 2024 20:27:24 -0700 [thread overview]
Message-ID: <20240912202724.10ce9c29@kernel.org> (raw)
In-Reply-To: <20240912174222.6de55d16@kernel.org>
On Thu, 12 Sep 2024 17:42:22 -0700 Jakub Kicinski wrote:
> On Thu, 12 Sep 2024 17:56:11 +0200 Eric Dumazet wrote:
> > I do not see any credits given to Qianqiang Liu, who is desperate to get his
> > first linux patch...
> >
> > https://lore.kernel.org/netdev/20240910152254.21238-1-qianqiang.liu@163.com/
>
> Right, odd, is there a reason you took over from Qianqiang Liu?
> Otherwise I'd prefer if they could send the next version.
> Last thing we need is arguments about ownership of trivial
> patches.
>
> This v2 has an unnecessary Fixes tag, this is not a fix.
Oh, I guess it may be a v2 of your own change:
https://lore.kernel.org/all/20240911105924.4028423-1-usama.anjum@collabora.com/
Are you both using the same tool? 5 year old code and suddenly we get
the same fix two times.
prev parent reply other threads:[~2024-09-13 3:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 13:58 [PATCH v2] net: ethernet: ag71xx: Remove dead code Muhammad Usama Anjum
2024-09-11 14:24 ` Andrew Lunn
2024-09-11 15:47 ` Vadim Fedorenko
2024-09-11 18:20 ` Oleksij Rempel
2024-09-12 15:56 ` Eric Dumazet
2024-09-12 16:28 ` Qianqiang Liu
2024-09-13 0:42 ` Jakub Kicinski
2024-09-13 3:27 ` 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=20240912202724.10ce9c29@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.snook@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=qianqiang.liu@163.com \
--cc=usama.anjum@collabora.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.