From: Baoquan He <bhe@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Eric Biederman <ebiederm@xmission.com>,
Philipp Rudo <prudo@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
Philipp Rudo <prudo@redhat.com>
Subject: Re: [PATCH] kexec: Support purgatories with .text.hot sections
Date: Thu, 23 Mar 2023 08:17:35 +0800 [thread overview]
Message-ID: <ZBuan2/9CVPffy9a@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230322110002.120cf674@gandalf.local.home>
On 03/22/23 at 11:00am, Steven Rostedt wrote:
> On Wed, 22 Mar 2023 22:52:04 +0800
> Baoquan He <bhe@redhat.com> wrote:
>
> > When you resne patch, please fix Philipp's mail adress as
> > 'Philipp Rudo <prudo@redhat.com>' if he should know this. He has joined
> > Redhat.
>
> But I thought redhat *was* IBM? ;-)
That's interesting questioin, maybe yes on capital operation, but no
from company operation and management, in an engineer's eyes.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Eric Biederman <ebiederm@xmission.com>,
Philipp Rudo <prudo@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
Philipp Rudo <prudo@redhat.com>
Subject: Re: [PATCH] kexec: Support purgatories with .text.hot sections
Date: Thu, 23 Mar 2023 08:17:35 +0800 [thread overview]
Message-ID: <ZBuan2/9CVPffy9a@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230322110002.120cf674@gandalf.local.home>
On 03/22/23 at 11:00am, Steven Rostedt wrote:
> On Wed, 22 Mar 2023 22:52:04 +0800
> Baoquan He <bhe@redhat.com> wrote:
>
> > When you resne patch, please fix Philipp's mail adress as
> > 'Philipp Rudo <prudo@redhat.com>' if he should know this. He has joined
> > Redhat.
>
> But I thought redhat *was* IBM? ;-)
That's interesting questioin, maybe yes on capital operation, but no
from company operation and management, in an engineer's eyes.
next prev parent reply other threads:[~2023-03-23 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 11:49 [PATCH] kexec: Support purgatories with .text.hot sections Ricardo Ribalda
2023-03-21 11:49 ` Ricardo Ribalda
2023-03-22 14:34 ` Steven Rostedt
2023-03-22 14:34 ` Steven Rostedt
2023-03-22 14:42 ` Ricardo Ribalda
2023-03-22 14:42 ` Ricardo Ribalda
2023-03-22 14:52 ` Baoquan He
2023-03-22 14:52 ` Baoquan He
2023-03-22 15:00 ` Steven Rostedt
2023-03-22 15:00 ` Steven Rostedt
2023-03-23 0:17 ` Baoquan He [this message]
2023-03-23 0:17 ` Baoquan He
2023-03-22 20:13 ` Ross Zwisler
2023-03-22 20:13 ` Ross Zwisler
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=ZBuan2/9CVPffy9a@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@linux.vnet.ibm.com \
--cc=prudo@redhat.com \
--cc=ribalda@chromium.org \
--cc=rostedt@goodmis.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.