From: Anatolij Gustschin <agust@denx.de>
To: David Miller <davem@davemloft.net>
Cc: wd@denx.de, dzu@denx.de, netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [net-next-2.6 PATCH v2 0/3] Support for MPC512x FEC
Date: Fri, 26 Feb 2010 21:18:08 +0100 [thread overview]
Message-ID: <20100226211808.37931258@wker> (raw)
In-Reply-To: <20100222.034452.193720264.davem@davemloft.net>
Hi David,
On Mon, 22 Feb 2010 03:44:52 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Anatolij Gustschin <agust@denx.de>
> Date: Mon, 22 Feb 2010 12:37:24 +0100
>
> > Could you please comment on this patch series.
>
> It's in the net-next-2.6 tree.
>
> If you need to make any more changes, they need to be relative
> to what went into my tree.
I've pulled your net-next-2.6 tree again and I don't see them
in net-next-2.6 tree. Could you please check it again. Thanks!
Anatolij
WARNING: multiple messages have this Message-ID (diff)
From: Anatolij Gustschin <agust@denx.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
grant.likely@secretlab.ca, dzu@denx.de, wd@denx.de,
jcrigby@gmail.com
Subject: Re: [net-next-2.6 PATCH v2 0/3] Support for MPC512x FEC
Date: Fri, 26 Feb 2010 21:18:08 +0100 [thread overview]
Message-ID: <20100226211808.37931258@wker> (raw)
In-Reply-To: <20100222.034452.193720264.davem@davemloft.net>
Hi David,
On Mon, 22 Feb 2010 03:44:52 -0800 (PST)
David Miller <davem@davemloft.net> wrote:
> From: Anatolij Gustschin <agust@denx.de>
> Date: Mon, 22 Feb 2010 12:37:24 +0100
>
> > Could you please comment on this patch series.
>
> It's in the net-next-2.6 tree.
>
> If you need to make any more changes, they need to be relative
> to what went into my tree.
I've pulled your net-next-2.6 tree again and I don't see them
in net-next-2.6 tree. Could you please check it again. Thanks!
Anatolij
next prev parent reply other threads:[~2010-02-26 20:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 14:55 [net-next-2.6 PATCH v2 0/3] Support for MPC512x FEC Anatolij Gustschin
2010-02-17 14:55 ` Anatolij Gustschin
2010-02-17 14:55 ` [net-next-2.6 PATCH v2 1/3] fs_enet: use dev_xxx instead of printk Anatolij Gustschin
2010-02-17 14:55 ` Anatolij Gustschin
2010-02-17 14:55 ` [net-next-2.6 PATCH v2 2/3] fs_enet: Add support for MPC512x to fs_enet driver Anatolij Gustschin
2010-02-17 14:55 ` Anatolij Gustschin
2010-02-17 14:55 ` [net-next-2.6 PATCH v2 3/3] fs_enet: add FEC TX buffer alignment workaround for MPC5121 Anatolij Gustschin
2010-02-17 14:55 ` Anatolij Gustschin
2010-02-17 15:13 ` Grant Likely
2010-02-17 15:13 ` Grant Likely
2010-02-17 15:17 ` Eric Dumazet
2010-02-17 15:17 ` Eric Dumazet
2010-02-17 21:31 ` Anatolij Gustschin
2010-02-17 21:31 ` Anatolij Gustschin
2010-02-17 22:08 ` [net-next-2.6 PATCH v3 " Anatolij Gustschin
2010-02-17 22:08 ` Anatolij Gustschin
2010-02-17 15:11 ` [net-next-2.6 PATCH v2 2/3] fs_enet: Add support for MPC512x to fs_enet driver Grant Likely
2010-02-17 15:11 ` Grant Likely
2010-02-22 11:37 ` [net-next-2.6 PATCH v2 0/3] Support for MPC512x FEC Anatolij Gustschin
2010-02-22 11:44 ` David Miller
2010-02-26 20:18 ` Anatolij Gustschin [this message]
2010-02-26 20:18 ` Anatolij Gustschin
2010-02-26 20:48 ` David Miller
2010-02-26 20:48 ` 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=20100226211808.37931258@wker \
--to=agust@denx.de \
--cc=davem@davemloft.net \
--cc=dzu@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=wd@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.