From: Mary Strodl <mstrodl@freedom.csh.rit.edu>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Mary Strodl <mstrodl@csh.rit.edu>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
urezki@gmail.com, hch@infradead.org, linux-mm@kvack.org,
lee@kernel.org, linux-i2c@vger.kernel.org,
s.hauer@pengutronix.de, christian.gmeiner@gmail.com
Subject: Re: [PATCH v3 1/2] x86: Add basic support for the Congatec CGEB BIOS interface
Date: Mon, 12 Aug 2024 07:45:00 -0400 [thread overview]
Message-ID: <Zrn1vNgn7q5npxU7@freedom.csh.rit.edu> (raw)
In-Reply-To: <ft2lkhphs25xmvmpbf5ssuafdnmkdnq5j7uqb6jjy6ewnwzn2l@6uoad3ii3h4m>
Hi Andi,
On Fri, Aug 09, 2024 at 01:46:44AM +0100, Andi Shyti wrote:
> If you use the SPDX identifier you don't need to mention the GPL
> parts here.
Gotcha, will remove the GPL blurb in next series
> the include files are normally alphabetically sorted.
Will-do!
> I'm counting too many global variables here and too many global
> structure definitions. It might get a bit hard to follow.
>
> I'd suggest to simplify this part as much as possible and keep
> everything in as less structures as possible (ideally just one).
>
> Please make local as many variables as you can.
I don't disagree with you here. Unfortunately everything between
the pack(push, 4) and pack(pop) needs to stay, since those are
the BIOS's ABI. I'd be open to putting them in a header file or
something though, but I wasn't sure what convention was on stuff like that.
What do you think? I think moving the BIOS ABI and maybe the over-the-wire
types (struct cgeb_request and friends) out would probably make it much
easier to follow.
> just return -EBUSY
Will-do!
> when you use constants like "5", you need to give it an
> explanation, either as a define (the name speaks by itself) or a
> comment. We don't want people asking "why 5?" :-)
I genuinely don't remember how this loop got into it. I'll see if it
behaves well without the loop.
> You either use brackets for every if/else/else fi or for no one.
Gotcha. I think I fixed all of them, will be in next series.
> just return err
Will-do!
>
> > +
> > + /* Wait for a response to the request */
> > + err = wait_for_completion_interruptible_timeout(
> > + &req->done, msecs_to_jiffies(20000));
> > + if (err == 0) {
> > + pr_err("CGEB: Timed out running request of type %d!\n",
> > + msg.type);
> > + err = -ETIMEDOUT;
>
> just "return -ETIMEDOUT;" and you can cleanup the code below
Here's where I landed on that:
/* Wait for a response to the request */
err = wait_for_completion_interruptible_timeout(
&req->done, msecs_to_jiffies(20000));
if (err == 0) {
pr_err("CGEB: Timed out running request of type %d!\n",
msg.type);
return -ETIMEDOUT;
} else if (err < 0) {
return err;
} else {
err = 0;
}
Unfortunately, I do still need to handle the err < 0 case,
but this is a little cleaner than it was.
> brackets!
Will-do
> I don't see any need for the out: label
Removed
> here it can be useful to have a goto statement:
>
> goto out;
> ...
> out:
> mutex_unlock(...);
> return;
Will-do!
Thanks again for taking the time to review.
next prev parent reply other threads:[~2024-08-12 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 18:35 [PATCH v3 0/2] Add support for " Mary Strodl
2024-08-08 18:35 ` [PATCH v3 1/2] x86: Add basic support for the " Mary Strodl
2024-08-09 0:46 ` Andi Shyti
2024-08-12 11:45 ` Mary Strodl [this message]
2024-08-12 20:16 ` Andi Shyti
2024-08-13 12:26 ` kernel test robot
2024-08-08 18:35 ` [PATCH v3 2/2] i2c: Add Congatec CGEB I2C driver Mary Strodl
2024-08-09 0:55 ` Andi Shyti
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=Zrn1vNgn7q5npxU7@freedom.csh.rit.edu \
--to=mstrodl@freedom.csh.rit.edu \
--cc=akpm@linux-foundation.org \
--cc=andi.shyti@kernel.org \
--cc=christian.gmeiner@gmail.com \
--cc=hch@infradead.org \
--cc=lee@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mstrodl@csh.rit.edu \
--cc=s.hauer@pengutronix.de \
--cc=urezki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox