linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: youling 257 <youling257@gmail.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH] early init: open /dev/console with O_LARGEFILE
Date: Thu, 2 Jan 2020 02:49:26 +0800	[thread overview]
Message-ID: <CAOzgRdYZB+-zNDbE8kUBoW89RdXFuTP-1JeDY1BvD-nM5Rx1vQ@mail.gmail.com> (raw)
In-Reply-To: <20200101184237.GA43049@light.dominikbrodowski.net>

of course, test this revert patch, no the system/bin/sh warning.

2020-01-02 2:42 GMT+08:00, Dominik Brodowski <linux@dominikbrodowski.net>:
> On Wed, Jan 01, 2020 at 12:59:32PM -0500, Arvind Sankar wrote:
>> On Wed, Jan 01, 2020 at 09:27:27PM +0800, youling 257 wrote:
>> > Unfortunately, test this patch still no help, has system/bin/sh
>> > warning.
>> >
>>
>> Just to confirm, the only change needed to make the warning go away is
>> reverting the single commit 8243186f0cc7 ("fs: remove ksys_dup()")?
>
> That's what he reported, yes.
>
> Thanks,
> 	Dominik
>

  reply	other threads:[~2020-01-01 18:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 15:02 [PATCH] early init: open /dev/console with O_LARGEFILE 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 [this message]
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
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=CAOzgRdYZB+-zNDbE8kUBoW89RdXFuTP-1JeDY1BvD-nM5Rx1vQ@mail.gmail.com \
    --to=youling257@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=nivedita@alum.mit.edu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).