From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>,
"ardeleanalex@gmail.com" <ardeleanalex@gmail.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [RFC][PATCH] iio: buffer: Don't allow buffers without any channels enabled to be activated
Date: Sat, 21 Mar 2020 23:44:57 +0200 [thread overview]
Message-ID: <CAHp75VecU4Y3Jku0hAgh4MuTCocbG1rGKaDsHB3QnjGeu1HiQA@mail.gmail.com> (raw)
In-Reply-To: <20200321182144.4c3226ee@archlinux>
On Sat, Mar 21, 2020 at 8:22 PM Jonathan Cameron <jic23@kernel.org> wrote:
> On Fri, 20 Mar 2020 11:16:12 +0000
> "Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> > On Fri, 2020-03-20 at 11:55 +0100, Lars-Peter Clausen wrote:
> > > On 3/20/20 11:40 AM, Alexandru Ardelean wrote:
> > > > + if (bitmap_empty(insert_buffer->scan_mask,
> > > > + indio_dev->masklength)) {
I guess it's much better to put on one line (despite possible over 80 limit).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-03-21 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 10:40 [RFC][PATCH] iio: buffer: Don't allow buffers without any channels enabled to be activated Alexandru Ardelean
2020-03-20 10:55 ` Lars-Peter Clausen
2020-03-20 11:16 ` Ardelean, Alexandru
2020-03-21 18:21 ` Jonathan Cameron
2020-03-21 21:44 ` Andy Shevchenko [this message]
2020-03-25 8:17 ` Ardelean, Alexandru
2020-03-25 8:23 ` Ardelean, Alexandru
2020-03-25 10:01 ` [PATCH v2] " Alexandru Ardelean
2020-03-25 10:12 ` Ardelean, Alexandru
2020-03-25 15:57 ` Andy Shevchenko
2020-03-26 7:42 ` Ardelean, Alexandru
2020-03-26 7:44 ` Lars-Peter Clausen
2020-03-26 7:46 ` Ardelean, Alexandru
2020-03-26 9:30 ` [PATCH v3] " Alexandru Ardelean
2020-03-28 13:13 ` 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=CAHp75VecU4Y3Jku0hAgh4MuTCocbG1rGKaDsHB3QnjGeu1HiQA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=alexandru.Ardelean@analog.com \
--cc=ardeleanalex@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
/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).