From: Linus Walleij <linus.walleij@linaro.org>
To: linux-kernel@vger.kernel.org, cch.devel@gmail.com
Cc: ext Tony Lindgren <tony@atomide.com>
Subject: Re: HSI subsystem status
Date: Mon, 7 Jan 2013 08:38:27 +0100 [thread overview]
Message-ID: <CACRpkdZmM4oNhXcaFWEFLkABCLcxEXDRxKmoev=_vx4g+o0qtA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZD6XWxgVFfO3-h_8+2y36o4mnT+ZW0d+GAVTOpC2yWRA@mail.gmail.com>
On Mon, Jan 7, 2013 at 12:11 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> Hi Carlos,
>
> 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...
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-01-07 7:38 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 [this message]
2013-01-07 14:38 ` Linus Walleij
2013-02-08 0:14 ` Sebastian Reichel
2013-02-08 21:41 ` Linus Walleij
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='CACRpkdZmM4oNhXcaFWEFLkABCLcxEXDRxKmoev=_vx4g+o0qtA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=cch.devel@gmail.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).