Request inclusion of ARM v7 cache optimization patch into linux-next

Request inclusion of ARM v7 cache optimization patch into linux-next

[Lorenzo Pieralisi]

Hi Stephen,

can I ask you please to include the following branch into linux-next:

git://linux-arm.org/linux-2.6-lp.git v7-cache-opt

It contains a patch implementing cache optimizations for ARM 32-bit v7
architectures, it was reviewed and tested but -next would give it wider
test coverage before it gets merged in the coming cycle, so please
include it as soon as you deem fit.

Thank you very much,
Lorenzo

Request inclusion of ARM v7 cache optimization patch into linux-next

[Stephen Rothwell]

Hi Lorenzo,

On Mon, 25 Nov 2013 11:23:18 +0000 Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
>
> can I ask you please to include the following branch into linux-next:
> 
> git://linux-arm.org/linux-2.6-lp.git v7-cache-opt
> 
> It contains a patch implementing cache optimizations for ARM 32-bit v7
> architectures, it was reviewed and tested but -next would give it wider
> test coverage before it gets merged in the coming cycle, so please
> include it as soon as you deem fit.

Included from today.  Please remember to ask me to remove it when it has
been merged upstream (since I assume it will no longer be necessary).

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 at 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131126/38c7ba05/attachment.sig>

Request inclusion of ARM v7 cache optimization patch into linux-next

[Lorenzo Pieralisi]

Hi Stephen,

On Mon, Nov 25, 2013 at 11:33:43PM +0000, Stephen Rothwell wrote:
> Hi Lorenzo,
> 
> On Mon, 25 Nov 2013 11:23:18 +0000 Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> >
> > can I ask you please to include the following branch into linux-next:
> > 
> > git://linux-arm.org/linux-2.6-lp.git v7-cache-opt
> > 
> > It contains a patch implementing cache optimizations for ARM 32-bit v7
> > architectures, it was reviewed and tested but -next would give it wider
> > test coverage before it gets merged in the coming cycle, so please
> > include it as soon as you deem fit.
> 
> Included from today.  Please remember to ask me to remove it when it has
> been merged upstream (since I assume it will no longer be necessary).

You can remove the branch now, since the patch has been queued through
the ARM tree and will reappear shortly as such.

Thank you very much for your help,
Lorenzo