From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Estner <michaelestner@web.de>
Cc: michaelestner@web.de, Lee Jones <lee.jones@linaro.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] avoid crashing the kernel
Date: Sun, 26 Sep 2021 10:38:57 +0200 [thread overview]
Message-ID: <7598246.TGqz6ispmn@localhost.localdomain> (raw)
In-Reply-To: <20210925200433.8329-1-michaelestner@web.de>
On Saturday, September 25, 2021 10:04:30 PM CEST Michael Estner wrote:
> To avoid chrashing the kernel I use WARN_ON instead.
"[] I use WARN_ON instead". Instead of what?
Changelogs must be self-contained. I had to look at the diff to complete that
sentence in my mind.
Please don't ask reviewers to go back and forth commit messages and code in
order to get the whole picture.
However, my suggestion is only about the formal aspects of proper patch
construction. The actual top priority is to properly solve this problem using
the tips provided by Greg K-H with his review.
Thanks,
Fabio
P.S.: "chrashing" => "crashing".
>
> Signed-off-by: Michael Estner <michaelestner@web.de>
> ---
> drivers/staging/most/i2c/i2c.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/most/i2c/i2c.c b/drivers/staging/most/i2c/
i2c.c
> index 7042f10887bb..e1edd892f9fd 100644
> --- a/drivers/staging/most/i2c/i2c.c
> +++ b/drivers/staging/most/i2c/i2c.c
> @@ -68,7 +68,7 @@ static int configure_channel(struct most_interface
*most_iface,
> struct hdm_i2c *dev = to_hdm(most_iface);
> unsigned int delay, pr;
>
> - BUG_ON(ch_idx < 0 || ch_idx >= NUM_CHANNELS);
> + WARN_ON(ch_idx < 0 || ch_idx >= NUM_CHANNELS);
next prev parent reply other threads:[~2021-09-26 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 20:04 [PATCH] avoid crashing the kernel Michael Estner
2021-09-26 6:51 ` Greg Kroah-Hartman
2021-09-26 8:38 ` Fabio M. De Francesco [this message]
2021-09-27 13:15 ` 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=7598246.TGqz6ispmn@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=michaelestner@web.de \
/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