All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corentin LABBE <clabbe@baylibre.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	heiko@sntech.de, linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] crypto: Remove surplus dev_err() when using platform_get_irq()
Date: Fri, 4 Nov 2022 08:30:42 +0100	[thread overview]
Message-ID: <Y2S/osIvNJzs1jU5@Red> (raw)
In-Reply-To: <20221101021751.89362-1-yang.lee@linux.alibaba.com>

Le Tue, Nov 01, 2022 at 10:17:51AM +0800, Yang Li a écrit :
> There is no need to call the dev_err() function directly to print a
> custom message when handling an error from either the platform_get_irq()
> or platform_get_irq_byname() functions as both are going to display an
> appropriate error message in case of a failure.
> 
> ./drivers/crypto/rockchip/rk3288_crypto.c:351:2-9: line 351 is
> redundant because platform_get_irq() already prints an error
> 
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2677
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---

Hello

The subject should start by "crypto: rockchip:"

Otherwise it is:
Acked-by: Corentin Labbe <clabbe@baylibre.com>

Thanks

WARNING: multiple messages have this Message-ID (diff)
From: Corentin LABBE <clabbe@baylibre.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	heiko@sntech.de, linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] crypto: Remove surplus dev_err() when using platform_get_irq()
Date: Fri, 4 Nov 2022 08:30:42 +0100	[thread overview]
Message-ID: <Y2S/osIvNJzs1jU5@Red> (raw)
In-Reply-To: <20221101021751.89362-1-yang.lee@linux.alibaba.com>

Le Tue, Nov 01, 2022 at 10:17:51AM +0800, Yang Li a écrit :
> There is no need to call the dev_err() function directly to print a
> custom message when handling an error from either the platform_get_irq()
> or platform_get_irq_byname() functions as both are going to display an
> appropriate error message in case of a failure.
> 
> ./drivers/crypto/rockchip/rk3288_crypto.c:351:2-9: line 351 is
> redundant because platform_get_irq() already prints an error
> 
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2677
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---

Hello

The subject should start by "crypto: rockchip:"

Otherwise it is:
Acked-by: Corentin Labbe <clabbe@baylibre.com>

Thanks

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Corentin LABBE <clabbe@baylibre.com>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	heiko@sntech.de, linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] crypto: Remove surplus dev_err() when using platform_get_irq()
Date: Fri, 4 Nov 2022 08:30:42 +0100	[thread overview]
Message-ID: <Y2S/osIvNJzs1jU5@Red> (raw)
In-Reply-To: <20221101021751.89362-1-yang.lee@linux.alibaba.com>

Le Tue, Nov 01, 2022 at 10:17:51AM +0800, Yang Li a écrit :
> There is no need to call the dev_err() function directly to print a
> custom message when handling an error from either the platform_get_irq()
> or platform_get_irq_byname() functions as both are going to display an
> appropriate error message in case of a failure.
> 
> ./drivers/crypto/rockchip/rk3288_crypto.c:351:2-9: line 351 is
> redundant because platform_get_irq() already prints an error
> 
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2677
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---

Hello

The subject should start by "crypto: rockchip:"

Otherwise it is:
Acked-by: Corentin Labbe <clabbe@baylibre.com>

Thanks

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-04  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  2:17 [PATCH -next] crypto: Remove surplus dev_err() when using platform_get_irq() Yang Li
2022-11-01  2:17 ` Yang Li
2022-11-01  2:17 ` Yang Li
2022-11-04  7:30 ` Corentin LABBE [this message]
2022-11-04  7:30   ` Corentin LABBE
2022-11-04  7:30   ` Corentin LABBE

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=Y2S/osIvNJzs1jU5@Red \
    --to=clabbe@baylibre.com \
    --cc=abaci@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=heiko@sntech.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=yang.lee@linux.alibaba.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.