From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-usb@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>
Subject: Re: [PATCH] thunderbolt: Add missing kernel-doc parameter descriptions
Date: Thu, 13 Feb 2020 12:12:34 +0200 [thread overview]
Message-ID: <20200213101234.GS2667@lahna.fi.intel.com> (raw)
In-Reply-To: <20200213100907.xeuvsiaz4hwxnmb4@wunner.de>
On Thu, Feb 13, 2020 at 11:09:07AM +0100, Lukas Wunner wrote:
> On Thu, Feb 13, 2020 at 01:02:07PM +0300, Mika Westerberg wrote:
> > @@ -296,6 +297,9 @@ static int usb4_switch_drom_read_block(struct tb_switch *sw,
> > /**
> > * usb4_switch_drom_read() - Read arbitrary bytes from USB4 router DROM
> > * @sw: USB4 router
> > + * @address: Byte address inside DROM to start reading
> > + * @buf: Buffer where the DROM contens is stored
>
> Either "content is" or "contents are".
Heh, indeed. I'll use "content is" in v2.
prev parent reply other threads:[~2020-02-13 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 10:02 [PATCH] thunderbolt: Add missing kernel-doc parameter descriptions Mika Westerberg
2020-02-13 10:09 ` Lukas Wunner
2020-02-13 10:12 ` Mika Westerberg [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=20200213101234.GS2667@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.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;
as well as URLs for NNTP newsgroup(s).