From: Sasha Levin <sashal@kernel.org>
To: Sean Paul <sean@poorly.run>
Cc: Lyude Paul <lyude@redhat.com>,
dri-devel@lists.freedesktop.org,
Sean Paul <seanpaul@chromium.org>,
Todd Previte <tprevite@gmail.com>,
Dave Airlie <airlied@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm: mst: Fix query_payload ack reply struct
Date: Thu, 29 Aug 2019 16:52:09 -0400 [thread overview]
Message-ID: <20190829205209.GL5281@sasha-vm> (raw)
In-Reply-To: <20190829184415.GI218215@art_vandelay>
On Thu, Aug 29, 2019 at 02:44:15PM -0400, Sean Paul wrote:
>On Thu, Aug 29, 2019 at 01:06:58PM -0400, Lyude Paul wrote:
>> Is it worth actually CCing stable on this? This patch is certainly correct but
>> I don't think we use this struct for anything quite yet.
>>
>> Otherwise: Reviewed-by: Lyude Paul <lyude@redhat.com>
>
>Thanks for the review! I've stripped the cc stable tag and pushed to
>drm-misc-next. We'll have to keep an eye out for Sasha's stable AI bot, I'm
>guessing it'll try to backport this to stable regardless.
Knowing the bot, it probably will :)
I'll add a note for myself...
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sean Paul <sean@poorly.run>
Cc: Lyude Paul <lyude@redhat.com>,
dri-devel@lists.freedesktop.org,
Sean Paul <seanpaul@chromium.org>,
Todd Previte <tprevite@gmail.com>,
Dave Airlie <airlied@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm: mst: Fix query_payload ack reply struct
Date: Thu, 29 Aug 2019 16:52:09 -0400 [thread overview]
Message-ID: <20190829205209.GL5281@sasha-vm> (raw)
In-Reply-To: <20190829184415.GI218215@art_vandelay>
On Thu, Aug 29, 2019 at 02:44:15PM -0400, Sean Paul wrote:
>On Thu, Aug 29, 2019 at 01:06:58PM -0400, Lyude Paul wrote:
>> Is it worth actually CCing stable on this? This patch is certainly correct but
>> I don't think we use this struct for anything quite yet.
>>
>> Otherwise: Reviewed-by: Lyude Paul <lyude@redhat.com>
>
>Thanks for the review! I've stripped the cc stable tag and pushed to
>drm-misc-next. We'll have to keep an eye out for Sasha's stable AI bot, I'm
>guessing it'll try to backport this to stable regardless.
Knowing the bot, it probably will :)
I'll add a note for myself...
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-08-29 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 16:52 [PATCH] drm: mst: Fix query_payload ack reply struct Sean Paul
2019-08-29 17:06 ` Lyude Paul
2019-08-29 18:44 ` Sean Paul
2019-08-29 20:52 ` Sasha Levin [this message]
2019-08-29 20:52 ` Sasha Levin
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=20190829205209.GL5281@sasha-vm \
--to=sashal@kernel.org \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tprevite@gmail.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 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.