From: Grant Likely <grant.likely@secretlab.ca>
To: David Miller <davem@davemloft.net>
Cc: Joakim.Tjernlund@transmode.se, netdev@vger.kernel.org,
linuxppc-dev@ozlabs.org, afleming@freescale.com, olof@lixom.net
Subject: Re: [PATCH 00/14] Add common OF device tree support for MDIO busses
Date: Tue, 31 Mar 2009 16:19:42 -0600 [thread overview]
Message-ID: <fa686aa40903311519m3108c697v52180d192975a3b1@mail.gmail.com> (raw)
In-Reply-To: <20090331.145738.36845509.davem@davemloft.net>
On Tue, Mar 31, 2009 at 3:57 PM, David Miller <davem@davemloft.net> wrote:
> From: Grant Likely <grant.likely@secretlab.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 =A06) 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. =A0There 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.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-03-31 22:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 8:26 [PATCH 00/14] Add common OF device tree support for MDIO busses Grant Likely
2009-03-31 8:26 ` [PATCH 01/14] of: add of_parse_phandle() helper for parsing phandle properties Grant Likely
2009-03-31 8:26 ` [PATCH 02/14] net/fec_mpc52xx: Migrate to net_device_ops Grant Likely
2009-03-31 8:26 ` [PATCH 03/14] net/fec_mpc52xx: Don't dereference phy_device if it is NULL Grant Likely
2009-03-31 8:27 ` [PATCH 04/14] phylib: rework to prepare for OF registration of PHYs Grant Likely
2009-03-31 8:27 ` [PATCH 05/14] phylib: add *_direct() variants of phy_connect and phy_attach functions Grant Likely
2009-04-15 21:10 ` Andy Fleming
2009-04-18 6:08 ` Grant Likely
2009-04-18 6:18 ` Grant Likely
2009-03-31 8:27 ` [PATCH 06/14] openfirmware: Add OF phylib support code Grant Likely
2009-03-31 8:27 ` [PATCH 07/14] net: Rework mpc5200 fec driver to use of_mdio infrastructure Grant Likely
2009-03-31 8:27 ` [PATCH 08/14] net: rework fsl_pq_mdio " Grant Likely
2009-03-31 8:27 ` [PATCH 09/14] net: Rework gianfar " Grant Likely
2009-04-15 23:01 ` Andy Fleming
2009-04-18 6:34 ` Grant Likely
2009-03-31 8:27 ` [PATCH 10/14] net: Rework ucc_geth " Grant Likely
2009-03-31 8:27 ` [PATCH 11/14] net: Rework pasemi_mac " Grant Likely
2009-03-31 8:27 ` [PATCH 12/14] powerpc/82xx: Rework Embedded Planet ep8248e platform to use of_mdio Grant Likely
2009-03-31 8:27 ` [PATCH 13/14] net: Rework fs_enet driver to use of_mdio infrastructure Grant Likely
2009-03-31 8:27 ` [PATCH 14/14] net: add Xilinx ll_temac device driver Grant Likely
2009-03-31 21:57 ` [PATCH 00/14] Add common OF device tree support for MDIO busses David Miller
2009-03-31 22:19 ` Grant Likely [this message]
2009-03-31 22:22 ` David Miller
2009-04-01 1:45 ` Grant Likely
2009-04-01 3:38 ` David Miller
2009-04-01 4:56 ` Grant Likely
2009-04-01 5:16 ` David Miller
2009-04-01 5:21 ` Grant Likely
2009-04-15 23:06 ` Andy Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa686aa40903311519m3108c697v52180d192975a3b1@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Joakim.Tjernlund@transmode.se \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).