From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Wei Liu <wei.liu@kernel.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"bhe@redhat.com" <bhe@redhat.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"pmladek@suse.com" <pmladek@suse.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"kernel-dev@igalia.com" <kernel-dev@igalia.com>,
"kernel@gpiccoli.net" <kernel@gpiccoli.net>,
Andrea Parri <parri.andrea@gmail.com>,
Dexuan Cui <decui@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Tianyu Lan <Tianyu.Lan@microsoft.com>
Subject: Re: [PATCH V3 10/11] drivers/hv/vmbus, video/hyperv_fb: Untangle and refactor Hyper-V panic notifiers
Date: Sat, 12 Nov 2022 18:53:57 -0300 [thread overview]
Message-ID: <44bce9f3-365b-9592-83a9-8608b0cba20b@igalia.com> (raw)
In-Reply-To: <Y27XsybzcgCQ3fzD@liuwe-devbox-debian-v2>
On 11/11/2022 20:16, Wei Liu wrote:
> On Fri, Nov 11, 2022 at 10:47:17PM +0000, Wei Liu wrote:
>> On Thu, Nov 10, 2022 at 06:32:54PM -0300, Guilherme G. Piccoli wrote:
>>> [Trimming long CC list]
>>>
>>> Hi Wei / Michael, just out of curiosity, did this (and patch 9) ended-up
>>> being queued in hyperv-next?
>>>
>>
>> No. They are not queued.
>>
>> I didn't notice Michael's email and thought they would be picked up by
>> someone else while dealing with the whole series.
>>
>> I will pick them up later.
>
> They are now queued to hyperv-next. Thanks.
Thanks a lot Wei and Michael, much appreciated =)
next prev parent reply other threads:[~2022-11-12 21:54 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 22:17 [PATCH V3 00/11] The panic notifiers refactor - fixes/clean-ups (V3) Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 01/11] ARM: Disable FIQs (but not IRQs) on CPUs shutdown paths Guilherme G. Piccoli
2022-09-18 13:58 ` Guilherme G. Piccoli
2022-10-17 14:00 ` Guilherme G. Piccoli
2022-10-17 14:17 ` Russell King (Oracle)
2022-10-17 14:50 ` Guilherme G. Piccoli
2022-10-17 17:47 ` Russell King (Oracle)
2022-10-17 19:43 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 02/11] notifier: Add panic notifiers info and purge trailing whitespaces Guilherme G. Piccoli
2022-11-22 13:19 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 03/11] alpha: Clean-up the panic notifier code Guilherme G. Piccoli
2022-11-22 13:22 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 04/11] um: Improve panic notifiers consistency and ordering Guilherme G. Piccoli
2022-09-18 14:00 ` Guilherme G. Piccoli
2022-09-18 21:19 ` Richard Weinberger
2022-09-19 11:44 ` Guilherme G. Piccoli
2022-10-17 14:01 ` Guilherme G. Piccoli
2022-10-17 14:10 ` Richard Weinberger
2022-10-17 14:22 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 05/11] parisc: Replace regular spinlock with spin_trylock on panic path Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 06/11] tracing: Improve panic/die notifiers Guilherme G. Piccoli
2022-09-18 14:04 ` Guilherme G. Piccoli
2022-10-17 14:02 ` Guilherme G. Piccoli
2022-10-20 21:29 ` Steven Rostedt
2022-10-20 21:53 ` Guilherme G. Piccoli
2022-10-20 22:22 ` Steven Rostedt
2022-10-20 22:37 ` Guilherme G. Piccoli
2022-11-22 13:27 ` Guilherme G. Piccoli
2022-12-13 23:51 ` Guilherme G. Piccoli
2022-12-14 0:06 ` Steven Rostedt
2022-12-14 0:52 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 07/11] notifiers: Add tracepoints to the notifiers infrastructure Guilherme G. Piccoli
2022-09-18 14:07 ` Guilherme G. Piccoli
2022-10-17 14:04 ` Guilherme G. Piccoli
2022-11-22 13:30 ` Guilherme G. Piccoli
2022-08-19 22:17 ` [PATCH V3 08/11] EDAC/altera: Skip the panic notifier if kdump is loaded Guilherme G. Piccoli
2022-09-18 14:10 ` Guilherme G. Piccoli
2022-10-17 14:05 ` Guilherme G. Piccoli
2022-11-22 13:33 ` Guilherme G. Piccoli
2022-11-22 15:06 ` Borislav Petkov
2023-02-10 16:01 ` Guilherme G. Piccoli
2022-12-09 16:03 ` Petr Mladek
2022-08-19 22:17 ` [PATCH V3 09/11] video/hyperv_fb: Avoid taking busy spinlock on panic path Guilherme G. Piccoli
2022-09-18 14:12 ` Guilherme G. Piccoli
2022-10-04 16:17 ` Michael Kelley (LINUX)
2022-08-19 22:17 ` [PATCH V3 10/11] drivers/hv/vmbus, video/hyperv_fb: Untangle and refactor Hyper-V panic notifiers Guilherme G. Piccoli
2022-10-04 16:24 ` Michael Kelley (LINUX)
2022-10-04 17:20 ` Guilherme G. Piccoli
2022-10-17 15:26 ` Michael Kelley (LINUX)
2022-11-10 21:32 ` Guilherme G. Piccoli
2022-11-11 22:47 ` Wei Liu
2022-11-11 23:16 ` Wei Liu
2022-11-12 21:53 ` Guilherme G. Piccoli [this message]
2022-08-19 22:17 ` [PATCH V3 11/11] panic: Fixes the panic_print NMI backtrace setting Guilherme G. Piccoli
2022-09-18 14:13 ` Guilherme G. Piccoli
2022-11-22 13:35 ` Guilherme G. Piccoli
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=44bce9f3-365b-9592-83a9-8608b0cba20b@igalia.com \
--to=gpiccoli@igalia.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=parri.andrea@gmail.com \
--cc=pmladek@suse.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=x86@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 NNTP newsgroup(s).