From: "Fancer's opinion" <fancer.lancer@gmail.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Paul Burton <Paul.Burton@mips.com>,
Linux-MIPS <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>, Huacai Chen <chenhc@lemote.com>,
Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips: switch to NO_BOOTMEM
Date: Thu, 9 Aug 2018 00:30:03 +0300 [thread overview]
Message-ID: <CAMPMW8qq-aEm-0dQrWh08SBBSRp3xAqR1PL5Oe-RvkJgUk6LjA@mail.gmail.com> (raw)
In-Reply-To: <20180802115550.GA10232@rapoport-lnx>
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
Hello Mike,
I haven't read your patch text yet. I am waiting for the subsystem
maintainers response at least
about the necessity to have this type of changes being merged into the
sources (I mean
memblock/no-bootmem alteration). If they find it pointless (although I
would strongly disagree), then
nothing to discuss. Otherwise we can come up with a solution.
-Sergey
On Thu, Aug 2, 2018 at 2:56 PM Mike Rapoport <rppt@linux.vnet.ibm.com>
wrote:
> Hi,
>
> On Thu, Jul 26, 2018 at 10:55:53PM +0300, Fancer's opinion wrote:
> > Hello, folks
> > Regarding the no_bootmem patchset I've sent earlier.
> > I'm terribly sorry about huge delay with response. I got sucked in a new
> > project, so just didn't have a time to proceed with the series, answer
> to the
> > questions and resend the set.
> > If it is still relevant and needed for community, I can get back to the
> series
> > on the next week, answer to the Mett's questions (sorry, man, for doing
> it so
> > long), rebase it on top of the kernel 4.18 and resend the new version.
> We also
> > can try to combine it with this patch, if it is found convenient.
>
> So, what would be the best way to move forward?
>
> > Regards,
> > -Sergey
> >
> >
> > On Thu, 26 Jul 2018, 20:20 Paul Burton, <paul.burton@mips.com> wrote:
> >
> > Hi Mike,
> >
> > On Thu, Jul 26, 2018 at 10:03:56AM +0300, Mike Rapoport wrote:
> > > Any comments on this?
> >
> > I haven't looked at this in detail yet, but there was a much larger
> > series submitted to accomplish this not too long ago, which needed
> > another revision:
> >
> >
> https://patchwork.linux-mips.org/project/linux-mips/list/?series=787&
> > state=*
> >
> > Given that, I'd be (pleasantly) surprised if this one smaller patch
> is
> > enough.
> >
> > Thanks,
> > Paul
> >
>
> --
> Sincerely yours,
> Mike.
>
>
[-- Attachment #2: Type: text/html, Size: 2704 bytes --]
next prev parent reply other threads:[~2018-08-08 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 7:47 [PATCH] mips: switch to NO_BOOTMEM Mike Rapoport
2018-07-26 7:03 ` Mike Rapoport
2018-07-26 17:20 ` Paul Burton
2018-07-26 19:55 ` Fancer's opinion
2018-08-02 11:55 ` Mike Rapoport
2018-08-08 21:30 ` Fancer's opinion [this message]
2018-08-08 21:42 ` Paul Burton
2018-08-09 12:34 ` Mike Rapoport
2018-07-27 21:23 ` Mike Rapoport
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=CAMPMW8qq-aEm-0dQrWh08SBBSRp3xAqR1PL5Oe-RvkJgUk6LjA@mail.gmail.com \
--to=fancer.lancer@gmail.com \
--cc=Paul.Burton@mips.com \
--cc=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=ralf@linux-mips.org \
--cc=rppt@linux.vnet.ibm.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).