From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: "Dan Malek" <dan@embeddededge.com>,
"Jean-Denis Boyer" <jdboyer@m5t.com>,
"Steffen Rumler" <Steffen.Rumler@siemens.com>,
"linuxppc" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problem of concurrency in arch/ppc/8260_io/uart.c
Date: Fri, 26 Sep 2003 20:34:28 +0200 [thread overview]
Message-ID: <003d01c3845c$d212c910$020120b0@jockeXP> (raw)
In-Reply-To: 20030926163102.GB904@ip68-0-152-218.tc.ph.cox.net
> On Wed, Sep 17, 2003 at 06:33:06PM +0200, Joakim Tjernlund wrote:
>
> >
> > > > Whatever the boot rom initializes.
> > >
> > > OK, then I will assume TX buffer length of 1, until serial_console_setup has run and
> > > initialize it to 4.
> > >
> > > Jocke
> >
> > Here we go again. This patch adds the above. I am unable to break it, please try to :)
>
> What tree is this against, specifically? It doesn't apply cleanly to
> 2_4_devel, 2_4 or kernel.org.
It is against 2_4_devel minus the recent white space cleanup, as far as I can tell.
I should apply if you ignore white space differences. Can you try?
>
> I've just moved a bunch of Dan's old changes from _devel out to a tree
> Marcelo pulls from as well as linuxppc-2.4, so can you please re-do this
> patch against that tree? Thanks.
I can only run & patch against 2_4_devel since I have made custom changes to my tree.
My tree is a bit behind right now, sorry.
> --
> Tom Rini
> http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-26 18:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 16:26 Problem of concurrency in arch/ppc/8260_io/uart.c Jean-Denis Boyer
2003-09-15 18:37 ` Joakim Tjernlund
2003-09-15 18:53 ` Dan Malek
2003-09-15 20:02 ` Joakim Tjernlund
2003-09-16 12:25 ` Joakim Tjernlund
2003-09-17 9:33 ` Joakim Tjernlund
2003-09-17 13:38 ` Joakim Tjernlund
2003-09-17 14:58 ` Dan Malek
2003-09-17 15:22 ` Joakim Tjernlund
2003-09-17 16:33 ` Joakim Tjernlund
2003-09-23 8:28 ` Joakim Tjernlund
2003-09-26 16:31 ` Tom Rini
2003-09-26 18:34 ` Joakim Tjernlund [this message]
2003-09-26 18:38 ` Tom Rini
2003-09-26 21:24 ` Tom Rini
2003-09-26 22:20 ` Dan Malek
2003-09-26 22:39 ` Joakim Tjernlund
2003-09-26 23:12 ` Dan Malek
2003-09-27 8:07 ` Joakim Tjernlund
2003-09-27 13:43 ` Joakim Tjernlund
2003-09-29 15:33 ` Tom Rini
2003-09-30 15:28 ` Dan Malek
2003-10-01 14:26 ` Kumar Gala
2003-10-01 14:32 ` Tom Rini
2003-10-01 14:48 ` Gary Thomas
2003-10-01 21:20 ` Joakim Tjernlund
2003-10-01 21:32 ` Tom Rini
2003-10-01 21:51 ` Joakim Tjernlund
2003-10-01 22:00 ` Tom Rini
2003-10-01 22:17 ` Joakim Tjernlund
2003-10-01 22:31 ` Tom Rini
2003-10-01 23:23 ` Robin Gilks
2003-10-01 23:51 ` Tom Rini
2003-10-02 0:47 ` Wolfgang Denk
2003-10-02 6:03 ` Dan Kegel
2003-10-02 19:15 ` Tom Rini
[not found] <3F8E8817.5ACD7ACB@siemens.com>
2003-10-16 14:11 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2003-09-15 10:18 Steffen Rumler
2003-09-15 13:30 ` Joakim Tjernlund
2003-03-07 15:18 Jean-Denis Boyer
2003-03-07 12:52 Dayton, Dean
2003-03-06 21:39 Jean-Denis Boyer
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='003d01c3845c$d212c910$020120b0@jockeXP' \
--to=joakim.tjernlund@lumentis.se \
--cc=Steffen.Rumler@siemens.com \
--cc=dan@embeddededge.com \
--cc=jdboyer@m5t.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 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.