linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
	Jeff Garzik <jeff@garzik.org>,
	adrian.bunk@movial.fi
Subject: Re: [RFC] Make board force selection of PHYLIB
Date: Tue, 03 Jun 2008 10:56:59 -0500	[thread overview]
Message-ID: <484569CB.9090104@freescale.com> (raw)
In-Reply-To: <F7DB0156-66BA-4E52-9CA6-F1405E3D31C6@kernel.crashing.org>

Kumar Gala wrote:
> I see.  However, I don't like the idea I have to build in the PHYLIB
> if I don't need it at all.

Understood, but in practice I don't think the 10K or so matters that
much on a typical 85xx board, and if the user really needs to trim
things down, they always have the option of manually ripping the phy
stuff out.

> It seems like the type of breakage you are talking about exists today
> all over the place.

It exists in a few places, but it's not that common, and often it's 
obvious what went wrong when the module won't load because some kernel 
hook didn't get built.  It's not a huge deal, but I'd rather avoid 
introducing another instance.

-Scott

  reply	other threads:[~2008-06-03 15:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 15:58 [PATCH] phylib: Don't allow core of phylib to build as a module Kumar Gala
2008-06-02 16:03 ` Jeff Garzik
2008-06-02 16:25   ` Kumar Gala
2008-06-02 16:32     ` Scott Wood
2008-06-02 16:39     ` Jeff Garzik
2008-06-02 19:19       ` Kumar Gala
2008-06-02 20:29         ` Jeff Garzik
2008-06-02 23:06           ` Kumar Gala
2008-06-02 19:30       ` Kumar Gala
2008-06-02 19:44         ` Andy Fleming
2008-06-02 20:30           ` Jeff Garzik
2008-06-02 23:07             ` Kumar Gala
2008-06-02 23:20               ` Scott Wood
2008-06-03 14:47                 ` [RFC] Make board force selection of PHYLIB Kumar Gala
2008-06-03 15:10                   ` Scott Wood
2008-06-03 15:14                     ` Kumar Gala
2008-06-03 15:18                       ` Scott Wood
2008-06-03 15:31                         ` Kumar Gala
2008-06-03 15:36                           ` Scott Wood
2008-06-03 15:40                             ` Kumar Gala
2008-06-03 15:56                               ` Scott Wood [this message]
2008-06-03 18:07                           ` Andy Fleming
2008-06-03 17:00                   ` Adrian Bunk
2008-06-03 18:11                     ` Andy Fleming
2008-06-03 18:23                     ` Kumar Gala
2008-06-06 15:19                 ` [PATCH] phylib: Don't allow core of phylib to build as a module Grant Likely
2008-06-02 16:54     ` Adrian Bunk
2008-06-02 19:24       ` Kumar Gala
2008-06-06 15:40         ` [PATCH] [POWERPC] 85xx: MPC85xx MDS - Unconditionally select PHYLIB for board fixups Kumar Gala
2008-06-06 17:48           ` 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=484569CB.9090104@freescale.com \
    --to=scottwood@freescale.com \
    --cc=adrian.bunk@movial.fi \
    --cc=galak@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --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).