From: Alexandra Winter <wintera@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>, netdev@vger.kernel.org
Cc: Thorsten Winkler <twinkler@linux.ibm.com>,
linux-s390@vger.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>
Subject: Re: [PATCH v2 net-next] net/iucv: clean up iucv kernel-doc warnings
Date: Tue, 3 Feb 2026 10:39:23 +0100 [thread overview]
Message-ID: <823b3697-d806-47f6-8815-fe17a616bf97@linux.ibm.com> (raw)
In-Reply-To: <136674a3-cf8d-4da9-a82d-d0edea6aca03@infradead.org>
On 02.02.26 23:07, Randy Dunlap wrote:
>> All the fixes look good to me. And they get rid of the mentioned warnings.
>> I appreciate your approach to use the existing wording, though it may not
>> be according to the latest style guidelines.
> Is that IBM style guidelines or kernel?
I was referring to kernel style. I'm not saying that any rules are broken, but
some of the 'short descriptions' are a bit verbose. Mix of imperative and present mood,
Periods at the end of descriptions, etc
I don't think it's worth polishing that, I'd rather keep the original wording of the authors.
I highly appreciate getting rid of the warnings.
next prev parent reply other threads:[~2026-02-03 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 7:23 [PATCH v2 net-next] net/iucv: clean up iucv kernel-doc warnings Randy Dunlap
2026-02-02 15:35 ` Alexandra Winter
2026-02-02 22:07 ` Randy Dunlap
2026-02-03 9:39 ` Alexandra Winter [this message]
2026-02-06 7:01 ` Randy Dunlap
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=823b3697-d806-47f6-8815-fe17a616bf97@linux.ibm.com \
--to=wintera@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=twinkler@linux.ibm.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