From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
gospo@redhat.com, bphilips@novell.com
Subject: Re: [PATCH 2/2] igbvf.txt: Add igbvf Documentation
Date: Sun, 8 Aug 2010 17:25:44 -0700 [thread overview]
Message-ID: <AANLkTinFNm0B37vtnqcFH_weq3zL9FZiRfE5QVk647PC@mail.gmail.com> (raw)
In-Reply-To: <20100807.230156.25112206.davem@davemloft.net>
On Sat, Aug 7, 2010 at 23:01, David Miller <davem@davemloft.net> wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Date: Tue, 03 Aug 2010 17:16:17 -0700
>
>> Adds documentation for the igbvf (igb virtual function driver).
>>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
>
> Tons of trailing whitespace, GIT nearly craps itself when I try
> to apply this.
>
> Please fix this, and also submit the fixed up 1/1 ixgbe.txt doc patch
> and even more importantly the ixgbe FCOE build fix you promised I'd
> have two nights ago :-)
>
> Thanks.
> --
I will get you everything tonight, sorry about not getting the ixgbe
FCOE build fix when I said I would. I was expecting better internet
connectivity than what I had the last couple of days.
--
Cheers,
Jeff
next prev parent reply other threads:[~2010-08-09 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 0:15 [PATCH 1/2] igb.txt: Add igb documentation Jeff Kirsher
2010-08-04 0:16 ` [PATCH 2/2] igbvf.txt: Add igbvf Documentation Jeff Kirsher
2010-08-08 6:01 ` David Miller
2010-08-09 0:25 ` Jeff Kirsher [this message]
2010-08-04 0:39 ` [PATCH 1/2] igb.txt: Add igb documentation Joe Perches
2010-08-04 0:43 ` Jeff Kirsher
2010-08-04 2:34 ` Ben Hutchings
2010-08-05 4:20 ` Jeff Kirsher
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=AANLkTinFNm0B37vtnqcFH_weq3zL9FZiRfE5QVk647PC@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bphilips@novell.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).