All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Phil Elwell <phil@raspberrypi.com>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Ard Biesheuvel <ardb@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: initialize jump labels before setup_machine_fdt()
Date: Wed, 8 Jun 2022 10:16:16 +0100	[thread overview]
Message-ID: <YqBo4LfSmL7A5eM1@arm.com> (raw)
In-Reply-To: <CAHmME9p+FxQhTQYKWKkxkGiYxErP6NHuvSiFEat7ts1XgsM6YA@mail.gmail.com>

Hi Jason,

On Wed, Jun 08, 2022 at 10:20:21AM +0200, Jason A. Donenfeld wrote:
> On Tue, Jun 7, 2022 at 12:07 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > Do you plan to fix the crng_ready() static branch differently? If you
> > do, I'd like to revert the corresponding arm64 commit as well. It seems
> > to be harmless but I'd rather not keep it if no longer needed. So please
> > keep me updated whatever you decide.
> 
> Feel free to revert. I'm aborting this line of inquiry and will just
> fix it downstream in random.c.

Thanks for the update.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Phil Elwell <phil@raspberrypi.com>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Ard Biesheuvel <ardb@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: initialize jump labels before setup_machine_fdt()
Date: Wed, 8 Jun 2022 10:16:16 +0100	[thread overview]
Message-ID: <YqBo4LfSmL7A5eM1@arm.com> (raw)
In-Reply-To: <CAHmME9p+FxQhTQYKWKkxkGiYxErP6NHuvSiFEat7ts1XgsM6YA@mail.gmail.com>

Hi Jason,

On Wed, Jun 08, 2022 at 10:20:21AM +0200, Jason A. Donenfeld wrote:
> On Tue, Jun 7, 2022 at 12:07 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > Do you plan to fix the crng_ready() static branch differently? If you
> > do, I'd like to revert the corresponding arm64 commit as well. It seems
> > to be harmless but I'd rather not keep it if no longer needed. So please
> > keep me updated whatever you decide.
> 
> Feel free to revert. I'm aborting this line of inquiry and will just
> fix it downstream in random.c.

Thanks for the update.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-08  9:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  8:29 [PATCH v2] ARM: initialize jump labels before setup_machine_fdt() Phil Elwell
2022-06-07  8:30 ` Jason A. Donenfeld
2022-06-07  8:30   ` Jason A. Donenfeld
2022-06-07  8:47   ` Phil Elwell
2022-06-07  8:47     ` Phil Elwell
2022-06-07  8:51     ` Jason A. Donenfeld
2022-06-07  8:51       ` Jason A. Donenfeld
2022-06-07 10:06       ` Catalin Marinas
2022-06-07 10:06         ` Catalin Marinas
2022-06-07 10:11         ` Jason A. Donenfeld
2022-06-07 10:11           ` Jason A. Donenfeld
2022-06-08  8:20         ` Jason A. Donenfeld
2022-06-08  8:20           ` Jason A. Donenfeld
2022-06-08  9:16           ` Catalin Marinas [this message]
2022-06-08  9:16             ` Catalin Marinas
2022-06-07  9:10     ` Greg KH
2022-06-07  9:10       ` Greg KH
2022-06-07 11:04       ` Phil Elwell
2022-06-07 11:04         ` Phil Elwell
2022-06-07 11:09         ` Jason A. Donenfeld
2022-06-07 11:09           ` Jason A. Donenfeld
2022-06-07  9:14   ` Russell King (Oracle)
2022-06-07  9:14     ` Russell King (Oracle)
2022-06-07  9:16     ` Jason A. Donenfeld
2022-06-07  9:16       ` Jason A. Donenfeld
2022-06-07  8:43 ` Jason A. Donenfeld
2022-06-07  8:43   ` Jason A. Donenfeld
2022-06-07  9:15   ` Phil Elwell
2022-06-07  9:15     ` Phil Elwell
2022-06-07 15:14     ` Jason A. Donenfeld
2022-06-07 15:14       ` Jason A. Donenfeld
2022-06-07 15:35       ` Phil Elwell
2022-06-07 15:35         ` Phil Elwell
2022-06-07 15:44         ` Jason A. Donenfeld
2022-06-07 15:44           ` Jason A. Donenfeld
2022-06-07 15:51           ` Phil Elwell
2022-06-07 15:51             ` Phil Elwell
2022-06-07 19:30           ` [PATCH v3] " Jason A. Donenfeld
2022-06-07 19:30             ` Jason A. Donenfeld
2022-06-08  8:18             ` Jason A. Donenfeld
2022-06-08  8:18               ` Jason A. Donenfeld
  -- strict thread matches above, loose matches on Subject: below --
2022-06-03 12:15 [PATCH v2] " Jason A. Donenfeld
2022-06-03 12:15 ` Jason A. Donenfeld

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=YqBo4LfSmL7A5eM1@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=phil@raspberrypi.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stable@vger.kernel.org \
    --cc=swboyd@chromium.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.