From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755134AbcITPSJ (ORCPT ); Tue, 20 Sep 2016 11:18:09 -0400 Received: from casper.infradead.org ([85.118.1.10]:54596 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752028AbcITPSI (ORCPT ); Tue, 20 Sep 2016 11:18:08 -0400 Date: Tue, 20 Sep 2016 16:18:01 +0100 (BST) From: James Simmons To: Dan Carpenter cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, James Simmons , Andreas Dilger , Linux Kernel Mailing List , Oleg Drokin , Lustre Development List Subject: Re: [PATCH] staging: lustre: ptlrpc: re-export lustre_swab_[lmv|lov]_mds_md In-Reply-To: <20160920085134.GH13620@mwanda> Message-ID: References: <1474306025-1942-1-git-send-email-jsimmons@infradead.org> <20160920064702.GB8527@kroah.com> <20160920085134.GH13620@mwanda> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20160920_161801_144642_525FB019 X-CRM114-Status: GOOD ( 15.52 ) X-Spam-Score: -1.9 (-) X-Spam-Report: SpamAssassin version 3.4.1 on casper.infradead.org summary: Content analysis details: (-1.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 NO_RELAYS Informational: message was not relayed via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > On Mon, Sep 19, 2016 at 01:27:05PM -0400, James Simmons wrote: > > > Being over zealous in removing unused EXPORT_SYMBOLs two functions > > > lustre_swab_[lmv|lov]_mds_md exports were removed. They need to be > > > exported so this patch restores those EXPORT_SYMBOLS. Same mistake > > > was done when porting to the upstream client. > > > > How did our build testing not catch this? What needs these exports? Is > > it any in-kernel code? > > > > confused, > > It did catch it... James, every patch has to be buildable (bisectable) > so the original patch is never going to be merged. We missed it original as well due to the fact it showed up on only specific platforms. I have no idea why that is. The majority of the time it works. BTW is there a way to run kbuild bot on a patch set before submission to avoid these corner cases.