From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: David Miller <davem@davemloft.net>, fengguang.wu@intel.com
Cc: kbuild-all@01.org, ajaykumar.hotchandani@oracle.com,
ssantosh@kernel.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 1267/1290] net/rds/ib_recv.c:382:28: sparse: incorrect type in initializer (different base types)
Date: Tue, 25 Aug 2015 16:03:57 -0700 [thread overview]
Message-ID: <55DCF45D.6080501@oracle.com> (raw)
In-Reply-To: <20150825.155500.290194488854444995.davem@davemloft.net>
On 8/25/15 3:55 PM, David Miller wrote:
> From: kbuild test robot <fengguang.wu@intel.com>
> Date: Wed, 26 Aug 2015 06:42:39 +0800
>
>> sparse warnings: (new ones prefixed by >>)
>>
>>>> net/rds/ib_recv.c:382:28: sparse: incorrect type in initializer (different base types)
>> net/rds/ib_recv.c:382:28: expected int [signed] can_wait
>> net/rds/ib_recv.c:382:28: got restricted gfp_t
>> net/rds/ib_recv.c:828:23: sparse: cast to restricted __le64
>
> Fixed by:
>
> ====================
> [PATCH] rds: Fix improper gfp_t usage.
>
>>> net/rds/ib_recv.c:382:28: sparse: incorrect type in initializer (different base types)
> net/rds/ib_recv.c:382:28: expected int [signed] can_wait
> net/rds/ib_recv.c:382:28: got restricted gfp_t
> net/rds/ib_recv.c:828:23: sparse: cast to restricted __le64
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
Thanks Dave. I was just creating the patch after noticing
the error from kbuild on my tree.
Regards,
Santosh
prev parent reply other threads:[~2015-08-25 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 22:42 [net-next:master 1267/1290] net/rds/ib_recv.c:382:28: sparse: incorrect type in initializer (different base types) kbuild test robot
2015-08-25 22:55 ` David Miller
2015-08-25 23:03 ` santosh.shilimkar [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=55DCF45D.6080501@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=ssantosh@kernel.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.