From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] dmaengine: xgene-dma: Fix sparse wannings and coccinelle warnings
Date: Mon, 27 Apr 2015 08:43:15 +0530 [thread overview]
Message-ID: <20150427031315.GG2738@intel.com> (raw)
In-Reply-To: <CAFd313y-HfW_us0FVQFEkGAzf-ZCKpRtF6eYweaK0V94MBg4iQ@mail.gmail.com>
On Mon, Apr 20, 2015 at 08:38:18AM +0530, Rameshwar Sahu wrote:
> Hi Vinod,
>> >> @@ -2085,6 +2043,5 @@ module_platform_driver(xgene_dma_driver);
> >>
> >> MODULE_DESCRIPTION("APM X-Gene SoC DMA driver");
> >> MODULE_AUTHOR("Rameshwar Prasad Sahu <rsahu@apm.com>");
> >> -MODULE_AUTHOR("Loc Ho <lho@apm.com>");
> > And why this?
>
> I saw below warning reported by the kbuild robot test
>
> drivers/dma/xgene-dma.c:2088:1: sparse: symbol
> '__UNIQUE_ID_author__COUNTER__' has multiple initializers (originally
> initialized at drivers/dma/xgene-dma.c:2087)
> So, I kept only one author here.
No that is not right, sparse shouldn't have cribbed here.
Fengguang can we get the bot to ignore this please
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Rameshwar Sahu <rsahu@apm.com>, fengguang.wu@intel.com
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jcm@redhat.com,
patches@apm.com
Subject: Re: [PATCH v3] dmaengine: xgene-dma: Fix sparse wannings and coccinelle warnings
Date: Mon, 27 Apr 2015 08:43:15 +0530 [thread overview]
Message-ID: <20150427031315.GG2738@intel.com> (raw)
In-Reply-To: <CAFd313y-HfW_us0FVQFEkGAzf-ZCKpRtF6eYweaK0V94MBg4iQ@mail.gmail.com>
On Mon, Apr 20, 2015 at 08:38:18AM +0530, Rameshwar Sahu wrote:
> Hi Vinod,
>> >> @@ -2085,6 +2043,5 @@ module_platform_driver(xgene_dma_driver);
> >>
> >> MODULE_DESCRIPTION("APM X-Gene SoC DMA driver");
> >> MODULE_AUTHOR("Rameshwar Prasad Sahu <rsahu@apm.com>");
> >> -MODULE_AUTHOR("Loc Ho <lho@apm.com>");
> > And why this?
>
> I saw below warning reported by the kbuild robot test
>
> drivers/dma/xgene-dma.c:2088:1: sparse: symbol
> '__UNIQUE_ID_author__COUNTER__' has multiple initializers (originally
> initialized at drivers/dma/xgene-dma.c:2087)
> So, I kept only one author here.
No that is not right, sparse shouldn't have cribbed here.
Fengguang can we get the bot to ignore this please
--
~Vinod
next prev parent reply other threads:[~2015-04-27 3:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 19:31 [PATCH v3] dmaengine: xgene-dma: Fix sparse wannings and coccinelle warnings Rameshwar Prasad Sahu
2015-04-16 19:31 ` Rameshwar Prasad Sahu
2015-04-16 19:31 ` Rameshwar Prasad Sahu
2015-04-17 8:49 ` Arnd Bergmann
2015-04-17 8:49 ` Arnd Bergmann
2015-04-17 8:49 ` Arnd Bergmann
2015-04-17 9:11 ` Rameshwar Sahu
2015-04-17 9:11 ` Rameshwar Sahu
2015-04-17 9:56 ` Arnd Bergmann
2015-04-17 9:56 ` Arnd Bergmann
2015-04-17 18:29 ` Vinod Koul
2015-04-17 18:29 ` Vinod Koul
2015-04-20 3:08 ` Rameshwar Sahu
2015-04-20 3:08 ` Rameshwar Sahu
2015-04-27 3:13 ` Vinod Koul [this message]
2015-04-27 3:13 ` Vinod Koul
2015-04-27 5:20 ` Fengguang Wu
2015-04-27 5:20 ` Fengguang Wu
2015-06-12 0:36 ` Christopher Li
2015-06-12 0:36 ` Christopher Li
2015-06-12 1:00 ` Fengguang Wu
2015-06-12 1:00 ` Fengguang Wu
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=20150427031315.GG2738@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.