From: Greg KH <greg@kroah.com>
To: Joe Eloff <kagen101@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Simon Horman <horms@verge.net.au>,
devel <devel@driverdev.osuosl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Staging: dt3155: fix coding style issues in dt3155_drv.c
Date: Thu, 8 Jul 2010 12:59:02 -0700 [thread overview]
Message-ID: <20100708195902.GA3530@kroah.com> (raw)
In-Reply-To: <1278350030.5396.25.camel@dermezel>
On Mon, Jul 05, 2010 at 07:13:50PM +0200, Joe Eloff wrote:
> >From a19d065175340cdf0b93e3b23c134b887678fdf4 Mon Sep 17 00:00:00 2001
> From: Joe Eloff <kagen101@gmail.com>
> Date: Mon, 5 Jul 2010 18:55:08 +0200
> Subject: [PATCH] Staging: dt3155: fix coding style issues in dt3155_drv.c
>
> This is a patch to the dt3155_drv.c file that fixes up most warnings and errors found by the checkpatch.pl tool.
> * Errors: 93 -> 10
> * Warnings: 103-> 14
> Signed-off-by: Joe Eloff <kagen101@gmail.com>
This doesn't apply to the latest linux-next tree, care to redo it?
thanks,
greg k-h
prev parent reply other threads:[~2010-07-08 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 17:13 [PATCH 1/2] Staging: dt3155: fix coding style issues in dt3155_drv.c Joe Eloff
2010-07-08 19:59 ` 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=20100708195902.GA3530@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=horms@verge.net.au \
--cc=hsweeten@visionengravers.com \
--cc=kagen101@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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