From: Greg KH <greg@kroah.com>
To: Morgan Gatti <morgan.gatti@gmail.com>
Cc: gregkh@suse.de, ak@linux.intel.com, kevin.granade@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sjakub@gmail.com
Subject: Re: [PATCH 2/2] Staging:asus_oled:fix style issue in assus_oled.c
Date: Tue, 18 May 2010 14:38:52 -0700 [thread overview]
Message-ID: <20100518213852.GA18525@kroah.com> (raw)
In-Reply-To: <1274017021-2727-1-git-send-email-morgan.gatti@gmail.com>
On Sun, May 16, 2010 at 03:37:01PM +0200, Morgan Gatti wrote:
> This is a patch to the assus_oled.c file that fix the space and tabs errors founded
> by the checkpatch.pl tool
> Signed-off-by: Morgan Gatti <morgan.gatti@gmail.com>
> ---
> drivers/staging/asus_oled/asus_oled.c | 2 +-
Sorry, but this patch has already been sent in and applied to the tree.
Try making patches against the linux-next tree instead of Linus's tree
to prevent from doing duplicate work.
thanks,
greg k-h
prev parent reply other threads:[~2010-05-18 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 13:37 Morgan Gatti
2010-05-18 21:38 ` 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=20100518213852.GA18525@kroah.com \
--to=greg@kroah.com \
--cc=ak@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=kevin.granade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan.gatti@gmail.com \
--cc=sjakub@gmail.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
Powered by JetHome