From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Sebastian Reichel <sre@debian.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: CarlosChinea <carlos.chinea@nokia.com>,
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>,
Andras Domokos <andras.domokos@nokia.com>,
ext Shubhrajyoti <shubhrajyoti@ti.com>,
ext Shubhrajyoti Datta <omaplinuxkernel@gmail.com>,
ext Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [GIT PULL] HSI framework
Date: Wed, 07 Mar 2012 13:17:04 +0200 [thread overview]
Message-ID: <1331119024.29171.1.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120307104923.GB18093@earth.universe>
On Wed, 2012-03-07 at 11:49 +0100, Sebastian Reichel wrote:
> > Hi Linus,
> >
> > I've noticed that you have not pulled this (yet). I would like to
> > confirm that we at Intel are also very interested to have HSI upstream.
> >
> > I believe this code base is more than worth merging since it has many
> > users and it has proven itself in real Nokia products. Would you please
> > pull it?
>
> Hi,
>
> I think we never got a reply why the HSI framework has not been
> pulled into 3.3. So what needs to be done to get it pulled into 3.4?
Hi,
Because this question is for Linus, he should be in "To:" instead of
"Cc:" - correcting.
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2012-03-07 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 13:25 [GIT PULL] HSI framework Carlos Chinea
2012-01-19 12:14 ` Artem Bityutskiy
2012-03-07 10:49 ` Sebastian Reichel
2012-03-07 11:17 ` Artem Bityutskiy [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=1331119024.29171.1.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andras.domokos@nokia.com \
--cc=carlos.chinea@nokia.com \
--cc=govindraj.ti@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=omaplinuxkernel@gmail.com \
--cc=pawel.szyszuk@stericsson.com \
--cc=peter_henn@gmx.de \
--cc=shubhrajyoti@ti.com \
--cc=sjur.brandeland@stericsson.com \
--cc=sre@debian.org \
--cc=torvalds@linux-foundation.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).