Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
	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 18:53:54 +1000
Message-ID: <20200731185354.70926525@canb.auug.org.au> (raw)
In-Reply-To: <CA+G9fYvykg9Ly=tRXLrf4hvd4siYKAt5eM0EMnwMgqVDHnbVYQ@mail.gmail.com>


[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

Hi Naresh,

On Fri, 31 Jul 2020 14:00:57 +0530 Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> > Presumably caused by commit
> >
> >   b902bfb3f0e9 ("arm64: stop using <asm/compat.h> directly")  
> 
> I have reverted this commit
>   b902bfb3f0e9 ("arm64: stop using <asm/compat.h> directly")
> 
> and rebuilt arm64 failed due to below errors/warnings.

That commit was in preparation for the following 3 commits.  You would
have to revert them as well to get a good build.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply index

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 [this message]
2020-07-31  9:00         ` Christoph Hellwig
2020-07-31  9:42           ` Stephen Rothwell
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=20200731185354.70926525@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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git