From: "Theodore Ts'o" <tytso@mit.edu>
To: nick <xerofoify@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>,
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 14:45:02 -0400 [thread overview]
Message-ID: <20150703184501.GJ9456@thunk.org> (raw)
In-Reply-To: <5596BDB6.5060708@gmail.com>
On Fri, Jul 03, 2015 at 12:52:06PM -0400, nick wrote:
> I agree with you 100 percent. The reason I can't test this is I don't have the
> hardware otherwise I would have tested it by now.
Then don't send the patch out. Work on some other piece of part of
the kernel, or better yet, some other userspace code where testing is
easier. It's really quite simple.
You don't have the technical skills, or at this point, the reputation,
to send patches without tesitng them first. The fact that sometimes
people like Linus will send out a patch labelled with "COMPLETELY
UNTESTED", is because he's skilled and trusted enough that he can get
away with it. You have neither of those advantages.
Best regards,
- Ted
next prev parent reply other threads:[~2015-07-03 18:45 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 ` [PATCH] mm:Make the function zap_huge_pmd bool 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
[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 [this message]
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=20150703184501.GJ9456@thunk.org \
--to=tytso@mit.edu \
--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=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