public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>,
	"Martin-Éric Racine" <q-funk@pp.fishpool.fi>
Subject: Re: [PATCH] For test only: pmac_zilog fixes (cups lockup at boot):
Date: Fri, 5 Mar 2004 18:52:40 +0100	[thread overview]
Message-ID: <20040305175239.GC16646@kiste> (raw)
In-Reply-To: <20040305094807.E22156@flint.arm.linux.org.uk>

Hi,

Russell King:
> Like I said, I can't see the twigs for the forest due to the shear
> noise caused by the up -> uap change.
> 
That's quite easy to filter out.

$ sed -e s/uap/up/g < uart.patch | patch -p1 -g1
$ bk -r diffs -ub | less
$ bk -r unedit # ;-)

Anyway, as for the lock, remember that there are two serial ports on one
interrupt, so you can't use a tty-specific lock for them.

-- 
Matthias Urlichs

      parent reply	other threads:[~2004-03-05 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05  7:54 [PATCH] For test only: pmac_zilog fixes (cups lockup at boot): Benjamin Herrenschmidt
2004-03-05  8:58 ` Russell King
2004-03-05  9:02   ` Benjamin Herrenschmidt
2004-03-05  9:18     ` serial driver / tty issues Benjamin Herrenschmidt
2004-03-05  9:41       ` Russell King
2004-03-05 11:13         ` Benjamin Herrenschmidt
2004-03-05  9:05   ` [PATCH] For test only: pmac_zilog fixes (cups lockup at boot): Benjamin Herrenschmidt
2004-03-05  9:24     ` Russell King
2004-03-05  9:29       ` Benjamin Herrenschmidt
2004-03-05  9:48         ` Russell King
2004-03-05 11:14           ` Benjamin Herrenschmidt
2004-03-05 17:52           ` Matthias Urlichs [this message]

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=20040305175239.GC16646@kiste \
    --to=smurf@smurf.noris.de \
    --cc=benh@kernel.crashing.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=q-funk@pp.fishpool.fi \
    /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