linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Deepak Saxena <dsaxena@linaro.org>
Subject: Re: HSI subsystem status
Date: Fri, 8 Feb 2013 22:41:19 +0100	[thread overview]
Message-ID: <CACRpkdZFgVtMYBOfz3hKFLZnRXX3PThna1aFNKTFNC_ec7wx7g@mail.gmail.com> (raw)
In-Reply-To: <20130208001458.GA24140@earth.universe>

On Fri, Feb 8, 2013 at 1:14 AM, Sebastian Reichel <sre@debian.org> wrote:
> On Mon, Jan 07, 2013 at 03:38:21PM +0100, Linus Walleij wrote:
>> >> what is the status on the HSI subsystem? We have based some patches for
>> >> HSI master on top of the OMAP HSI master patches, but these never seem
>> >> to reach the tree?
>> >
>> > Ping on the cch.devel address instead...
>> And ping on Carlos' private mail address, hehe :-)
>
> Did you receive a private answer? I'm interested in seeing OMAP HSI
> patches in the mainline kernel, so that the Nokia N900 modem can be
> used with a mainline kernel.

Yes, so realizing that this needs maintenance, and since it is part of
the HW in several Linaro member company boards, I put an item forward
to Linaro, who work cross ARM-boards, to try to locate a new
(co-)maintainer for HSI. However that needs to be processed and
prioritized.
https://blueprints.launchpad.net/linux-linaro/+spec/hsi-subsystem-maint

Yours,
Linus Walleij

      reply	other threads:[~2013-02-08 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 23:11 HSI subsystem status Linus Walleij
2013-01-06 23:15 ` Linus Walleij
2013-01-07  5:09   ` Randy Dunlap
2013-01-07  7:38 ` Linus Walleij
2013-01-07 14:38   ` Linus Walleij
2013-02-08  0:14     ` Sebastian Reichel
2013-02-08 21:41       ` Linus Walleij [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=CACRpkdZFgVtMYBOfz3hKFLZnRXX3PThna1aFNKTFNC_ec7wx7g@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=dsaxena@linaro.org \
    --cc=linux-kernel@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 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).