From: olof@lixom•net (Olof Johansson)
To: Dale Farnsworth <dale@farnsworth•org>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] powerpc: Add Marvell mv64x60 udbg putc/getc functions
Date: Wed, 23 May 2007 20:53:05 -0500 [thread overview]
Message-ID: <20070524015305.GA5755@lixom.net> (raw)
In-Reply-To: <20070524000237.GB11608@xyzzy.farnsworth.org>
On Wed, May 23, 2007 at 05:02:37PM -0700, Dale Farnsworth wrote:
> On Wed, May 23, 2007 at 06:27:45PM -0500, Olof Johansson wrote:
> > On Wed, May 23, 2007 at 03:05:18PM -0700, Dale Farnsworth wrote:
> >
> > > arch/powerpc/platforms/embedded6xx/prpmc2800.c | 1
> > > arch/powerpc/sysdev/Makefile | 3
> > > arch/powerpc/sysdev/mv64x60.h | 1
> > > arch/powerpc/sysdev/mv64x60_udbg.c | 152 +++++++++++++++
> > > 4 files changed, 156 insertions(+), 1 deletion(-)
> >
> > Is there a reason you're not putting it with the other udbg code, and
> > not naming it with the same scheme (kernel/udbg_<xxx>)?
>
> Not really. I just put it with some other mv64x60 code.
>
> > Or maybe we should just move the udbg_16550 code to sysdev instead, it's
> > roots are from ppc64 where we didn't have sysdev.
>
> Shrug.
Yeah, shrug. :) This shouldn't stop this from going in, it just made
me realize that we should probably move the 16550 stuff.
-Olof
next prev parent reply other threads:[~2007-05-24 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 22:05 [PATCH] powerpc: Add Marvell mv64x60 udbg putc/getc functions Dale Farnsworth
2007-05-23 23:27 ` Olof Johansson
2007-05-24 0:02 ` Dale Farnsworth
2007-05-24 1:53 ` Olof Johansson [this message]
2007-06-06 6:06 ` Paul Mackerras
2007-06-06 17:29 ` Dale Farnsworth
2007-06-08 2:15 ` Michael Ellerman
2007-06-08 17:20 ` Dale Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2007-05-14 19:52 Dale Farnsworth
2007-05-15 18:55 ` Mark A. Greer
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=20070524015305.GA5755@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=dale@farnsworth$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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