On Fri, Feb 22, 2008 at 03:57:13PM +1100, Stephen Rothwell wrote:
> Hi Ananth,
>
> On Fri, 22 Feb 2008 09:12:31 +0530 Ananth N Mavinakayanahalli <[EMAIL
> PROTECTED]> wrote:
> >
> > The patchset in question is just a major code movement - basically to
> > move all in-kernel tests to live under a
Hi Ananth,
On Fri, 22 Feb 2008 09:12:31 +0530 Ananth N Mavinakayanahalli <[EMAIL
PROTECTED]> wrote:
>
> The patchset in question is just a major code movement - basically to
> move all in-kernel tests to live under a toplevel tests/ directory. As
> such, all the stakeholders have acked the
On Tue, Feb 19, 2008 at 08:21:53PM +0100, Sam Ravnborg wrote:
> Hi Anath.
>
> Linus did not pull this in the -rc1 to -rc2 timeframe
> so please resubmit the patch serie one week into the
> next merge window (when most of the trees has hit linus' tree
> and Andrew has made his first merge).
>
>
On Tue, Feb 19, 2008 at 08:21:53PM +0100, Sam Ravnborg wrote:
Hi Anath.
Linus did not pull this in the -rc1 to -rc2 timeframe
so please resubmit the patch serie one week into the
next merge window (when most of the trees has hit linus' tree
and Andrew has made his first merge).
IF you
Hi Ananth,
On Fri, 22 Feb 2008 09:12:31 +0530 Ananth N Mavinakayanahalli [EMAIL
PROTECTED] wrote:
The patchset in question is just a major code movement - basically to
move all in-kernel tests to live under a toplevel tests/ directory. As
such, all the stakeholders have acked the patchset,
On Fri, Feb 22, 2008 at 03:57:13PM +1100, Stephen Rothwell wrote:
Hi Ananth,
On Fri, 22 Feb 2008 09:12:31 +0530 Ananth N Mavinakayanahalli [EMAIL
PROTECTED] wrote:
The patchset in question is just a major code movement - basically to
move all in-kernel tests to live under a toplevel
On Tue, Feb 19, 2008 at 08:21:53PM +0100, Sam Ravnborg wrote:
> Hi Anath.
Hi Sam,
> Linus did not pull this in the -rc1 to -rc2 timeframe
> so please resubmit the patch serie one week into the
> next merge window (when most of the trees has hit linus' tree
> and Andrew has made his first merge).
On Tue, Feb 19, 2008 at 08:21:53PM +0100, Sam Ravnborg wrote:
Hi Anath.
Hi Sam,
Linus did not pull this in the -rc1 to -rc2 timeframe
so please resubmit the patch serie one week into the
next merge window (when most of the trees has hit linus' tree
and Andrew has made his first merge).
Hi Anath.
Linus did not pull this in the -rc1 to -rc2 timeframe
so please resubmit the patch serie one week into the
next merge window (when most of the trees has hit linus' tree
and Andrew has made his first merge).
IF you need an extra eye balling then you can submit
a few weeks before the
Hi Anath.
Linus did not pull this in the -rc1 to -rc2 timeframe
so please resubmit the patch serie one week into the
next merge window (when most of the trees has hit linus' tree
and Andrew has made his first merge).
IF you need an extra eye balling then you can submit
a few weeks before the
* Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> {kernel => tests}/backtracetest.c |0
> {drivers/misc => tests}/lkdtm.c | 12 ++--
> {lib => tests}/locking-selftest-hardirq.h |0
> {lib => tests}/locking-selftest-mutex.h |0
> {lib =>
* Sam Ravnborg [EMAIL PROTECTED] wrote:
{kernel = tests}/backtracetest.c |0
{drivers/misc = tests}/lkdtm.c | 12 ++--
{lib = tests}/locking-selftest-hardirq.h |0
{lib = tests}/locking-selftest-mutex.h |0
{lib =
Sam Ravnborg wrote:
Hi Linus.
Will you consider such a primary code-movement for -rc1
or shall we wait until next merge window?
Had we hit -rc2 I would not have sent this pull req and
feel free to flame me anyway.
The rationale to get it merged is obviously to avoid
merge conflicts and the
Hi Linus.
Will you consider such a primary code-movement for -rc1
or shall we wait until next merge window?
Had we hit -rc2 I would not have sent this pull req and
feel free to flame me anyway.
The rationale to get it merged is obviously to avoid
merge conflicts and the only reason I ask is
Sam Ravnborg wrote:
Hi Linus.
Will you consider such a primary code-movement for -rc1
or shall we wait until next merge window?
Had we hit -rc2 I would not have sent this pull req and
feel free to flame me anyway.
The rationale to get it merged is obviously to avoid
merge conflicts and the
Hi Linus.
Will you consider such a primary code-movement for -rc1
or shall we wait until next merge window?
Had we hit -rc2 I would not have sent this pull req and
feel free to flame me anyway.
The rationale to get it merged is obviously to avoid
merge conflicts and the only reason I ask is
16 matches
Mail list logo
