From: Linus Torvalds <torvalds@linux-foundation.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>, Linux-MM <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v3 0/3] bootconfig: Fixes to bootconfig memory management
Date: Wed, 15 Sep 2021 09:47:06 -0700 [thread overview]
Message-ID: <CAHk-=wjtP5U-jr7cpTS78iqyh6rys15-Gf0VwoqngNNH1AQH8Q@mail.gmail.com> (raw)
In-Reply-To: <163171196689.590070.15063104707696447188.stgit@devnote2>
On Wed, Sep 15, 2021 at 6:19 AM Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> But still I'm thinking how I can move lib/bootconfig.c and bootconfig.h
So having slept on it, I think the solution for now is "it's been a
problem only this once, let's ignore it for now"
IOW, I'll apply your trivial fixup for the bootconfig copy of
memblock.h, and forget about it, and then if we end up having more
problems with it later, we can look at a bigger fix.
Linus
next prev parent reply other threads:[~2021-09-15 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 13:19 Masami Hiramatsu
2021-09-15 13:19 ` [PATCH v3 1/3] bootconfig: init: Fix memblock leak in xbc_make_cmdline() Masami Hiramatsu
2021-09-15 13:19 ` [PATCH v3 2/3] bootconfig: init: Fix memblock leak in setup_boot_config() Masami Hiramatsu
2021-09-15 13:19 ` [PATCH v3 3/3] bootconfig: Free xbc_data in xbc_destroy_all() Masami Hiramatsu
2021-09-15 14:23 ` Steven Rostedt
2021-09-16 0:05 ` Masami Hiramatsu
2021-09-16 0:17 ` Steven Rostedt
2021-09-15 16:47 ` Linus Torvalds [this message]
2021-09-15 16:51 ` [PATCH v3 0/3] bootconfig: Fixes to bootconfig memory management Linus Torvalds
2021-09-16 0:07 ` Masami Hiramatsu
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='CAHk-=wjtP5U-jr7cpTS78iqyh6rys15-Gf0VwoqngNNH1AQH8Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
/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