From: nick <xerofoify@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
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, 03 Jul 2015 11:03:11 -0400 [thread overview]
Message-ID: <5596A42F.60901@gmail.com> (raw)
In-Reply-To: <20150703150117.GA3688@dhcp22.suse.cz>
On 2015-07-03 11:01 AM, Michal Hocko wrote:
> 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.
>
Michael,
The reason I am doing this is Ted is trying to find a bug that I fixed in order to prove
to Greg Kroah Hartman I have changed. Otherwise I would be pushing this through the
drm maintainer(s).
Nick
--
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:[~2015-07-03 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 18:27 Nicholas Krause
2015-07-02 7:26 ` Michal Hocko
2015-07-02 16:03 ` Theodore Ts'o
2015-07-02 16:08 ` nick
2015-07-02 17:07 ` nick
2015-07-03 14:46 ` Theodore Ts'o
2015-07-03 14:54 ` nick
2015-07-03 15:01 ` Michal Hocko
2015-07-03 15:03 ` nick [this message]
2015-07-03 16:49 ` Theodore Ts'o
2015-07-03 16:52 ` nick
2015-07-03 18:45 ` Theodore Ts'o
2015-07-03 19:49 ` nick
2015-07-03 20:13 ` Mel Gorman
2015-07-03 20:47 ` nick
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=5596A42F.60901@gmail.com \
--to=xerofoify@gmail.com \
--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=mhocko@suse.cz \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
/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