From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: "Valdis Klētnieks" <valdis.kletnieks-PjAqaU27lzQ@public.gmane.org>
Cc: David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: linux-next 20200508 - build failure in kernel/resource.c w/ SPARSEMEM=n
Date: Sat, 9 May 2020 16:08:02 +0200 [thread overview]
Message-ID: <20200509140802.GA26307@lst.de> (raw)
In-Reply-To: <17362.1589022588@turing-police>
I think the problem is the select of CONFIG_DEVICE_PRIVATE. Jason is
looking into it already.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>,
Christoph Hellwig <hch@lst.de>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next 20200508 - build failure in kernel/resource.c w/ SPARSEMEM=n
Date: Sat, 9 May 2020 16:08:02 +0200 [thread overview]
Message-ID: <20200509140802.GA26307@lst.de> (raw)
In-Reply-To: <17362.1589022588@turing-police>
I think the problem is the select of CONFIG_DEVICE_PRIVATE. Jason is
looking into it already.
next prev parent reply other threads:[~2020-05-09 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 11:09 linux-next 20200508 - build failure in kernel/resource.c w/ SPARSEMEM=n Valdis Klētnieks
2020-05-09 11:09 ` Valdis Klētnieks
2020-05-09 14:08 ` Christoph Hellwig [this message]
2020-05-09 14:08 ` 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=20200509140802.GA26307@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=valdis.kletnieks-PjAqaU27lzQ@public.gmane.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.