From: Mark Brown <broonie@kernel.org>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
joel@jms.id.au, andrew@aj.id.au
Subject: Re: [PATCH] spi: Add FSI-attached SPI controller driver
Date: Thu, 30 Jan 2020 14:46:09 +0000 [thread overview]
Message-ID: <20200130144609.GD6682@sirena.org.uk> (raw)
In-Reply-To: <1580328504-436-1-git-send-email-eajames@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Wed, Jan 29, 2020 at 02:08:24PM -0600, Eddie James wrote:
Overall this looks good, some comments below but they're all fairly
minor.
> +++ b/drivers/spi/spi-fsi.c
> @@ -0,0 +1,547 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) IBM Corporation 2020
> + */
Please make the entire comment a C++ one so things look more
intentional.
> +
> +static int fsi_spi_data_in(u64 in, u8 *rx, int len)
> +{
> + int i;
> + int num_bytes = len > 8 ? 8 : len;
Please write normal conditional statements to improve legibility, the
ternery operator isn't really needed here.
> +static int fsi_spi_reset(struct fsi_spi *ctx)
> +{
> + int rc;
> +
> + dev_info(ctx->dev, "Resetting SPI controller.\n");
This should be lowered to dev_dbg() at most, it's not really adding
anything otherwise.
> +static int fsi_spi_remove(struct device *dev)
> +{
> + return 0;
> +}
Remove empty functions, if they can safely be empty then it should be
possible to omit them.
> +static const struct fsi_device_id fsi_spi_ids[] = {
> + { FSI_ENGID_SPI, FSI_VERSION_ANY },
> + { }
> +};
This needs a MODULE_DEVICE_TABLE annotation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-30 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 20:08 [PATCH] spi: Add FSI-attached SPI controller driver Eddie James
2020-01-30 14:46 ` Mark Brown [this message]
2020-01-30 15:32 ` Eddie James
2020-01-30 16:37 ` Andy Shevchenko
2020-02-03 20:33 ` Eddie James
2020-02-04 11:02 ` Andy Shevchenko
2020-02-04 16:06 ` Eddie James
2020-02-05 15:51 ` Andy Shevchenko
2020-02-07 19:28 ` Eddie James
2020-02-07 19:39 ` Andy Shevchenko
2020-02-07 20:04 ` Eddie James
2020-02-07 20:34 ` Andy Shevchenko
2020-02-07 20:59 ` Eddie James
2020-02-07 22:04 ` Andy Shevchenko
2020-02-10 20:05 ` Eddie James
2020-02-10 20:33 ` Andy Shevchenko
2020-02-10 20:50 ` Eddie James
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=20200130144609.GD6682@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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 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).