mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org, Jianpeng Ma <jianpeng.ma@intel.com>,
	Jens Axboe <axboe@kernel.dk>, Qiaowei Ren <qiaowei.ren@intel.com>
Subject: Re: next-20210420 build breakage on 32-bit - include/uapi/linux/bcache-nvm.h
Date: Wed, 21 Apr 2021 18:00:10 +0800	[thread overview]
Message-ID: <046326c5-8059-355a-9991-2eac7be282a4@suse.de> (raw)
In-Reply-To: <697668.1618991971@turing-police>

On 4/21/21 3:59 PM, Valdis Klētnieks wrote:
> commit 97d69b16cb973e04ea5309b9cb4356aa6b42c54e
> Author: Coly Li <colyli@suse.de>
> Date:   Wed Apr 14 13:46:36 2021 +0800
> 
>     bcache: add initial data structures for nvm pages
> 
> contains this code:
> 
> +#if (__BITS_PER_LONG != 64)
> +       #error "Non-64bit platform is not supported"
> +#endif
> 
> This breaks the build on arm and other 32-bit systems:
> 
>   HDRTEST usr/include/linux/bcache-nvm.h
> In file included from <command-line>:32:
> ./usr/include/linux/bcache-nvm.h:109:3: error: #error "Non-64bit platform is not supported"
>   #error "Non-64bit platform is not supported"
>    ^~~~~
> make[3]: *** [/usr/src/linux-next/usr/include/Makefile:106: usr/include/linux/bcache-nvm.hdrtest] Error 1
> make[2]: *** [/usr/src/linux-next/scripts/Makefile.build:534: usr/include] Error 2
> make[1]: *** [/usr/src/linux-next/Makefile:1967: usr] Error 2
> 

Hi Valdis,

This series is withdrawn from 5.13 queue, this failure can be safely
ignored.

Thanks.

Coly Li

      reply	other threads:[~2021-04-21 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  7:59 Valdis Klētnieks
2021-04-21 10:00 ` Coly Li [this message]

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=046326c5-8059-355a-9991-2eac7be282a4@suse.de \
    --to=colyli@suse.de \
    --cc=axboe@kernel.dk \
    --cc=jianpeng.ma@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiaowei.ren@intel.com \
    --cc=valdis.kletnieks@vt.edu \
    /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

all inboxes | Powered by JetHome®