From: Andi Kleen <andi@firstfloor.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>,
peterz@infradead.org, x86@kernel.org, eranian@google.com,
kan.liang@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] x86/cpufeature: Add facility to match microcode revisions
Date: Thu, 25 Oct 2018 16:23:09 -0700 [thread overview]
Message-ID: <20181025232309.6bbxedhkf2ffndsw@two.firstfloor.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1810210954440.1651@nanos.tec.linutronix.de>
On Sun, Oct 21, 2018 at 12:20:47PM +0200, Thomas Gleixner wrote:
> Andi,
>
> On Sat, 20 Oct 2018, Andi Kleen wrote:
> > On Sat, Oct 20, 2018 at 10:19:37AM +0200, Thomas Gleixner wrote:
> > > On Fri, 19 Oct 2018, Andi Kleen wrote:
> > > There is no point to return the pointer because it's not a compound
> > > structure. If you want to provide the possibility to use the index then
> > > return the index and an error code if it does not match.
> >
> > It will be useful with the driver_data pointer, which you short sightedly
> > forced me to remove, and likely will need to be readded at some point
> > anyways if this gets more widely used.
>
> It's good and established practice not to add functionality on a 'might be
> used' basis. If you'd provide at least one or two patches which demonstrate
> how that is useful then that would be convincing.
>
> > At least with the pointer not all callers will need to be changed then.
>
> It doesn't need to be changed at all, when done correctly.
Thanks.
I opted for the simpler method of returning a boolean now.
-Andi
prev parent reply other threads:[~2018-10-25 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 16:26 Andi Kleen
2018-10-10 16:26 ` [PATCH v2 2/2] perf/x86/kvm: Avoid unnecessary work in guest filtering Andi Kleen
2018-10-10 16:37 ` [PATCH v2 1/2] x86/cpufeature: Add facility to match microcode revisions Borislav Petkov
2018-10-11 11:43 ` Henrique de Moraes Holschuh
2018-10-17 9:59 ` Thomas Gleixner
2018-10-19 23:47 ` Andi Kleen
2018-10-20 8:19 ` Thomas Gleixner
2018-10-20 14:38 ` Andi Kleen
2018-10-21 10:20 ` Thomas Gleixner
2018-10-21 15:13 ` Borislav Petkov
2018-10-25 23:23 ` Andi Kleen [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=20181025232309.6bbxedhkf2ffndsw@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome