linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Regzbot (on behalf of Thorsten Leemhuis)" 
	<regressions@leemhuis.info>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
Date: Fri, 20 May 2022 19:01:29 -1000	[thread overview]
Message-ID: <CAHk-=wjKtV3mT3S=vxgqe__MUzxRrZ7=fopKQtTKOeQJAVyoUQ@mail.gmail.com> (raw)
In-Reply-To: <063d7fdb-2d4c-5798-773b-d82b4f0e918a@redhat.com>

On Thu, May 19, 2022 at 6:10 AM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Note this is not part of any pending drm-fixes* pull-reqs yet though.

It has now hit my tree as part of Dave's drm pull today.

Will go out after the usual basic build test.

               Linus

  reply	other threads:[~2022-05-21  5:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09  8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09  9:13   ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20   ` Linus Torvalds
2022-05-09 19:04     ` Hans de Goede
2022-05-10 14:41       ` Maarten Lankhorst
2022-05-17 15:50       ` Hans de Goede
2022-05-19 16:09         ` Hans de Goede
2022-05-21  5:01           ` Linus Torvalds [this message]
2022-05-21 11:30             ` Thorsten Leemhuis
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck

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='CAHk-=wjKtV3mT3S=vxgqe__MUzxRrZ7=fopKQtTKOeQJAVyoUQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=hdegoede@redhat.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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 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).