From: Alexey Lukyachuk <skif@skif-web.ru>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix
Date: Tue, 3 Jan 2023 13:24:26 +0300 [thread overview]
Message-ID: <20230103132426.0c6d144f@alexey-Swift-SF314-42> (raw)
In-Reply-To: <87a630ylg5.fsf@intel.com>
On Tue, 03 Jan 2023 12:14:02 +0200
Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 02 Jan 2023, Alexey Lukyachuk <skif@skif-web.ru> wrote:
> > Regarding to your question about fdo gitlab, I went to do it.
>
> What's the URL for the issue?
>
> BR,
> Jani.
>
I have not submited issue in bug tracker because I found solution in git.
("Before filing the bug, please try to reproduce your issue with the
latest kernel. Use the latest drm-tip branch from
http://cgit.freedesktop.org/drm-tip and build as instructed on
our Build Guide.")
Should I do it?
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Lukyachuk <skif@skif-web.ru>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix
Date: Tue, 3 Jan 2023 13:24:26 +0300 [thread overview]
Message-ID: <20230103132426.0c6d144f@alexey-Swift-SF314-42> (raw)
In-Reply-To: <87a630ylg5.fsf@intel.com>
On Tue, 03 Jan 2023 12:14:02 +0200
Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 02 Jan 2023, Alexey Lukyachuk <skif@skif-web.ru> wrote:
> > Regarding to your question about fdo gitlab, I went to do it.
>
> What's the URL for the issue?
>
> BR,
> Jani.
>
I have not submited issue in bug tracker because I found solution in git.
("Before filing the bug, please try to reproduce your issue with the
latest kernel. Use the latest drm-tip branch from
http://cgit.freedesktop.org/drm-tip and build as instructed on
our Build Guide.")
Should I do it?
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Lukyachuk <skif@skif-web.ru>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: dell wyse 3040 shutdown fix
Date: Tue, 3 Jan 2023 13:24:26 +0300 [thread overview]
Message-ID: <20230103132426.0c6d144f@alexey-Swift-SF314-42> (raw)
In-Reply-To: <87a630ylg5.fsf@intel.com>
On Tue, 03 Jan 2023 12:14:02 +0200
Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 02 Jan 2023, Alexey Lukyachuk <skif@skif-web.ru> wrote:
> > Regarding to your question about fdo gitlab, I went to do it.
>
> What's the URL for the issue?
>
> BR,
> Jani.
>
I have not submited issue in bug tracker because I found solution in git.
("Before filing the bug, please try to reproduce your issue with the
latest kernel. Use the latest drm-tip branch from
http://cgit.freedesktop.org/drm-tip and build as instructed on
our Build Guide.")
Should I do it?
next prev parent reply other threads:[~2023-01-03 10:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 18:44 [PATCH] drm/i915/: dell wyse 3040 shutdown fix Alexey Lukyanchuk
2022-12-25 18:55 ` [PATCH v2] drm/i915: " Alexey Lukyanchuk
2022-12-25 18:55 ` Alexey Lukyanchuk
2022-12-25 18:55 ` [Intel-gfx] " Alexey Lukyanchuk
2022-12-27 16:39 ` Rodrigo Vivi
2022-12-27 16:39 ` Rodrigo Vivi
2022-12-27 16:39 ` Rodrigo Vivi
2022-12-27 17:40 ` Alexey Lukyachuk
2022-12-27 17:40 ` Alexey Lukyachuk
2022-12-27 17:40 ` Alexey Lukyachuk
2022-12-28 8:50 ` Jani Nikula
2022-12-28 8:50 ` Jani Nikula
2022-12-28 8:50 ` Jani Nikula
2023-01-02 13:56 ` Alexey Lukyachuk
2023-01-02 13:56 ` Alexey Lukyachuk
2023-01-02 13:56 ` Alexey Lukyachuk
2023-01-03 10:14 ` Jani Nikula
2023-01-03 10:14 ` Jani Nikula
2023-01-03 10:14 ` Jani Nikula
2023-01-03 10:24 ` Alexey Lukyachuk [this message]
2023-01-03 10:24 ` Alexey Lukyachuk
2023-01-03 10:24 ` Alexey Lukyachuk
2023-01-04 14:08 ` Jani Nikula
2023-01-04 14:08 ` Jani Nikula
2023-01-04 14:08 ` Jani Nikula
2023-01-03 12:46 ` Rodrigo Vivi
2023-01-03 12:46 ` Rodrigo Vivi
2023-01-03 12:46 ` Rodrigo Vivi
2023-01-03 13:43 ` Jani Nikula
2023-01-03 13:43 ` Jani Nikula
2023-01-03 13:43 ` Jani Nikula
2023-01-03 16:09 ` Alexey Lukyachuk
2023-01-03 16:09 ` Alexey Lukyachuk
2023-01-03 16:09 ` Alexey Lukyachuk
2023-01-03 16:18 ` Rodrigo Vivi
2023-01-03 16:18 ` Rodrigo Vivi
2023-01-03 16:18 ` Rodrigo Vivi
2022-12-25 19:05 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
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=20230103132426.0c6d144f@alexey-Swift-SF314-42 \
--to=skif@skif-web.ru \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.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.