public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Reorganize perf kernel side
Date: Fri, 4 Dec 2015 23:09:07 +0100	[thread overview]
Message-ID: <20151204220907.GJ17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20151204211756.GR21177@pd.tnic>

On Fri, Dec 04, 2015 at 10:17:56PM +0100, Borislav Petkov wrote:
> Hi guys,
> 
> so I've had my eyes on this for a long time now and it has managed to
> get on my nerves just enough to do something about it :-)
> 
> So how about moving perf stuff to arch/x86/perf/ and get rid of the
> prefixes in the filenames. This also flattens our folder structure which
> is a good thing and which we've been talking about in the past.
> 
> In order to diminish churn, I can do the whole thing in 4-5 patches'
> sets, after having run enough *config smoke tests and 0day bot too.
> Anyway, something like that.
> 
> perf_event_<vendor>_<type>.c
> 
> can then move to arch/x86/perf/<vendor>/type.c
> 
> and have much saner structure.
> 
> Thoughts?

I _will_ blame you for at least a month after every time I mistype a
pathname because of this ;-)

git blame --follow must keep working. That is, git had better be able to
understand this code movement, loosing history is just a total PITA.

Also, a script that can auto-convert patches would be nice.

  reply	other threads:[~2015-12-04 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 21:17 Reorganize perf kernel side Borislav Petkov
2015-12-04 22:09 ` Peter Zijlstra [this message]
2015-12-04 22:40   ` Borislav Petkov
2015-12-06  9:54 ` Ingo Molnar

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=20151204220907.GJ17308@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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