[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563d9db7.6293420a.cdda3.ffffa5c8@mx.google.com>
Date: Fri, 06 Nov 2015 22:44:07 -0800 (PST)
From: Palmer Dabbelt <palmer@...belt.com>
To: peterz@...radead.org
CC: x86@...nel.org
Subject: Re: [PATCH 09/13] Move bp_type_idx to kernel/event/hw_breakpoint.c
On Wed, 04 Nov 2015 04:21:51 PST (-0800), peterz@...radead.org wrote:
> On Wed, Nov 04, 2015 at 12:41:06PM +0100, Peter Zijlstra wrote:
>> On Tue, Nov 03, 2015 at 11:46:30AM -0800, Palmer Dabbelt wrote:
>> > This has a "#ifdef CONFIG_*" that used to be exposed to userspace.
>> >
>> > The names in here are so generic that I don't think it's a good idea
>> > to expose them to userspace (or even the rest of the kernel). Since
>> > there's only one kernel user, it's been moved to that file.
>> >
>> > Signed-off-by: Palmer Dabbelt <palmer@...belt.com>
>> > Reviewed-by: Andrew Waterman <waterman@...s.berkeley.edu>
>> > Reviewed-by: Albert Ou <aou@...s.berkeley.edu>
>>
>> Assuming you want to keep all these patches together in a tree or so.
>> Let me know if you want me to take this patch.
Well, the plan was to try to get the whole patch set all upstream together.
I'd prefer that, because it'll be easier to make sure everything gets in before
the last checker patch. Since it touches so many different places I'd be OK
with doing it peicemeal.
I'm kind of new to this whole process: do you think someone is likely to take
this patch set all together?
>> Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>
>
> Ah, build-bot finds your change is broken and you didn't grep right. It
> is used in more places.
Sorry about that, I must have mis-grep'd. I guess that's what the build-bot is
for :).
> How about moving it to include/linux/hw_breakpoint.h, instead of having
> it in the uapi crud?
Yep, that makes sense.
I'm going to re-submit a v5 of this patch set, since there was also a missing
patch for blackfin that the buildbot found.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists