From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Stefano Brivio <sbrivio@redhat.com>, netdev@vger.kernel.org
Cc: Bhumika Goyal <bhumirks@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
David Windsor <dwindsor@gmail.com>,
Elena Reshetova <elena.reshetova@intel.com>,
Hans Liljestrand <ishkamiel@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
Kees Cook <keescook@chromium.org>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: atm/clip: Use seq_puts() in svc_addr()
Date: Sun, 7 Jan 2018 09:19:17 +0100 [thread overview]
Message-ID: <a42edf4b-92c7-469d-dab1-3238cd7487bd@users.sourceforge.net> (raw)
In-Reply-To: <20180106232539.5d6bb620@elisabeth>
>> Two strings should be quickly put into a sequence by two function calls.
>> Thus use the function "seq_puts" instead of "seq_printf".
>>
>> This issue was detected by using the Coccinelle software.
>
> Can you please explain what the issue really is and what you're trying
> to do here?
Is the function "seq_puts" a bit more efficient for the desired output
of a single string in comparison to calling the function "seq_printf"
for this purpose?
> One shouldn't need to dig into Coccinelle patterns to find
> out what you mean,
Why did an attribution for a software tool confuse you?
> and "strings should be quickly put into a sequence"
> isn't terribly helpful.
Which wording would you find more appropriate for the suggested
adjustment of these function calls?
Regards,
Markus
next prev parent reply other threads:[~2018-01-07 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 21:44 [PATCH] atm/clip: Use seq_puts() in svc_addr() SF Markus Elfring
2018-01-06 22:25 ` Stefano Brivio
2018-01-07 8:19 ` SF Markus Elfring [this message]
2018-01-07 15:30 ` Stefano Brivio
2018-01-07 16:30 ` SF Markus Elfring
2018-01-07 22:58 ` [PATCH] " Andy Shevchenko
2018-01-08 7:25 ` 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=a42edf4b-92c7-469d-dab1-3238cd7487bd@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=bhumirks@gmail.com \
--cc=davem@davemloft.net \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=ishkamiel@gmail.com \
--cc=johannes.berg@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sbrivio@redhat.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;
as well as URLs for NNTP newsgroup(s).