From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 02 Aug 2018 13:56:19 +0200 (CEST) Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:59372 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S23993973AbeHBL4QFUBAq (ORCPT ); Thu, 2 Aug 2018 13:56:16 +0200 Received: from pps.filterd (m0098416.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w72BsCtn132202 for ; Thu, 2 Aug 2018 07:56:13 -0400 Received: from e06smtp05.uk.ibm.com (e06smtp05.uk.ibm.com [195.75.94.101]) by mx0b-001b2d01.pphosted.com with ESMTP id 2kkx7h8jjd-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 02 Aug 2018 07:56:13 -0400 Received: from localhost by e06smtp05.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 2 Aug 2018 12:56:06 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp05.uk.ibm.com (192.168.101.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 2 Aug 2018 12:56:02 +0100 Received: from d06av25.portsmouth.uk.ibm.com (d06av25.portsmouth.uk.ibm.com [9.149.105.61]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w72Bu1sw34865164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 2 Aug 2018 11:56:01 GMT Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2E0EB11C04A; Thu, 2 Aug 2018 14:56:11 +0100 (BST) Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 74D4811C052; Thu, 2 Aug 2018 14:56:06 +0100 (BST) Received: from rapoport-lnx (unknown [9.148.207.181]) by d06av25.portsmouth.uk.ibm.com (Postfix) with ESMTPS; Thu, 2 Aug 2018 14:56:05 +0100 (BST) Date: Thu, 2 Aug 2018 14:55:51 +0300 From: Mike Rapoport To: "Fancer's opinion" , Paul Burton Cc: Linux-MIPS , Ralf Baechle , James Hogan , Huacai Chen , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mips: switch to NO_BOOTMEM References: <1531727262-11520-1-git-send-email-rppt@linux.vnet.ibm.com> <20180726070355.GD8477@rapoport-lnx> <20180726172005.pgjmkvwz2lpflpor@pburton-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-TM-AS-GCONF: 00 x-cbid: 18080211-0020-0000-0000-000002AFF113 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18080211-0021-0000-0000-000020FC1D95 Message-Id: <20180802115550.GA10232@rapoport-lnx> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-02_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=818 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1808020125 Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 65352 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: rppt@linux.vnet.ibm.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips 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, 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f71.google.com (mail-oi0-f71.google.com [209.85.218.71]) by kanga.kvack.org (Postfix) with ESMTP id CF6DA6B026B for ; Thu, 2 Aug 2018 07:56:11 -0400 (EDT) Received: by mail-oi0-f71.google.com with SMTP id w185-v6so1652743oig.19 for ; Thu, 02 Aug 2018 04:56:11 -0700 (PDT) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com. [148.163.156.1]) by mx.google.com with ESMTPS id u8-v6si1170107oib.9.2018.08.02.04.56.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Aug 2018 04:56:10 -0700 (PDT) Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w72Bs5XX030376 for ; Thu, 2 Aug 2018 07:56:09 -0400 Received: from e06smtp05.uk.ibm.com (e06smtp05.uk.ibm.com [195.75.94.101]) by mx0a-001b2d01.pphosted.com with ESMTP id 2km0kp2f0m-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 02 Aug 2018 07:56:09 -0400 Received: from localhost by e06smtp05.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 2 Aug 2018 12:56:06 +0100 Date: Thu, 2 Aug 2018 14:55:51 +0300 From: Mike Rapoport Subject: Re: [PATCH] mips: switch to NO_BOOTMEM References: <1531727262-11520-1-git-send-email-rppt@linux.vnet.ibm.com> <20180726070355.GD8477@rapoport-lnx> <20180726172005.pgjmkvwz2lpflpor@pburton-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Message-Id: <20180802115550.GA10232@rapoport-lnx> Sender: owner-linux-mm@kvack.org List-ID: To: Fancer's opinion , Paul Burton Cc: Linux-MIPS , Ralf Baechle , James Hogan , Huacai Chen , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org 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, 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.