From: Chen Gang <gang.chen@asianux.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>, Mel Gorman <mgorman@suse.de>,
sasha.levin@oracle.com, linux@rasmusvillemoes.dk,
kosaki.motohiro@jp.fujitsu.com,
Wu Fengguang <fengguang.wu@intel.com>,
lczerner@redhat.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm/readahead.c: need always return 0 when system call readahead() succeeds
Date: Thu, 17 Oct 2013 10:37:00 +0800 [thread overview]
Message-ID: <525F4D4C.2090002@asianux.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310161918260.21167@chino.kir.corp.google.com>
On 10/17/2013 10:21 AM, David Rientjes wrote:
> On Thu, 17 Oct 2013, Chen Gang wrote:
>
>>> I think your patches should be acked before being merged into linux-next,
>>> Hugh just had to revert another one that did affect Linus's tree in
>>> 1ecfd533f4c5 ("mm/mremap.c: call pud_free() after fail calling
>>> pmd_alloc()"). I had to revert your entire series of mpol_to_str()
>>> changes in -mm. It's getting ridiculous and a waste of other people's
>>> time.
>>>
>>
>> If always get no reply, what to do, next?
>>
>
> If nobody ever acks your patches, they probably aren't that important. At
> the very least, something that nobody has looked at shouldn't be included
> if it's going to introduce a regression.
>
At least, that is not quite polite.
And when get conclusion, please based on the proofs: "is it necessary to
list them to check whether they are 'important' or not"?
>> But all together, I welcome you to help ack/nack my patches for mm
>> sub-system (although I don't know your ack/nack whether have effect or not).
>>
>
> If it touches mm, then there is someone on this list who can ack it and
> you can cc them by looking at the output of scripts/get_maintainer.pl. If
> nobody is interested in it, or if it doesn't do anything important, nobody
> is going to spend their time reviewing it.
>
Of cause, every time, I send patch according to "scripts/get_maintainer.pl".
So again: "is it necessary to list them to check whether they are
'important' or not?"
> I'm not going to continue this thread, the patch in question has been
> removed from -mm so I have no further interest in discussing it.
>
>
OK, end discussing if you no reply.
Thanks.
--
Chen Gang
--
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:[~2013-10-17 2:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 3:31 [PATCH] mm: readahead: return the value which force_page_cache_readahead() returns Chen Gang
2013-08-20 23:16 ` Andrew Morton
2013-08-21 2:29 ` Chen Gang
2013-08-21 2:41 ` [PATCH v2] m: " Chen Gang
2013-09-03 5:27 ` Chen Gang
2013-09-17 22:56 ` Andrew Morton
2013-09-18 1:59 ` Chen Gang
2013-10-15 8:06 ` [PATCH] mm/readahead.c: need always return 0 when system call readahead() succeeds Chen Gang
2013-10-15 12:12 ` [PATCH] mm/madvise.c: return 0 instead of read bytes after force_page_cache_readahead() succeeds Chen Gang
2013-10-16 23:06 ` [PATCH] mm/readahead.c: need always return 0 when system call readahead() succeeds David Rientjes
2013-10-17 0:57 ` Chen Gang
2013-10-17 1:17 ` David Rientjes
2013-10-17 1:32 ` Chen Gang
2013-10-17 2:21 ` David Rientjes
2013-10-17 2:37 ` Chen Gang [this message]
2013-10-17 2:40 ` Chen Gang
2013-10-15 8:20 ` [PATCH v2] m: readahead: return the value which force_page_cache_readahead() returns Chen Gang
2013-10-17 9:56 ` Chen Gang
2013-11-04 5:31 ` [PATCH v3] mm: readahead: check return " Chen Gang
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=525F4D4C.2090002@asianux.com \
--to=gang.chen@asianux.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lczerner@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mgorman@suse.de \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox