Linux kernel staging patches
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: <shao.mingyin@zte.com.cn>
Cc: <lars@metafoo.de>, <yang.yang29@zte.com.cn>,
	<xu.xin16@zte.com.cn>, <ye.xingchen@zte.com.cn>,
	<feng.wei8@zte.com.cn>, <michael.hennerich@analog.com>,
	<gregkh@linuxfoundation.org>, <linux-iio@vger.kernel.org>,
	<linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: iio: adt7316: replace irqd_get_trigger_type with irq_get_trigger_type
Date: Thu, 27 Mar 2025 15:14:15 +0000	[thread overview]
Message-ID: <20250327151415.791f65e9@jic23-huawei> (raw)
In-Reply-To: <202503270957044481PK0Xb23i08BgwkodLtEC@zte.com.cn>

On Thu, 27 Mar 2025 09:57:04 +0800 (CST)
<shao.mingyin@zte.com.cn> wrote:

> From: Feng Wei <feng.wei8@zte.com.cn>
> 
> Convert irqd_get_trigger_type(irq_get_irq_data(irq)) cases to the more
> simple irq_get_trigger_type(irq).
> 
> Signed-off-by: Feng Wei <feng.wei8@zte.com.cn>
> Signed-off-by: Shao Mingyin <shao.mingyin@zte.com.cn>
Applied.
> ---
>  drivers/staging/iio/addac/adt7316.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/addac/adt7316.c b/drivers/staging/iio/addac/adt7316.c
> index f4260786d50a..16f30c4f1aa0 100644
> --- a/drivers/staging/iio/addac/adt7316.c
> +++ b/drivers/staging/iio/addac/adt7316.c
> @@ -1794,7 +1794,7 @@ static int adt7316_setup_irq(struct iio_dev *indio_dev)
>  	struct adt7316_chip_info *chip = iio_priv(indio_dev);
>  	int irq_type, ret;
> 
> -	irq_type = irqd_get_trigger_type(irq_get_irq_data(chip->bus.irq));
> +	irq_type = irq_get_trigger_type(chip->bus.irq);
> 
>  	switch (irq_type) {
>  	case IRQF_TRIGGER_HIGH:


      reply	other threads:[~2025-03-27 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27  1:57 [PATCH] staging: iio: adt7316: replace irqd_get_trigger_type with irq_get_trigger_type shao.mingyin
2025-03-27 15:14 ` Jonathan Cameron [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=20250327151415.791f65e9@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=feng.wei8@zte.com.cn \
    --cc=gregkh@linuxfoundation.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=michael.hennerich@analog.com \
    --cc=shao.mingyin@zte.com.cn \
    --cc=xu.xin16@zte.com.cn \
    --cc=yang.yang29@zte.com.cn \
    --cc=ye.xingchen@zte.com.cn \
    /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