From: Colin Ian King <colin.king@canonical.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
David Miller <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>
Cc: Yisen Zhuang <yisen.zhuang@huawei.com>,
salil.mehta@huawei.com, huangdaode <huangdaode@hisilicon.com>,
yankejian <yankejian@huawei.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
oulijun@huawei.com, netdev <netdev@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][netdev-next] net: hns: make guid hns_dsaf_acpi_dsm_guid static
Date: Tue, 13 Jun 2017 21:40:15 +0100 [thread overview]
Message-ID: <5b3235bb-5058-82a6-d8be-76d805594cea@canonical.com> (raw)
In-Reply-To: <CAHp75VfQZN8bQj+7J-5tBE8gA5CmQL0xSdf3kajW8z92kCiBmQ@mail.gmail.com>
On 13/06/17 20:24, Andy Shevchenko wrote:
> On Tue, Jun 13, 2017 at 8:56 PM, David Miller <davem@davemloft.net> wrote:
>> From: Colin King <colin.king@canonical.com>
>> Date: Tue, 13 Jun 2017 14:03:21 +0100
>>
>>> From: Colin Ian King <colin.king@canonical.com>
>>>
>>> The guid hns_dsaf_acpi_dsm_guid does not need to be in global
>>> scope, so make it static.
>>>
>>> Cleans up sparse warning:
>>> "symbol 'hns_dsaf_acpi_dsm_guid' was not declared. Should it be static?"
>>>
>>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>>
>> That symbol doesn't even exist in th net-next tree.
>
> It looks like the patch is done against UUID tree.
> Cc'ed Christoph.
>
Sorry, I messed up on determining the original tree it came from in
linux-next when I looked at the output from get_maintainer.pl
Colin
prev parent reply other threads:[~2017-06-13 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 13:03 Colin King
2017-06-13 14:16 ` Andy Shevchenko
2017-06-13 17:56 ` David Miller
2017-06-13 19:24 ` Andy Shevchenko
2017-06-13 20:40 ` Colin Ian King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b3235bb-5058-82a6-d8be-76d805594cea@canonical.com \
--to=colin.king@canonical.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=huangdaode@hisilicon.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oulijun@huawei.com \
--cc=salil.mehta@huawei.com \
--cc=yankejian@huawei.com \
--cc=yisen.zhuang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®