From: <Tudor.Ambarus@microchip.com>
To: <sergei.shtylyov@cogentembedded.com>
Cc: richard@nod.at, linux-mtd@lists.infradead.org, vigneshr@ti.com,
miquel.raynal@bootlin.com
Subject: Re: [PATCH v2 0/5] Fix kernel-doc comments for 'struct spi_nor'
Date: Tue, 28 Apr 2020 08:35:06 +0000 [thread overview]
Message-ID: <2604434.NqclOjlLZl@192.168.0.120> (raw)
In-Reply-To: <b82675c7-9c90-d0a5-f221-9f51f89e448e@cogentembedded.com>
On Friday, April 3, 2020 11:39:25 PM EEST Sergei Shtylyov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Hello!
>
> Here's a set of 5 patches against the 'spi-nor/next' branch of the MTD
> 'linux.git' repo. I'm fixing a number of issues in the kernel-doc comment
> to 'struct spi_nor' accumulated since its creation. Instead of a single
> patch, I'm fixing the kernel-doc comment with several patches, each fixing
> its own broken commit -- this simplifies porting to the stable kernels (if
> that ever happens). :-)
>
> [1/5] mtd: spi-nor: fix kernel-doc for 'struct spi_nor'
> [2/5] mtd: spi-nor: fix kernel-doc for spi_nor::mtd
> [3/5] mtd: spi-nor: fix kernel-doc for spi_nor::reg_proto
> [4/5] mtd: spi-nor: fix kernel-doc for spi_nor::info
> [5/5] mtd: spi-nor: fix kernel-doc for spi_nor::spimem
>
> MBR, Sergei
s/SPI-NOR/SPI NOR in 4/5. All applied, thanks.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-04-28 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 20:39 [PATCH v2 0/5] Fix kernel-doc comments for 'struct spi_nor' Sergei Shtylyov
2020-04-03 20:41 ` [PATCH v2 1/5] mtd: spi-nor: fix kernel-doc " Sergei Shtylyov
2020-04-03 20:44 ` [PATCH v2 2/5] mtd: spi-nor: fix kernel-doc for spi_nor::mtd Sergei Shtylyov
2020-04-03 20:45 ` [PATCH v2 3/5] mtd: spi-nor: fix kernel-doc for spi_nor::reg_proto Sergei Shtylyov
2020-04-03 20:49 ` [PATCH v2 4/5] mtd: spi-nor: fix kernel-doc for spi_nor::info Sergei Shtylyov
2020-04-20 9:20 ` Tudor.Ambarus
2020-04-21 3:50 ` Tudor.Ambarus
2020-04-28 8:47 ` [PATCH trivial] mtd: spi-nor: Fix SPI NOR acronym Tudor.Ambarus
2020-04-28 8:56 ` Tudor.Ambarus
2020-05-01 19:53 ` Sergei Shtylyov
2020-05-28 8:11 ` Tudor.Ambarus
2020-04-03 20:50 ` [PATCH v2 5/5] mtd: spi-nor: fix kernel-doc for spi_nor::spimem Sergei Shtylyov
2020-04-28 8:35 ` Tudor.Ambarus [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=2604434.NqclOjlLZl@192.168.0.120 \
--to=tudor.ambarus@microchip.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vigneshr@ti.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).