From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: kbuild-all@lists.01.org
Subject: Re: arch/mips/sibyte/common/sb_tbprof.c:515:23: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Tue, 15 Feb 2022 16:03:00 +0100 [thread overview]
Message-ID: <20220215150300.GA23034@alpha.franken.de> (raw)
In-Reply-To: <20220214080429.GA18136@lst.de>
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
On Mon, Feb 14, 2022 at 09:04:29AM +0100, Christoph Hellwig wrote:
> Thomas, can you find someone who cares about the sibyte support to
> fix up the address space annotations in this code?
I'll have a look.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Christoph Hellwig <hch@lst.de>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/mips/sibyte/common/sb_tbprof.c:515:23: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Tue, 15 Feb 2022 16:03:00 +0100 [thread overview]
Message-ID: <20220215150300.GA23034@alpha.franken.de> (raw)
In-Reply-To: <20220214080429.GA18136@lst.de>
On Mon, Feb 14, 2022 at 09:04:29AM +0100, Christoph Hellwig wrote:
> Thomas, can you find someone who cares about the sibyte support to
> fix up the address space annotations in this code?
I'll have a look.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-02-15 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 21:00 arch/mips/sibyte/common/sb_tbprof.c:515:23: sparse: sparse: incorrect type in initializer (different address spaces) kernel test robot
2022-02-12 21:00 ` kernel test robot
2022-02-14 8:04 ` Christoph Hellwig
2022-02-14 8:04 ` Christoph Hellwig
2022-02-15 15:03 ` Thomas Bogendoerfer [this message]
2022-02-15 15:03 ` Thomas Bogendoerfer
-- strict thread matches above, loose matches on Subject: below --
2021-12-16 10:19 kernel test robot
2021-12-16 10:19 ` kernel test robot
2021-12-02 10:36 kernel test robot
2021-12-02 10:36 ` kernel test robot
2021-05-18 21:54 kernel test robot
2021-05-18 21:54 ` kernel test robot
2021-05-01 21:30 kernel test robot
2021-05-01 21:30 ` kernel test robot
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=20220215150300.GA23034@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=kbuild-all@lists.01.org \
/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.