From: Greg KH <greg@kroah.com>
To: Gorskin Ilya <revent82@gmail.com>
Cc: gregkh@suse.de, andre@bitwigglers.org, ak@linux.intel.com,
peterhuewe@gmx.de, kevin.granade@gmail.com,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging:asus_oled: fix tabs coding style issue in asus_oled.c This is a patch to the asus_oled.c file that fixes up a tabs warning found by the checkpatch.pl tool
Date: Tue, 27 Apr 2010 10:24:55 -0700 [thread overview]
Message-ID: <20100427172455.GF28779@kroah.com> (raw)
In-Reply-To: <1268421177-20527-1-git-send-email-revent82@gmail.com>
On Sat, Mar 13, 2010 at 12:12:57AM +0500, Gorskin Ilya wrote:
> Signed-off-by: Gorskin Ilya <revent82@gmail.com>
Sorry, someone else already sent this fix in.
greg k-h
prev parent reply other threads:[~2010-04-27 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 19:12 [PATCH] Staging:asus_oled: fix tabs coding style issue in asus_oled.c This is a patch to the asus_oled.c file that fixes up a tabs warning found by the checkpatch.pl tool Gorskin Ilya
2010-04-27 17: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=20100427172455.GF28779@kroah.com \
--to=greg@kroah.com \
--cc=ak@linux.intel.com \
--cc=andre@bitwigglers.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=kevin.granade@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=revent82@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