From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kernel/locking: Add context to ww_mutex_trylock.
Date: Mon, 20 Sep 2021 18:02:21 +0300 [thread overview]
Message-ID: <163215014127.5950.11970655278841631448@jlahtine-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <YUSUb+JP+e0f+00G@hirez.programming.kicks-ass.net>
Quoting Peter Zijlstra (2021-09-17 16:13:19)
> On Thu, Sep 16, 2021 at 03:28:11PM +0200, Peter Zijlstra wrote:
> > On Thu, Sep 16, 2021 at 03:00:39PM +0200, Maarten Lankhorst wrote:
> >
> > > > For merge logistics, can we pls have a stable branch? I expect that the
> > > > i915 patches will be ready for 5.16.
> > > >
> > > > Or send it in for -rc2 so that the interface change doesn't cause needless
> > > > conflicts, whatever you think is best.
> >
> > > Yeah, some central branch drm could pull from, would make upstreaming patches that depends on it easier. :)
> >
> > I think I'll make tip/locking/wwmutex and include that in
> > tip/locking/core, let me have a poke.
>
> This is now so. Enjoy!
This is now merged to drm-intel-gt-next.
Regards, Joonas
WARNING: multiple messages have this Message-ID (diff)
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2] kernel/locking: Add context to ww_mutex_trylock.
Date: Mon, 20 Sep 2021 18:02:21 +0300 [thread overview]
Message-ID: <163215014127.5950.11970655278841631448@jlahtine-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <YUSUb+JP+e0f+00G@hirez.programming.kicks-ass.net>
Quoting Peter Zijlstra (2021-09-17 16:13:19)
> On Thu, Sep 16, 2021 at 03:28:11PM +0200, Peter Zijlstra wrote:
> > On Thu, Sep 16, 2021 at 03:00:39PM +0200, Maarten Lankhorst wrote:
> >
> > > > For merge logistics, can we pls have a stable branch? I expect that the
> > > > i915 patches will be ready for 5.16.
> > > >
> > > > Or send it in for -rc2 so that the interface change doesn't cause needless
> > > > conflicts, whatever you think is best.
> >
> > > Yeah, some central branch drm could pull from, would make upstreaming patches that depends on it easier. :)
> >
> > I think I'll make tip/locking/wwmutex and include that in
> > tip/locking/core, let me have a poke.
>
> This is now so. Enjoy!
This is now merged to drm-intel-gt-next.
Regards, Joonas
next prev parent reply other threads:[~2021-09-20 15:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:20 [PATCH] kernel/locking: Add context to ww_mutex_trylock Maarten Lankhorst
2021-09-07 13:20 ` [Intel-gfx] " Maarten Lankhorst
2021-09-07 13:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-09-07 14:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-07 14:59 ` [PATCH] " kernel test robot
2021-09-07 14:59 ` kernel test robot
2021-09-07 14:59 ` [Intel-gfx] " kernel test robot
2021-09-07 17:28 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2021-09-08 10:14 ` [PATCH] " Peter Zijlstra
2021-09-08 10:14 ` [Intel-gfx] " Peter Zijlstra
2021-09-08 18:30 ` Daniel Vetter
2021-09-08 18:30 ` [Intel-gfx] " Daniel Vetter
2021-09-09 5:38 ` Maarten Lankhorst
2021-09-09 5:38 ` [Intel-gfx] " Maarten Lankhorst
2021-09-09 8:22 ` Peter Zijlstra
2021-09-09 8:22 ` [Intel-gfx] " Peter Zijlstra
2021-09-09 9:32 ` [PATCH v2] " Maarten Lankhorst
2021-09-09 9:32 ` [Intel-gfx] " Maarten Lankhorst
2021-09-10 15:02 ` Peter Zijlstra
2021-09-10 15:02 ` [Intel-gfx] " Peter Zijlstra
2021-09-10 17:27 ` Peter Zijlstra
2021-09-10 17:27 ` [Intel-gfx] " Peter Zijlstra
2021-09-13 8:42 ` Maarten Lankhorst
2021-09-13 8:42 ` [Intel-gfx] " Maarten Lankhorst
2021-09-14 6:50 ` Peter Zijlstra
2021-09-14 6:50 ` [Intel-gfx] " Peter Zijlstra
2021-09-14 12:43 ` Maarten Lankhorst
2021-09-14 12:43 ` [Intel-gfx] " Maarten Lankhorst
2021-09-14 13:54 ` Daniel Vetter
2021-09-14 13:54 ` [Intel-gfx] " Daniel Vetter
2021-09-16 13:00 ` Maarten Lankhorst
2021-09-16 13:00 ` [Intel-gfx] " Maarten Lankhorst
2021-09-16 13:28 ` Peter Zijlstra
2021-09-16 13:28 ` [Intel-gfx] " Peter Zijlstra
2021-09-17 13:13 ` Peter Zijlstra
2021-09-17 13:13 ` [Intel-gfx] " Peter Zijlstra
2021-09-20 15:02 ` Joonas Lahtinen [this message]
2021-09-20 15:02 ` Joonas Lahtinen
2021-09-17 13:17 ` [tip: locking/core] kernel/locking: Add context to ww_mutex_trylock() tip-bot2 for Maarten Lankhorst
2021-11-04 12:27 ` [PATCH] kernel/locking: Use a pointer in ww_mutex_trylock() Sebastian Andrzej Siewior
2021-11-04 12:27 ` [Intel-gfx] " Sebastian Andrzej Siewior
2021-11-04 12:27 ` Sebastian Andrzej Siewior
2021-11-17 13:59 ` [tip: locking/core] " tip-bot2 for Sebastian Andrzej Siewior
2021-09-10 18:06 ` [PATCH v2] kernel/locking: Add context to ww_mutex_trylock Mark Brown
2021-09-10 18:06 ` [Intel-gfx] " Mark Brown
2021-09-09 9:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for kernel/locking: Add context to ww_mutex_trylock. (rev2) Patchwork
2021-09-10 15:36 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for kernel/locking: Add context to ww_mutex_trylock. (rev3) Patchwork
2021-09-14 9:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for kernel/locking: Add context to ww_mutex_trylock. (rev4) Patchwork
2021-09-14 9:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-04 16:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for kernel/locking: Add context to ww_mutex_trylock. (rev5) Patchwork
2021-11-04 18:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=163215014127.5950.11970655278841631448@jlahtine-mobl.ger.corp.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=boqun.feng@gmail.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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.