[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170521095654.bzpaa2obfszrajgb@ninjato>
Date: Sun, 21 May 2017 11:56:54 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-mm@...ck.org, Dan Streetman <ddstreet@...e.org>,
Seth Jennings <sjenning@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: zswap: Delete an error message for a failed memory allocation in
zswap_dstmem_prepare()
Markus,
> > Markus, can you please stop CCing me on every of those patches?
>
> Yes, of course.
Thanks!
> >> Link: http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
>
> Did I interpret any information from your presentation slides in an
> inappropriate way?
Have you read my LWN article "Best practices for a big patch series"?
https://lwn.net/Articles/585782/
> > And why do you create a patch for every occasion in the same file?
>
> This can occasionally happen when I am more unsure about the change acceptance
> for a specific place.
Why were you unsure here?
> This can also happen as a side effect if such a source code search pattern
> will point hundreds of places out for further software development considerations.
> How would you prefer to clarify the remaining update candidates there?
Maybe the article mentioned can provice further guidance?
Have a nice sunday,
Wolfram
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists