[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00000141b8591950-3f399b8b-fdc7-41a0-b84c-bb632e8adba7-000000@email.amazonses.com>
Date: Mon, 14 Oct 2013 19:02:29 +0000
From: Christoph Lameter <cl@...ux.com>
To: Peter Zijlstra <peterz@...radead.org>
cc: Ingo Molnar <mingo@...nel.org>, David Miller <davem@...emloft.net>,
tj@...nel.org, akpm@...uxfoundation.org, srostedt@...hat.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: Re: [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu
operations V4
On Mon, 14 Oct 2013, Peter Zijlstra wrote:
> > Most kernel developers tend to use 'git send-email' to send patches to
> > lkml, and that method is working pretty reliably.
>
> I always use quilt mail, it typically adds a reference to the 0/0 email
> and ensures the time of each msg is one second ahead of the previous one
> to ensure order is correct.
Yes that I also what I expected to happen and what always happened in the
past.
> I've no idea how Christoph managed to wreck this, but normally quilt
> mail DTRT (as opposed to git send-email which used to default to
> endlessly deep threads -- got fixed in 1.6 or 1.7 or thereabouts).
Well this is going through Amazon cloud email which may be wrecking
things. Had a number of issues already with messages being delayed etc. I
can try to revert to my home setup and see if that fixes things.
--
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