public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 12:49:44 -0400	[thread overview]
Message-ID: <20150703164944.GG9456@thunk.org> (raw)
In-Reply-To: <5596A42F.60901@gmail.com>

On Fri, Jul 03, 2015 at 11:03:11AM -0400, nick wrote:
> 
> 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).

I am trying to determine if you have changed.  Your comment justifying
your lack of testing because "it's hard to test" is ample evidence
that you have *not* changed.

Simply coming up with a commit that happens to be correct is a
necessary, but not sufficient condition.  Especially when you feel
that you need to send dozens of low-value patches and hope that one of
them is correct, and then use that as "proof".  It's the attitude
which is problem, not whether or not you can manage to come up with a
correct patch.

I've described to you what you need to do in order to demonstrate that
you have the attitude and inclinations in order to be a kernel
developer that a maintainer can trust as being capable of authoring a
patch that doesn't create more problems than whatever benefits it
might have.  I respectfully ask that you try to work on that, and stop
bothering me (and everyone else).

Best regards,

						- Ted

  parent reply	other threads:[~2015-07-03 16:50 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 [this message]
     [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=20150703164944.GG9456@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