[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wh3iWk6nu1u2OZ9JeyM-aJ_nCm1tMihPir8Yu3Q08f4aA@mail.gmail.com>
Date: Mon, 28 Jan 2019 10:42:25 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Michal Hocko <mhocko@...nel.org>
Cc: robert shteynfeld <robert.shteynfeld@...il.com>,
Mikhail Zaslonko <zaslonko@...ux.ibm.com>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Gerald Schaefer <gerald.schaefer@...ibm.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Dave Hansen <dave.hansen@...el.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Steven Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Bob Picco <bob.picco@...cle.com>
Subject: Re: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684
On Mon, Jan 28, 2019 at 3:44 AM Michal Hocko <mhocko@...nel.org> wrote:
>
> >
> > Linus, could you take the revert please?
>
> or should I post the patch as a reply to make your life easier?
I've taken that revert now, but yes, in general, it's much better if a
patch is sent separately from the discussion as a very explicit patch
(ie subject line has that usual "[PATCH] ..." format etc) simply
because I get too much email and I can often miss things otherwise.
Particularly inside a thread where the developers are discussing
things, I go "ah, good, things are still being discussed" without
looking any closer into the details.
That's particularly true when traveling - I only noticed this one on
this second reminder email.. I'm home now, but Friday, when you sent
it originally, was 45 hours long for me with 24 hours on airplanes and
airports, so I had entirely missed the original email back then.
Thanks,
Linus
Powered by blists - more mailing lists