All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Scott Wood <scottwood@freescale.com>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/9] fs_enet: Whitespace cleanup.
Date: Sat, 29 Sep 2007 01:21:06 -0400	[thread overview]
Message-ID: <46FDE0C2.5010207@pobox.com> (raw)
In-Reply-To: <20070920220116.GA28784@loki.buserror.net>

Scott Wood wrote:
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
>  drivers/net/fs_enet/fs_enet-main.c |   85 ++++++++++++++++-------------------
>  drivers/net/fs_enet/fs_enet.h      |    4 +-
>  drivers/net/fs_enet/mac-fcc.c      |    1 -
>  drivers/net/fs_enet/mii-bitbang.c  |    3 -
>  drivers/net/fs_enet/mii-fec.c      |    1 -
>  5 files changed, 41 insertions(+), 53 deletions(-)

ACK patches 1-2, 4-9

This patch doesn't apply cleanly to netdev-2.6.git#upstream (nor 
net-2.6.24.git), so this and the rest of the patch series failed to apply.

Please resend series on top of netdev-2.6.git#upstream or net-2.6.24.git.

  reply	other threads:[~2007-09-29  5:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20 22:00 [PATCH 0/9] fs enet and mdio bitbang patches Scott Wood
2007-09-20 22:01 ` [PATCH 1/9] fs_enet: Whitespace cleanup Scott Wood
2007-09-29  5:21   ` Jeff Garzik [this message]
2007-09-20 22:01 ` [PATCH 2/9] fs_enet: Include linux/string.h from linux/fs_enet_pd.h Scott Wood
2007-09-20 22:01 ` [PATCH 3/9] fs_enet: Don't share the interrupt Scott Wood
2007-09-29  5:18   ` Jeff Garzik
2007-09-20 22:01 ` [PATCH 4/9] fs_enet: mac-fcc: Eliminate __fcc-* macros Scott Wood
2007-09-20 22:01 ` [PATCH 5/9] fs_enet: Align receive buffers Scott Wood
2007-09-20 22:01 ` [PATCH 6/9] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set Scott Wood
2007-09-21  0:08   ` Stephen Rothwell
2007-09-21  0:08     ` Stephen Rothwell
2007-09-21  0:44     ` Scott Wood
2007-09-21  0:44       ` Scott Wood
2007-10-02  7:10   ` Esben Haabendal
2008-02-15 12:50   ` Laurent Pinchart
2008-02-15 12:50     ` Laurent Pinchart
2008-02-15 15:38     ` Sergej Stepanov
2008-02-15 15:38       ` Sergej Stepanov
2008-03-07 15:23       ` Laurent Pinchart
2008-03-07 15:23         ` Laurent Pinchart
2008-03-07 16:37         ` Scott Wood
2008-03-07 16:37           ` Scott Wood
2008-03-10  7:50           ` Sergej Stepanov
2008-03-10  7:50             ` Sergej Stepanov
2008-03-10 11:05             ` Laurent Pinchart
2008-03-10 13:17               ` Sergej Stepanov
2008-03-10 15:02               ` [PATCH v3] using mii-bitbang on different processor ports - update the booting-without-of.txt-file Sergej Stepanov
2007-09-20 22:01 ` [PATCH 7/9] Generic bitbanged MDIO library Scott Wood
2007-10-18 19:20   ` [PATCH] phy/bitbang: missing MODULE_LICENSE Randy Dunlap
2007-10-18 19:20     ` Randy Dunlap
2007-10-20  3:03     ` Jeff Garzik
2007-10-20  3:03       ` Jeff Garzik
2007-09-20 22:01 ` [PATCH 8/9] fs_enet: Convert mii-bitbang to use the generic bitbang MDIO code Scott Wood
2007-09-20 22:01 ` [PATCH 9/9] fs_enet: sparse fixes Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2007-10-01 19:20 [PATCH 1/9] fs_enet: Whitespace cleanup Scott Wood
2007-10-02 17:31 ` Jeff Garzik

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=46FDE0C2.5010207@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=scottwood@freescale.com \
    /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.