From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
rafael@kernel.org, torvalds@linux-foundation.org,
viro@zeniv.linux.org.uk, clang-built-linux@googlegroups.com
Subject: Re: [PATCH 3/3] init: use do_mount() instead of ksys_mount()
Date: Tue, 17 Dec 2019 07:38:46 +0100 [thread overview]
Message-ID: <20191217063846.GA3247@light.dominikbrodowski.net> (raw)
In-Reply-To: <20191216211228.153485-1-ndesaulniers@google.com>
On Mon, Dec 16, 2019 at 01:12:28PM -0800, Nick Desaulniers wrote:
> Shouldn't patches bake for a while in -next? (That way we catch regressions
> before they hit mainline?)
>
> This lit up our CI this morning.
>
> https://travis-ci.com/ClangBuiltLinux/continuous-integration/builds
>
> (Apologies for missing context, replying via lore.kernel.org directions.)
> https://lore.kernel.org/lkml/20191212135724.331342-4-linux@dominikbrodowski.net/
A fix for this issue is already upstream, 7de7de7ca0ae .
Thanks,
Dominik
next prev parent reply other threads:[~2019-12-17 6:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 13:57 [PATCH 0/3] use do_mount() instead of ksys_mount() Dominik Brodowski
2019-12-12 13:57 ` [PATCH 1/3] devtmpfs: " Dominik Brodowski
2019-12-12 13:57 ` [PATCH 2/3] initrd: " Dominik Brodowski
2019-12-12 13:57 ` [PATCH 3/3] init: " Dominik Brodowski
2019-12-16 1:35 ` Ondřej Jirman
2019-12-16 1:36 ` Ondřej Jirman
2019-12-16 3:50 ` Linus Torvalds
2019-12-16 5:13 ` Eric Biggers
2019-12-16 13:21 ` Geert Uytterhoeven
2019-12-16 15:04 ` Guenter Roeck
2019-12-16 15:53 ` Guido Günther
2019-12-16 21:12 ` Nick Desaulniers
2019-12-17 6:38 ` Dominik Brodowski [this message]
2019-12-17 18:04 ` Nick Desaulniers
2019-12-12 17:11 ` [PATCH 0/3] " Linus Torvalds
2019-12-12 18:37 ` Al Viro
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=20191217063846.GA3247@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rafael@kernel.org \
--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).