From: Artem Bityutskiy <dedekind1@gmail.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd/nand.h: cleanups
Date: Tue, 05 Oct 2010 21:48:26 +0300 [thread overview]
Message-ID: <1286304506.1797.2.camel@brekeke> (raw)
In-Reply-To: <20101005182656.GA21067@pengutronix.de>
On Tue, 2010-10-05 at 20:26 +0200, Wolfram Sang wrote:
> Hi Sebastian,
>
> just a minor comment.
[Side note: it is much more reader-friendly to avoid citing whole patch
and making the readers search where you put the comment, like this:]
> > @@ -457,24 +492,32 @@ struct nand_chip {
> >
> > uint8_t (*read_byte)(struct mtd_info *mtd);
> > u16 (*read_word)(struct mtd_info *mtd);
> > - void (*write_buf)(struct mtd_info *mtd, const uint8_t *buf, int len);
> > - void (*read_buf)(struct mtd_info *mtd, uint8_t *buf, int len);
> > - int (*verify_buf)(struct mtd_info *mtd, const uint8_t *buf, int len);
> > + void (*write_buf)(struct mtd_info *mtd, const uint8_t *buf,
> > + int len);
>
> It might be more readable to get rid of the tabs after the type and keep the
> arguments in one line?
I agree with this. Sebastian, I'll put your patch to my l2 tree when
git.infradead.org is back. But if you could send a separate follow up
patch which kills these ugly tabs - it would be nice.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-10-05 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 10:41 [PATCH] mtd/nand.h: cleanups Sebastian Andrzej Siewior
2010-10-05 18:26 ` Wolfram Sang
2010-10-05 18:48 ` Artem Bityutskiy [this message]
2010-10-06 21:06 ` [PATCH] mtd/nand.h: little more cleanup Sebastian Andrzej Siewior
2010-10-06 21:21 ` Wolfram Sang
2010-10-07 19:30 ` Artem Bityutskiy
2010-10-07 19:41 ` Sebastian Andrzej Siewior
2010-10-07 19:48 ` [PATCH v2] " Sebastian Andrzej Siewior
2010-10-08 6:00 ` Artem Bityutskiy
2010-10-07 19:17 ` [PATCH] mtd/nand.h: cleanups Artem Bityutskiy
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=1286304506.1797.2.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=w.sang@pengutronix.de \
/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).