All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: ext Jean Pihet <jpihet@mvista.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP2 OneNAND GPIO fix
Date: Tue, 16 Dec 2008 08:37:03 -0800	[thread overview]
Message-ID: <20081216163702.GQ19551@atomide.com> (raw)
In-Reply-To: <20081216103909.60b9ba67.jarkko.nikula@nokia.com>

* Jarkko Nikula <jarkko.nikula@nokia.com> [081216 00:39]:
> On Tue, 16 Dec 2008 09:19:24 +0100
> "ext Jean Pihet" <jpihet@mvista.com> wrote:
> 
> > On Tuesday 16 December 2008 00:40:59 Tony Lindgren wrote:
> > > * Jean Pihet <jpihet@mvista.com> [081211 09:02]:
> > > > Hi,
> > > >
> > > > Here is a patch to have the OMAP2 OneNAND driver compile on the latest
> > > > tree. I do not know if this has been addressed already, here is a patch.
> > >
> > > Looks like I already applied similar fixes. These are queued up for
> > > mainline too BTW.
> > Ok. My patch also changes the request and free omap calls to the standard 
> > version. I can generate a new patch if needed.
> > 
> IRCC gpiolib conversion patches are already going. Tony?

Yeah, should be about to get pulled into Russell's queue, also
available here:

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=shortlog;h=hsmmc-init

So Jean, if you can check what still needs to be patched there, and
we can queue it via omap-fixes.

Regards,

Tony

  reply	other threads:[~2008-12-16 16:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 16:59 [PATCH] OMAP2 OneNAND GPIO fix Jean Pihet
2008-12-15 23:40 ` Tony Lindgren
2008-12-16  8:19   ` Jean Pihet
2008-12-16  8:39     ` Jarkko Nikula
2008-12-16 16:37       ` Tony Lindgren [this message]
2008-12-16 18:28         ` Jean Pihet
2009-01-08 12:10           ` Tony Lindgren
2009-01-08 12:56             ` Jean Pihet
2009-01-08 13:12               ` Tony Lindgren

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=20081216163702.GQ19551@atomide.com \
    --to=tony@atomide.com \
    --cc=jarkko.nikula@nokia.com \
    --cc=jpihet@mvista.com \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.