linux-kernel - Re: [GIT]: Networking

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20080508.212452.236396317.davem@davemloft.net>
Date:	Thu, 08 May 2008 21:24:52 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
Cc:	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT]: Networking

From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Thu, 8 May 2008 18:51:08 -0700 (PDT)

> David, you need to stop sending patches like this after -rc1.
> 
> This is too big. I'm taking it, but there's something wrong in this. Your 
> merges after -rc1 have generally been way too large, and I need to shut 
> you down if this gets to be a big pattern.
> 
> It's one thing taking a totally new driver (that couldn't have worked 
> before and cannot be a regression) or adding new PCI ID's. It's a totally 
> different thing to take 800 lines of code to an old driver that people 
> depend on. These things need to happen during the merge window, and just 
> because they are drivers doesn't mean that they can just do anythign they 
> want.

I saw that e1000e commit from Jeff's tree and was about to push
back on him.  But I decided not to.

I will next time if it's such a big deal, but frankly I thought this
one was OK.  It's stupid to make people wait until 2.6.27 to be able
to use the e1000e cards with the new PHY type.  It causes some hw bug
workaround to need to be added to the e1000e driver, and that's where
the bulk of that 800 line change is from.

Distributions are going to add that e1000e PHY support patch anyways,
regardless of what we do, and isn't that one of the reasons we were
talking about more aggressively merging new drivers?

Who the heck are we kidding if we don't put changes like that into the
tree when pretty much every distribution will?  Yes, even after rc1.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/