Received: by 10.223.185.116 with SMTP id b49csp1038579wrg; Fri, 16 Feb 2018 11:15:59 -0800 (PST) X-Google-Smtp-Source: AH8x225japjVWSXhY7Vo8EHjEdINBIUXPKKD3Gv/aLvkU/DEaipghTBSq2YiguOSA7vwUhF788PT X-Received: by 10.98.21.82 with SMTP id 79mr7060711pfv.150.1518808559853; Fri, 16 Feb 2018 11:15:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518808559; cv=none; d=google.com; s=arc-20160816; b=KNxEzqNxhQzd6IR67hA87tio0JgaUxGcnvPE/cAzPtyfnH485y5Wv2HUG5bRfUnJWQ dc5N9tunIPWHL+glUdPvVqXpCQQillLqiUMG1OQsuim7c+QqiPF2ygQNJkyHAhz6b3MM t+QDb6Gra/rm5KkDauHPH2GZX8whqaYHHdDGPjZpuBv0/Fktfz1swkCqOHYStEPs9nvL j1lb5xliXTXOpIJz6B97YmBWEcUu3Mm09UgJVzfgEpBtfSWXuebq5ENVBT9JUie/kboo a5Q7rThUnkFD+pZ6A2sg4Q0X3sapHTArcYUzRCg6WgsFBqS00JVEBHE97dytPVHvYZJT xKVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:in-reply-to :subject:cc:to:from:date:arc-authentication-results; bh=+KfHnBd6FnS2mHbS4j2O5/mX5Z764lvFpTgGS28KfyY=; b=bjE1JWdTJUGckbtM6AzyFqV4v8sd/MJ0rxaCpQLjo+EKwP/H5yCtQHvQ/9Vwbzq0tp 0UIHn9tnohCzGT1KYSjeQxLXzg/qU0xPVT2a4XPhQnCz76XkR8Wdz8WwjlBOo95XZKP4 ZTXxmQSZTaRkYcOfaDYKncNr5o4cjr0mc7JoIdRTwCsdgEFQlkcpiCxV+sTjY+npraeK +6hhY2CR7P3NGY2tzGDaz3W8H2LaumEmQycquKvZ/O6LIagntjumiw4g0nOJfcFqR2n2 /J6NZq8woqWkN3YilQPoaQeRIz9Gmuga0iWd56UhlkFqW2hlap8ZgtOjHmKcRc6pQMsH xzxg== 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 a5-v6si66921plh.450.2018.02.16.11.15.45; Fri, 16 Feb 2018 11:15:59 -0800 (PST) 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 S1754714AbeBPPSg (ORCPT + 99 others); Fri, 16 Feb 2018 10:18:36 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:53620 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752192AbeBPPSf (ORCPT ); Fri, 16 Feb 2018 10:18:35 -0500 Received: (qmail 1604 invoked by uid 2102); 16 Feb 2018 10:18:34 -0500 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Feb 2018 10:18:34 -0500 Date: Fri, 16 Feb 2018 10:18:34 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Akira Yokosawa cc: "Paul E. McKenney" , , , , , , , , , , , Patrick Bellasi Subject: Re: Trial of conflict resolution of Alan's patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Feb 2018, Akira Yokosawa wrote: > Hi, > > My forward-port patch doesn't apply to the "lkmm" branch. > It looks like "linux-kernel-hardware.cat" is intentionally omitted there. > Am I guessing right? > > If this is the case, I can prepare a patch to be applied to "lkmm". > But I can't compose a proper change log. So I'd like Alan to post > a patch with my SOB appended. Does this approach sound reasonable? The patch is not yet ready to be merged. At the very least, I need to include an update to explanation.txt along with it. When it is all ready, I will rebase it on Paul's repository and post it. Which reminds me: Now that the material has been accepted into the kernel, do we need to keep the github repository? It has the linux-kernel-hardware.cat file, but otherwise it seems to be redundant. Alan