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: tfp410 and i2c_bus_num
Date: Wed, 21 Nov 2012 09:57:47 -0800	[thread overview]
Message-ID: <20121121175747.GV18567@atomide.com> (raw)
In-Reply-To: <20121119121630.GC15540@arwen.pp.htv.fi>

* Felipe Balbi <balbi@ti.com> [121119 04:25]:
> On Mon, Nov 19, 2012 at 01:09:42PM +0200, Tomi Valkeinen wrote:
> > On 2012-11-19 11:27, Felipe Balbi wrote:
> > > 
> > > fair enough... it looks like this is going nowhere, so best we come back
> > > to this later. No reason to block your patch.
> > 
> > Well, the patch is a fix for stable kernels, so even if we had a great
> > idea how to rewrite the dss device handling, it wouldn't affect this
> > patch =).
> 
> ok good ;-)

FYI I'm assuming Tomi will resend the patch as there were some
changes requested early on in the thread.

Tony

  reply	other threads:[~2012-11-21 17:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353068553-26897-1-git-send-email-tomi.valkeinen@ti.com>
2012-11-16 13:51 ` [PATCH] OMAP: board-files: fix i2c_bus for tfp410 Felipe Balbi
2012-11-16 14:27   ` Tomi Valkeinen
2012-11-16 15:19     ` Felipe Balbi
2012-11-16 15:39       ` Tomi Valkeinen
2012-11-16 18:21         ` tfp410 and i2c_bus_num (was: Re: [PATCH] OMAP: board-files: fix i2c_bus for tfp410) Felipe Balbi
2012-11-17  5:41           ` tfp410 and i2c_bus_num Tomi Valkeinen
2012-11-18 11:34             ` Felipe Balbi
2012-11-19  6:38               ` Tomi Valkeinen
2012-11-19  9:27                 ` Felipe Balbi
2012-11-19 11:09                   ` Tomi Valkeinen
2012-11-19 12:16                     ` Felipe Balbi
2012-11-21 17:57                       ` Tony Lindgren [this message]
2012-11-22  8:28                         ` Tomi Valkeinen

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=20121121175747.GV18567@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).