From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking tree changes for v3.16
Date: Thu, 5 Jun 2014 11:24:37 +0200 [thread overview]
Message-ID: <20140605092437.GA4453@gmail.com> (raw)
In-Reply-To: <20140605092130.GC6758@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Jun 05, 2014 at 10:17:42AM +0200, Ingo Molnar wrote:
> >
> > Right now I'm somewhat 'missing' because I fell ill right when the
> > merge window began :-/ But I merged all your pending bits shortly
> > before the merge window started. During the merge window itself I
> > try not to merge fresh patches.
>
> Yeah, no problem that, it just shows we need to better arrange
> things for when you're not available.
>
> My/our quilt workflow works really good for me when you're there,
> but its obviously somewhat broken without you. We just need to work
> out a (better) fallback case.
Agreed.
> The timing was just somewhat unfortunate.
Yeah, and another part of the problem was that I reported the breakage
in private which really made it harder for others to see why there's a
delay.
Thanks,
Ingo
next prev parent reply other threads:[~2014-06-05 9:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 11:48 [GIT PULL] locking tree changes for v3.16 Ingo Molnar
2014-06-03 21:50 ` Davidlohr Bueso
2014-06-03 21:55 ` Andrew Morton
2014-06-03 22:02 ` Davidlohr Bueso
2014-06-03 22:53 ` Andrew Morton
2014-06-04 10:30 ` Peter Zijlstra
2014-06-04 16:17 ` Linus Torvalds
2014-06-04 17:22 ` Peter Zijlstra
2014-06-04 21:22 ` Linus Torvalds
2014-06-04 21:35 ` Thomas Gleixner
2014-06-05 1:22 ` Davidlohr Bueso
2014-06-05 8:19 ` Ingo Molnar
2014-06-05 8:22 ` Thomas Gleixner
2014-06-05 8:29 ` Ingo Molnar
2014-06-05 8:17 ` Ingo Molnar
2014-06-05 9:21 ` Peter Zijlstra
2014-06-05 9:24 ` Ingo Molnar [this message]
2014-06-05 11:11 ` Ingo Molnar
2014-06-05 11:20 ` Ingo Molnar
2014-06-05 12:27 ` Peter Zijlstra
2014-06-05 12:35 ` Ingo Molnar
2014-06-05 12:41 ` Peter Zijlstra
2014-06-05 12:47 ` Ingo Molnar
2014-06-05 12:53 ` Peter Zijlstra
2014-06-05 13:13 ` Peter Zijlstra
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=20140605092437.GA4453@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.