From: SF Markus Elfring <elfring@users.sourceforge.net>
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>
Subject: Re: iio/…: Use common error handling code
Date: Sun, 10 Dec 2017 12:33:01 +0000 [thread overview]
Message-ID: <e7292cc3-e4e2-0943-7cf9-4852cf37ef36@users.sourceforge.net> (raw)
In-Reply-To: <20171026174200.5c00b06d@archlinux>
> 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
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
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>
Subject: Re: iio/…: Use common error handling code
Date: Sun, 10 Dec 2017 13:33:01 +0100 [thread overview]
Message-ID: <e7292cc3-e4e2-0943-7cf9-4852cf37ef36@users.sourceforge.net> (raw)
In-Reply-To: <20171026174200.5c00b06d@archlinux>
> 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
next prev parent reply other threads:[~2017-12-10 12:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 20:15 [PATCH 0/2] iio/accel/stk8ba50: Fine-tuning for two function implementations SF Markus Elfring
2017-10-25 20:15 ` SF Markus Elfring
2017-10-25 20:16 ` [PATCH 1/2] iio/accel/stk8ba50: Use common error handling code in stk8ba50_probe() SF Markus Elfring
2017-10-25 20:16 ` SF Markus Elfring
2017-10-26 16:42 ` Jonathan Cameron
2017-10-26 16:42 ` Jonathan Cameron
2017-10-26 17:09 ` SF Markus Elfring
2017-10-26 17:09 ` SF Markus Elfring
2017-12-10 12:33 ` SF Markus Elfring [this message]
2017-12-10 12:33 ` iio/…: Use common error handling code SF Markus Elfring
2017-12-10 16:08 ` Jonathan Cameron
2017-12-10 16:08 ` Jonathan Cameron
2017-12-10 16:43 ` SF Markus Elfring
2017-12-10 16:43 ` SF Markus Elfring
2017-12-10 19:45 ` Jonathan Cameron
2017-10-25 20:17 ` [PATCH 2/2] iio/accel/stk8ba50: Improve unlocking of a mutex in stk8ba50_read_raw() SF Markus Elfring
2017-10-25 20:17 ` SF Markus Elfring
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=e7292cc3-e4e2-0943-7cf9-4852cf37ef36@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.