From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Wolfram Sang <wsa@the-dreams.de>, linux-mm@kvack.org
Cc: Dan Streetman <ddstreet@ieee.org>,
Seth Jennings <sjenning@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare()
Date: Sun, 21 May 2017 09:40:06 +0000 [thread overview]
Message-ID: <7bd4b458-6f6e-416b-97a9-b1b3d0840144@users.sourceforge.net> (raw)
In-Reply-To: <20170521084734.GB1456@katana>
> Markus, can you please stop CCing me on every of those patches?
Yes, of course.
>> 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?
> 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.
> Do you want to increase your patch count?
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?
Regards,
Markus
next prev parent reply other threads:[~2017-05-21 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:23 [PATCH 0/3] zswap: Adjustments for three function implementations SF Markus Elfring
2017-05-21 8:25 ` [PATCH 1/3] zswap: Delete an error message for a failed memory allocation in zswap_pool_create() SF Markus Elfring
2017-05-30 23:18 ` Dan Streetman
2017-05-21 8:26 ` [PATCH 2/3] zswap: Improve a size determination in zswap_frontswap_init() SF Markus Elfring
2017-05-30 23:19 ` Dan Streetman
2017-05-21 8:27 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare() SF Markus Elfring
2017-05-21 8:47 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepar Wolfram Sang
2017-05-21 9:40 ` SF Markus Elfring [this message]
2017-05-21 9:56 ` zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepare() Wolfram Sang
2017-05-21 10:12 ` Using best practices for big software change possibilities SF Markus Elfring
2017-05-21 10:27 ` Wolfram Sang
2017-05-21 10:45 ` SF Markus Elfring
2017-05-30 23:20 ` [PATCH 3/3] zswap: Delete an error message for a failed memory allocation in zswap_dstmem_prepar Dan Streetman
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=7bd4b458-6f6e-416b-97a9-b1b3d0840144@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ddstreet@ieee.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjenning@redhat.com \
--cc=wsa@the-dreams.de \
/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