Re: [RFC] Create instrumentation directory (git repository)

Mathieu Desnoyers wrote:

Putting stuff in instrumentation/ by no way means that it becomes
optional for a subsystem, but merely that it could either export
information useful for kernel instrumentation or have some

infrastructure parts merged with others.

More reason why you should not be moving stuff all around the tree...

Really, file structure is one of the LEAST important issues around -- while moving files around introduces a non-zero amount of pain.

New files -- like that godawful and nearly empty samples/ directory -- sure, fix that up before release. But let's not break diffs of existing architectures without good reason.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC] Create instrumentation directory (git repository)
    • From: Mathieu Desnoyers <[email protected]>
  • Re: [RFC] Create instrumentation directory (git repository)
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] Create instrumentation directory (git repository)
    • From: Mathieu Desnoyers <[email protected]>

• Prev by Date: Re: [RFC] Create instrumentation directory (git repository)
• Next by Date: Re: [PATCH] Revert x86: add lapic_shutdown for x86_64
• Previous by thread: Re: [RFC] Create instrumentation directory (git repository)
• Next by thread: [PATCH] quirk_vialatency: Omit reading pci revision ID
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]