From: Ido Schimmel <idosch@nvidia.com>
To: Lawrence Lee <lfqlee314@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Arun Ajith S <aajith@arista.com>,
Roopa Prabhu <roopa@nvidia.com>,
Jaehee Park <jhpark1013@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next] ipv6: update NUD_FAILED neighbors from NA messages
Date: Sun, 30 Aug 2026 14:27:09 +0300 [thread overview]
Message-ID: <20260830112709.GA2879069@shredder> (raw)
In-Reply-To: <DL0QFI20UBL6.3BM3CZWLDS1K3@gmail.com>
On Fri, Aug 28, 2026 at 04:54:00PM +0000, Lawrence Lee wrote:
> I will be sure to mention these points in the message. Is it appropriate
> to credit you with a 'Suggested-By' tag in the commit messages as well?
Not really: "A Suggested-by: tag indicates that the patch idea is
suggested by the person named and ensures credit to the person for the
idea" [1].
[1] Documentation/process/submitting-patches.rst
> I'm not sure what the proper attribution convention is here for commit
> message content.
No need for attribution. Simply copy me on v2 and I will review it.
prev parent reply other threads:[~2026-08-30 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 23:33 [RFC net-next] ipv6: update NUD_FAILED neighbors from NA messages Lawrence Lee
2026-08-25 11:52 ` Ido Schimmel
2026-08-25 18:07 ` Lawrence Lee
2026-08-27 9:05 ` Ido Schimmel
2026-08-28 16:54 ` Lawrence Lee
2026-08-30 11:27 ` Ido Schimmel [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=20260830112709.GA2879069@shredder \
--to=idosch@nvidia.com \
--cc=aajith@arista.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhpark1013@gmail.com \
--cc=kuba@kernel.org \
--cc=lfqlee314@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.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.