From: Greg KH <greg@kroah.com>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] staging: ath6kl: Including a header file to fix a compilation error
Date: Fri, 17 Sep 2010 22:11:22 -0700 [thread overview]
Message-ID: <20100918051122.GA18733@kroah.com> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F23A2763A@SC1EXMB-MBCL.global.atheros.com>
On Fri, Sep 17, 2010 at 07:06:42PM -0700, Vipin Mehta wrote:
> >
> > {sigh} Line length please...
> Sorry about that. I have now configured outlook to wrap the line at 70 characters. It was 76 by default. Hopefully, it shows up better now.
No, it's still wrong, you need to fix outlook to properly add line ends
for your lines.
Or better yet, don't use outlook. Seriously. There are lots of other
email clients out there that are way better, and free, and some even
will work with your exchange server.
good luck,
greg k-h
next prev parent reply other threads:[~2010-09-18 5:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 16:54 [PATCH] staging: ath6kl: Including a header file to fix a compilation error Vipin Mehta
2010-09-17 17:23 ` Randy Dunlap
2010-09-17 18:00 ` Greg KH
2010-09-17 23:26 ` Vipin Mehta
2010-09-17 23:46 ` Greg KH
2010-09-18 2:06 ` Vipin Mehta
2010-09-18 5:11 ` Greg KH [this message]
2010-09-17 23:11 ` Vipin Mehta
2010-09-17 23:26 ` Greg KH
2010-09-18 2:00 ` Vipin Mehta
2010-09-18 5:12 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-09-17 0:08 Vipin Mehta
2010-09-17 0:10 ` Luis R. Rodriguez
2010-09-17 0:13 ` Vipin Mehta
2010-09-17 0:17 ` Greg KH
2010-09-17 0:14 ` Greg KH
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=20100918051122.GA18733@kroah.com \
--to=greg@kroah.com \
--cc=Vipin.Mehta@Atheros.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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).