From: Greg KH <greg@kroah.com>
To: "Henri Häkkinen" <henuxd@gmail.com>
Cc: gregkh@suse.de, wfp5p@virginia.edu, rich.folsom@gmail.com,
mithlesh@linsyssoft.com, jirislaby@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging:comedi: Fixed coding conventions on `adl_pci9111.c'
Date: Thu, 17 Jun 2010 16:03:13 -0700 [thread overview]
Message-ID: <20100617230313.GA419@kroah.com> (raw)
In-Reply-To: <1276502691-5573-1-git-send-email-henuxd@gmail.com>
On Mon, Jun 14, 2010 at 11:04:51AM +0300, Henri Häkkinen wrote:
> Cleaned up and fixed coding convention issues as reported by checkpatch.pl
> on the file `drivers/adl_pci9111.c' as well as other minor changes for
> consistency and clarity.
For some reason, parts of this patch no longer apply. Can you redo it
against the latest linux-next tree and resend it?
thanks,
greg k-h
prev parent reply other threads:[~2010-06-17 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:04 [PATCH] staging:comedi: Fixed coding conventions on `adl_pci9111.c' Henri Häkkinen
2010-06-17 23:03 ` 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=20100617230313.GA419@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=henuxd@gmail.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mithlesh@linsyssoft.com \
--cc=rich.folsom@gmail.com \
--cc=wfp5p@virginia.edu \
/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