From: Alexandru Ardelean <alexandru.ardelean@analog.com>
To: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>
Cc: <lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<jic23@kernel.org>, <nuno.sa@analog.com>,
<dragos.bogdan@analog.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>
Subject: [PATCH 0/2] iio: core,buffer-dma: 2 fixes for the recent IIO buffer series
Date: Fri, 19 Feb 2021 10:58:24 +0200 [thread overview]
Message-ID: <20210219085826.46622-1-alexandru.ardelean@analog.com> (raw)
Patchset contains 2 fixes for some patches that are present in the
iio/testing branch.
No idea what's best now, either to re-send the series or to just send these
fixes on their own.
For now I chose to send the fixes on their (due to lack of time).
These could be squashed into the original.
I can also re-send the series, but not from an Analog email; since I will
not have access to it.
Alexandru Ardelean (2):
iio: core: use kfree_const in iio_free_chan_devattr_list() to free
names
iio: buffer-dma: fix type of 'i' in iio_dma_buffer_alloc_blocks()
drivers/iio/buffer/industrialio-buffer-dma.c | 3 +--
drivers/iio/industrialio-core.c | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.27.0
next reply other threads:[~2021-02-19 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 8:58 Alexandru Ardelean [this message]
2021-02-19 8:58 ` [PATCH 1/2] iio: core: use kfree_const in iio_free_chan_devattr_list() to free names Alexandru Ardelean
2021-02-22 16:01 ` Jonathan Cameron
2021-02-23 6:36 ` Alexandru Ardelean
2021-02-23 7:29 ` [PATCH v2] iio: core: use kstrdup_const/kfree_const for buffer attributes Alexandru Ardelean
2021-02-27 17:49 ` Jonathan Cameron
2021-02-19 8:58 ` [PATCH 2/2] iio: buffer-dma: fix type of 'i' in iio_dma_buffer_alloc_blocks() Alexandru Ardelean
2021-02-21 11:55 ` [PATCH 0/2] iio: core,buffer-dma: 2 fixes for the recent IIO buffer series 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=20210219085826.46622-1-alexandru.ardelean@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=dragos.bogdan@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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 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.