From: Christopher Li <sparse@chrisli.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Vinod Koul <vinod.koul@intel.com>, Rameshwar Sahu <rsahu@apm.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
jcm@redhat.com, patches@apm.com,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v3] dmaengine: xgene-dma: Fix sparse wannings and coccinelle warnings
Date: Thu, 11 Jun 2015 17:36:00 -0700 [thread overview]
Message-ID: <CANeU7Q=0VT5EOjKXEFJ4WgKQGcZhufEgksLoN4PDLEbc+q0pgQ@mail.gmail.com> (raw)
In-Reply-To: <20150427052045.GA5199@wfg-t540p.sh.intel.com>
On Sun, Apr 26, 2015 at 10:20 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> >
>> > 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
Sorry for the late reply.
That looks like the __COUNTER__ macro feature. It has been implemented in
sparse git tree already.
Chris
next prev parent reply other threads:[~2015-06-12 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1429212673-22254-1-git-send-email-rsahu@apm.com>
[not found] ` <20150417182937.GN30624@intel.com>
[not found] ` <CAFd313y-HfW_us0FVQFEkGAzf-ZCKpRtF6eYweaK0V94MBg4iQ@mail.gmail.com>
[not found] ` <20150427031315.GG2738@intel.com>
2015-04-27 5:20 ` [PATCH v3] dmaengine: xgene-dma: Fix sparse wannings and coccinelle warnings Fengguang Wu
2015-06-12 0:36 ` Christopher Li [this message]
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='CANeU7Q=0VT5EOjKXEFJ4WgKQGcZhufEgksLoN4PDLEbc+q0pgQ@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=patches@apm.com \
--cc=rsahu@apm.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).