HSI framework for linux-next

HSI framework for linux-next

[Carlos Chinea]

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>

Re: HSI framework for linux-next

[Artem Bityutskiy]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

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.

Thanks!

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: HSI framework for linux-next

[Shubhrajyoti]

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!
>

Re: HSI framework for linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

Hi Carlos,

On Fri, 28 Oct 2011 12:27:46 +0300 Carlos Chinea <carlos.chinea@nokia.com> wrote:
>
> 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 ? 

I will try to remember, but if I forget, then ping me when v3.2-rc1 has
been released.  I don't put future code into linux-next until after -rc1
to save false problems with the stuff that has still not been sent to
Linus.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: HSI framework for linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

Hi Carlos,

On Fri, 28 Oct 2011 12:27:46 +0300 Carlos Chinea <carlos.chinea@nokia.com> wrote:
>
> 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)

Right, so -rc1 has been released so I can consider this.  Just a couple of things:

	Linus (and the rest of us) is being a bit nmore paranoid about
where to fetch trees from.  Public git hosters (like gitorious) can be
problematic since it is hard for us to verify the owners of trees
reliably.  You either need to apply for a kernel.org account, or you will
need to add a signed tag to your tree before asking Linus to pull from
it.  And that atg will have to be singned with a GPG key that can be
verified by Linus ...

	I am not sure how to translate that gitorious URI above into a
simple, publically fetchable URI (git://gitorious.org...).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: HSI framework for linux-next

[Sebastian Reichel]

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Wed, Nov 09, 2011 at 08:51:40AM +1100, Stephen Rothwell wrote:
> Hi Carlos,
> 
> On Fri, 28 Oct 2011 12:27:46 +0300 Carlos Chinea <carlos.chinea@nokia.com> wrote:
> > ...
> 
> Right, so -rc1 has been released so I can consider this.  Just a couple of things:
> 
> 	Linus (and the rest of us) is being a bit nmore paranoid about
> where to fetch trees from.  Public git hosters (like gitorious) can be
> problematic since it is hard for us to verify the owners of trees
> reliably.  You either need to apply for a kernel.org account, or you will
> need to add a signed tag to your tree before asking Linus to pull from
> it.  And that atg will have to be singned with a GPG key that can be
> verified by Linus ...
> 
> 	I am not sure how to translate that gitorious URI above into a
> simple, publically fetchable URI (git://gitorious.org...).

It has been two weeks. Did I miss any status updates?

Here's the git fetchable URI: git://gitorious.org/kernel-hsi/kernel-hsi.git
The existing tag is not signed though.

-- Sebastian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: HSI framework for linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

Hi Carlos,

On Fri, 28 Oct 2011 12:27:46 +0300 Carlos Chinea <carlos.chinea@nokia.com> wrote:
>
> 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

I have added that tree to linux-next today using
git://gitorious.org/kernel-hsi/kernel-hsi.git as the URL and just you as
the contact in case if issues.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]