From: Alex Elder <elder@linaro.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Johan Hovold <johan@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Alex Elder <elder@kernel.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
greybus-dev@lists.linaro.org
Subject: Re: [greybus-dev] [PATCH v4] staging: greybus: Convert uart.c from IDR to XArray
Date: Wed, 1 Sep 2021 07:09:16 -0500 [thread overview]
Message-ID: <794b3ff8-0240-ff14-8721-cdf510f52be3@linaro.org> (raw)
In-Reply-To: <6155058.TBsaUTXu4T@localhost.localdomain>
On 8/31/21 6:50 AM, Fabio M. De Francesco wrote:
> I was wrong in assuming that trivial patches to Greybus are welcome as they
> are for other drivers.
This is not a correct statement.
But as Johan pointed out, even for a trivial patch if you
must understand the consequences of what the change does.
If testing is not possible, you must work extra hard to
ensure your patch is correct.
In the first (or an early) version of your patch I pointed
out a bug. Later, I suggested
the lock might not be necessary
and asked you to either confirm
it was or explain why it was
not, but you didn't do that.
I agree that the change appeared trivial, and even sensible,
but even trivial patches must result in correct code. And
all patches should have good and complete explanations.
-Alex
next prev parent reply other threads:[~2021-09-01 12:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 9:22 [PATCH v4] staging: greybus: Convert uart.c from IDR to XArray Fabio M. De Francesco
2021-08-30 9:12 ` Johan Hovold
2021-08-30 11:10 ` Fabio M. De Francesco
2021-08-30 11:52 ` Johan Hovold
2021-08-30 12:16 ` Matthew Wilcox
2021-08-30 12:33 ` Johan Hovold
2021-08-30 13:16 ` Fabio M. De Francesco
2021-08-30 13:20 ` [greybus-dev] " Alex Elder
2021-08-31 8:07 ` Johan Hovold
2021-08-31 10:42 ` Alex Elder
2021-08-31 11:51 ` Johan Hovold
2021-08-31 11:50 ` Fabio M. De Francesco
2021-08-31 12:18 ` Johan Hovold
2021-09-01 12:09 ` Alex Elder [this message]
2021-09-01 13:56 ` Fabio M. De Francesco
2021-09-01 14:29 ` Matthew Wilcox
2021-09-01 15:39 ` Fabio M. De Francesco
2021-08-30 13:31 ` Matthew Wilcox
2021-08-31 8:16 ` Johan Hovold
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=794b3ff8-0240-ff14-8721-cdf510f52be3@linaro.org \
--to=elder@linaro.org \
--cc=elder@kernel.org \
--cc=fmdefrancesco@gmail.com \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).