From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v7 1/1] gpio: add sloppy logic analyzer using polling
Date: Mon, 28 Mar 2022 11:37:32 +0200 [thread overview]
Message-ID: <YkGB3AgME/OZAdoG@ninjato> (raw)
In-Reply-To: <YjiC6Lg5k5gK/BfP@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
Hi Andy,
> > + for (i = 0; i < priv->trig_len; i+= 2) {
>
> Missed space.
Yes.
> > +static int fops_buf_size_set(void *data, u64 val)
> > +{
> > + struct gpio_la_poll_priv *priv = data;
>
> > + int ret = 0;
>
> Instead of this assignment and other related things, can we do the following?
>
> > + void *p;
> > +
> > + if (!val)
> > + return -EINVAL;
> > +
> > + mutex_lock(&priv->lock);
> > +
> > + vfree(priv->blob.data);
>
> priv->blob.data = NULL;
> priv->blob.size = 0;
>
> > + p = vzalloc(val);
> > + if (!p) {
> > + val = 0;
> > + ret = -ENOMEM;
> > + }
>
> p = vzalloc(val);
> if (!p)
> return -ENOMEM;
>
> > + priv->blob.data = p;
> > + priv->blob.size = val;
I don't like assigning 'priv' memebers twice, so I'd like to keep it as
is.
> > +static const struct file_operations fops_trigger = {
> > + .owner = THIS_MODULE,
> > + .open = trigger_open,
> > + .write = trigger_write,
> > + .llseek = no_llseek,
> > + .release = single_release,
> > +};
>
> Can it be wrapped by DEFINE_SHOW_ATTRIBUTE()?
I don't see a way. Do you?
> > + dev_info(dev, "initialized");
>
> Not sure how this one would be helpful.
Then please check my comments on your previous reviews.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-28 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 8:50 [PATCH v7 0/1] gpio: add simple " Wolfram Sang
2022-03-17 8:50 ` [PATCH v7 1/1] gpio: add sloppy " Wolfram Sang
2022-03-21 13:51 ` Andy Shevchenko
2022-03-28 9:37 ` Wolfram Sang [this message]
2022-03-28 10:49 ` Andy Shevchenko
2022-03-28 12:19 ` Wolfram Sang
2022-03-28 12:51 ` Andy Shevchenko
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=YkGB3AgME/OZAdoG@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@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
all inboxes | Powered by JetHome®