From: David Howells <dhowells@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: dhowells@redhat.com, kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: Re: [ammarfaizi2-block:dhowells/linux-fs/afs-testing 44/45] arch/sparc/include/asm/cmpxchg_64.h:95:36: sparse: sparse: cast truncates bits from constant value (5e5ee5e5 becomes e5e5)
Date: Mon, 28 Mar 2022 13:00:43 +0100 [thread overview]
Message-ID: <2579599.1648468843@warthog.procyon.org.uk> (raw)
In-Reply-To: <202203270732.dEGMthw5-lkp@intel.com>
kernel test robot <lkp@intel.com> wrote:
> >> arch/sparc/include/asm/cmpxchg_64.h:95:36: sparse: sparse: cast truncates bits from constant value (5e5ee5e5 becomes e5e5)
Just ignore this. The patch that triggered the objection is a debugging patch
designed to track down a specific problem and is not intended for upstreaming.
David
prev parent reply other threads:[~2022-03-28 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 23:37 [ammarfaizi2-block:dhowells/linux-fs/afs-testing 44/45] arch/sparc/include/asm/cmpxchg_64.h:95:36: sparse: sparse: cast truncates bits from constant value (5e5ee5e5 becomes e5e5) kernel test robot
2022-03-28 12:00 ` David Howells [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=2579599.1648468843@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox