From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>,
anshuman.gupta@intel.com, intel-gfx@lists.freedesktop.org,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH] drm/i915/hwmon: Fix a build error used with clang compiler
Date: Thu, 27 Oct 2022 09:53:15 -0700 [thread overview]
Message-ID: <877d0lxl6s.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <CAKwvOdkpQvk31zbipLDPXfsDZ8FpGHs9t-+9JfFQO85Bs4h=wg@mail.gmail.com>
On Thu, 27 Oct 2022 09:35:24 -0700, Nick Desaulniers wrote:
>
Hi Nick,
> On Tue, Oct 25, 2022 at 5:18 PM Andi Shyti <andi.shyti@linux.intel.com> wrote:
> >
> > Hi Ashutosh,
> >
> > > But I'd wait to hear from clang/llvm folks first.
> >
> > Yeah! Looking forward to getting some ideas :)
>
> Gwan-gyeong, which tree and set of configs are necessary to reproduce
> the observed warning?
>
> Warnings are treated as errors, so I don't want this breaking our CI.
The following or equivalent should do it:
git clone https://anongit.freedesktop.org/git/drm/drm-tip
git checkout drm-tip
Kernel config:
CONFIG_DRM_I915=m
CONFIG_HWMON=y
Files:
drivers/gpu/drm/i915/i915_hwmon.c/.h
Thanks for taking a look.
--
Ashutosh
next prev parent reply other threads:[~2022-10-27 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221024210953.1572998-1-gwan-gyeong.mun@intel.com>
[not found] ` <87mt9kppb6.wl-ashutosh.dixit@intel.com>
[not found] ` <Y1ercgaqQwfqt42U@ashyti-mobl2.lan>
2022-10-25 16:46 ` [PATCH] drm/i915/hwmon: Fix a build error used with clang compiler Nick Desaulniers
2022-10-25 18:45 ` Dixit, Ashutosh
2022-10-26 0:18 ` Andi Shyti
2022-10-27 16:35 ` Nick Desaulniers
2022-10-27 16:53 ` Dixit, Ashutosh [this message]
2022-10-27 17:16 ` Nick Desaulniers
2022-10-27 18:32 ` Dixit, Ashutosh
2022-10-28 6:26 ` Gwan-gyeong Mun
2022-10-28 6:43 ` Gwan-gyeong Mun
2022-10-28 8:46 ` Jani Nikula
2022-11-02 6:32 ` [Intel-gfx] " Joonas Lahtinen
2022-11-02 10:41 ` Gwan-gyeong Mun
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=877d0lxl6s.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=gwan-gyeong.mun@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.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