netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 01/26] bmac: convert to net_device_ops
Date: Thu, 16 Apr 2009 02:24:57 -0700 (PDT)	[thread overview]
Message-ID: <20090416.022457.38272224.davem@davemloft.net> (raw)
In-Reply-To: <1239835980-22502-1-git-send-email-a.beregalov@gmail.com>

From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Thu, 16 Apr 2009 02:52:35 +0400

> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>

Since this is becomming more than I'm comfortable trying to
get into net-2.6 I'm merging these 26 patches into net-next-2.6
instead.

Thanks!

      parent reply	other threads:[~2009-04-16  9:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 22:52 [PATCH 01/26] bmac: convert to net_device_ops Alexander Beregalov
2009-04-15 22:52 ` [PATCH 02/26] cpmac: " Alexander Beregalov
2009-04-15 22:52   ` [PATCH 03/26] dm9000: " Alexander Beregalov
2009-04-15 22:52     ` [PATCH 04/26] hplance: " Alexander Beregalov
2009-04-15 22:52       ` [PATCH 05/26] ibmveth: " Alexander Beregalov
2009-04-15 22:52         ` [PATCH 06/26] irda/au1k_ir: " Alexander Beregalov
2009-04-15 22:52           ` [PATCH 07/26] irda/pxaficp_ir: " Alexander Beregalov
2009-04-15 22:52             ` [PATCH 08/26] irda/sa1100_ir: " Alexander Beregalov
2009-04-15 22:52               ` [PATCH 09/26] iseries_veth: " Alexander Beregalov
2009-04-15 22:52                 ` [PATCH 10/26] ixp2000/ixpdev: " Alexander Beregalov
2009-04-15 22:52                   ` [PATCH 11/26] jazzsonic: " Alexander Beregalov
2009-04-15 22:52                     ` [PATCH 12/26] korina: " Alexander Beregalov
2009-04-15 22:52                       ` [PATCH 13/26] lib82596: " Alexander Beregalov
2009-04-15 22:52                         ` [PATCH 14/26] mace: " Alexander Beregalov
2009-04-15 22:52                           ` [PATCH 15/26] macmace: " Alexander Beregalov
2009-04-15 22:52                             ` [PATCH 16/26] meth: " Alexander Beregalov
2009-04-15 22:52                               ` [PATCH 17/26] mipsnet: " Alexander Beregalov
2009-04-15 22:52                                 ` [PATCH 18/26] mvme147: " Alexander Beregalov
2009-04-15 22:52                                   ` [PATCH 19/26] netx-eth: " Alexander Beregalov
2009-04-15 22:52                                     ` [PATCH 20/26] pasemi_mac: " Alexander Beregalov
2009-04-15 22:52                                       ` [PATCH 21/26] pci-skeleton: " Alexander Beregalov
2009-04-15 22:52                                         ` [PATCH 22/26] rionet: " Alexander Beregalov
2009-04-15 22:52                                           ` [PATCH 23/26] sb1250-mac: " Alexander Beregalov
2009-04-15 22:52                                             ` [PATCH 24/26] sgiseeq: " Alexander Beregalov
2009-04-15 22:52                                               ` [PATCH 25/26] smc911x: " Alexander Beregalov
2009-04-15 22:53                                                 ` [PATCH 26/26] sun3lance: " Alexander Beregalov
2009-04-16  9:24 ` David Miller [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=20090416.022457.38272224.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=a.beregalov@gmail.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;
as well as URLs for NNTP newsgroup(s).