All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Laurent Dufour <ldufour@linux.ibm.com>, Daniel Axtens <dja@axtens.net>
Subject: Re: (subset) [PATCH v4 0/5] powerpc: watchdog fixes
Date: Wed, 08 Dec 2021 00:26:54 +1100	[thread overview]
Message-ID: <163888361403.3690807.15839669782410709977.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20211119113146.752759-1-npiggin@gmail.com>

On Fri, 19 Nov 2021 21:31:41 +1000, Nicholas Piggin wrote:
> These are some watchdog fixes and improvements, in particular a
> deadlock between the wd_smp_lock and console lock when the watchdog
> fires, found by Laurent.
> 
> Thanks,
> Nick
> 
> [...]

Patch 5 applied to powerpc/next.

[5/5] powerpc/watchdog: help remote CPUs to flush NMI printk output
      https://git.kernel.org/powerpc/c/e012c499985c608c936410d8bab29d9596d62859

cheers

      parent reply	other threads:[~2021-12-07 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 11:31 [PATCH v4 0/5] powerpc: watchdog fixes Nicholas Piggin
2021-11-19 11:31 ` [PATCH v4 1/5] powerpc/watchdog: Fix missed watchdog reset due to memory ordering race Nicholas Piggin
2021-11-19 11:31 ` [PATCH v4 2/5] powerpc/watchdog: tighten non-atomic read-modify-write access Nicholas Piggin
2021-11-19 11:31 ` [PATCH v4 3/5] powerpc/watchdog: Avoid holding wd_smp_lock over printk and smp_send_nmi_ipi Nicholas Piggin
2021-11-19 11:31 ` [PATCH v4 4/5] powerpc/watchdog: read TB close to where it is used Nicholas Piggin
2021-11-19 11:31 ` [PATCH v4 5/5] powerpc/watchdog: help remote CPUs to flush NMI printk output Nicholas Piggin
2021-11-19 15:32   ` Laurent Dufour
2021-12-07 13:26 ` Michael Ellerman [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=163888361403.3690807.15839669782410709977.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=dja@axtens.net \
    --cc=ldufour@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    /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.