From: Joe Perches <joe@perches.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] rtlwifi: Use is_zero_ether_addr, remove line continuation
Date: Sat, 17 Mar 2012 14:18:25 -0700 [thread overview]
Message-ID: <1332019105.27069.4.camel@joe2Laptop> (raw)
In-Reply-To: <4F64FECD.9000802@lwfinger.net>
On Sat, 2012-03-17 at 16:14 -0500, Larry Finger wrote:
> Is there a PATCH 2/2? I did not receive it.
Yes.
It's a line continuation removal patch to other files.
https://lkml.org/lkml/2012/3/17/72
next prev parent reply other threads:[~2012-03-17 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 19:13 [PATCH 1/2] rtlwifi: Use is_zero_ether_addr, remove line continuation Joe Perches
2012-03-17 21:14 ` Larry Finger
2012-03-17 21:18 ` Joe Perches [this message]
2012-03-17 21:18 ` David Miller
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=1332019105.27069.4.camel@joe2Laptop \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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