Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754527AbcJZJzq (ORCPT ); Wed, 26 Oct 2016 05:55:46 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:53151 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752681AbcJZJzl (ORCPT ); Wed, 26 Oct 2016 05:55:41 -0400 From: Arnd Bergmann To: Baoyou Xie Cc: yisen.zhuang@huawei.com, salil.mehta@huawei.com, davem@davemloft.net, yankejian@huawei.com, huangdaode@hisilicon.com, lisheng011@huawei.com, fabf@skynet.be, xieqianqian@huawei.com, lipeng321@huawei.com, Colin King , weiyongjun1@huawei.com, oulijun@huawei.com, vinod.koul@intel.com, andrew@lunn.ch, Philippe Reynes , xypron.glpk@gmx.de, Network Development , Linux Kernel Mailing List , xie.baoyou@zte.com.cn, han.fei@zte.com.cn, tang.qiang007@zte.com.cn Subject: Re: [PATCH] net: hns: mark symbols static where possible Date: Wed, 26 Oct 2016 11:53:06 +0200 Message-ID: <21348245.KSjHuUMv5P@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: References: <1477474968-13123-1-git-send-email-baoyou.xie@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:wxFf4cTB7HZJ5Cghye1oKMSJrTbE7hLH15DxbuMdjkT20W2Empf 5K7Sgk8rjzS1cFYjy/o84lneNIH4GfBCfcGWzqgJo0ZFtoMpm7Nhnwr6Fz2xKH6vpX9BcK0 S4HiRKGtYe9HDGyiJwgg7lOnYTMY2VAp2ioMScEAKT31T0XQmBy4K/mfENuRQwvaCY227dy +DWeIajHli2gr1tjFDKQw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ianNxfKyoI4=:UnLIL4vBO5+VuUWVmceji/ VvywAXSWlTiaP8W9//+ee6HUtFNuSrtrHYDXkLj5HcJTRnkhMYZjvfmeTYDI41jvB2WdM8o1v lCVSpVNFqXo4NlAGrLeafEKtnqTJlAwaZzWHO6EeODzTmKfacdSBEtDL7CkoQ4x0AUhFTCfVk zBqgXyWxhjrn1NW4xsCkhUpYXs+n96pLaaBP0zuDXtUTxMhIceFBdHxTYyzaehHgNCFkgAhRK /I+yWk+3CatjiEra0juE40KTq1vESsiHryOXhgVJk+T0ubtJHIAD0BXtja/o+3LUIVSmOqf04 DJgquZwbLR47Sm4e79pMlDjOIcCMuErvh0x2vTvT7oWwyshGtt9bwLsFMQEDEnTp5omtMV3/z lQrAGUcgjr4JYOxaUvvwHP69L81DREDpuwBXeFxXoI8+5CnwLFG2WEk082v469ZgjazoO1aIC zhA2PjnRSnWwbz0Vr7hYJP63+LqP1OeXY3c3aL8gCMFD50kQAD662YRYc+Fb9GHBvSgv+rZ9z ykKs/J1/MXOBK2DwEsLT0YdCauIOm+cNYiK1/g8GbkBnwiLL7mel/wmx7mcoj9jSmbDgYqy/L bys2bjx+6mjXlXwbVpzFS7PANn294HAiu7VDTM+8UgtSOy4vNcSbC0buKkkkv8M/yr42ahYcE E1R/yJKGhvy/L4AKX6Jd7wacGagXXKYlf51s0e4h2p2PXISNU0Os3khvlwjG0FfMNX7K1tGez QSt9Bev35xWFfozK Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 786 Lines: 21 On Wednesday, October 26, 2016 5:48:32 PM CEST Baoyou Xie wrote: > In fact, last month I sent a similar patch to fix the warnings, but this > older patch is based on linux-next, not net git tree, so the patch didn't > apply. > > now, I rework the patch base on git:// > git.kernel.org/pub/scm/linux/kernel/git/davem/net.git. I think I see the mistake that led to the confusion before: you should base cleanups for network drivers on net-next.git, not net.git. The correct URL is git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git and it is usually very close to linux-next, except for patches that just got applied and have not made it into the latest linux-next. Only if you find a serious bug, use net.git instead so the fix can go into the mainline kernel. Arnd