From: Arvind Sankar <nivedita@alum.mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: youling 257 <youling257@gmail.com>,
Arvind Sankar <nivedita@alum.mit.edu>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] early init: open /dev/console with O_LARGEFILE
Date: Wed, 1 Jan 2020 23:10:57 -0500 [thread overview]
Message-ID: <20200102041056.GA535736@rani.riverdale.lan> (raw)
In-Reply-To: <CAHk-=wj4CBDJ=VvUkQBcYC1XwyG6bDpWXg+iv6NyEE1eV+SKKA@mail.gmail.com>
On Wed, Jan 01, 2020 at 08:00:25PM -0800, Linus Torvalds wrote:
> On Wed, Jan 1, 2020 at 7:09 PM youling 257 <youling257@gmail.com> wrote:
> >
> > test this patch.diff, no the system/bin/sh warning, fixed.
>
> Good to finally have figured out the silly reason this broke.
>
> I may end up deciding just to revert after all, but even if I do that,
> I'll just feel a lot better about knowing _why_ things broke.
>
> Thanks a lot for all the testing you did,
>
> Linus
Huh. Feels good to have helped finding the bug, even though I thought it
couldn't *possibly* be the source of the problem.
"There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy."
next prev parent reply other threads:[~2020-01-02 4:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 15:02 Dominik Brodowski
2019-12-31 15:55 ` youling 257
2020-01-01 0:30 ` Arvind Sankar
2020-01-01 10:43 ` Dominik Brodowski
2020-01-01 13:27 ` youling 257
2020-01-01 17:24 ` Dominik Brodowski
2020-01-01 17:59 ` Arvind Sankar
2020-01-01 18:42 ` Dominik Brodowski
2020-01-01 18:49 ` youling 257
2020-01-01 18:32 ` Arvind Sankar
2020-01-01 21:39 ` Linus Torvalds
2020-01-01 22:50 ` Arvind Sankar
2020-01-01 23:01 ` Linus Torvalds
2020-01-01 23:08 ` Arvind Sankar
2020-01-02 3:09 ` youling 257
2020-01-02 4:00 ` Linus Torvalds
2020-01-02 4:10 ` Arvind Sankar [this message]
2020-01-02 17:53 ` Dominik Brodowski
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=20200102041056.GA535736@rani.riverdale.lan \
--to=nivedita@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=youling257@gmail.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
all inboxes | Powered by JetHome®