From: Joe Perches <joe@perches.com>
To: Gabriel Beauchamp <beauchampgabriel@gmail.com>,
gregkh@linuxfoundation.org, christian.gromm@microchip.com,
colin.king@canonical.com, gustavo@embeddedor.com
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: most: fix coding style issues
Date: Sat, 29 Jun 2019 16:58:46 -0700 [thread overview]
Message-ID: <dbe411be6aa32a32aafc5a5b77f08e8507b45da3.camel@perches.com> (raw)
In-Reply-To: <20190629234427.20746-1-beauchampgabriel@gmail.com>
On Sat, 2019-06-29 at 16:44 -0700, Gabriel Beauchamp wrote:
> This is a patch for the core.[ch] files that fixes up warnings
> found with the checkpatch.pl tool.
[]
> diff --git a/drivers/staging/most/core.c b/drivers/staging/most/core.c
[]
> @@ -303,7 +303,8 @@ static ssize_t set_datatype_show(struct device *dev,
>
> for (i = 0; i < ARRAY_SIZE(ch_data_type); i++) {
> if (c->cfg.data_type & ch_data_type[i].most_ch_data_type)
> - return snprintf(buf, PAGE_SIZE, "%s", ch_data_type[i].name);
> + return snprintf(buf, PAGE_SIZE,
> + "%s", ch_data_type[i].name);
> }
> return snprintf(buf, PAGE_SIZE, "unconfigured\n");
> }
Assuming the newline difference is unintentional,
(if not change "unconfigured" to "unconfigured\n")
How about using a single sprintf and reducing object code size too?
char *type = "unconfigured";
for (...)
if (c-> etc...) {
type = ch_data_type[i].name;
break;
}
}
return snprintf(buf, PAGE_SIZE, "%s", type);
next prev parent reply other threads:[~2019-06-30 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 23:44 Gabriel Beauchamp
2019-06-29 23:58 ` Joe Perches [this message]
2019-06-30 15:27 ` [PATCH v2] " Gabriel Beauchamp
2019-06-30 16:56 ` [PATCH v3] " Gabriel Beauchamp
2019-07-01 13:41 ` kbuild test robot
2019-07-01 17:40 ` kbuild test robot
2019-07-02 12:24 ` [PATCH v4] " Gabriel Beauchamp
2019-07-02 12:28 ` Greg KH
2019-07-23 13:43 ` [PATCH v3] " kbuild test robot
2019-08-08 14:23 ` kbuild test robot
2019-07-01 6:48 ` [PATCH v2] " Greg KH
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=dbe411be6aa32a32aafc5a5b77f08e8507b45da3.camel@perches.com \
--to=joe@perches.com \
--cc=beauchampgabriel@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@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®