From: Greg KH <greg@kroah.com>
To: David Cross <david.cross@cypress.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] West Bridge Astoria Driver 2.6.35, minor block and device driver updates
Date: Sat, 4 Sep 2010 22:24:23 -0700 [thread overview]
Message-ID: <20100905052423.GA4396@kroah.com> (raw)
In-Reply-To: <1283467794.4378.17.camel@odc-laptop>
On Thu, Sep 02, 2010 at 03:49:54PM -0700, David Cross wrote:
> This patch contains minor updates to the west bridge block and device
> drivers, including the addition of a common lock and a minor update to
> remove the blk_fs_request call based on a kernel update. These changes
> could possibly be separated, but are very minor in scope and as such
> have been submitted together.
Again, one patch per logical change please. That's the way patches for
the kernel work. So can you please separate these and resend them?
> Signed-off-by: David Cross <david.cross@cypress.com>
>
> diff -uprN -X linux-next-vanilla/Documentation/dontdiff linux-next-vanilla/drivers/staging/westbridge/astoria/block/cyasblkdev_block.c linux-next-incl-sdk/drivers/staging/westbridge/astoria/block/cyasblkdev_block.c
> --- linux-next-vanilla/drivers/staging/westbridge/astoria/block/cyasblkdev_block.c 2010-08-31 19:32:51.000000000 -0700
> +++ linux-next-incl-sdk/drivers/staging/westbridge/astoria/block/cyasblkdev_block.c 2010-08-25 18:29:44.000000000 -0700
> @@ -389,7 +389,7 @@ int cyasblkdev_media_changed(struct gend
> struct cyasblkdev_blk_data *bd;
>
> #ifndef WESTBRIDGE_NDEBUG
> - cy_as_hal_print_message("cyasblkdev_media_changed() is called\n");
> + cy_as_hal_print_message(KERN_INFO"cyasblkdev_media_changed() is called\n");
Ick. How about a ' ' after KERN_INFO? And do you really always want to
do this? You can enable tracing to get this type of info.
> #endif
The whole NDEBUG stuff should be removed from the .c files and put in
the .h file if it's really needed.
> @@ -493,7 +493,7 @@ static void cyasblkdev_issuecallback(
> {
> int retry_cnt = 0;
> DBGPRN_FUNC_NAME;
> -
> +
> if (status != CY_AS_ERROR_SUCCESS) {
> #ifndef WESTBRIDGE_NDEBUG
> cy_as_hal_print_message(
You added a line of trailing spaces for no good reason :(
> @@ -509,7 +509,10 @@ static void cyasblkdev_issuecallback(
> __func__, (unsigned int) gl_bd->queue.req, status,
> (unsigned int) blk_rq_sectors(gl_bd->queue.req)) ;
> #endif
> -
> +
> + if(rq_data_dir(gl_bd->queue.req) != READ) {
> + cy_as_release_common_lock();
> + }
No need for the extra {}, please take a look at
Documentation/CodingStyle for how to do things for the kernel. Also a
space is needed after the 'if'.
Please run your patches through the scripts/checkpatch.pl tool before
sending them to me. Yes, there's lots of checkpatch issues in the
driver already, but don't add new ones now please.
Care to redo this?
thanks,
greg k-h
prev parent reply other threads:[~2010-09-05 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5BFACB1451C1459BA8562A5561D0A4E6@stanford.edu>
2010-09-02 0:08 ` [PATCH] West Bridge Astoria Driver 2.6.35, Kconfig fixes David Cross
2010-09-02 1:37 ` Greg KH
2010-09-02 22:43 ` [PATCH] West Bridge Astoria Driver 2.6.35, Kconfig and HAL fixes David Cross
2010-09-05 5:17 ` Greg KH
2010-09-07 19:22 ` [PATCH] west bridge, kconfig and hal fixes David Cross
2010-09-07 23:57 ` Greg KH
2010-09-08 20:56 ` David Cross
2010-09-09 3:51 ` Greg KH
2010-09-02 22:47 ` [PATCH] West Bridge Astoria Driver 2.6.35, cyasgadget fixes and mpage_cleardirty David Cross
2010-09-05 5:20 ` Greg KH
2010-09-02 22:49 ` [PATCH] West Bridge Astoria Driver 2.6.35, minor block and device driver updates David Cross
2010-09-05 5:24 ` Greg KH [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=20100905052423.GA4396@kroah.com \
--to=greg@kroah.com \
--cc=david.cross@cypress.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.