From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
"lorenzo.bianconi83@gmail.com" <lorenzo.bianconi83@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"lars@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH 2/3] iio: make use of iio_device_attach_kfifo_buffer() where straightforward
Date: Tue, 7 Apr 2020 09:28:50 +0000 [thread overview]
Message-ID: <a8fd15498fc71fb1d6a02e463aeaade44574c06a.camel@analog.com> (raw)
In-Reply-To: <36669e0f-c41c-5cc8-7218-be5cad5cf8a5@web.de>
On Tue, 2020-04-07 at 11:26 +0200, Markus Elfring wrote:
> [External]
>
> How do you think about a patch subject like “iio: Increase use of
> iio_device_attach_kfifo_buffer()”?
>
>
> > This change does that.
>
> I suggest to improve also this commit message.
>
> * Would you like to consider a wording like “Convert a specific function call
> combination to a better programming interface.”?
>
> * Do you imagine any more software fine-tuning because of related
> collateral evolution?
>
I'll see.
This patchset is kind of stopped.
Will need a rework for it.
> Regards,
> Markus
next prev parent reply other threads:[~2020-04-07 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 9:26 Markus Elfring
2020-04-07 9:28 ` Ardelean, Alexandru [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-01 12:59 [PATCH 1/3] iio: kfifo: add iio_device_attach_kfifo_buffer() helper Alexandru Ardelean
2020-04-01 12:59 ` [PATCH 2/3] iio: make use of iio_device_attach_kfifo_buffer() where straightforward Alexandru Ardelean
2020-04-05 10:44 ` Jonathan Cameron
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=a8fd15498fc71fb1d6a02e463aeaade44574c06a.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Markus.Elfring@web.de \
--cc=devel@driverdev.osuosl.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--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
all inboxes | Powered by JetHome®