[Fwd: [PULL] hardware latency detector]

[Fwd: [PULL] hardware latency detector]

[Jon Masters]

[-- Attachment #1: Type: text/plain, Size: 218 bytes --]

Stephen,

I've posted this for merge, but plan to continue developing against the
"master" branch of this tree and then push to "for-linus" before
posting. Perhaps you'd like to add either branch to linux-next.

Jon.


[-- Attachment #2: Forwarded message - [PULL] hardware latency detector --]
[-- Type: message/rfc822, Size: 1845 bytes --]

From: Jon Masters <jcm@jonmasters.org>
To: mingo@elte.hu, tglx@linutronix.de, williams@redhat.com, jcm@redhat.com, jcm@jonmasters.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: [PULL] hardware latency detector
Date: Thu, 18 Jun 2009 21:21:22 -0400
Message-ID: <E1MHSnC-0006bC-OW@tonnant>

Linus,

Please pull "hwlat", the hardware latency detector for 2.6.31.

Patches can be pulled from:

  git://git.kernel.org/pub/scm/linux/kernel/git/jcm/linux-2.6-hwlat.git for-linus

Jon Masters (2):
      hwlat_detector: A system hardware latency detector
      hwlat_detector: include linux/delay.h in hwlat_detector

 Documentation/hwlat_detector.txt |   64 ++
 MAINTAINERS                      |    9 +
 drivers/misc/Kconfig             |   28 +
 drivers/misc/Makefile            |    1 +
 drivers/misc/hwlat_detector.c    | 1208 ++++++++++++++++++++++++++++++++++++++
 5 files changed, 1310 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/hwlat_detector.txt
 create mode 100644 drivers/misc/hwlat_detector.c

Re: [Fwd: [PULL] hardware latency detector]

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

Hi Jon,

On Thu, 18 Jun 2009 21:27:11 -0400 Jon Masters <jonathan@jonmasters.org> wrote:
>
> I've posted this for merge, but plan to continue developing against the
> "master" branch of this tree and then push to "for-linus" before
> posting. Perhaps you'd like to add either branch to linux-next.

I'll add your for-linus branch to linux-next on Monday (the next tree I
will create).

What I tell everyone: all patches/commits in the tree/series must
have been:

	posted to a relevant mailing list
	reviewed
	unit tested
	destined for the next merge window (or the current release)

*before* they are included.  The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

I'll switch to your master branch if all the above holds for it.  Some
people have three "public" branches: "bug fixes", "ready for linus" and
"development" (called various different things), and I generally stick
to the "ready for linus" stuff ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [Fwd: [PULL] hardware latency detector]

[Jon Masters]

On Sat, 2009-06-20 at 08:31 +1000, Stephen Rothwell wrote:
> Hi Jon,
> 
> On Thu, 18 Jun 2009 21:27:11 -0400 Jon Masters <jonathan@jonmasters.org> wrote:
> >
> > I've posted this for merge, but plan to continue developing against the
> > "master" branch of this tree and then push to "for-linus" before
> > posting. Perhaps you'd like to add either branch to linux-next.
> 
> I'll add your for-linus branch to linux-next on Monday (the next tree I
> will create).

Yeah, I figured all the following bits about the rules - thanks for
that! I created the for-linus branch for precisely those reasons :)

Jon.

P.S. You do an amazing job and we are very grateful to you for it. I
especially enjoy tracking your tree for my podcast, which forces me to
keep up with exactly what is in it at any moment.