From: Richard Weinberger <richard@nod.at>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kent overstreet <kent.overstreet@linux.dev>,
SeongJae Park <sj@kernel.org>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-mm <linux-mm@kvack.org>,
linux-um <linux-um@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc
Date: Mon, 22 Apr 2024 22:50:00 +0200 (CEST) [thread overview]
Message-ID: <714170984.15180.1713819000411.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAJuCfpFsrQxa2CX66xQtxp=Y-=R5_YkJMMX9VQ-g32rdCrukeg@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "Suren Baghdasaryan" <surenb@google.com>
>> > It's in mm-unstable under dc26c7e79daf2fc11169b23c150862f0e878ee5a. I
>> > think it just didn't reach Linus' tree yet.
>>
>> Hmm, so we better postpone this path until said commit hits Linus tree,
>> or you carry it together with the commit in mm-unstable.
>
> Oh, sorry, I didn't realize you were talking about the `Fixes:
> 576477564ede` part... Yeah, unfortunately SHAs in mm-unstable are
> unstable, so the change being fixed is under
> edf0a25633bda1e5b7844478dd13b4326a3d5d09 now. I think Andrew placed
> this fix right after the change it fixes with intention to merge them
> together later on.
Ah, the patch itself goes via Andrew's tree, works for me!
Let me note this in the uml patchwork system.
Acked-by: Richard Weinberger <richard@nod.at>
Thanks,
//richard
prev parent reply other threads:[~2024-04-22 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 7:37 [PATCH 1/1] arch/um: fix forward declaration for vmalloc Suren Baghdasaryan
2024-03-26 15:37 ` SeongJae Park
2024-03-28 8:48 ` Johannes Berg
2024-04-22 20:11 ` Richard Weinberger
2024-04-22 20:19 ` Suren Baghdasaryan
2024-04-22 20:31 ` Richard Weinberger
2024-04-22 20:39 ` Suren Baghdasaryan
2024-04-22 20:50 ` Richard Weinberger [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=714170984.15180.1713819000411.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sj@kernel.org \
--cc=surenb@google.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;
as well as URLs for NNTP newsgroup(s).