Received: by 10.192.165.156 with SMTP id m28csp101600imm; Tue, 17 Apr 2018 07:12:08 -0700 (PDT) X-Google-Smtp-Source: AIpwx49U4HJ2A09fUi+igQVpgkCeGbHhZDp2Qz0eSJO4paONunrFQ0SSr7CVvduafxNf2sASlWCK X-Received: by 10.99.100.6 with SMTP id y6mr1933995pgb.205.1523974328166; Tue, 17 Apr 2018 07:12:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523974328; cv=none; d=google.com; s=arc-20160816; b=g80cebyUhCqsQN/mBvbdMAB9Nay7AOVfbtaMVdcO83DqJXdhNg10+TIhd+DjAELPJd Hma5+JnJpokeHBXk0x3OoHEL+yj0X+txR9gMUMWiEkVD136r1QRbm3y39dGlMz2MBCWe TrPRW9xukuvItWTMjPou30zJ6FSjddhNAGi007r+z+i6L4WDPVKqtw8h7Dlt013Zec4d VP1Uu4ZfnnTRyoHbHKJjYyhLjGTXiavUFejEBmOIf80QzR+2BPshfo8CG5f1gtmSgd4v 71lbbxQIFhGk8CIx2wstJxuLOLQU3O3fNB2PZbi1t/UsVq1MM9GIuNnahN94RxqjHTHw X0Sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:arc-authentication-results; bh=cbHpCNSfK7aybvrzadiVlcCuQV23HDr44hEnEdizFog=; b=fWPxYaHQTMOqmOgbrQOHre8paNsTP7LtbU79sDhrPF5hcja66ONKLDb+oOJd4z1Lq2 bLLsc7PFy6uun79HnjJW22lLTNSGJ8Bp2xGBWBA++iy1jxC+BE169Kg9e5xeR3lPdl3X /Z4xdmF4UQqLClHfzPvWVLTBQdou+ZaokORiOZeRiwcADY0j0A23u6VcjRtRAdKNOd8m VvNao7tNGBDSBeyImIcMdTZyRHhqkawWVL0QQlThjfcCpNP25d+gXSxMZ0OD3HWHdaw9 VjGwgy9KhwqxstwFabQOKQ8bck1ZURISc12snE7+lxZo1Y1sPoOVJnm/tfHNJMtmWhlE faeg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g9si12672319pfi.113.2018.04.17.07.11.54; Tue, 17 Apr 2018 07:12:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752947AbeDQOKE (ORCPT + 99 others); Tue, 17 Apr 2018 10:10:04 -0400 Received: from mail.kernel.org ([198.145.29.99]:33890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751211AbeDQOKC (ORCPT ); Tue, 17 Apr 2018 10:10:02 -0400 Received: from localhost (unknown [69.71.5.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 56B8E21727; Tue, 17 Apr 2018 14:10:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 56B8E21727 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Tue, 17 Apr 2018 09:09:59 -0500 From: Bjorn Helgaas To: Philipp Rudo Cc: Eric Biederman , Thiago Jung Bauermann , Michael Ellerman , Dave Young , kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 0/2] kexec: Remove "weak" annotations from headers Message-ID: <20180417140959.GG28657@bhelgaas-glaptop.roam.corp.google.com> References: <152355706051.36693.9856090891621551967.stgit@bhelgaas-glaptop.roam.corp.google.com> <20180413110820.662d4879@ThinkPad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180413110820.662d4879@ThinkPad> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 13, 2018 at 11:08:20AM +0200, Philipp Rudo wrote: > Hi Bjorn, > > in recent patches AKASHI [1] and I [2] made some changes to the declarations > you are touching and already removed some of the weak statements. The patches > got accepted on linux-next and will (hopefully) be pulled for v4.17. So you > should prepare for some merge conflicts. Nevertheless three weak statements > still remain (arch_kexec_walk_mem & arch_kexec_apply_relocations*) so your > patch still makes totally sense. Thanks, I see those changes in v4.17-rc1. I'll update my patches and post a v2.