public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Tony Lindgren <tony@atomide.com>
Cc: David Brownell <david-b@pacbell.net>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-omap@vger.kernel.org, Deepak Saxena <dsaxena@plexity.net>
Subject: Re: testers wanted: isp1301_omap conversion to new-style i2c driver
Date: Fri, 8 Aug 2008 11:17:51 +0200	[thread overview]
Message-ID: <20080808111751.494702cc@hyperion.delvare> (raw)
In-Reply-To: <20080808072954.GH24923@atomide.com>

Hi Tony,

On Fri, 8 Aug 2008 10:29:55 +0300, Tony Lindgren wrote:
> * David Brownell <david-b@pacbell.net> [080808 02:51]:
> > On Thursday 07 August 2008, Jean Delvare wrote:
> > > Still no testers for these patches? 
> > 
> > Right now I don't seem to be able to boot OMAP1 in mainline,
> > so pulling that H2 out of its box would be futile.  :(
> 
> Grr, looks like I can't access my H2 remotely right now as my
> remote power switch is hung, and would need to be remote rebooted..
> 
> So I can't access H2 for few more weeks, can somebody else test
> on H2 meanwhile?
> 
> BTW, this patch should OK to apply as we've had it in the
> linux-omap tree since December, and I've occasionally boot tested
> H2, last time I think was when I removed the __REG macros few
> months ago.

It is possible that you have had the 1st patch in your tree for some
time. However, the second patch I wrote 1.5 month ago or so, so I doubt
that you can have it in your tree since December 2007 ;)

Maybe your can update the omap tree with my patches? This would give
them the testing they are missing, and then we can push them upstream.
Ideally that would have gone in 2.6.27, but it starts being a bit late
for that now.

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2008-08-08  9:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17 18:43 testers wanted: isp1301_omap conversion to new-style i2c driver Jean Delvare
2008-08-07 16:34 ` Jean Delvare
2008-08-07 23:51   ` David Brownell
2008-08-08  7:29     ` Tony Lindgren
2008-08-08  9:17       ` Jean Delvare [this message]
2008-08-08  9:39         ` Felipe Balbi
2008-08-08  9:45         ` Tony Lindgren
2008-08-08  9:48           ` Felipe Balbi
2008-08-11 15:24             ` [PATCH] Fix isp1301_omap compile (Re: testers wanted: isp1301_omap conversion to new-style i2c driver) Tony Lindgren
2008-08-11 16:23               ` Jean Delvare
2008-08-11 18:40                 ` David Brownell
2008-08-12  9:29                   ` Tony Lindgren
2008-08-12  9:51                     ` Jean Delvare
2008-08-18 12:21                       ` Tony Lindgren
2008-08-18 12:34                         ` Jean Delvare
2008-08-18 12:42                           ` Tony Lindgren
2008-08-12 10:17                     ` David Brownell
2008-08-11 18:46               ` David Brownell
2008-09-10 22:31             ` testers wanted: isp1301_omap conversion to new-style i2c driver Tony Lindgren
2008-09-11  7:15               ` Jean Delvare

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=20080808111751.494702cc@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=david-b@pacbell.net \
    --cc=dsaxena@plexity.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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