From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, maddy@linux.ibm.com,
mpe@ellerman.id.au
Cc: npiggin@gmail.com, chleroy@kernel.org, shivangu@linux.ibm.com,
hbathini@linux.ibm.com, mahesh@linux.ibm.com,
adityag@linux.ibm.com, venkat88@linux.ibm.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2 0/3] powerpc/crash: protect kdump from active watchdogs
Date: Mon, 13 Jul 2026 17:09:18 +0530 [thread overview]
Message-ID: <jyqzunix.ritesh.list@gmail.com> (raw)
In-Reply-To: <a5f57d59-a246-4279-946f-2e41d1b438a7@linux.ibm.com>
Sourabh Jain <sourabhjain@linux.ibm.com> writes:
>
> Okay, for stable tree inclusion, CCing is enough.
yup, by ccing here means, adding a "Cc: stable@vger.kernel.org" tag to
the commit should do.
-ritesh
prev parent reply other threads:[~2026-07-13 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 3:59 [PATCH v2 0/3] powerpc/crash: protect kdump from active watchdogs Sourabh Jain
2026-07-13 3:59 ` [PATCH v2 1/3] powerpc/pseries: Move H_WATCHDOG definitions to a common header Sourabh Jain
2026-07-13 4:18 ` Ritesh Harjani
2026-07-13 4:29 ` Sourabh Jain
2026-07-13 3:59 ` [PATCH v2 2/3] powerpc/pseries: Handle and log pseries-wdt registration failures Sourabh Jain
2026-07-13 4:29 ` Ritesh Harjani
2026-07-13 4:44 ` Sourabh Jain
2026-07-13 3:59 ` [PATCH v2 3/3] powerpc/crash: stop watchdogs before booting kdump kernel Sourabh Jain
2026-07-13 5:10 ` Ritesh Harjani
2026-07-13 13:37 ` Sourabh Jain
2026-07-13 5:21 ` [PATCH v2 0/3] powerpc/crash: protect kdump from active watchdogs Ritesh Harjani
2026-07-13 5:59 ` Sourabh Jain
2026-07-13 6:40 ` Ritesh Harjani
2026-07-13 11:30 ` Sourabh Jain
2026-07-13 11:39 ` Ritesh Harjani [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=jyqzunix.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=adityag@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=shivangu@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=venkat88@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox