From: Lyude Paul <lyude@redhat.com>
To: khsieh@codeaurora.org
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
robdclark@gmail.com, sean@poorly.run, swboyd@chromium.org,
abhinavk@codeaurora.org, aravindh@codeaurora.org,
rsubbia@codeaurora.org, rnayak@codeaurora.org,
freedreno@lists.freedesktop.org, airlied@linux.ie,
daniel@ffwll.ch, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/dp_mst: Fix return code on sideband message failure
Date: Tue, 27 Jul 2021 18:44:34 -0400 [thread overview]
Message-ID: <e725235a77935184cd20dab5af55da95b28d9e88.camel@redhat.com> (raw)
In-Reply-To: <696a009e2ab34747abd12bda03c103c7@codeaurora.org>
Nice timing, you literally got me as I was 2 minutes away from leaving work
for the day :P. I will go ahead and push it now.
BTW - in the future I recommend using dim to add Fixes: tags as it'll add Cc:
to stable as appropriate (this patch in particular should be Cc:
stable@vger.kernel.org # v5.3+). will add these tags when I push it
On Tue, 2021-07-27 at 15:41 -0700, khsieh@codeaurora.org wrote:
> On 2021-07-27 12:21, Lyude Paul wrote:
> > On Thu, 2021-07-22 at 15:28 -0700, khsieh@codeaurora.org wrote:
> > >
> > > It looks like this patch is good to go (mainlined).
> > > Anything needed from me to do?
> > > Thanks,
> >
> > Do you have access for pushing this patch? If not let me know and I can
> > go
> > ahead and push it to drm-misc-next for you.
> no, I do not have access to drm-misc-next.
> Please push it for me.
> Thanks a lots.
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
WARNING: multiple messages have this Message-ID (diff)
From: Lyude Paul <lyude@redhat.com>
To: khsieh@codeaurora.org
Cc: rnayak@codeaurora.org, tzimmermann@suse.de, airlied@linux.ie,
freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, abhinavk@codeaurora.org,
swboyd@chromium.org, aravindh@codeaurora.org, sean@poorly.run,
rsubbia@codeaurora.org
Subject: Re: [PATCH v3] drm/dp_mst: Fix return code on sideband message failure
Date: Tue, 27 Jul 2021 18:44:34 -0400 [thread overview]
Message-ID: <e725235a77935184cd20dab5af55da95b28d9e88.camel@redhat.com> (raw)
In-Reply-To: <696a009e2ab34747abd12bda03c103c7@codeaurora.org>
Nice timing, you literally got me as I was 2 minutes away from leaving work
for the day :P. I will go ahead and push it now.
BTW - in the future I recommend using dim to add Fixes: tags as it'll add Cc:
to stable as appropriate (this patch in particular should be Cc:
stable@vger.kernel.org # v5.3+). will add these tags when I push it
On Tue, 2021-07-27 at 15:41 -0700, khsieh@codeaurora.org wrote:
> On 2021-07-27 12:21, Lyude Paul wrote:
> > On Thu, 2021-07-22 at 15:28 -0700, khsieh@codeaurora.org wrote:
> > >
> > > It looks like this patch is good to go (mainlined).
> > > Anything needed from me to do?
> > > Thanks,
> >
> > Do you have access for pushing this patch? If not let me know and I can
> > go
> > ahead and push it to drm-misc-next for you.
> no, I do not have access to drm-misc-next.
> Please push it for me.
> Thanks a lots.
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
next prev parent reply other threads:[~2021-07-27 22:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 15:30 [PATCH v3] drm/dp_mst: Fix return code on sideband message failure Kuogee Hsieh
2021-07-06 15:30 ` Kuogee Hsieh
2021-07-07 8:37 ` Jani Nikula
2021-07-07 8:37 ` Jani Nikula
2021-07-13 22:24 ` khsieh
2021-07-13 22:24 ` khsieh
2021-07-22 17:53 ` Lyude Paul
2021-07-22 17:53 ` Lyude Paul
2021-07-22 22:28 ` khsieh
2021-07-22 22:28 ` khsieh
2021-07-27 19:21 ` Lyude Paul
2021-07-27 19:21 ` Lyude Paul
2021-07-27 22:41 ` khsieh
2021-07-27 22:41 ` khsieh
2021-07-27 22:44 ` Lyude Paul [this message]
2021-07-27 22:44 ` Lyude Paul
2021-08-25 16:06 ` khsieh
2021-08-25 16:26 ` Lyude Paul
2021-08-25 16:26 ` Lyude Paul
2021-08-30 15:56 ` khsieh
2021-08-30 16:58 ` Lyude Paul
2021-08-30 16:58 ` Lyude Paul
2021-08-30 22:57 ` Stephen Boyd
2021-08-30 22:57 ` Stephen Boyd
2021-09-07 20:47 ` khsieh
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=e725235a77935184cd20dab5af55da95b28d9e88.camel@redhat.com \
--to=lyude@redhat.com \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=aravindh@codeaurora.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=khsieh@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rnayak@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=rsubbia@codeaurora.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=tzimmermann@suse.de \
/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.