From: David Gibson <dwg@au1.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, Russell King <rmk@arm.linux.org.uk>,
paulus@samba.org
Subject: Re: [PATCH] Use resource_size_t for serial port IO addresses
Date: Tue, 24 Jul 2007 11:57:43 +1000 [thread overview]
Message-ID: <20070724015743.GD28577@localhost.localdomain> (raw)
In-Reply-To: <20070723123411.07fc6568.akpm@linux-foundation.org>
On Mon, Jul 23, 2007 at 12:34:11PM -0700, Andrew Morton wrote:
> On Mon, 23 Jul 2007 09:08:37 -0500
> Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:
>
> > On Sun, 2007-07-15 at 12:06 +0100, Russell King wrote:
> > > > This is something we should do, but I have recollections of Russell
> > > > identifying problems with this patch, or at least an earlier version of it?
> > >
> > > Basically, there's two patches. This one (let's call this patch A)
> > > and another to prevent users being surprised (let's call that patch B).
> > >
> > > I didn't have any real objections to patch A, provided something like
> > > patch B was merged. I did have objections against patch B, and I was
> > > intermittently working on a revised solution.
> > >
> > > However, for whatever reason [*], during the last merge window patch B
> > > got merged and patch A got dropped, and as a result I've now given up
> > > with my revised solution, and TBH, I no longer care.
> >
> > Patch B in this case was commit abb4a2390. Since that has already been
> > merged, can we please merge this patch into 2.6.23? I'd really like to
> > avoid 44x not working in yet another kernel, so if this patch can't be
> > merged I'll have to come up with some alternate solution soon.
> >
>
> I still have a large pile of not-completely-obviously-ready patches to go
> through, of which this is one.
>
> There _were_ issues with this patch when it first turned up, but I failed
> to record what they were.
Heh. Nor did I ever hear what they might be.
>
> Oh well, here's hoping it got fixed.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2007-07-24 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 14:02 [PATCH] Use resource_size_t for serial port IO addresses Josh Boyer
2007-07-13 19:02 ` Andrew Morton
2007-07-13 19:24 ` Josh Boyer
2007-07-15 11:06 ` Russell King
2007-07-23 14:08 ` Josh Boyer
2007-07-23 19:34 ` Andrew Morton
2007-07-24 1:57 ` David Gibson [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=20070724015743.GD28577@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
/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).