From: Michal Hocko <mhocko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: robert shteynfeld <robert.shteynfeld@gmail.com>,
Mikhail Zaslonko <zaslonko@linux.ibm.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Steven Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Bob Picco <bob.picco@oracle.com>
Subject: Re: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684
Date: Mon, 28 Jan 2019 20:02:45 +0100 [thread overview]
Message-ID: <20190128190245.GV18811@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHk-=wh3iWk6nu1u2OZ9JeyM-aJ_nCm1tMihPir8Yu3Q08f4aA@mail.gmail.com>
On Mon 28-01-19 10:42:25, Linus Torvalds wrote:
> On Mon, Jan 28, 2019 at 3:44 AM Michal Hocko <mhocko@kernel.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.
Sure, I usually do it that way. I was just awaiting some review feedback
on the changelog first.
> 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.
No problem. Andrew has already queued it as well so I guess he simply
drops it when it reaches your tree.
Thanks!
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-01-28 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADfvbxqC1+XoSsn0sEDqFE16tN1Pq46-QDAaCu=AXJdZeY3rDQ@mail.gmail.com>
2019-01-24 15:48 ` Fwd: kernel panic due to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2830bf6f05fb3e05bc4743274b806c821807a684 robert shteynfeld
2019-01-25 4:48 ` Linus Torvalds
2019-01-25 7:37 ` Michal Hocko
2019-01-25 8:19 ` Michal Hocko
2019-01-25 8:29 ` Michal Hocko
2019-01-25 15:52 ` robert shteynfeld
2019-01-25 15:58 ` Michal Hocko
2019-01-25 16:16 ` robert shteynfeld
2019-01-25 16:39 ` Michal Hocko
2019-01-25 16:51 ` robert shteynfeld
2019-01-25 17:33 ` Michal Hocko
2019-01-25 18:15 ` Michal Hocko
2019-01-28 6:37 ` Mikhail Gavrilov
2019-01-28 6:43 ` Michal Hocko
2019-01-28 11:43 ` Michal Hocko
2019-01-28 18:42 ` Linus Torvalds
2019-01-28 19:02 ` Michal Hocko [this message]
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=20190128190245.GV18811@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=bob.picco@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.hansen@intel.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=pasha.tatashin@oracle.com \
--cc=robert.shteynfeld@gmail.com \
--cc=steven.sistare@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=zaslonko@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).