From: Christoph Hellwig <hch@lst.de>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: iommu@lists.linux-foundation.org, kasan-dev@googlegroups.com,
Alexander Potapenko <glider@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
Daniel Mentz <danielmentz@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Philipp Reisner <philipp.reisner@linbit.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/2] lib: Adjustments for 11 function implementations
Date: Sun, 8 Oct 2017 10:42:24 +0200 [thread overview]
Message-ID: <20171008084224.GA12482@lst.de> (raw)
In-Reply-To: <9a81d82d-fb1b-38d3-1dbf-31e6bf4ff677@users.sourceforge.net>
Please stop sending this crap. It's a move from one preference to
another slightly different one. You are free to apply your preference
if you do a major overhaul of some code (subject to maintainer approval),
but without that they simply are churn.
NAK for both patches.
next prev parent reply other threads:[~2017-10-08 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 17:46 [PATCH 0/2] lib: Adjustments for 11 function implementations SF Markus Elfring
2017-10-07 17:48 ` [PATCH 1/2] lib/test: Delete five error messages for a failed memory allocation SF Markus Elfring
2017-10-09 6:24 ` Michal Hocko
2017-10-07 17:50 ` [PATCH 2/2] lib: Improve a size determination in seven functions SF Markus Elfring
2017-10-08 10:49 ` Geert Uytterhoeven
2017-10-08 8:42 ` Christoph Hellwig [this message]
2017-10-08 14:21 ` [PATCH 0/2] lib: Adjustments for 11 function implementations Andy Shevchenko
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=20171008084224.GA12482@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=danielmentz@google.com \
--cc=dvyukov@google.com \
--cc=elfring@users.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mcgrof@kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.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