From: ian@opensource.wolfsonmicro.com (Ian Lartey)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Fixing ethernet driver compilation error for i.MX31 ADS board
Date: Thu, 30 Sep 2010 15:49:31 +0100 [thread overview]
Message-ID: <1285858171.1864.10033.camel@Tapajos> (raw)
In-Reply-To: <20100930132914.GP29811@pengutronix.de>
On Thu, 2010-09-30 at 15:29 +0200, Uwe Kleine-K?nig wrote:
> Hi Ian,
>
> On Thu, Sep 30, 2010 at 01:57:24PM +0100, Ian Lartey wrote:
> > This is only a partial revert of "ARM: mx3/mx31ads: fold board header in its only user"
> > [commit ccfa7c269843001077df02d98918c6c9bde91395)]
> >
> > As some of the the board defines are also used in the cs89x0 ethernet driver by the i.MX31 ADS.
> Can you please line break the commit log. AFAIK up to 76 chars are
> usual for the kernel.
Ah, sorry about that, I'll reformat the lines.
>
> Hmmm, I took a look into drivers/net/cs89x0.c. This driver definitly
> needs a cleanup, e.g. should start to provide a platform driver.
> Maybe it can even be merged with drivers/net/mac89x0.c?
>
> I think the best for know would be the following:
>
> - reintroduce mach/board-mx31ads.h but only defining the symbols used
> by cs89x0 together with a comment saying that the constants are
> needed for the cs89x0 ethernet driver.
This time round I have just added the defines needed for the cs89x0
to the ones that were moved back into mach-mx31ads.h from
mach-mx31ads.c . I think this is what you mean, yes ?
>
> - In a second patch add CS89x0 to mx31_defconfig
Will do.
>
> Best regards
> Uwe
>
Regards,
Ian.
next prev parent reply other threads:[~2010-09-30 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 12:57 [PATCH] Fixing ethernet driver compilation error for i.MX31 ADS board Ian Lartey
2010-09-30 13:29 ` Uwe Kleine-König
2010-09-30 14:49 ` Ian Lartey [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-14 11:07 Ian Lartey
2010-09-23 15:32 Ian Lartey
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=1285858171.1864.10033.camel@Tapajos \
--to=ian@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).