From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Boot regression in Linux v6.4-rc3
Date: Tue, 30 May 2023 21:11:06 +0000 [thread overview]
Message-ID: <20230530-richly-vowed-cbd6d6@meerkat> (raw)
In-Reply-To: <abb1166d-27a9-fbae-59cd-841480fba78a@web.de>
On Tue, May 30, 2023 at 05:04:56PM -0400, Linus Torvalds wrote:
> On Tue, May 30, 2023 at 4:21 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> >
> > We only add things to lore when someone asks, and nobody's asked. :) I guess
> > I'll consider this an ask and put it on the radar.
>
> Thanks. It would probably be good to see if there are any other
> vger.kernel.org lists with any appreciable traffic that aren't on
> lore.
Yes, that will auto-fix itself as we continue to migrate things over to
subspace ("new vger").
-K
WARNING: multiple messages have this Message-ID (diff)
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frank Scheiner <frank.scheiner@web.de>,
Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
linux-ia64@vger.kernel.org, song@kernel.org,
debian-ia64 <debian-ia64@lists.debian.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: Boot regression in Linux v6.4-rc3
Date: Tue, 30 May 2023 17:11:06 -0400 [thread overview]
Message-ID: <20230530-richly-vowed-cbd6d6@meerkat> (raw)
Message-ID: <20230530211106.umcc9MqZWT6XSiZ-Ffn6i3PNMFs-cOO14xjHxH1SgLU@z> (raw)
In-Reply-To: <CAHk-=wh=mF941kP0DduTt91V+HSuTqBAU8pXp34wSn6DSMPmrQ@mail.gmail.com>
On Tue, May 30, 2023 at 05:04:56PM -0400, Linus Torvalds wrote:
> On Tue, May 30, 2023 at 4:21 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> >
> > We only add things to lore when someone asks, and nobody's asked. :) I guess
> > I'll consider this an ask and put it on the radar.
>
> Thanks. It would probably be good to see if there are any other
> vger.kernel.org lists with any appreciable traffic that aren't on
> lore.
Yes, that will auto-fix itself as we continue to migrate things over to
subspace ("new vger").
-K
next prev parent reply other threads:[~2023-05-30 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 10:55 Boot regression in Linux v6.4-rc3 Frank Scheiner
2023-05-26 16:49 ` Song Liu
2023-05-26 18:30 ` Frank Scheiner
2023-05-26 21:01 ` Song Liu
2023-05-26 21:59 ` Luis Chamberlain
2023-05-26 22:22 ` Linus Torvalds
2023-05-26 22:39 ` Song Liu
2023-05-27 6:26 ` Frank Scheiner
2023-05-27 7:01 ` Frank Scheiner
2023-05-27 17:08 ` Linus Torvalds
2023-05-27 18:34 ` Frank Scheiner
2023-05-27 19:34 ` Linus Torvalds
2023-05-27 21:13 ` Frank Scheiner
2023-05-28 5:24 ` Song Liu
2023-05-28 7:30 ` Frank Scheiner
2023-05-28 8:09 ` Frank Scheiner
2023-05-28 10:13 ` John Paul Adrian Glaubitz
2023-05-28 22:46 ` Song Liu
2023-05-30 20:21 ` Konstantin Ryabitsev
2023-05-30 21:04 ` Linus Torvalds
2023-05-30 21:04 ` Linus Torvalds
2023-05-30 21:11 ` Konstantin Ryabitsev [this message]
2023-05-30 21:11 ` Konstantin Ryabitsev
-- strict thread matches above, loose matches on Subject: below --
2023-05-31 18:15 Frank Scheiner
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=20230530-richly-vowed-cbd6d6@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=linux-ia64@vger.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).