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, 31 Mar 2009 16:19:42 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, linuxppc-dev@...abs.org, olof@...om.net,
	afleming@...escale.com, galak@...nel.crashing.org,
	avorontsov@...mvista.com, Joakim.Tjernlund@...nsmode.se
Subject: Re: [PATCH 00/14] Add common OF device tree support for MDIO busses

On Tue, Mar 31, 2009 at 3:57 PM, David Miller <davem@...emloft.net> wrote:
> From: Grant Likely <grant.likely@...retlab.ca>
> Date: Tue, 31 Mar 2009 02:26:43 -0600
>
>> David, as I mentioned below, I'd really like to get the core changes
>> (1, 4, 5  6) merged into 2.6.30 (assuming Andy confirms they are okay).
>
> No, sorry.
>
> We could have worked out the interdependencies before the merge window
> openned up.  There is no reason this could not have sat in at least
> somebody's tree before the merge window started.

It's been out there on the list since before the merge window, getting
tested by more than just me.  This is not series which has simply
dropped out of thin air.  I've been working hard to address issues
reported by others (Thanks Olof!) and to keep it building and applying
cleanly to the top of tree.

> It therefore didn't get any -next exposure, so it's unreasonable to
> merge this stuff now.

Since when has sitting in a -next tree been a requirement for merging
when the series has been kept up to date and tested?  I purposefully
kept it out of -next to ensure that when it was applied for real to a
-next tree it would be as complete, bug free, and bisectable as
possible since once it hits a signed-off -next branch the individual
commit cannot be modified.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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