linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: Fix DEBUG_LL uart to access phys addr when MMU isn't enable
Date: Wed, 4 Aug 2010 08:28:38 +0300	[thread overview]
Message-ID: <20100804052834.GA6840@atomide.com> (raw)
In-Reply-To: <20100803194717.GA28048@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [100803 22:40]:
> On Tue, Aug 03, 2010 at 03:38:29PM +0300, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [100803 10:18]:
> > > On Tue, Aug 03, 2010 at 03:11:41PM +0800, Eric Miao wrote:
> > > > We also need to take care of Jeremy's recent patchset to remove
> > > > .io_pg_offst and .phys_io, which modifies all the addruart macros.
> > > 
> > > I don't think Jeremy's patches will be going in for this merge window as
> > > we can't intentionally break OMAP's support because we don't understand
> > > OMAP.  I think Jeremy's patches will have to wait for the next merge
> > > window now.
> > 
> > Well now we understand there's a bug.. Here's what's needed to make
> > Jason's fix to work on Jeremy's mdesc series.
> 
> That's not quite the point - Jeremy's patches with working OMAP support
> haven't been tested in linux-next, and so hasn't had visibility to the
> wider community, and so it shouldn't be going into the current merge
> window.

OK. It's best to test them properly. I'll add Jason's original fix
into omap-for-linus then for this merge window.

Tony

      reply	other threads:[~2010-08-04  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03  3:44 [PATCH] omap: Fix DEBUG_LL uart to access phys addr when MMU isn't enable Jason Wang
2010-08-03  4:36 ` Eric Miao
2010-08-03  6:57   ` Tony Lindgren
2010-08-03  7:11     ` Eric Miao
2010-08-03  7:25       ` Russell King - ARM Linux
2010-08-03 12:38         ` Tony Lindgren
2010-08-03 19:47           ` Russell King - ARM Linux
2010-08-04  5:28             ` Tony Lindgren [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=20100804052834.GA6840@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).