public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "jic23@kernel.org" <jic23@kernel.org>,
	"zhongjiang@huawei.com" <zhongjiang@huawei.com>
Cc: "Popa, Stefan Serban" <StefanSerban.Popa@analog.com>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 0/2] iio: use DEFINE_DEBUGFS_ATTRIBUTE to define debugfs fops
Date: Wed, 30 Oct 2019 09:12:10 +0000	[thread overview]
Message-ID: <e32709c02e455b6a97b18f16c19e17d9658fe8f1.camel@analog.com> (raw)
In-Reply-To: <1572423581-59762-1-git-send-email-zhongjiang@huawei.com>

On Wed, 2019-10-30 at 16:19 +0800, zhong jiang wrote:
> [External]
> 

Thanks for the patches.
They look good.

> The issue is detected with the help of coccinelle.
> 
> zhong jiang (2):
>   iio: imu: adis16460: use DEFINE_DEBUGFS_ATTRIBUTE to define debugfs
>     fops
>   iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE to define debugfs
>     fops
> 
>  drivers/iio/imu/adis16400.c | 4 ++--
>  drivers/iio/imu/adis16460.c | 6 +++---
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 

      parent reply	other threads:[~2019-10-30  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  8:19 [PATCH 0/2] iio: use DEFINE_DEBUGFS_ATTRIBUTE to define debugfs fops zhong jiang
2019-10-30  8:19 ` [PATCH 1/2] iio: imu: adis16460: " zhong jiang
2019-10-30  9:13   ` Ardelean, Alexandru
2019-10-30  9:33     ` zhong jiang
2019-11-03 11:25       ` Jonathan Cameron
2019-11-04 11:12         ` Ardelean, Alexandru
2019-10-30  8:19 ` [PATCH 2/2] iio: imu: adis16400: " zhong jiang
2019-10-30  9:13   ` Ardelean, Alexandru
2019-10-30  9:12 ` Ardelean, Alexandru [this message]

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=e32709c02e455b6a97b18f16c19e17d9658fe8f1.camel@analog.com \
    --to=alexandru.ardelean@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=StefanSerban.Popa@analog.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhongjiang@huawei.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