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:	Tue, 10 Feb 2009 11:48:55 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	David Miller <davem@...emloft.net>
Cc:	tony@...mide.com, linux-omap@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Remaining bits for basic support of LDP

On Mon, Feb 02, 2009 at 10:29:09PM +0000, Russell King - ARM Linux wrote:
> On Mon, Feb 02, 2009 at 01:45:30PM -0800, David Miller wrote:
> > From: Russell King - ARM Linux <linux@....linux.org.uk>
> > Date: Mon, 2 Feb 2009 21:39:53 +0000
> > 
> > > The patch to fix these issues would seem to be relatively small (12
> > > lines in the smc911x and one line change in board-ldp.c) - is it
> > > something we want done for -rc4 or do we scrap the ethernet support 
> > > on the LDP until the SMSC driver has been merged ?
> > > 
> > > Obviously, having working ethernet would be helpful, and since it was
> > > half heartedly merged when the initial OMAP3 stuff went upstream we
> > > should do something with it one way or another.
> > 
> > Well, the SMSC driver is there already in the tree.
> >
> > The only thing not currently being scheduled to hit
> > 2.6.29-rcX are the recent changes to support platform
> > specified interrupt flags and all of that stuff.
> > 
> > If you want, we can look into pushing that work into
> > 2.6.29-rcX
> 
> Hmm.  Since we should assume that the other smc911x using platforms work
> as-is, merging Steve's first four and the LDP patch seems to be a sane
> idea.  We can queue the remainder for when bugs are reported or the
> next merge window, whichever comes earlier.

So, what's happening on this?
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ