From: Jeff Garzik <jgarzik@pobox.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org, vbordug@ru.mvista.com, netdev@vger.kernel.org
Subject: Re: [PATCH] fs_enet: Remove unused fields in the fs_mii_bb_platform_info structure.
Date: Tue, 22 Jul 2008 16:09:50 -0400 [thread overview]
Message-ID: <48863E8E.4080308@pobox.com> (raw)
In-Reply-To: <200807221743.47807.laurentp@cse-semaphore.com>
Laurent Pinchart wrote:
> The mdio_port, mdio_bit, mdc_port and mdc_bit fields in the
> fs_mii_bb_platform_info structure are left-overs from the move to the Phy
> Abstraction Layer subsystem. They are not used anymore and can be safely
> removed.
>
> Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> ---
> include/linux/fs_enet_pd.h | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/fs_enet_pd.h b/include/linux/fs_enet_pd.h
> index 9bc045b..decc4b5 100644
> --- a/include/linux/fs_enet_pd.h
> +++ b/include/linux/fs_enet_pd.h
> @@ -103,10 +103,6 @@ struct fs_mii_bb_platform_info {
> struct fs_mii_bit mdio_dir;
> struct fs_mii_bit mdio_dat;
> struct fs_mii_bit mdc_dat;
> - int mdio_port; /* port & bit for MDIO */
> - int mdio_bit;
> - int mdc_port; /* port & bit for MDC */
> - int mdc_bit;
> int delay; /* delay in us */
> int irq[32]; /* irqs per phy's */
applied
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@pobox.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org, vbordug@ru.mvista.com
Subject: Re: [PATCH] fs_enet: Remove unused fields in the fs_mii_bb_platform_info structure.
Date: Tue, 22 Jul 2008 16:09:50 -0400 [thread overview]
Message-ID: <48863E8E.4080308@pobox.com> (raw)
In-Reply-To: <200807221743.47807.laurentp@cse-semaphore.com>
Laurent Pinchart wrote:
> The mdio_port, mdio_bit, mdc_port and mdc_bit fields in the
> fs_mii_bb_platform_info structure are left-overs from the move to the Phy
> Abstraction Layer subsystem. They are not used anymore and can be safely
> removed.
>
> Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> ---
> include/linux/fs_enet_pd.h | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/fs_enet_pd.h b/include/linux/fs_enet_pd.h
> index 9bc045b..decc4b5 100644
> --- a/include/linux/fs_enet_pd.h
> +++ b/include/linux/fs_enet_pd.h
> @@ -103,10 +103,6 @@ struct fs_mii_bb_platform_info {
> struct fs_mii_bit mdio_dir;
> struct fs_mii_bit mdio_dat;
> struct fs_mii_bit mdc_dat;
> - int mdio_port; /* port & bit for MDIO */
> - int mdio_bit;
> - int mdc_port; /* port & bit for MDC */
> - int mdc_bit;
> int delay; /* delay in us */
> int irq[32]; /* irqs per phy's */
applied
next prev parent reply other threads:[~2008-07-22 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 15:43 [PATCH] fs_enet: Remove unused fields in the fs_mii_bb_platform_info structure Laurent Pinchart
2008-07-22 15:43 ` Laurent Pinchart
2008-07-22 20:09 ` Jeff Garzik [this message]
2008-07-22 20:09 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2008-02-15 13:27 Laurent Pinchart
2008-02-28 12:49 ` Laurent Pinchart
2008-02-28 18:50 ` Scott Wood
2008-03-07 15:00 ` Kumar Gala
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=48863E8E.4080308@pobox.com \
--to=jgarzik@pobox.com \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=vbordug@ru.mvista.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.