public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: Komal Shah <komal_shah802003@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Missed OMAP IrDA patch for 2.6.19?
Date: Wed, 18 Oct 2006 20:16:53 +0300	[thread overview]
Message-ID: <20061018171652.GF4439@atomide.com> (raw)
In-Reply-To: <20061009231042.GC4696@sortiz.org>

Hi,

* Samuel Ortiz <samuel@sortiz.org> [061009 18:56]:
> Hi Komal,
> 
> On Thu, Oct 05, 2006 at 10:09:06AM -0700, Komal Shah wrote:
> > Samuel,
> > 
> > Why the following patch never made it to -mm tree
> > OR to your IrDA tree for considering under 2.6.19?
> I had another look at the patch, and I just saw that it depends on
> GPIOEXPANDER_OMAP. This symbol is currently only defined in Tony's tree, so
> it would make more sense for Tony to push it there first.

OK, netdev tree is the way to get this into mainline. Mainline tree
already has include/asm-arm/arch-omap/gpioexpander.h, but not
drivers/i2c/chips/gpio_expander_omap.c.

The gpio_expander_omap.c (which really is TI PCF8574) issues need
to be sorted out with the I2C folks, so meanwhile I suggest to continue
these two independently of each other. Especially since the IrDA drive
driver is usable on H2.
 
> Tony, can you push this patch to your tree ? I ACKed it after the second
> iteration.
> 
> Cheers,
> Samuel.
> 
> 
> > http://lkml.org/lkml/2006/8/27/141

I'll push it, I guess I must have missed the original message.

Regards,

Tony

      reply	other threads:[~2006-10-18 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:09 Missed OMAP IrDA patch for 2.6.19? Komal Shah
2006-10-06  9:32 ` samuel
2006-10-09 23:10 ` Samuel Ortiz
2006-10-18 17:16   ` 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=20061018171652.GF4439@atomide.com \
    --to=tony@atomide.com \
    --cc=komal_shah802003@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel@sortiz.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