From: Karol Herbst <email@example.com> To: Salvatore Bonaccorso <firstname.lastname@example.org> Cc: Lyude Paul <email@example.com>, Jeremy Cline <firstname.lastname@example.org>, Ben Skeggs <email@example.com>, David Airlie <firstname.lastname@example.org>, nouveau <email@example.com>, dri-devel <firstname.lastname@example.org>, LKML <email@example.com> Subject: Re: [PATCH v2 0/3] drm/nouveau: fix a use-after-free in postclose() Date: Mon, 11 Oct 2021 13:05:21 +0200 [thread overview] Message-ID: <CACO55tvokQBKz1ZyhK_2hN=V7rgV3n_L=PYNh8RLA+y8n93qRQ@mail.gmail.com> (raw) In-Reply-To: <YWPiU+9G0AKglHmi@eldamar.lan> I am currently checking the ML for such old patches, just have to make sure it's actually fine and not breaking stuff as well. But I think we will pull this in soonish, I just also work on improving our CI stuff at the same time by trying out some things. On Mon, Oct 11, 2021 at 9:06 AM Salvatore Bonaccorso <firstname.lastname@example.org> wrote: > > Hi Ben, > > On Tue, Aug 17, 2021 at 04:32:31PM -0400, Lyude Paul wrote: > > It may have been, we're in the process of trying to change around how we > > currently accept nouveau patches to stop this from happening in the future. > > > > Ben, whenever you get a moment can you take a look at this? > > > > On Mon, 2021-08-16 at 09:03 +0200, Salvatore Bonaccorso wrote: > > > Hi, > > > > > > On Fri, Mar 26, 2021 at 06:00:51PM -0400, Lyude Paul wrote: > > > > This patch series is: > > > > > > > > Reviewed-by: Lyude Paul <email@example.com> > > > > > > > > Btw - in the future if you need to send a respin of multiple patches, you > > > > need > > > > to send it as it's own separate series instead of replying to the previous > > > > one > > > > (one-off respins can just be posted as replies though), otherwise > > > > patchwork > > > > won't pick it up > > > > > > Did this patch series somehow fall through the cracks or got lost? > > Looking some older threads, noticed this one. Ben did you got a chance > to look at it, or is it now irrelevant by other means? > > Regards, > Salvatore >
prev parent reply other threads:[~2021-10-11 11:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-03 19:49 [PATCH " Jeremy Cline 2020-11-03 19:49 ` [PATCH 1/3] drm/nouveau: use drm_dev_unplug() during device removal Jeremy Cline 2020-11-03 19:49 ` [PATCH 2/3] drm/nouveau: Add a dedicated mutex for the clients list Jeremy Cline 2020-11-25 18:37 ` Lyude Paul 2020-11-25 19:45 ` Jeremy Cline 2020-11-03 19:49 ` [PATCH 3/3] drm/nouveau: clean up all clients on device removal Jeremy Cline 2020-11-25 18:44 ` Lyude Paul 2020-11-25 20:26 ` [PATCH v2 0/3] drm/nouveau: fix a use-after-free in postclose() Jeremy Cline 2020-11-25 20:26 ` [PATCH v2 1/3] drm/nouveau: use drm_dev_unplug() during device removal Jeremy Cline 2020-11-25 20:26 ` [PATCH v2 2/3] drm/nouveau: Add a dedicated mutex for the clients list Jeremy Cline 2020-11-25 20:26 ` [PATCH v2 3/3] drm/nouveau: clean up all clients on device removal Jeremy Cline 2021-03-26 22:00 ` [PATCH v2 0/3] drm/nouveau: fix a use-after-free in postclose() Lyude Paul 2021-08-16 7:03 ` Salvatore Bonaccorso 2021-08-17 20:32 ` Lyude Paul 2021-10-11 7:05 ` Salvatore Bonaccorso 2021-10-11 11:05 ` Karol Herbst [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='CACO55tvokQBKz1ZyhK_2hN=V7rgV3n_L=PYNh8RLA+y8n93qRQ@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v2 0/3] drm/nouveau: fix a use-after-free in postclose()' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).