From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] of_serial: ignore unknown serial port
Date: Wed, 6 Jun 2007 15:44:39 +0200 [thread overview]
Message-ID: <f3272d0bef12738b1f45f656f6fda83c@kernel.crashing.org> (raw)
In-Reply-To: <200706061501.15853.arnd@arndb.de>
>>> Is this a bugfix that needs to go in 2.6.22?
>>
>> This potentially breaks lots of other platforms, so no
>> please, put it in early in the next cycle and give those
>> others time to recover from this change.
>
> I would expect that the bugfix is relatively harmless,
Sure, but you cannot prove that without checking all possibly
affected systems' device trees, that's my whole point. If
you need a fix for .22 you can always put a conditional on
celleb around the offending code. Anyway, Paul's choice.
Segher
next prev parent reply other threads:[~2007-06-06 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 9:30 [PATCH] of_serial: ignore unknown serial port Ishizaki Kou
2007-05-31 10:46 ` Arnd Bergmann
2007-06-06 5:58 ` Paul Mackerras
2007-06-06 9:09 ` Segher Boessenkool
2007-06-06 13:01 ` Arnd Bergmann
2007-06-06 13:44 ` Segher Boessenkool [this message]
2007-06-06 9:28 ` kouish
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=f3272d0bef12738b1f45f656f6fda83c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).