From: Greg KH <greg@kroah.com>
To: Audun Hoem <audun.hoem@gmail.com>
Cc: gregkh@suse.de, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: bcm: Arp.c: Checkpatch.pl fix
Date: Tue, 16 Nov 2010 12:08:41 -0800 [thread overview]
Message-ID: <20101116200841.GD12492@kroah.com> (raw)
In-Reply-To: <1289870088-18871-1-git-send-email-audun.hoem@gmail.com>
On Tue, Nov 16, 2010 at 02:14:48AM +0100, Audun Hoem wrote:
> Cleaned up the coding style. 80 line length limit warnings are in a comment.
>
> Signed-off-by: Audun Hoem <audun.hoem@gmail.com>
> ---
> drivers/staging/bcm/Arp.c | 63 ++++++++++++++++++++------------------------
This file is no longer in the linux-next tree so I can't apply this
patch :)
Care to resync and send patches only on the linux-next tree?
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-16 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 1:14 [PATCH] staging: bcm: Arp.c: Checkpatch.pl fix Audun Hoem
2010-11-16 20:08 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-16 1:14 Audun Hoem
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=20101116200841.GD12492@kroah.com \
--to=greg@kroah.com \
--cc=audun.hoem@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).