From: Paul Walmsley <paul.walmsley@sifive.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Sagar Shrikant Kadam <sagar.kadam@sifive.com>,
marek.vasut@gmail.com, tudor.ambarus@microchip.com,
dwmw2@infradead.org, computersforpeace@gmail.com,
bbrezillon@kernel.org, richard@nod.at, palmer@sifive.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 3/3] mtd: spi-nor: add locking support for is25xxxxx device
Date: Tue, 30 Apr 2019 10:19:46 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1904301019280.7063@viisi.sifive.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1904301004060.7063@viisi.sifive.com>
On Tue, 30 Apr 2019, Paul Walmsley wrote:
> The above sequence indicates a kerneldoc-style comment, but the format of
> the comment is not in kerneldoc format. Please fix this comment to
> conform with
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/kernel-docs.rst
This, rather:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/doc-guide/kernel-doc.rst#n57
- Paul
prev parent reply other threads:[~2019-04-30 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 18:09 [PATCH v2 0/3] add support for is25wp256 spi-nor device Sagar Shrikant Kadam
2019-04-28 18:09 ` [PATCH v2 1/3] mtd: spi-nor: add support for is25wp256 Sagar Shrikant Kadam
2019-04-30 17:03 ` Paul Walmsley
2019-05-02 9:50 ` Sagar Kadam
2019-04-28 18:09 ` [PATCH v2 2/3] mtd: spi-nor: add support to unlock flash device Sagar Shrikant Kadam
2019-04-30 17:19 ` Paul Walmsley
2019-05-02 9:56 ` Sagar Kadam
2019-04-28 18:09 ` [PATCH v2 3/3] mtd: spi-nor: add locking support for is25xxxxx device Sagar Shrikant Kadam
2019-04-30 17:13 ` Paul Walmsley
2019-04-30 17:19 ` Paul Walmsley [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=alpine.DEB.2.21.9999.1904301019280.7063@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=palmer@sifive.com \
--cc=richard@nod.at \
--cc=sagar.kadam@sifive.com \
--cc=tudor.ambarus@microchip.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
all inboxes | Powered by JetHome®