From: Tom Rini <trini@kernel.crashing.org>
To: Bastos Fernandez Alexandre <ALEBAS@televes.com>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Leo Li <leoli@freescale.com>,
"Balasaygun, Oray (Oray)" <oray@lucent.com>
Subject: Re: [PATCH] ppc32: Update 8260_io/fcc_enet.c to function again
Date: Wed, 16 Mar 2005 07:54:36 -0700 [thread overview]
Message-ID: <20050316145435.GY8345@smtp.west.cox.net> (raw)
In-Reply-To: <51DB8827D393D411BB69003048003F46FDCFDE@tvesntr>
On Wed, Mar 16, 2005 at 09:00:51AM +0100, Bastos Fernandez Alexandre wrote:
> What can we do?
> Has Oray's patch been commited? Or not yet?
>
> I suggest commiting all the changes in this driver from linuxppc tree to
> linux tree
> and after this ask Oray to test again the driver and submmit new patch.
> Or ask Oray to submmit changes patch to linuxppc
So, Oray's patch has two things in it, it looks like. The basic
re-porting to 2.6 APIs, and support for the EON8260. The EON8260
changes should be a bit cleaner to redo after the patch I sent goes in
as some of the other cleanups will help there. But I'd also like to see
the full EON8260 changes :) The 2.6 API parts look close, but I went
and expanded a good bit more on them.
I'd like to drop Oray's patch for now, and have the EON8260 work be
resubmitted to lkml/linuxppc-embedded@ozlabs.org.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-03-16 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 8:00 Bastos Fernandez Alexandre
2005-03-16 14:54 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-16 15:04 Balasaygun, Oray (Oray)
2005-03-15 18:25 Tom Rini
2005-03-16 6:31 ` Andrew Morton
2005-03-16 18:43 ` 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=20050316145435.GY8345@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=ALEBAS@televes.com \
--cc=akpm@osdl.org \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oray@lucent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®