Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3121651imm; Tue, 29 May 2018 01:08:52 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqrHEZ/loDtE/Pq1Tygier8YrZnSBSHobhzL2uBJf7KclApRUaK6gwA+AhtthC3pCAykQT8 X-Received: by 2002:a17:902:8f94:: with SMTP id z20-v6mr16710211plo.391.1527581332343; Tue, 29 May 2018 01:08:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527581332; cv=none; d=google.com; s=arc-20160816; b=k59J7KQKL+GYYICgQIU5rF/winBoxXK7UZOcuMHD0Gv22FgOf/CD/WF2FlOQ0wTkyb kDHfh8tWdm2jozbDsa1LxdTZydrmYk4Ch0wjIwoGEZMqKGE0RXLHxkQxugSNZG3bz4q4 5mUVk+Sk+5o1kj3XGTVirRb1uhgp5HyhyCTc9UMuYp+H7YFVOK+k1loOxq4H2QqBCgDn L/3SPrsg0uwet5FdghcZxaPZmTM4tqCwSug4Y8M4qeinID0A9bpDmvhhodHdTbWhyXg1 fVQf1q+ZQRWX50agOPYwY+GMvq/4YjQfWnLhABO8uTziUmikONR2YGBEAw0to77US6iR NkkQ== 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:arc-authentication-results; bh=/RC5BXnqmWQsV9YVly9cnEoK6Uw0dBltfrwUuzEhFQs=; b=a8OvfooS4zbdVH4V7fYlASYA3w4FxHDn63Gq9pFFcDsqeg3Uae0w1bL9qoYqwJpjOo D/DcXiD44EiaSiUxmQqvy/B+4onWlATq3ZOpqCmWgvYhVNNF81gdextZrPTUUw0cbl95 ZolFXyVYxSX0MxUpPi+QPkT8KgImlV9di9r2KNw7cD8YqGit0yY3xxsbLLJ/SHsVU0Yp R9RHR/EqhaLdFLMTaOoyjoLQYm02VTxdKKg9YyvzJCFF58dL7VeXMbOXNpyGmJfuw9Uk EZDQAqSCO2dItU/yFJT3ILxDV3tGxyz3vXDZ+4BzwHjd+Oh7yV7Mp1tFDwEnqMa/WFTV +0dQ== 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 c196-v6si25198895pga.494.2018.05.29.01.08.38; Tue, 29 May 2018 01:08:52 -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 S1755320AbeE2IGE (ORCPT + 99 others); Tue, 29 May 2018 04:06:04 -0400 Received: from verein.lst.de ([213.95.11.211]:53837 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754942AbeE2IFz (ORCPT ); Tue, 29 May 2018 04:05:55 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 411A668E42; Tue, 29 May 2018 10:12:05 +0200 (CEST) Date: Tue, 29 May 2018 10:12:05 +0200 From: Christoph Hellwig To: Stephen Rothwell Cc: Jens Axboe , Al Viro , Linux-Next Mailing List , Linux Kernel Mailing List , Christoph Hellwig , Joe Perches Subject: Re: linux-next: manual merge of the block tree with the vfs tree Message-ID: <20180529081205.GB1416@lst.de> References: <20180529143357.2a66b0af@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180529143357.2a66b0af@canb.auug.org.au> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Meh. Do we really need these switch to octal patches to start with? I mean, I personally prefer octal, but just switching around in random code that isn't otherwise changed creates nothing but churn. On Tue, May 29, 2018 at 02:33:57PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the block tree got a conflict in: > > drivers/block/DAC960.c > > between commit: > > 3f3942aca6da ("proc: introduce proc_create_single{,_data}") > > from the vfs tree and commit: > > 5657a819a8d9 ("block drivers/block: Use octal not symbolic permissions") > > from the block tree. > > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for merging. You may also want to consider cooperating > with the maintainer of the conflicting tree to minimise any particularly > complex conflicts. > > -- > Cheers, > Stephen Rothwell > > diff --cc drivers/block/DAC960.c > index 6918c3d9482e,7c3887a7e534..000000000000 > --- a/drivers/block/DAC960.c > +++ b/drivers/block/DAC960.c > @@@ -6553,11 -6587,9 +6548,11 @@@ static void DAC960_CreateProcEntries(DA > "c%d", Controller->ControllerNumber); > ControllerProcEntry = proc_mkdir(Controller->ControllerName, > DAC960_ProcDirectoryEntry); > - proc_create_data("initial_status", 0, ControllerProcEntry, &dac960_initial_status_proc_fops, Controller); > - proc_create_data("current_status", 0, ControllerProcEntry, &dac960_current_status_proc_fops, Controller); > + proc_create_single_data("initial_status", 0, ControllerProcEntry, > + dac960_initial_status_proc_show, Controller); > + proc_create_single_data("current_status", 0, ControllerProcEntry, > + dac960_current_status_proc_show, Controller); > - proc_create_data("user_command", S_IWUSR | S_IRUSR, ControllerProcEntry, &dac960_user_command_proc_fops, Controller); > + proc_create_data("user_command", 0600, ControllerProcEntry, &dac960_user_command_proc_fops, Controller); > Controller->ControllerProcEntry = ControllerProcEntry; > } > ---end quoted text---