From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754405AbbG3BfN (ORCPT ); Wed, 29 Jul 2015 21:35:13 -0400 Received: from mail-ob0-f173.google.com ([209.85.214.173]:35765 "EHLO mail-ob0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752424AbbG3BfL (ORCPT ); Wed, 29 Jul 2015 21:35:11 -0400 MIME-Version: 1.0 In-Reply-To: <20150730112325.72240f81@canb.auug.org.au> References: <20150730112325.72240f81@canb.auug.org.au> Date: Wed, 29 Jul 2015 21:35:11 -0400 Message-ID: Subject: Re: linux-next: manual merge of the nfsd tree with Linus' tree From: Trond Myklebust To: Stephen Rothwell Cc: "J. Bruce Fields" , Linux Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Wed, Jul 29, 2015 at 9:23 PM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the nfsd tree got a conflict in: > > fs/nfs/nfs42proc.c > > between commit: > > bdcc2cd14e4e ("NFSv4.2: handle NFS-specific llseek errors") > > from Linus' tree and commit: > > 0183ae17c741 ("NFSv4.2: handle NFS-specific llseek errors") > > from the nfsd tree. > > The only difference here is that _nfs42_proc_llseek is static in the > former, so I used that. > Yes, I snuck that declaration into the patch since it was obvious that we would never want to export _nfs42_proc_llseek(), and because "sparse" complained. Apologies if that caused a conflict... Cheers Trond