From: Takashi Iwai <tiwai@suse.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects
Date: Thu, 08 Apr 2021 19:29:51 +0200 [thread overview]
Message-ID: <s5hy2ds65ww.wl-tiwai@suse.de> (raw)
In-Reply-To: <YG81picGSzpb84fU@intel.com>
On Thu, 08 Apr 2021 18:56:06 +0200,
Ville Syrjälä wrote:
>
> On Thu, Apr 08, 2021 at 06:34:06PM +0200, Takashi Iwai wrote:
> > On Thu, 08 Apr 2021 09:51:18 +0200,
> > Takashi Iwai wrote:
> > >
> > > On Wed, 07 Apr 2021 23:28:48 +0200,
> > > Ville Syrjälä wrote:
> > > >
> > > > Oh, could you ask the bug reporter to attach an acpidump to the
> > > > bug? Might be good to have that stuff on record somewhere if/when
> > > > someone wants to actually figure out what's going on here.
> > >
> > > OK, I'll ask.
> >
> > Available at
> > acpidump: https://susepaste.org/59777448
> > hwinfo: https://susepaste.org/86284020
>
> Those will apparently expire real soon. I took local copies out
> of morbid curiosity, but that's not going to help anyone else
> in the future. I rather wish bug reporting tools would flat out
> refuse to accept any pastebin links.
Yeah, don't worry, I'll upload them to Bugzilla later in anyway.
Takashi
prev parent reply other threads:[~2021-04-08 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 8:23 [PATCH v2] drm/i915: Fix invalid access to ACPI _DSM objects Takashi Iwai
2021-04-07 16:34 ` [Intel-gfx] " Ville Syrjälä
2021-04-07 16:56 ` Takashi Iwai
2021-04-07 21:28 ` Ville Syrjälä
2021-04-08 7:51 ` Takashi Iwai
2021-04-08 16:34 ` Takashi Iwai
2021-04-08 16:56 ` Ville Syrjälä
2021-04-08 17:29 ` Takashi Iwai [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=s5hy2ds65ww.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@linux.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