From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Felipe Balbi <me@felipebalbi.com>
Cc: David Brownell <david-b@pacbell.net>,
Felipe Balbi <felipe.balbi@nokia.com>,
linux-omap@vger.kernel.org, gdavis@mvista.com,
Tony Lindgren <tony@atomide.com>,
wim@iguana.be
Subject: Re: [PATCH] watchdog: another ioremap() fix
Date: Thu, 18 Sep 2008 21:15:07 +0100 [thread overview]
Message-ID: <20080918201507.GB14307@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080918200245.GA6617@frodo>
On Thu, Sep 18, 2008 at 11:02:58PM +0300, Felipe Balbi wrote:
> Hi,
>
> On Thu, Sep 18, 2008 at 08:50:07PM +0100, Russell King - ARM Linux wrote:
> > On Thu, Sep 18, 2008 at 10:03:16AM -0700, David Brownell wrote:
> > > On Thursday 18 September 2008, Felipe Balbi wrote:
> > > > convert to use ioremap() and __raw_{read/write} friends.
> > >
> > > Why is this going to the OMAP list, not to LKML and cc'd
> > > the watchdog maintainer? (I added Wim to the cc list...)
> > >
> > > If it's worth having, it's worth having in mainline...
> >
> > Indeed, this is definitely something that can go into mainline now and
> > trickle back down into the OMAP tree.
> >
> > In other words, don't merge this into any OMAP tree, but get it into
> > mainline and wait for it to come back. Same goes for any other fixes.
> > That means less work needs to be done by a very small number of
> > individuals who don't have enough time to push everything from the OMAP
> > tree upstream.
>
> Unfortunately I'll have to disagree here, a diff on omap_wdt.c against
> mainline shows quite a few changes since omap3 was introduced. Several
> patches never went to mainline. I'll prepare a sync up patch from omap to
> mainline and send both, but the omap3 stuff, won't be able to go in.
> Maybe i'll try to get rid of all the if (cpu_is_XXX()) stuff in
> omap_wdt.c and then send my patch on top of that.
Actually, you're wrong on that. You can take the entire driver and
build it as it currently stands in mainline. I just did exactly
that by doing the following:
$ diff -u linux-2.6-rmk/drivers/watchdog/omap_wdt.c \
linux-2.6-omap/drivers/watchdog/omap_wdt.c > wdt.diff
$ cd linux-2.6-rmk
$ patch -p1 -i ../wdt.diff
patching file drivers/watchdog/omap_wdt.c
$ emake O=../build/omap2/ drivers/watchdog/
...
CC drivers/watchdog/omap_wdt.o
LD drivers/watchdog/built-in.o
So there should be no problems with merging up the OMAP3 changes in
this driver.
next prev parent reply other threads:[~2008-09-18 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 13:55 [PATCH] watchdog: another ioremap() fix Felipe Balbi
2008-09-18 17:03 ` David Brownell
2008-09-18 17:26 ` Felipe Balbi
2008-09-19 8:06 ` Wim Van Sebroeck
2008-09-18 19:50 ` Russell King - ARM Linux
2008-09-18 20:02 ` Felipe Balbi
2008-09-18 20:15 ` Russell King - ARM Linux [this message]
2008-09-18 20:34 ` Russell King - ARM Linux
2008-09-18 20:55 ` Felipe Balbi
2008-09-19 8:30 ` Wim Van Sebroeck
2008-09-18 20:10 ` David Brownell
2008-09-21 18:20 ` Tony Lindgren
2008-09-18 18:29 ` George G. Davis
2008-09-18 18:40 ` Felipe Balbi
2008-09-18 18:45 ` George G. Davis
2008-09-18 18:49 ` Felipe Balbi
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=20080918201507.GB14307@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=gdavis@mvista.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=tony@atomide.com \
--cc=wim@iguana.be \
/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