From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Stefan Wahren <stefan.wahren@i2se.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Philippe Reynes <tremyfr@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: qca_debug: Reduce function calls for sequence output in qcaspi_info_show()
Date: Tue, 9 May 2017 09:57:57 +0200 [thread overview]
Message-ID: <f9fef8a0-13c2-8dae-cb2a-7d39491e47f4@users.sourceforge.net> (raw)
In-Reply-To: <290d2473-73bd-70db-b6ef-c50331812f31@i2se.com>
> The only benefit is a little bit higher performance.
I would prefer such a small code reduction. I am not so concerned
about an other readability impression at this place.
> But for debugfs this won't be necessary.
I would appreciate also another improvement there.
Regards,
Markus
prev parent reply other threads:[~2017-05-09 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 17:29 [PATCH] qca_debug: Reduce function calls for sequence output in qcaspi_info_show() SF Markus Elfring
2017-05-09 7:07 ` Stefan Wahren
2017-05-09 7:57 ` SF Markus Elfring [this message]
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=f9fef8a0-13c2-8dae-cb2a-7d39491e47f4@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=tremyfr@gmail.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).