From: Carlos Chinea <carlos.chinea@nokia.com>
To: ext Stephen Rothwell <sfr@canb.auug.org.au>
Cc: 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: HSI framework for linux-next
Date: Fri, 28 Oct 2011 12:27:46 +0300 [thread overview]
Message-ID: <1319794066.28874.22.camel@groo> (raw)
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
Therefore, could you add the following tree to linux-next ?
git@gitorious.org:kernel-hsi/kernel-hsi.git for-next
Currently the framework does not have any HSI/SSI controller driver, but
myself I am working on an SSI OMAP one, which needs some changes to get
full acceptance. So hopefully I will have the changes done and acked on
time.
There are also other people preparing their controllers for integration
(see the integration discussion)
Thanks and br,
--
Carlos Chinea <carlos.chinea@nokia.com>
next reply other threads:[~2011-10-28 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 9:27 Carlos Chinea [this message]
2011-10-28 11:23 ` HSI framework for linux-next Artem Bityutskiy
2011-10-28 15:17 ` Shubhrajyoti
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=1319794066.28874.22.camel@groo \
--to=carlos.chinea@nokia.com \
--cc=govindraj.ti@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pawel.szyszuk@stericsson.com \
--cc=peter_henn@gmx.de \
--cc=sfr@canb.auug.org.au \
--cc=sjur.brandeland@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