From: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Matan Barak <matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: linux-next: Tree for Mar 23 (infiniband: mlx5)
Date: Wed, 23 Mar 2016 10:26:35 -0700 [thread overview]
Message-ID: <56F2D1CB.8080600@infradead.org> (raw)
In-Reply-To: <20160323132208.54ba0c1a-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On 03/22/16 19:22, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.7 related material to your linux-next included
> trees until after v4.6-rc1 is released.
>
> Changes since 20160322:
>
on i386 or x86_64:
../drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_add':
../drivers/infiniband/hw/mlx5/main.c:2358:31: error: 'mlx5_ib_get_vf_config' undeclared (first use in this function)
dev->ib_dev.get_vf_config = mlx5_ib_get_vf_config;
^
../drivers/infiniband/hw/mlx5/main.c:2358:31: note: each undeclared identifier is reported only once for each function it appears in
../drivers/infiniband/hw/mlx5/main.c:2359:35: error: 'mlx5_ib_set_vf_link_state' undeclared (first use in this function)
dev->ib_dev.set_vf_link_state = mlx5_ib_set_vf_link_state;
^
../drivers/infiniband/hw/mlx5/main.c:2360:30: error: 'mlx5_ib_get_vf_stats' undeclared (first use in this function)
dev->ib_dev.get_vf_stats = mlx5_ib_get_vf_stats;
^
../drivers/infiniband/hw/mlx5/main.c:2361:30: error: 'mlx5_ib_set_vf_guid' undeclared (first use in this function)
dev->ib_dev.set_vf_guid = mlx5_ib_set_vf_guid;
^
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Matan Barak <matanb@mellanox.com>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: linux-next: Tree for Mar 23 (infiniband: mlx5)
Date: Wed, 23 Mar 2016 10:26:35 -0700 [thread overview]
Message-ID: <56F2D1CB.8080600@infradead.org> (raw)
In-Reply-To: <20160323132208.54ba0c1a@canb.auug.org.au>
On 03/22/16 19:22, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v4.7 related material to your linux-next included
> trees until after v4.6-rc1 is released.
>
> Changes since 20160322:
>
on i386 or x86_64:
../drivers/infiniband/hw/mlx5/main.c: In function 'mlx5_ib_add':
../drivers/infiniband/hw/mlx5/main.c:2358:31: error: 'mlx5_ib_get_vf_config' undeclared (first use in this function)
dev->ib_dev.get_vf_config = mlx5_ib_get_vf_config;
^
../drivers/infiniband/hw/mlx5/main.c:2358:31: note: each undeclared identifier is reported only once for each function it appears in
../drivers/infiniband/hw/mlx5/main.c:2359:35: error: 'mlx5_ib_set_vf_link_state' undeclared (first use in this function)
dev->ib_dev.set_vf_link_state = mlx5_ib_set_vf_link_state;
^
../drivers/infiniband/hw/mlx5/main.c:2360:30: error: 'mlx5_ib_get_vf_stats' undeclared (first use in this function)
dev->ib_dev.get_vf_stats = mlx5_ib_get_vf_stats;
^
../drivers/infiniband/hw/mlx5/main.c:2361:30: error: 'mlx5_ib_set_vf_guid' undeclared (first use in this function)
dev->ib_dev.set_vf_guid = mlx5_ib_set_vf_guid;
^
--
~Randy
next prev parent reply other threads:[~2016-03-23 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 2:22 linux-next: Tree for Mar 23 Stephen Rothwell
[not found] ` <20160323132208.54ba0c1a-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2016-03-23 17:26 ` Randy Dunlap [this message]
2016-03-23 17:26 ` linux-next: Tree for Mar 23 (infiniband: mlx5) Randy Dunlap
2016-03-23 18:13 ` Leon Romanovsky
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=56F2D1CB.8080600@infradead.org \
--to=rdunlap-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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.