From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=SYmy=DG=users.sourceforge.net=elfring@kernel.org>
Subject: =?UTF-8?Q?Re:_iio/=e2=80=a6:_Use_common_error_handling_code?=
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org,
 Hans de Goede <hdegoede@redhat.com>, Hartmut Knaack <knaack.h@gmx.de>,
 Lars-Peter Clausen <lars@metafoo.de>,
 Peter Meerwald-Stadler <pmeerw@pmeerw.net>
References: <5ab7e200-2dea-63e2-06db-0e185f563d16@users.sourceforge.net>
 <0f26a13b-7bbf-525b-a864-8aa8e13c3aef@users.sourceforge.net>
 <20171026174200.5c00b06d@archlinux>
From: SF Markus Elfring <elfring@users.sourceforge.net>
Message-ID: <e7292cc3-e4e2-0943-7cf9-4852cf37ef36@users.sourceforge.net>
Date: Sun, 10 Dec 2017 13:33:01 +0100
MIME-Version: 1.0
In-Reply-To: <20171026174200.5c00b06d@archlinux>
Content-Type: text/plain; charset=utf-8
List-ID: <linux-iio@vger.kernel.org>

> Again, a general kernel development rule is to float only one
> patch of a given type until you have had feedback on it.

A few weeks later …


> As I said in one of the other patches, I always reply to all
> patches I am rejecting so that anyone coming across them later
> on their own from an archive or similar can immediately see the
> reasons why they are a bad idea without having to know the mailing
> list context.

Can you get into the mood to clarify any remaining change possibilities
a bit more?

Regards,
Markus