Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 21 May 2020 16:09:06 +0100
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
Message-ID: <20200521150906.u2obtw5qcybkjjxz@holly.lan>
References: <20200522001209.07c19400@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200522001209.07c19400@canb.auug.org.au>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.