From: Greg KH <greg@kroah.com>
To: James K Pruitt <pruittjk@cableone.net>
Cc: gregkh@suse.de, mauricedawson2699@googlemail.com,
stewart_r@aliencamel.com, mithlesh@linsyssoft.com,
u.kleine-koenig@pengutronix.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: fixed KERN_ facility level warning
Date: Thu, 8 Jul 2010 13:07:10 -0700 [thread overview]
Message-ID: <20100708200710.GA30172@kroah.com> (raw)
In-Reply-To: <1278259791-29441-1-git-send-email-pruittjk@cableone.net>
On Sun, Jul 04, 2010 at 11:09:51AM -0500, James K Pruitt wrote:
> This is a patch to the ni_labpc.c file that fixes a "KERN_" facility level
> warning on line 529 found by the checkpatch.pl utility.
>
> Signed-off-by: James K Pruitt <pruittjk@cableone.net>
This doesn't apply to the linux-next tree, care to respin it?
thanks,
greg k-h
prev parent reply other threads:[~2010-07-08 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 16:09 [PATCH] staging: comedi: fixed KERN_ facility level warning James K Pruitt
2010-07-08 20:07 ` 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=20100708200710.GA30172@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mauricedawson2699@googlemail.com \
--cc=mithlesh@linsyssoft.com \
--cc=pruittjk@cableone.net \
--cc=stewart_r@aliencamel.com \
--cc=u.kleine-koenig@pengutronix.de \
/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