All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: anish <anish198519851985@gmail.com>
Cc: teddy.wang@siliconmotion.com.cn, linux-kernel@vger.kernel.org
Subject: Re: [patch]: Coding style changes for Staging sm7xx
Date: Wed, 11 May 2011 11:52:32 -0700	[thread overview]
Message-ID: <20110511185232.GA25009@kroah.com> (raw)
In-Reply-To: <1305139294.2030.51.camel@anish-desktop>

On Thu, May 12, 2011 at 12:11:34AM +0530, anish wrote:
> Hi Greg,
> 
> This patch is for staging sm7xx 
> (Silicon Motion SM7XX frame buffer device).
> Patch contains some coding style changes.
> 
> I have compiled and built it against linus tree.

You should always do this against the linux-next tree, otherwise it
probably will not apply due to the few hundred pending patches already
queued up for the next merge window.

Please redo it against the linux-next tree and resend with the below
changes as well.

> Please find the patch as attachment and checked with checkpatch.
> 
> ps:this is my first patch for linux kernel.
> Regards,
> anish

> >From 1c66ca66cf230dfa610fc1a899c45f4ac3cb6070 Mon Sep 17 00:00:00 2001
> From: anish kumar <anish198519851985@gmail.com>

Please don't attach patches, include them as the whole email.

> Date: Wed, 11 May 2011 23:12:53 +0530
> Subject: [PATCH 1/2] Coding style changes to align with linux

Please be more descriptive, what does this mean?

Also, where is patch 2/2?

> Signed-off-by: anish<anish198519851985@gmail.com>

I need a real, and full, name here.

As for the patch itself, you are doing a lot of different "cleanups"
here, please split them out into one-type-of-cleanup-per-patch and
resend them as multiple patches.

hope this helps,

greg k-h

      reply	other threads:[~2011-05-11 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 18:41 [patch]: Coding style changes for Staging sm7xx anish
2011-05-11 18:52 ` 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=20110511185232.GA25009@kroah.com \
    --to=greg@kroah.com \
    --cc=anish198519851985@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teddy.wang@siliconmotion.com.cn \
    /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.