From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-next@vger.kernel.org, nacc@linux.vnet.ibm.com,
Richard Weinberger <richard@nod.at>
Subject: Re: mmotm 2014-04-22-15-20 uploaded (uml 32- and 64-bit defconfigs)
Date: Wed, 23 Apr 2014 17:00:10 -0700 [thread overview]
Message-ID: <5358540A.3030302@infradead.org> (raw)
In-Reply-To: <20140424083100.c5f32e14abd2f6ed05673cb9@canb.auug.org.au>
On 04/23/14 15:31, Stephen Rothwell wrote:
> Hi Andrew,
>
> On Wed, 23 Apr 2014 15:18:19 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> Stephen who?
>>
>> Oh, that guy who sends stuff first then comes last when others use LIFO :)
>
> Ah ha! So all I have to do is stamp my emails a day ahead? Or queue
> them up and send them via a cron job just after "Andrew's breakfast
> time"? :-)
>
> Anyway, I was more suggesting that Randy and the others could have saved
> themselves time by reading that email.
Agreed, thanks for kicking me. ;)
I think that it also means that there is still plenty of room for process
improvement with akpm including linux-next and linux-next including (parts of)
akpm-current. IMHO.
--
~Randy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-next@vger.kernel.org, nacc@linux.vnet.ibm.com,
Richard Weinberger <richard@nod.at>
Subject: Re: mmotm 2014-04-22-15-20 uploaded (uml 32- and 64-bit defconfigs)
Date: Wed, 23 Apr 2014 17:00:10 -0700 [thread overview]
Message-ID: <5358540A.3030302@infradead.org> (raw)
In-Reply-To: <20140424083100.c5f32e14abd2f6ed05673cb9@canb.auug.org.au>
On 04/23/14 15:31, Stephen Rothwell wrote:
> Hi Andrew,
>
> On Wed, 23 Apr 2014 15:18:19 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> Stephen who?
>>
>> Oh, that guy who sends stuff first then comes last when others use LIFO :)
>
> Ah ha! So all I have to do is stamp my emails a day ahead? Or queue
> them up and send them via a cron job just after "Andrew's breakfast
> time"? :-)
>
> Anyway, I was more suggesting that Randy and the others could have saved
> themselves time by reading that email.
Agreed, thanks for kicking me. ;)
I think that it also means that there is still plenty of room for process
improvement with akpm including linux-next and linux-next including (parts of)
akpm-current. IMHO.
--
~Randy
next prev parent reply other threads:[~2014-04-24 0:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 22:21 mmotm 2014-04-22-15-20 uploaded akpm
2014-04-22 22:21 ` akpm
2014-04-22 22:21 ` akpm
2014-04-23 17:10 ` mmotm 2014-04-22-15-20 uploaded (uml 32- and 64-bit defconfigs) Randy Dunlap
2014-04-23 17:10 ` Randy Dunlap
2014-04-23 17:41 ` Luiz Capitulino
2014-04-23 17:41 ` Luiz Capitulino
2014-04-23 17:48 ` Randy Dunlap
2014-04-23 18:16 ` Luiz Capitulino
2014-04-23 18:16 ` Luiz Capitulino
2014-04-23 18:20 ` Randy Dunlap
2014-04-23 18:20 ` Randy Dunlap
2014-04-23 18:24 ` Andrew Morton
2014-04-23 18:24 ` Andrew Morton
2014-04-23 19:24 ` Nishanth Aravamudan
2014-04-23 19:24 ` Nishanth Aravamudan
2014-04-23 22:10 ` Stephen Rothwell
2014-04-23 22:18 ` Andrew Morton
2014-04-23 22:18 ` Andrew Morton
2014-04-23 22:31 ` Stephen Rothwell
2014-04-23 22:41 ` Andrew Morton
2014-04-23 22:41 ` Andrew Morton
2014-04-24 0:00 ` Randy Dunlap [this message]
2014-04-24 0:00 ` Randy Dunlap
2014-04-23 23:31 ` Nishanth Aravamudan
2014-04-23 23:31 ` Nishanth Aravamudan
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=5358540A.3030302@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.