From: Daniel Thompson <daniel.thompson@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>
Subject: Re: linux-next: Tree for May 21
Date: Thu, 21 May 2020 16:09:06 +0100 [thread overview]
Message-ID: <20200521150906.u2obtw5qcybkjjxz@holly.lan> (raw)
In-Reply-To: <20200522001209.07c19400@canb.auug.org.au>
On Fri, May 22, 2020 at 12:12:09AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200519:
>
> My fixes tree contains:
>
> cd2b06ec45d6 ("device_cgroup: Fix RCU list debugging warning")
>
> The f2fs tree gained a conflict against the fscrypt tree.
>
> The drm-msm tree still had its build failure so I applied a patch.
>
> The kvm tree gained a semantic conflict against the tip tree.
>
> The usb-gadget tree gained a conflict against the usb tree.
>
> The userns tree gained a build failure so I used ther version from
> next-20200519.
>
> The kgdb tree still had its build failure so I used the version from
> next-20200518.
Doh... I have updated my pre-push tests, merged the fix and tested.
Unfortunately I then pushed the results to the wrong git server :-(.
Thanks, and should be all set for tomorrow.
Daniel.
next prev parent reply other threads:[~2020-05-21 15:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 14:12 linux-next: Tree for May 21 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson [this message]
2020-05-22 2:34 ` linux-next: Tree for May 21 (objtool warnings) Randy Dunlap
2020-05-22 16:34 ` Josh Poimboeuf
2020-05-25 10:10 ` Miroslav Benes
2020-05-25 11:07 ` Miroslav Benes
2020-05-26 14:01 ` Josh Poimboeuf
2020-05-26 16:39 ` Miroslav Benes
2020-05-25 18:04 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 6:44 linux-next: Tree for May 21 Stephen Rothwell
2019-05-21 5:14 Stephen Rothwell
2019-05-21 5:48 ` Masahiro Yamada
2019-05-21 6:18 ` Stephen Rothwell
2015-05-21 8:57 Stephen Rothwell
2014-05-21 7:50 Stephen Rothwell
2014-05-22 10:45 ` Michael Kerrisk
2014-05-22 22:06 ` Stephen Rothwell
2014-05-23 4:22 ` Michael Kerrisk (man-pages)
2013-05-21 5:03 Stephen Rothwell
2012-05-21 9:05 Stephen Rothwell
2012-05-21 15:09 ` Randy Dunlap
2012-05-21 15:41 ` Stephen Rothwell
2012-05-21 15:44 ` Stephen Rothwell
2010-05-21 6:51 Stephen Rothwell
2009-05-21 8:14 Stephen Rothwell
2008-05-21 5:59 Stephen Rothwell
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=20200521150906.u2obtw5qcybkjjxz@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).