From: Haiying Wang <Haiying.Wang@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] net/phy/marvell: update m88e1111 support for SGMII mode
Date: Tue, 02 Jun 2009 10:03:59 -0400 [thread overview]
Message-ID: <1243951440.2927.7.camel@r54964-12.am.freescale.net> (raw)
In-Reply-To: <20090601.025151.146454973.davem@davemloft.net>
On Mon, 2009-06-01 at 02:51 -0700, David Miller wrote:
> Patch 3 of this series doesn't apply cleanly to net-next-2.6
> so I'm dropping the entire patch set.
> Also, in patch 3 you put your signoff in the Subject line.
>
> Please fix all of this up and resubmit your patch series.
I only verified the first three patches could be applied to your
net-2.6, did not verify whether they could be applied for net-next-2.6.
Sorry.
I've fixed the patch3 against net-next-2.6 now, and will resubmit the
patches.
But the patch4 can not be applied to your net-next-2.6 since there is
not 8569mds support in that tree. Hope Kumar can pick up the patch 4.
Thanks.
Haiying
next prev parent reply other threads:[~2009-06-02 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 13:20 [PATCH 1/4] net/phy/marvell: update m88e1111 support for SGMII mode Haiying Wang
2009-05-28 13:20 ` [PATCH 2/4] fsl_pq_mido: Set the first UCC as the mii management interface master Haiying Wang
2009-05-28 13:20 ` [PATCH 3/4] net/ucc_geth: Add SGMII support for UEC GETH driver Signed-off-by: Haiying Wang <Haiying.Wang@freescale.com> Haiying Wang
2009-05-28 13:20 ` [PATCH 4/4] MPC85xx: Add UCC6 and UCC8 nodes in SGMII mode for MPC8569MDS Haiying Wang
2009-06-01 9:51 ` [PATCH 1/4] net/phy/marvell: update m88e1111 support for SGMII mode David Miller
2009-06-02 14:03 ` Haiying Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-02 14:04 Haiying Wang
2009-06-03 10:50 ` David Miller
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=1243951440.2927.7.camel@r54964-12.am.freescale.net \
--to=haiying.wang@freescale.com \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
/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).