netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.arm.linux.org.uk, netdev@vger.kernel.org,
	shemminger@vyatta.com
Subject: Re: Yet more fixes to etherh.c
Date: Sat, 21 Feb 2009 23:44:48 -0800 (PST)	[thread overview]
Message-ID: <20090221.234448.26454123.davem@davemloft.net> (raw)
In-Reply-To: <20090221193633.GD16596@n2100.arm.linux.org.uk>

From: Russell King - ARM Linux <linux@arm.linux.org.uk>
Date: Sat, 21 Feb 2009 19:36:33 +0000

> Further to a71558d, this is round five of fixes to make etherh work
> again. As mainline kernels stand, the fixes in b9a9b4b were the wrong
> approach.
 ...
> Fix up b9a9b4b by making etherh's net_device_ops refer to the internal
> lib8390 functions, and remove the build of the ISA 8390.c driver.
> 
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

Applied to net-next-2.6, thanks Russell.

You mention this as a fix against mainline, but your patch
only applied to net-next-2.6 because the "eth_set_mac_addr"
fix to this driver only exists there.

Let me know if you want me to propagate both changes to net-2.6
and push to Linus.

  reply	other threads:[~2009-02-22  7:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 19:36 Yet more fixes to etherh.c Russell King - ARM Linux
2009-02-22  7:44 ` David Miller [this message]
2009-02-22  8:19   ` Russell King - ARM Linux
2009-02-22  8:24     ` David Miller
2009-02-22  8:45       ` Russell King - ARM Linux
2009-02-22 10:39         ` David Miller
2009-02-22 11:46           ` Russell King - ARM Linux
2009-02-22 12:29             ` David Miller
2009-02-22 12:34               ` Russell King - ARM Linux
2009-02-22 12:36                 ` David Miller
2009-02-22 12:39                   ` Russell King - ARM Linux

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=20090221.234448.26454123.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux@arm.linux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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).