From: David Howells <dhowells@redhat.com>
To: Kenny Ho <y2kenny@gmail.com>
Cc: dhowells@redhat.com, Kenny Ho <Kenny.Ho@amd.com>,
David Laight <David.Laight@aculab.com>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Marc Dionne <marc.dionne@auristor.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"linux-afs@lists.infradead.org" <linux-afs@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
alexander.deucher@amd.com
Subject: Re: [PATCH] Truncate UTS_RELEASE for rxrpc version
Date: Thu, 25 May 2023 23:52:12 +0100 [thread overview]
Message-ID: <225785.1685055132@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAOWid-c2_atz6oQspoQq4MQQ=DQWfJ=-JgbV2QFY8PveC+Sb8Q@mail.gmail.com>
Kenny Ho <y2kenny@gmail.com> wrote:
> This makes sense and looks fine to me. I don't know the proper
> etiquette here, but
> Acked-by: Kenny Ho <Kenny.Ho@amd.com>
If I'm not going to pick the patch up, I tend to use Acked-by when reviewing a
patch that touches code I'm a listed maintainer for and Reviewed-by when it's
code that I'm not a maintainer for... but the descriptions in:
Documentation/process/submitting-patches.rst
seem to leave a lot of overlap.
David
next prev parent reply other threads:[~2023-05-25 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 21:13 [PATCH] Truncate UTS_RELEASE for rxrpc version Kenny Ho
2023-05-25 22:09 ` David Howells
2023-05-25 22:28 ` Kenny Ho
2023-05-25 22:52 ` David Howells [this message]
2023-05-26 9:38 ` Simon Horman
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=225785.1685055132@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=David.Laight@aculab.com \
--cc=Kenny.Ho@amd.com \
--cc=alexander.deucher@amd.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=y2kenny@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox