All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: David Miller <davem@davemloft.net>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next v5 8/8] i40e: include i40e in kernel proper
Date: Fri, 6 Sep 2013 11:30:30 -0700	[thread overview]
Message-ID: <20130906113030.000034a7@unknown> (raw)
In-Reply-To: <20130906.140141.2245821068783126791.davem@davemloft.net>

On Fri, 6 Sep 2013 14:01:41 -0400
David Miller <davem@davemloft.net> wrote:
> Please rename this Kbuild file to the normal Makefile instead of
> trying to be different from every single other driver in the
> networking for the sake of an issue that is your, and your problem
> alone.

Thanks Dave, will do, I'm preparing the patch now.

> You guys should really be grateful that anyone at all not being paid
> to do so is reviewing such a huge body of code for you, rather than
> complaining that all the issues weren't discovered the first time
> this series was posted.

We *are* really grateful for all the effort of any/all reviewers.  I
would like to personally thank you Dave, Joe Perches, Ben Hutchings,
and Stephen Hemminger for the non-trival amount of time spent on
reviewing this patch set.

------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

      reply	other threads:[~2013-09-06 18:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  6:01 [net-next v5 0/8][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 1/8] i40e: main driver core Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 2/8] i40e: transmit, receive, and NAPI Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 3/8] i40e: driver ethtool core Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 4/8] i40e: driver core headers Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 5/8] i40e: implement virtual device interface Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 6/8] i40e: init code and hardware support Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 7/8] i40e: debugfs interface Jeff Kirsher
2013-09-06  6:01 ` [net-next v5 8/8] i40e: include i40e in kernel proper Jeff Kirsher
2013-09-06  6:14   ` Stephen Hemminger
2013-09-06  6:28     ` [E1000-devel] " Brandeburg, Jesse
2013-09-06  6:47       ` Joe Perches
2013-09-06 17:28         ` Williams, Mitch A
2013-09-06 17:39           ` Stephen Hemminger
2013-09-06 18:20           ` Joe Perches
2013-09-06 18:23             ` David Miller
2013-09-06 18:01       ` David Miller
2013-09-06 18:30         ` Jesse Brandeburg [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=20130906113030.000034a7@unknown \
    --to=jesse.brandeburg@intel.com \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=gospo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.