From: Jonathan Cameron <jic23@kernel.org>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: linux-iio@vger.kernel.org, grekh@linuxfoundation.org,
devel@driverdev.osuosl.org
Subject: Re: [PATCH v3] staging: iio: update TODO
Date: Sun, 1 Mar 2020 11:49:22 +0000 [thread overview]
Message-ID: <20200301114922.6117def9@archlinux> (raw)
In-Reply-To: <5e5a6fbd.1c69fb81.f08c3.4cf0@mx.google.com>
On Sat, 29 Feb 2020 19:35:45 +0530
Rohit Sarkar <rohitsarkar5398@gmail.com> wrote:
> Since there are no uses of the old GPIO API, remove the item from
> the TODO.
>
> Changelog
> v3: Remove new items added.
> v2: Add work item mentioned by Alexandru in
> https://marc.info/?l=linux-iio&m=158261515624212&w=2
Change log belongs below the --- as we don't want this info in the
git history. I've tidied up and applied to the togreg branch of iio.git
(pushed out as testing for the autobuilders to play with it).
Thanks,
Jonathan
>
> Signed-off-by: Rohit Sarkar <rohitsarkar5398@gmail.com>
> ---
> drivers/staging/iio/TODO | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/staging/iio/TODO b/drivers/staging/iio/TODO
> index 1b8ebf2c1b69..4d469016a13a 100644
> --- a/drivers/staging/iio/TODO
> +++ b/drivers/staging/iio/TODO
> @@ -1,10 +1,4 @@
> -2018-04-15
> -
> -All affected drivers:
> -Convert all uses of the old GPIO API from <linux/gpio.h> to the
> -GPIO descriptor API in <linux/gpio/consumer.h> and look up GPIO
> -lines from device tree, ACPI or board files, board files should
> -use <linux/gpio/machine.h>.
> +2020-02-25
>
>
> ADI Drivers:
next prev parent reply other threads:[~2020-03-01 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 14:05 [PATCH v3] staging: iio: update TODO Rohit Sarkar
2020-03-01 11:49 ` Jonathan Cameron [this message]
2020-03-02 4:56 ` Rohit Sarkar
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=20200301114922.6117def9@archlinux \
--to=jic23@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=grekh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
--cc=rohitsarkar5398@gmail.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;
as well as URLs for NNTP newsgroup(s).