From: Michal Hocko <mhocko@suse.cz>
To: nick <xerofoify@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
akpm@linux-foundation.org, mgorman@suse.de,
n-horiguchi@ah.jp.nec.com, sasha.levin@oracle.com,
Yalin.Wang@sonymobile.com, jmarchan@redhat.com,
kirill@shutemov.name, rientjes@google.com, vbabka@suse.cz,
aneesh.kumar@linux.vnet.ibm.com, ebru.akagunduz@gmail.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm:Make the function zap_huge_pmd bool
Date: Fri, 3 Jul 2015 17:01:17 +0200 [thread overview]
Message-ID: <20150703150117.GA3688@dhcp22.suse.cz> (raw)
In-Reply-To: <5596A20F.6010509@gmail.com>
On Fri 03-07-15 10:54:07, nick wrote:
[...]
> Did you even look at the other patches I send you. Here is a bug fix
> for the gma500 driver code that someone else stated is right but I
> don't have the hardware so it's difficult to test.
This is really annoying. Please stop it! Ted is not maintainer of the
code you are trying to patch. There is absolutely no reason to try to
persuate him or try to push it through him. Go and try to "sell" your
patch to the maintainers of the said code.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2015-07-03 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435775277-27381-1-git-send-email-xerofoify@gmail.com>
2015-07-02 7:26 ` Michal Hocko
2015-07-02 16:03 ` Theodore Ts'o
[not found] ` <55956204.2060006@gmail.com>
2015-07-03 14:46 ` Theodore Ts'o
[not found] ` <5596A20F.6010509@gmail.com>
2015-07-03 15:01 ` Michal Hocko [this message]
[not found] ` <5596A42F.60901@gmail.com>
2015-07-03 16:49 ` Theodore Ts'o
[not found] ` <5596BDB6.5060708@gmail.com>
2015-07-03 18:45 ` Theodore Ts'o
2015-07-03 20:13 ` Mel Gorman
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=20150703150117.GA3688@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=Yalin.Wang@sonymobile.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ebru.akagunduz@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jmarchan@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=xerofoify@gmail.com \
/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
all inboxes | Powered by JetHome®