From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "rafael@kernel.org" <rafael@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"rppt@kernel.org" <rppt@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"pavel@ucw.cz" <pavel@ucw.cz>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"Lutomirski, Andy" <luto@kernel.org>,
"bp@alien8.de" <bp@alien8.de>, "Brown, Len" <len.brown@intel.com>
Subject: Re: [PATCH] x86/hibernate: Use fixmap for saving unmapped pages
Date: Tue, 10 Jan 2023 17:36:56 +0000 [thread overview]
Message-ID: <8f73fdf9d1c9b94cbe1587bf8f5271ca65f17caa.camel@intel.com> (raw)
In-Reply-To: <CAJZ5v0j6qd930BKWWf-e+_Vod0Wv16LZChCOa0yf0_uLC=UMyw@mail.gmail.com>
On Tue, 2023-01-03 at 18:55 +0100, Rafael J. Wysocki wrote:
> > > OK, so I don't feel like it is 6.2 material at this point.
> > >
> > > Please resend it when 6.2-rc1 is out so it gets some more
> > > significant
> > > linux-next coverage before going into the mainline.
> > >
> > > Thanks!
> >
> > Hi,
> >
> > This still applies fine on both tip and Linus' tree. Is it a good
> > time?
>
> Sure.
>
> Thanks!
I didn't see this picked up anywhere. Not sure if I'm missing it, or
this exchange was just ambiguous. I thought you could just apply this
send of it. Do you need anything from me?
Thanks,
Rick
next prev parent reply other threads:[~2023-01-10 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 0:28 Rick Edgecombe
2022-12-05 12:46 ` Rafael J. Wysocki
2023-01-03 17:23 ` Edgecombe, Rick P
2023-01-03 17:55 ` Rafael J. Wysocki
2023-01-10 17:36 ` Edgecombe, Rick P [this message]
2023-01-10 17:40 ` Rafael J. Wysocki
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=8f73fdf9d1c9b94cbe1587bf8f5271ca65f17caa.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®