All of lore.kernel.org
 help / color / mirror / Atom feed
From: nick <xerofoify@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, 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: Thu, 02 Jul 2015 12:08:36 -0400	[thread overview]
Message-ID: <55956204.2060006@gmail.com> (raw)
In-Reply-To: <20150702160341.GC9456@thunk.org>



On 2015-07-02 12:03 PM, Theodore Ts'o wrote:
> On Thu, Jul 02, 2015 at 09:26:21AM +0200, Michal Hocko wrote:
>> On Wed 01-07-15 14:27:57, Nicholas Krause wrote:
>>> This makes the function zap_huge_pmd have a return type of bool
>>> now due to this particular function always returning one or zero
>>> as its return value.
>>
>> How does this help anything? IMO this just generates a pointless churn
>> in the code without a good reason.
> 
> Hi Michal,
> 
> My recommendation is to ignore patches sent by Nick.  In my experience
> he doesn't understand code before trying to make mechanical changes,
> and very few of his patches add any new value, and at least one that
> he tried to send me just 2 weeks or so ago (cherry-picked to try to
> "prove" why he had turned over a new leaf, so that I would support the
> removal of his e-mail address from being blacklisted on
> vger.kernel.org) was buggy, and when I asked him some basic questions
> about what the code was doing, it was clear he had no clue how the
> seq_file abstraction worked.  This didn't stop him from trying to
> patch the code, and if he had tested it, it would have crashed and
> burned instantly.
> 
> Of course, do whatevery you want, but IMHO it's not really not worth
> your time to deal with his patches, and if you reply, most people
> won't see his original e-mail since the vger.kernel.org blacklist is
> still in effect.
> 
> Regards,
> 
> 						- Ted
> 
Ted,
I looked into that patch further and would were correct it was wrong.
However here is a bug fix for the drm driver code that somebody else
stated was right but haven gotten a reply to from the maintainer and
have tried resending.
Nick

  reply	other threads:[~2015-07-02 16:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 18:27 [PATCH] mm:Make the function zap_huge_pmd bool Nicholas Krause
2015-07-02  7:26 ` Michal Hocko
2015-07-02  7:26   ` Michal Hocko
2015-07-02 16:03   ` Theodore Ts'o
2015-07-02 16:03     ` Theodore Ts'o
2015-07-02 16:08     ` nick [this message]
2015-07-02 17:07       ` nick
2015-07-03 14:46       ` Theodore Ts'o
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:01             ` Michal Hocko
2015-07-03 15:03             ` nick
2015-07-03 16:49               ` Theodore Ts'o
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 18:45                     ` Theodore Ts'o
2015-07-03 19:49                     ` nick
2015-07-03 20:13                     ` Mel Gorman
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=55956204.2060006@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.