From: Shubhrajyoti <shubhrajyoti@ti•com>
To: artem.bityutskiy@linux•intel.com
Cc: Carlos Chinea <carlos.chinea@nokia•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"linux-omap@vger•kernel.org" <linux-omap@vger•kernel.org>,
ext Linus Walleij <linus.walleij@linaro•org>,
"peter_henn@gmx•de" <peter_henn@gmx•de>,
"sjur.brandeland@stericsson•com" <sjur.brandeland@stericsson•com>,
"govindraj.ti@gmail•com" <govindraj.ti@gmail•com>,
"pawel.szyszuk@stericsson•com" <pawel.szyszuk@stericsson•com>,
Sebastian Reichel <sre@debian•org>
Subject: Re: HSI framework for linux-next
Date: Fri, 28 Oct 2011 20:47:40 +0530 [thread overview]
Message-ID: <4EAAC794.8010809@ti.com> (raw)
In-Reply-To: <1319800996.31184.131.camel@sauron>
On Friday 28 October 2011 04:53 PM, Artem Bityutskiy wrote:
> On Fri, 2011-10-28 at 12:27 +0300, Carlos Chinea wrote:
>> Hi Stephen,
>>
>> I have been working in an HSI framework for linux:
>>
>> https://lkml.org/lkml/2011/6/10/280
>>
>> The framework is in good shape and is currently being used for some
>> people so we would like it to see it integrated, if possible, for 3.3
>>
>> Latest discussion for integration:
>> https://lkml.org/lkml/2011/10/20/177
> Stephen,
>
> I confirm that this is useful and solid framework, works well, and we
> are also interested to see it upstream.
>
Yes also it may help others to hook up their controller support.
> Thanks!
>
next prev parent reply other threads:[~2011-10-28 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 9:27 HSI framework for linux-next Carlos Chinea
2011-10-28 11:23 ` Artem Bityutskiy
2011-10-28 15:17 ` Shubhrajyoti [this message]
2011-10-28 18:45 ` Stephen Rothwell
2011-11-08 21:51 ` Stephen Rothwell
2011-11-23 17:26 ` Sebastian Reichel
2011-11-23 22:07 ` Stephen Rothwell
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=4EAAC794.8010809@ti.com \
--to=shubhrajyoti@ti$(echo .)com \
--cc=artem.bityutskiy@linux$(echo .)intel.com \
--cc=carlos.chinea@nokia$(echo .)com \
--cc=govindraj.ti@gmail$(echo .)com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=pawel.szyszuk@stericsson$(echo .)com \
--cc=peter_henn@gmx$(echo .)de \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sjur.brandeland@stericsson$(echo .)com \
--cc=sre@debian$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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