From: Greg KH <gregkh@suse.de>
To: Roel Van Nyen <roel.vannyen@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
acho@novell.com, error27@gmail.com
Subject: Re: [PATCH 1/2] Staging: keucr: Remove all the custom types from the driver except BOOLEAN
Date: Wed, 2 Mar 2011 16:15:54 -0500 [thread overview]
Message-ID: <20110302211554.GA24807@suse.de> (raw)
In-Reply-To: <1299099839-1416-1-git-send-email-roel.vannyen@gmail.com>
On Wed, Mar 02, 2011 at 10:03:59PM +0100, Roel Van Nyen wrote:
> Remove all the custom types from this driver except the BOOLEAN,
> that will be handled by a separate patch.
I have a pending patch that is about to delete a lot of files in this
directory. So care to redo this in a week or so after that one goes in
as this will conflict with it.
thanks,
greg k-h
prev parent reply other threads:[~2011-03-02 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 21:03 [PATCH 1/2] Staging: keucr: Remove all the custom types from the driver except BOOLEAN Roel Van Nyen
2011-03-02 21:15 ` 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=20110302211554.GA24807@suse.de \
--to=gregkh@suse.de \
--cc=acho@novell.com \
--cc=devel@driverdev.osuosl.org \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.vannyen@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