From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <adrian.bunk@movial.fi>
Cc: Tim Bird <tim.bird@am.sony.com>,
Marco Berizzi <pupilla@hotmail.com>,
Alistair John Strachan <alistair@devzero.co.uk>,
linux-kernel@vger.kernel.org,
Grant Coady <grant_lkml@dodo.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFT: 2.6 patch] fix text console corruptions
Date: Wed, 30 Jul 2008 16:24:49 +0100 [thread overview]
Message-ID: <1217431489.27925.258.camel@pmac.infradead.org> (raw)
In-Reply-To: <20080730140655.GC19966@cs181140183.pp.htv.fi>
On Wed, 2008-07-30 at 17:06 +0300, Adrian Bunk wrote:
> On Tue, Jul 29, 2008 at 05:03:47PM -0700, Tim Bird wrote:
> > Marco Berizzi wrote:
> > > alistair@devzero.co.uk wrote:
> > >
> > >> You don't actually say whether you had CONFIG_CONSOLE_TRANSLATIONS=y or not?
> > >
> > > yes console_translation is set to yes. It cannot be changed if embedded is not
> > > set.
> >
> > If console_translation is set to yes, the behavior should be unchanged from
> > 2.6.26.
> >...
>
> Your commit contains a change that breaks due to | having a higher
> precedence than ?: in C.
Oh, I think that's probably my fault then; sorry.
--
dwmw2
prev parent reply other threads:[~2008-07-30 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 15:42 commit a29ccf6f823a84d89e1c7aaaf221cf7282022024 break console on slackware 12.1 Marco Berizzi
2008-07-29 17:15 ` Alistair John Strachan
2008-07-29 18:57 ` Marco Berizzi
2008-07-30 0:03 ` Tim Bird
2008-07-30 0:30 ` Grant Coady
2008-07-30 20:11 ` Tim Bird
2008-07-30 23:47 ` Grant Coady
2008-07-31 11:02 ` Marco Berizzi
2008-07-30 21:54 ` Rene Herman
2008-07-30 23:40 ` Grant Coady
2008-07-30 1:16 ` Grant Coady
2008-07-30 6:36 ` Marco Berizzi
2008-07-30 14:06 ` [RFT: 2.6 patch] fix text console corruptions Adrian Bunk
2008-07-30 15:24 ` David Woodhouse [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=1217431489.27925.258.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=adrian.bunk@movial.fi \
--cc=akpm@linux-foundation.org \
--cc=alistair@devzero.co.uk \
--cc=grant_lkml@dodo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.com \
--cc=tim.bird@am.sony.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®