netdev - Re: [PATCH] dnet: Dave DNET ethernet controller driver

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]

Message-ID: <20090312180638.GG14491@shareable.org>
Date:	Thu, 12 Mar 2009 18:06:38 +0000
From:	Jamie Lokier <jamie@...reable.org>
To:	Christer Weinigel <christer@...nigel.se>
Cc:	David Miller <davem@...emloft.net>, nhorman@...driver.com,
	shemminger@...tta.com, s.hauer@...gutronix.de, yanok@...raft.com,
	linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org,
	wd@...x.de, dzu@...x.de
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver

Christer Weinigel wrote:
> David Miller wrote:
> > You can start with the debian installer, that's probably the
> > easiest to hack on and extend.
> > 
> > Or you can just continue to list excuses, that might be easier.
> 
> Or I can keep patching the drivers, that's even easier.  No it's not 
> something I expect to see in the official kernel, but who cares, I 
> always have loads of debug patches that won't get into the official 
> kernel either.  Keep the status quo.

Yes.  Patching your own initrd or your own modified Debian initrd is
_also_ not in the official trees, so I can't see any reason why
anybody would follow Dave's suggestion.  Much more work, different
private tree, same behaviour, probably more bloated, probably Debian's
initrd doesn't work on nommu anyway.

However there was some attempt to get a reference initrd build into
the kernel.  Did that go anywhere?  It would actually be good to use
that if it exists.

-- Jamie
--
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