From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Nuno Sá" <nuno.sa@analog.com>, linux-iio@vger.kernel.org
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH 3/3] iio: buffer: fix coding style warnings
Date: Mon, 27 Feb 2023 08:39:37 +0100 [thread overview]
Message-ID: <b0e25164a712c816f5dc227b5da21c653c57c4f1.camel@gmail.com> (raw)
In-Reply-To: <20230216101452.591805-4-nuno.sa@analog.com>
On Thu, 2023-02-16 at 11:14 +0100, Nuno Sá wrote:
> Just cosmetics. No functional change intended...
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> ---
> drivers/iio/industrialio-buffer.c | 98 +++++++++++++++--------------
> --
> 1 file changed, 49 insertions(+), 49 deletions(-)
>
> diff --git a/drivers/iio/industrialio-buffer.c
> b/drivers/iio/industrialio-buffer.c
> index 7e7ee307a3f7..e02a4cb3d491 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
>
Hi Jonathan,
I noticed this one was left behind but I just waited another week to
see what happened... Is there any special reason for not taking this
one?
- Nuno Sá
next prev parent reply other threads:[~2023-02-27 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:14 [PATCH 0/3] output buffer write fops fixes Nuno Sá
2023-02-16 10:14 ` [PATCH 1/3] iio: buffer: correctly return bytes written in output buffers Nuno Sá
2023-02-16 13:40 ` Lars-Peter Clausen
2023-02-18 14:07 ` Jonathan Cameron
2023-02-16 10:14 ` [PATCH 2/3] iio: buffer: make sure O_NONBLOCK is respected Nuno Sá
2023-02-16 14:00 ` Lars-Peter Clausen
2023-02-18 14:08 ` Jonathan Cameron
2023-02-16 10:14 ` [PATCH 3/3] iio: buffer: fix coding style warnings Nuno Sá
2023-02-16 14:07 ` Lars-Peter Clausen
2023-02-27 7:39 ` Nuno Sá [this message]
2023-03-04 13:03 ` Jonathan Cameron
2023-05-01 16:15 ` 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=b0e25164a712c816f5dc227b5da21c653c57c4f1.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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