From: Artem Bityutskiy <dedekind1@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/16] DocG3 fixes and write support
Date: Tue, 22 Nov 2011 23:29:08 +0200 [thread overview]
Message-ID: <1321997351.2222.14.camel@koala> (raw)
In-Reply-To: <1321714978-24543-1-git-send-email-robert.jarzmik@free.fr>
On Sat, 2011-11-19 at 16:02 +0100, Robert Jarzmik wrote:
> Hi Artem and David,
>
> This patchset has been in review for several weeks. All
> pending comments have been handled. I'd like to have it in
> for the next merge window. Do I need to do anything else to
> have it integrated (grouping patches to have lesser kernel
> history impact, ...) ?
Hi, pushed to l2-mtd-2.6.git, thanks!
1. The reviewers did not give you any "Reviewed-by:" ?
2. This series has one checkpatch.pl complaint in patch 15, which looks
fair:
ERROR: do not initialise statics to 0 or NULL
#74: FILE: drivers/mtd/devices/docg3.c:64:
+static unsigned int reliable_mode = 0;
total: 1 errors, 0 warnings, 206 lines checked
/home/dedekind/tmp/j15.mbox has style problems, please review.
3. When I compile with gcc-4.6 for x68_64 I see the following
compilation warnings:
CC [M] drivers/mtd/devices/docg3.o
drivers/mtd/devices/docg3.c: In function ‘doc_read_oob’:
drivers/mtd/devices/docg3.c:630:3: warning: passing argument 2 of ‘doc_get_hw_bch_syndroms’ from incompatible pointer type [enabled by default]
drivers/mtd/devices/docg3.c:513:13: note: expected ‘int *’ but argument is of type ‘u8 *’
drivers/mtd/devices/docg3.c: At top level:
drivers/mtd/devices/docg3.c:762:12: warning: ‘doc_get_erase_count’ defined but not used [-Wunused-function]
4. sparse gives the following warning:
CHECK drivers/mtd/devices/docg3.c
drivers/mtd/devices/docg3.c:630:48: warning: incorrect type in argument 2 (different type sizes)
drivers/mtd/devices/docg3.c:630:48: expected int *syns
drivers/mtd/devices/docg3.c:630:48: got unsigned char *<noident>
Could you please look at 2, 3, and 4? I did not look whether they are
fair or not. Please, do not re-send the series again, I think it is OK
if you send incremental fixes instead. Or if you at some point re-send
v4, you can incorporate the warnings fixes, but please, do not send 16
patches again only because of this :-)
Thanks!
next prev parent reply other threads:[~2011-11-22 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 15:02 [PATCH v3 00/16] DocG3 fixes and write support Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 01/16] mtd/docg3: fix debug log verbosity Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 02/16] mtd/docg3: fix tracing of IO in writeb Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 03/16] mtd/docg3: fix protection areas reading Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 04/16] mtd/docg3: fix BCH registers Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 05/16] mtd/docg3: fix reading oob+data without correction Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 06/16] mtd/docg3: add multiple floor support Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 07/16] mtd/docg3: add OOB layout to mtdinfo Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 08/16] mtd/docg3: add registers for erasing and writing Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 09/16] mtd/docg3: add OOB buffer to device structure Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 10/16] mtd/docg3: add write functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 11/16] mtd/docg3: add erase functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 12/16] mtd/docg3: map erase and write functions Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 13/16] mtd/docg3: add ECC correction code Robert Jarzmik
2011-11-24 10:24 ` Ivan Djelic
2011-11-24 17:56 ` Mike Dunn
2011-11-19 15:02 ` [PATCH v3 14/16] mtd/docg3: add suspend and resume Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 15/16] mtd/docg3: add fast mode Robert Jarzmik
2011-11-19 15:02 ` [PATCH v3 16/16] mtd/docg3: add protection areas sysfs access Robert Jarzmik
2011-11-26 23:57 ` Greg KH
2011-11-27 10:29 ` Robert Jarzmik
2011-11-22 21:29 ` Artem Bityutskiy [this message]
2011-11-25 17:44 ` [PATCH v3 00/16] DocG3 fixes and write support Robert Jarzmik
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=1321997351.2222.14.camel@koala \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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