From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: torvalds@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Pull request: DMA pool updates
Date: Mon, 28 Jan 2008 18:57:01 -0800 [thread overview]
Message-ID: <20080128185701.752fe2c8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080129024524.GA20198@parisc-linux.org>
On Mon, 28 Jan 2008 19:45:25 -0700 Matthew Wilcox <matthew@wil.cx> wrote:
> > afaik these patches have been tested by nobody except thyself?
>
> I've tested them myself, then I sent them to the perf team who ran the
> (4 hour long) benchmark, and they reported success. As with many patches
> these days, they sank into a pit of indifference.
I like to think that's because everyone is all fired up about bugfixes and
the regression reports. heh.
It's a simple matter for me to add another git tree, which gets things a
bit more exposure.
> Perhaps I need to
> take a leaf from my former government's book and sex up my patch
> descriptions a bit.
Well these two pulls came with effectively no description at all. Put
yourself in Linus's position...
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: torvalds@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Pull request: DMA pool updates
Date: Mon, 28 Jan 2008 18:57:01 -0800 [thread overview]
Message-ID: <20080128185701.752fe2c8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080129024524.GA20198@parisc-linux.org>
On Mon, 28 Jan 2008 19:45:25 -0700 Matthew Wilcox <matthew@wil.cx> wrote:
> > afaik these patches have been tested by nobody except thyself?
>
> I've tested them myself, then I sent them to the perf team who ran the
> (4 hour long) benchmark, and they reported success. As with many patches
> these days, they sank into a pit of indifference.
I like to think that's because everyone is all fired up about bugfixes and
the regression reports. heh.
It's a simple matter for me to add another git tree, which gets things a
bit more exposure.
> Perhaps I need to
> take a leaf from my former government's book and sex up my patch
> descriptions a bit.
Well these two pulls came with effectively no description at all. Put
yourself in Linus's position...
--
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>
next prev parent reply other threads:[~2008-01-29 2:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 0:11 Pull request: DMA pool updates Matthew Wilcox
2008-01-29 0:11 ` Matthew Wilcox
2008-01-29 1:07 ` Andrew Morton
2008-01-29 1:07 ` Andrew Morton
2008-01-29 2:45 ` Matthew Wilcox
2008-01-29 2:45 ` Matthew Wilcox
2008-01-29 2:57 ` Andrew Morton [this message]
2008-01-29 2:57 ` Andrew Morton
2008-02-04 17:55 ` mark gross
2008-02-04 17:55 ` mark gross
-- strict thread matches above, loose matches on Subject: below --
2008-02-06 2:52 Matthew Wilcox
2008-02-06 2:52 ` Matthew Wilcox
2008-02-06 3:22 ` Andrew Morton
2008-02-06 3:22 ` Andrew Morton
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=20080128185701.752fe2c8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--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 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.