netdev - Re: [PATCH v2 0/2] net: support for NS8390 based ethernet on ColdFire CPU boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Jul 2012 07:55:31 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	gerg@...pgear.com
Cc:	netdev@...r.kernel.org, linux-m68k@...r.kernel.org
Subject: Re: [PATCH v2 0/2] net: support for NS8390 based ethernet on
 ColdFire CPU boards

From: <gerg@...pgear.com>
Date: Thu, 5 Jul 2012 09:49:58 +1000

> 
> This is version 2 of patches that add platform support for using the NS8390
> based ethernet ports used on some ColdFire CPU boards. This version
> incorporates only minor changes from the first.
> 
> Patches to use these NS8390 devices on ColdFire boards have existed
> out-of-tree for years. Some of the base IO definitions (those in
> arch/m68k/include/asm/mcfne.h) have been in mainline, but unused for most
> of that time.
> 
> The first patch just neatens up mcfne.h (moving it to mcf8390.h). The
> second patch is the platform driver. The first patch would normaly just
> go through the m68knommu git tree, but I figured keeping these together made
> more sense.

Applied, thanks.

Can you explain why we've had this completely unused header
file mcfne.h in the tree?  Was it used by some external driver
sources that were never merged?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html