From: Andreas Schwab <schwab@linux-m68k.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, Michal Simek <monstr@monstr.eu>,
linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH] [RFC] Remove bdflush syscall stub
Date: Tue, 28 May 2019 10:25:09 +0000 [thread overview]
Message-ID: <mvmr28idgfu.fsf@linux-m68k.org> (raw)
In-Reply-To: <20190528101012.11402-1-chrubis@suse.cz> (Cyril Hrubis's message of "Tue, 28 May 2019 12:10:12 +0200")
On Mai 28 2019, Cyril Hrubis <chrubis@suse.cz> wrote:
> I've tested the patch on i386. Before the patch calling bdflush() with
> attempt to tune a variable returned 0 and after the patch the syscall
> fails with EINVAL.
Should be ENOSYS, doesn't it?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, Michal Simek <monstr@monstr.eu>,
linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
linux-xtensa@linux-xtensa.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH] [RFC] Remove bdflush syscall stub
Date: Tue, 28 May 2019 12:25:09 +0200 [thread overview]
Message-ID: <mvmr28idgfu.fsf@linux-m68k.org> (raw)
In-Reply-To: <20190528101012.11402-1-chrubis@suse.cz> (Cyril Hrubis's message of "Tue, 28 May 2019 12:10:12 +0200")
On Mai 28 2019, Cyril Hrubis <chrubis@suse.cz> wrote:
> I've tested the patch on i386. Before the patch calling bdflush() with
> attempt to tune a variable returned 0 and after the patch the syscall
> fails with EINVAL.
Should be ENOSYS, doesn't it?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: linux-s390@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-sh@vger.kernel.org, linux-api@vger.kernel.org,
linux-xtensa@linux-xtensa.org,
lkml <linux-kernel@vger.kernel.org>,
linux-mips@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-alpha@vger.kernel.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [RFC] Remove bdflush syscall stub
Date: Tue, 28 May 2019 12:25:09 +0200 [thread overview]
Message-ID: <mvmr28idgfu.fsf@linux-m68k.org> (raw)
In-Reply-To: <20190528101012.11402-1-chrubis@suse.cz> (Cyril Hrubis's message of "Tue, 28 May 2019 12:10:12 +0200")
On Mai 28 2019, Cyril Hrubis <chrubis@suse.cz> wrote:
> I've tested the patch on i386. Before the patch calling bdflush() with
> attempt to tune a variable returned 0 and after the patch the syscall
> fails with EINVAL.
Should be ENOSYS, doesn't it?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: linux-s390@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-sh@vger.kernel.org, linux-api@vger.kernel.org,
linux-xtensa@linux-xtensa.org,
lkml <linux-kernel@vger.kernel.org>,
linux-mips@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-alpha@vger.kernel.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [RFC] Remove bdflush syscall stub
Date: Tue, 28 May 2019 12:25:09 +0200 [thread overview]
Message-ID: <mvmr28idgfu.fsf@linux-m68k.org> (raw)
In-Reply-To: <20190528101012.11402-1-chrubis@suse.cz> (Cyril Hrubis's message of "Tue, 28 May 2019 12:10:12 +0200")
On Mai 28 2019, Cyril Hrubis <chrubis@suse.cz> wrote:
> I've tested the patch on i386. Before the patch calling bdflush() with
> attempt to tune a variable returned 0 and after the patch the syscall
> fails with EINVAL.
Should be ENOSYS, doesn't it?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-28 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 10:10 [PATCH] [RFC] Remove bdflush syscall stub Cyril Hrubis
2019-05-28 10:10 ` Cyril Hrubis
2019-05-28 10:25 ` Andreas Schwab [this message]
2019-05-28 10:25 ` Andreas Schwab
2019-05-28 10:25 ` Andreas Schwab
2019-05-28 10:25 ` Andreas Schwab
2019-05-28 10:40 ` Cyril Hrubis
2019-05-28 10:40 ` Cyril Hrubis
2019-05-28 11:03 ` Florian Weimer
2019-05-28 11:03 ` Florian Weimer
2019-05-28 11:03 ` Florian Weimer
2019-05-28 11:03 ` Florian Weimer
2019-05-28 11:20 ` Cyril Hrubis
2019-05-28 11:20 ` Cyril Hrubis
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=mvmr28idgfu.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=chrubis@suse.cz \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=monstr@monstr.eu \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.