From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: iio: Adjust checks for null pointers in six functions
Date: Sun, 25 Sep 2016 19:45:40 +0200 [thread overview]
Message-ID: <3b681d28-c3f9-7d54-f3f3-eccb51479356@users.sourceforge.net> (raw)
In-Reply-To: <e107c883-eff6-2002-46ba-05e691e142d1@kernel.org>
> Also, I'm afraid I don't care enough to put the time in for this one.
It's a pity.
>> Does the tool "Git" let you also apply this update step before
>> the other suggestions?
> It rarely copes with this sort of reordering as it doesn't have
> the semantic knowledge of what matters in the other patches.
I assume that the involved software developers got a specific impression
about the discussed patch series for this software module so that a few
relevant dependencies became clearer eventually.
I proposed some update steps where I chose a specific patch granularity
once more. So I imagine that a bit of variation in the patch order
could be supported already.
Will it be possible to apply also this one a bit later just because
the patch hunk contexts might be still valid in the (near) future?
Regards,
Markus
next prev parent reply other threads:[~2016-09-25 17:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566ABCD9.1060404@users.sourceforge.net>
2015-12-26 13:04 ` [PATCH] iio: qcom-spmi-vadc: One check less in vadc_measure_ref_points() after error detection SF Markus Elfring
2016-01-02 18:28 ` Jonathan Cameron
2016-09-24 6:22 ` [PATCH 0/7] iio: Fine-tuning for several function implementations SF Markus Elfring
2016-09-24 6:24 ` [PATCH 1/7] iio: Use kmalloc_array() in iio_scan_mask_set() SF Markus Elfring
2016-09-24 15:36 ` Jonathan Cameron
2016-09-24 16:18 ` SF Markus Elfring
2016-09-24 16:36 ` Jonathan Cameron
2016-09-24 6:25 ` [PATCH 2/7] iio: Rename a jump label in iio_buffer_store_watermark() SF Markus Elfring
2016-09-24 15:32 ` Jonathan Cameron
2016-09-24 19:21 ` SF Markus Elfring
2016-09-25 8:45 ` Jonathan Cameron
2016-09-25 13:00 ` SF Markus Elfring
2016-09-25 14:23 ` Jonathan Cameron
2016-09-25 15:17 ` SF Markus Elfring
2016-09-25 16:49 ` Jonathan Cameron
2016-09-25 17:31 ` SF Markus Elfring
2016-09-24 6:26 ` [PATCH 3/7] iio: Rename a jump label in iio_buffer_store_enable() SF Markus Elfring
2016-09-24 6:28 ` [PATCH 4/7] iio: Rename a jump label in iio_buffer_write_length() SF Markus Elfring
2016-09-24 6:29 ` [PATCH 5/7] iio: Rename a jump label in iio_scan_el_ts_store() SF Markus Elfring
2016-09-24 6:30 ` [PATCH 6/7] iio: Rename a jump label in iio_scan_el_store() SF Markus Elfring
2016-09-24 6:31 ` [PATCH 7/7] iio: Adjust checks for null pointers in six functions SF Markus Elfring
2016-09-25 14:24 ` Jonathan Cameron
2016-09-25 14:44 ` SF Markus Elfring
2016-09-25 16:51 ` Jonathan Cameron
2016-09-25 17:45 ` SF Markus Elfring [this message]
2016-09-25 18:15 ` Al Viro
2016-09-25 19:30 ` 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=3b681d28-c3f9-7d54-f3f3-eccb51479356@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=jic23@kernel.org \
--cc=julia.lawall@lip6.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).