linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Chinea <carlos.chinea@nokia.com>
To: ext Sebastian Reichel <sre@debian.org>
Cc: ext Linus Walleij <linus.walleij@linaro.org>,
	Govindraj <govindraj.ti@gmail.com>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
	pawel.szyszuk@stericsson.com
Subject: Re: [RFC PATCHv4 0/7] HSI framework and drivers
Date: Wed, 08 Jun 2011 10:12:45 +0300	[thread overview]
Message-ID: <1307517165.2819.33110.camel@groo> (raw)
In-Reply-To: <20110607150910.GA3780@earth.universe>

Hi,

On Tue, 2011-06-07 at 17:09 +0200, ext Sebastian Reichel wrote:
> On Tue, May 17, 2011 at 11:39:13AM +0300, Carlos Chinea wrote:
> > We are still committed to these patches. We are aiming to release a new
> > version in 3 weeks max, sooner if we can.
> > 
> > I am very sorry for the delay and I agree that starting to have several
> > out-of-tree drivers is not acceptable. I'll try my best to fix this
> > asap.
> 
> Do you also plan to add the platform code for rx51 to the mainline
> kernel?

Not yet in this patch set. If the HSI framework makes it into the
kernel, then I will try to push a couple of new HSI clients needed for
rx51 and the platform related code.

> 
> P.S.: 3 weeks are over today :)
> 

Yep, we are almost there with the patches :P A small problem in a last
minute test is keeping us from releasing the patches already.

Br,
-- 
Carlos Chinea <carlos.chinea@nokia.com>

      reply	other threads:[~2011-06-08  7:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 10:09 [RFC PATCHv4 0/7] HSI framework and drivers Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 1/7] HSI: hsi: Introducing HSI framework Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 2/7] HSI: omap_ssi: Introducing OMAP SSI driver Carlos Chinea
2010-12-18  0:30   ` Tony Lindgren
2010-12-20 16:38     ` Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 3/7] HSI: omap_ssi: Add OMAP SSI to the kernel configuration Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 4/7] HSI: hsi_char: Add HSI char device driver Carlos Chinea
2010-12-14 11:56   ` Alan Cox
2010-12-14 17:24     ` Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 5/7] HSI: hsi_char: Add HSI char device kernel configuration Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 6/7] HSI: Add HSI API documentation Carlos Chinea
2010-12-14 10:09 ` [RFC PATCHv4 7/7] HSI: hsi_char: Update ioctl-number.txt Carlos Chinea
2011-03-21  8:16 ` [RFC PATCHv4 0/7] HSI framework and drivers Linus Walleij
2011-03-22  9:50   ` Carlos Chinea
2011-05-12 12:17     ` Govindraj
2011-05-16 12:04       ` Linus Walleij
2011-05-17  8:39         ` Carlos Chinea
2011-06-07 15:09           ` Sebastian Reichel
2011-06-08  7:12             ` Carlos Chinea [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=1307517165.2819.33110.camel@groo \
    --to=carlos.chinea@nokia.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=govindraj.ti@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pawel.szyszuk@stericsson.com \
    --cc=sre@debian.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).