From: SF Markus Elfring <elfring@users.sourceforge.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show()
Date: Mon, 17 Oct 2016 12:50:57 +0000 [thread overview]
Message-ID: <d012ad47-9688-5c9c-6ffd-78300c7b21ae@users.sourceforge.net> (raw)
In-Reply-To: <20161017123726.GE29095@leverpostej>
> I prefer the code as-is. Unless there's a compelling reason to change it.
Is the chance for faster log output interesting enough?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show()
Date: Mon, 17 Oct 2016 14:50:57 +0200 [thread overview]
Message-ID: <d012ad47-9688-5c9c-6ffd-78300c7b21ae@users.sourceforge.net> (raw)
In-Reply-To: <20161017123726.GE29095@leverpostej>
> I prefer the code as-is. Unless there's a compelling reason to change it.
Is the chance for faster log output interesting enough?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Mark Rutland <mark.rutland@arm.com>
Cc: kernel-janitors@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Suzuki K. Poulose" <suzuki.poulose@arm.com>
Subject: Re: ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show()
Date: Mon, 17 Oct 2016 14:50:57 +0200 [thread overview]
Message-ID: <d012ad47-9688-5c9c-6ffd-78300c7b21ae@users.sourceforge.net> (raw)
In-Reply-To: <20161017123726.GE29095@leverpostej>
> I prefer the code as-is. Unless there's a compelling reason to change it.
Is the chance for faster log output interesting enough?
Regards,
Markus
next prev parent reply other threads:[~2016-10-17 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 19:03 [PATCH] ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show() SF Markus Elfring
2016-10-16 19:03 ` SF Markus Elfring
2016-10-16 19:03 ` SF Markus Elfring
2016-10-17 9:37 ` [PATCH] ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_sho Matthias Brugger
2016-10-17 9:37 ` [PATCH] ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show() Matthias Brugger
2016-10-17 9:37 ` Matthias Brugger
2016-10-17 10:56 ` [PATCH] ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_sho Mark Rutland
2016-10-17 10:56 ` [PATCH] ARM64-cpuinfo: Combine six calls for sequence output into one seq_printf() call in c_show() Mark Rutland
2016-10-17 10:56 ` Mark Rutland
2016-10-17 11:30 ` SF Markus Elfring
2016-10-17 11:30 ` SF Markus Elfring
2016-10-17 11:30 ` SF Markus Elfring
2016-10-17 12:37 ` Mark Rutland
2016-10-17 12:37 ` Mark Rutland
2016-10-17 12:37 ` Mark Rutland
2016-10-17 12:50 ` SF Markus Elfring [this message]
2016-10-17 12:50 ` SF Markus Elfring
2016-10-17 12:50 ` SF Markus Elfring
2016-10-17 13:10 ` Mark Rutland
2016-10-17 13:10 ` Mark Rutland
2016-10-17 13:10 ` Mark Rutland
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=d012ad47-9688-5c9c-6ffd-78300c7b21ae@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.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 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.