From: Greg KH <greg@kroah.com>
To: Norberto Lopes <nlopes.ml@gmail.com>
Cc: gregkh@suse.de, alan@linux.intel.com, andre.goddard@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Staging: rar: fix errors/warnings related to coding style
Date: Thu, 25 Feb 2010 15:40:20 -0800 [thread overview]
Message-ID: <20100225234020.GC24155@kroah.com> (raw)
In-Reply-To: <1266773827-729-1-git-send-email-nlopes.ml@gmail.com>
On Sun, Feb 21, 2010 at 06:37:07PM +0100, Norberto Lopes wrote:
>
> Signed-off-by: Norberto Lopes <nlopes.ml@gmail.com>
> ---
> drivers/staging/rar/rar_driver.c | 82 ++++++++++++++++++-------------------
Unfortunatly, I've taken a patch in my tree that moves this file and
renames it and then cleans up these issues (hopefully).
If you look at the linux-next tree, you will see these changes already,
so I can't accept this patch, sorry.
thanks,
greg k-h
prev parent reply other threads:[~2010-02-26 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 17:37 [PATCH 1/1] Staging: rar: fix errors/warnings related to coding style Norberto Lopes
2010-02-25 23:40 ` 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=20100225234020.GC24155@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=andre.goddard@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nlopes.ml@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