From: Julia Lawall <julia.lawall@inria.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] hw_random : platform_get_irq() already prints an error
Date: Sun, 18 Oct 2020 10:53:08 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2010181249280.2759@hadrien> (raw)
In-Reply-To: <20201018054912.GA76941@fedora-thirty-three>
This should also go to the maintainers of the file, which you can find
using the script scripts/get_maintainer.pl.
hw_random is not the right way to start the subject line for this file.
Use git log --oneline to see what others have done.
On Sun, 18 Oct 2020, Nigel Christian wrote:
> coccicheck
> drivers/char//hw_random/imx-rngc.c:256:2-9: line 256 is redundant because platform_get_irq() already prints an error
The log message should be limited to at most 75 columns, because when it
ends up in git it will be slightly indented.
The log message should explain what you are doing and why, not just repeat
the output of a tool. In particular, the file and line number should not
be included in the log message, because that information is already
available in the changes below.
julia
> Signed-off-by: Nigel Christian <nigel.l.christian@gmail.com>
> ---
> drivers/char/hw_random/imx-rngc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/char/hw_random/imx-rngc.c b/drivers/char/hw_random/imx-rngc.c
> index 61c844baf26e..69f13ff1bbec 100644
> --- a/drivers/char/hw_random/imx-rngc.c
> +++ b/drivers/char/hw_random/imx-rngc.c
> @@ -253,7 +253,6 @@ static int imx_rngc_probe(struct platform_device *pdev)
>
> irq = platform_get_irq(pdev, 0);
> if (irq <= 0) {
> - dev_err(&pdev->dev, "Couldn't get irq %d\n", irq);
> return irq;
> }
>
> --
> 2.28.0
>
>
next prev parent reply other threads:[~2020-10-18 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 5:49 [PATCH] hw_random : platform_get_irq() already prints an error Nigel Christian
2020-10-18 10:53 ` Julia Lawall [this message]
2020-10-27 11:22 ` Dan Carpenter
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=alpine.DEB.2.22.394.2010181249280.2759@hadrien \
--to=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
/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.