From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Naga Sureshkumar Relli <nagasure@xilinx.com>
Cc: "richard@nod.at" <richard@nod.at>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"mmayer@broadcom.com" <mmayer@broadcom.com>,
"rogerq@ti.com" <rogerq@ti.com>,
"ladis@linux-mips.org" <ladis@linux-mips.org>,
"ada@thorsis.com" <ada@thorsis.com>,
"honghui.zhang@mediatek.com" <honghui.zhang@mediatek.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"nagasureshkumarrelli@gmail.com" <nagasureshkumarrelli@gmail.com>,
Michal Simek <michals@xilinx.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [[LINUX PATCH v10] 3/4] Documentation: nand: pl353: Add documentation for controller and driver
Date: Mon, 25 Jun 2018 11:13:21 +0200 [thread overview]
Message-ID: <20180625111321.652d12ff@bbrezillon> (raw)
In-Reply-To: <MWHPR02MB26234FD1B68C2B5ECC6B87F6AF4A0@MWHPR02MB2623.namprd02.prod.outlook.com>
On Mon, 25 Jun 2018 08:56:41 +0000
Naga Sureshkumar Relli <nagasure@xilinx.com> wrote:
> Hi Boris,
>
> > -----Original Message-----
> > From: Boris Brezillon [mailto:boris.brezillon@bootlin.com]
> > Sent: Monday, June 25, 2018 2:24 AM
> > To: Naga Sureshkumar Relli <nagasure@xilinx.com>
> > Cc: richard@nod.at; dwmw2@infradead.org; computersforpeace@gmail.com;
> > marek.vasut@gmail.com; f.fainelli@gmail.com; mmayer@broadcom.com; rogerq@ti.com;
> > ladis@linux-mips.org; ada@thorsis.com; honghui.zhang@mediatek.com;
> > miquel.raynal@bootlin.com; nagasureshkumarrelli@gmail.com; Michal Simek
> > <michals@xilinx.com>; linux-mtd@lists.infradead.org; linux-kernel@vger.kernel.org
> > Subject: Re: [[LINUX PATCH v10] 3/4] Documentation: nand: pl353: Add documentation
> > for controller and driver
> >
> > On Thu, 21 Jun 2018 12:12:30 +0530
> > Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com> wrote:
> >
> > > Added notes about the controller and driver.
> > >
> > > Signed-off-by: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>
> > > ---
> > > Changes in v10:
> > > - None
> > > Changes in v9:
> > > - Addressed the comments given by Miquel and Randy
> > > Changes in v8
> > > - None
> > > Changes in v7:
> > > - None
> > > Changes in v6:
> > > - None
> > > Changes in v5:
> > > - Fixed the review comments
> > > Changes in v4:
> > > - None
> > > ---
> > > Documentation/mtd/nand/pl353-nand.txt | 99
> > +++++++++++++++++++++++++++++++++++
> > > 1 file changed, 99 insertions(+)
> > > create mode 100644 Documentation/mtd/nand/pl353-nand.txt
> >
> > Can we put these information directly in the driver instead of having
> > yet another place where we have things partially documented? I just
> > discovered a doc for the pxa NAND controller in this directory because
> > of this patch, which kind of proves my point :-).
> Ok, but could you please explain where to put in driver?
> Do you mean, as comments inside drivers/mtd/raw/pl353-nand.c?
Yes. Either inline, next to the relevant section of code, or at the
beginning of the file.
next prev parent reply other threads:[~2018-06-25 9:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 6:42 [[LINUX PATCH v10] 0/4] Add arm pl353 smc memory and nand driver for xilinx zynq soc Naga Sureshkumar Relli
2018-06-21 6:42 ` [[LINUX PATCH v10] 1/4] Devicetree: Add pl353 smc controller devicetree binding information Naga Sureshkumar Relli
2018-06-24 20:40 ` Boris Brezillon
2018-06-25 8:59 ` Naga Sureshkumar Relli
2018-06-27 11:07 ` Naga Sureshkumar Relli
2018-06-28 6:54 ` Linus Walleij
2018-06-28 7:56 ` Naga Sureshkumar Relli
2018-06-21 6:42 ` [[LINUX PATCH v10] 2/4] memory: pl353: Add driver for arm pl353 static memory controller Naga Sureshkumar Relli
2018-06-28 6:49 ` Linus Walleij
2018-06-28 12:10 ` Naga Sureshkumar Relli
2018-06-28 12:11 ` Naga Sureshkumar Relli
2018-06-28 18:11 ` Linus Walleij
2018-06-21 6:42 ` [[LINUX PATCH v10] 3/4] Documentation: nand: pl353: Add documentation for controller and driver Naga Sureshkumar Relli
2018-06-24 20:54 ` Boris Brezillon
2018-06-25 8:56 ` Naga Sureshkumar Relli
2018-06-25 9:13 ` Boris Brezillon [this message]
2018-06-21 6:42 ` [[LINUX PATCH v10] 4/4] mtd: rawnand: pl353: Add basic driver for arm pl353 smc nand interface Naga Sureshkumar Relli
2018-06-27 15:22 ` Miquel Raynal
2018-06-28 5:01 ` Naga Sureshkumar Relli
2018-06-28 7:14 ` Miquel Raynal
2018-06-28 7:37 ` Naga Sureshkumar Relli
2018-07-03 13:00 ` Naga Sureshkumar Relli
2018-07-08 12:38 ` Miquel Raynal
2018-06-28 7:43 ` Linus Walleij
2018-06-28 12:13 ` Naga Sureshkumar Relli
2018-06-28 18:13 ` Linus Walleij
2018-06-29 4:15 ` Naga Sureshkumar Relli
2018-07-02 13:47 ` Linus Walleij
2018-07-03 4:19 ` Naga Sureshkumar Relli
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=20180625111321.652d12ff@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=ada@thorsis.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=f.fainelli@gmail.com \
--cc=honghui.zhang@mediatek.com \
--cc=ladis@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=michals@xilinx.com \
--cc=miquel.raynal@bootlin.com \
--cc=mmayer@broadcom.com \
--cc=nagasure@xilinx.com \
--cc=nagasureshkumarrelli@gmail.com \
--cc=richard@nod.at \
--cc=rogerq@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