netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	Edward Hsu <edward_hsu@realtek.com.tw>
Subject: Re: [PATCH 0/2] Pull request for 'r8169-next' branch
Date: Fri, 04 Jul 2008 08:36:53 -0400	[thread overview]
Message-ID: <486E1965.30909@garzik.org> (raw)
In-Reply-To: <20080629131739.GA31201@electric-eye.fr.zoreil.com>

Francois Romieu wrote:
> Please pull from branch 'r8169-next' in repository
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/romieu/netdev-2.6.git r8169-next
> 
> to get the changes below.
> 
> Distance from 'davem-next' (be0976be9148f31ee0d1997354c3e30ff8d07587)
> ---------------------------------------------------------------------
> 
> 865c652d6be9929927cabdc54b137b7541eb6612
> 1087f4f4af302e6e2fa40dd741f306444d90bece
> 
> Diffstat
> --------
> 
>  drivers/net/Kconfig |   16 +-----
>  drivers/net/r8169.c |  145 +++++++++++++++-----------------------------------
>  2 files changed, 45 insertions(+), 116 deletions(-)
> 
> Shortlog
> --------
> 
> Francois Romieu (2):
>       r8169: multicast register update (sync with Realtek's 8.004.00 8168 driver)
>       r8169: remove non-napi code

pulled



      parent reply	other threads:[~2008-07-04 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29 13:17 [PATCH 0/2] Pull request for 'r8169-next' branch Francois Romieu
2008-06-29 13:18 ` [PATCH 1/2] r8169: multicast register update (sync with Realtek's 8.004.00 8168 driver) Francois Romieu
2008-06-30 10:02   ` Glen Gray
2008-06-30 21:17     ` Francois Romieu
2008-07-01  9:15       ` Glen Gray
2008-06-29 13:20 ` [PATCH 2/2] r8169: remove non-napi code Francois Romieu
2008-07-04 12:36 ` Jeff Garzik [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=486E1965.30909@garzik.org \
    --to=jeff@garzik.org \
    --cc=davem@davemloft.net \
    --cc=edward_hsu@realtek.com.tw \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.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).