From: SF Markus Elfring <elfring@users.sourceforge.net> To: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org Subject: [PATCH 1/3] Input: Use seq_putc() in input_seq_print_bitmap() Date: Mon, 8 May 2017 15:04:36 +0200 [thread overview] Message-ID: <7f53f603-1069-1e7a-67b6-78f8009aa0c1@users.sourceforge.net> (raw) In-Reply-To: <85bf6874-661a-9cab-1e9b-ea9e312b94de@users.sourceforge.net> From: Markus Elfring <elfring@users.sourceforge.net> Date: Mon, 8 May 2017 14:20:18 +0200 A single character should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring <elfring@users.sourceforge.net> --- drivers/input/input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/input.c b/drivers/input/input.c index 067d648028a2..0d204b841575 100644 --- a/drivers/input/input.c +++ b/drivers/input/input.c @@ -1126,7 +1126,7 @@ static void input_seq_print_bitmap(struct seq_file *seq, const char *name, * If no output was produced print a single 0. */ if (skip_empty) - seq_puts(seq, "0"); + seq_putc(seq, '0'); seq_putc(seq, '\n'); } -- 2.12.2
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net> To: linux-input@vger.kernel.org, Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org Subject: [PATCH 1/3] Input: Use seq_putc() in input_seq_print_bitmap() Date: Mon, 08 May 2017 13:04:36 +0000 [thread overview] Message-ID: <7f53f603-1069-1e7a-67b6-78f8009aa0c1@users.sourceforge.net> (raw) In-Reply-To: <85bf6874-661a-9cab-1e9b-ea9e312b94de@users.sourceforge.net> From: Markus Elfring <elfring@users.sourceforge.net> Date: Mon, 8 May 2017 14:20:18 +0200 A single character should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring <elfring@users.sourceforge.net> --- drivers/input/input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/input.c b/drivers/input/input.c index 067d648028a2..0d204b841575 100644 --- a/drivers/input/input.c +++ b/drivers/input/input.c @@ -1126,7 +1126,7 @@ static void input_seq_print_bitmap(struct seq_file *seq, const char *name, * If no output was produced print a single 0. */ if (skip_empty) - seq_puts(seq, "0"); + seq_putc(seq, '0'); seq_putc(seq, '\n'); } -- 2.12.2
next prev parent reply other threads:[~2017-05-08 13:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-08 13:03 [PATCH 0/3] Input: Fine-tuning for six function implementations SF Markus Elfring 2017-05-08 13:03 ` SF Markus Elfring 2017-05-08 13:04 ` SF Markus Elfring [this message] 2017-05-08 13:04 ` [PATCH 1/3] Input: Use seq_putc() in input_seq_print_bitmap() SF Markus Elfring 2017-05-08 13:05 ` [PATCH 2/3] Input: Use seq_puts() in input_devices_seq_show() SF Markus Elfring 2017-05-08 13:05 ` SF Markus Elfring 2017-05-08 13:06 ` [PATCH 3/3] Input: Improve a size determination in four functions SF Markus Elfring 2017-05-08 13:06 ` SF Markus Elfring
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=7f53f603-1069-1e7a-67b6-78f8009aa0c1@users.sourceforge.net \ --to=elfring@users.sourceforge.net \ --cc=dmitry.torokhov@gmail.com \ --cc=kernel-janitors@vger.kernel.org \ --cc=linux-input@vger.kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.