linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Rumler <Steffen.Rumler@siemens.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc <linuxppc-embedded@ozlabs.org>
Subject: Re: uart.c: avoid changing parameter RAM on-the-fly for the console
Date: Fri, 04 Feb 2005 09:55:36 +0100	[thread overview]
Message-ID: <42033888.4090706@siemens.com> (raw)
In-Reply-To: <754ecc31c2497b32a0c3f6df5ce21881@embeddededge.com>

> would you please read Documentation/CodingStyle and
> try sending the patch again?

What in detail is wrong concerning the coding style ?
Note, this is a serious problem for us.

> Although it doesn't make too much difference in this case,
> 2.4.20 is pretty old and it helps to get patches against
> the latest kernels.

2.4.20 is the kernel we are actually using.

> I suspect there is something else amiss, but I'll take a
> look at it.  What is the speed of the processor and the
> baud rate?

CPU:       MPC859T
CPU clock: 133Mhz
Baud Rate: 19200


Steffen

-- 


--------------------------------------------------------------

Steffen Rumler
ICN CP D NT SW 3
Siemens AG
Hofmannstr. 51                 Email: Steffen.Rumler@siemens.com
D-81359 Munich                 Phone: +49 89 722-44061
Germany                        Fax  : +49 89 722-36703

--------------------------------------------------------------

  reply	other threads:[~2005-02-04  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 15:17 uart.c: avoid changing parameter RAM on-the-fly for the console Steffen Rumler
2005-02-03 15:43 ` Dan Malek
2005-02-04  8:55   ` Steffen Rumler [this message]
2005-02-16  9:56   ` Steffen Rumler

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=42033888.4090706@siemens.com \
    --to=steffen.rumler@siemens.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@ozlabs.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).