From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
lkft-triage@lists.linaro.org
Subject: Re: linux-next: Tree for Jul 30 [build failure on arm64]
Date: Fri, 31 Jul 2020 19:42:04 +1000 [thread overview]
Message-ID: <20200731194204.1db950e4@canb.auug.org.au> (raw)
In-Reply-To: <20200731090022.GB12930@lst.de>
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
Hi Christoph,
On Fri, 31 Jul 2020 11:00:22 +0200 Christoph Hellwig <hch@lst.de> wrote:
>
> Please just drop the branch for now.
I will revert those 4 commits from today's linux-next and all Al needs
to do is reset his for-next branch to its parent.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-31 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 11:46 linux-next: Tree for Jul 30 Stephen Rothwell
2020-07-30 15:07 ` linux-next: Tree for Jul 30 (drivers/crypto/chelsio/) Randy Dunlap
2020-07-31 2:46 ` linux-next: Tree for Jul 30 [build failure on arm64] Shaokun Zhang
2020-07-31 4:08 ` Stephen Rothwell
2020-07-31 8:30 ` Naresh Kamboju
2020-07-31 8:53 ` Stephen Rothwell
2020-07-31 9:00 ` Christoph Hellwig
2020-07-31 9:42 ` Stephen Rothwell [this message]
2020-07-31 8:56 ` Shaokun Zhang
2020-07-31 9:18 ` Christoph Hellwig
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=20200731194204.1db950e4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zhangshaokun@hisilicon.com \
/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.