linux-kernel - Re: [PATCH] rpmsg: rename virtqueue_add_buf_gfp to virtqueue_add

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK=WgbY2Kw0G7OkkN6f7=rExFpBzHVy_7r1xCrHe02nSuOUC3Q@mail.gmail.com>
Date:	Tue, 13 Dec 2011 09:20:57 +0200
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	Axel Lin <axel.lin@...il.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org,
	Rusty Russell <rusty@...tcorp.com.au>,
	linux-next@...r.kernel.org
Subject: Re: [PATCH] rpmsg: rename virtqueue_add_buf_gfp to virtqueue_add_buf

On Tue, Dec 13, 2011 at 9:14 AM, Axel Lin <axel.lin@...il.com> wrote:
> Since commit 7bb7aef2 "virtio: rename virtqueue_add_buf_gfp to virtqueue_add_buf",
> virtqueue_add_buf_gfp is renamed to virtqueue_add_buf now.
>
> This patch fixes below build error:
>  CC [M]  drivers/rpmsg/virtio_rpmsg_bus.o
> drivers/rpmsg/virtio_rpmsg_bus.c: In function 'rpmsg_send_offchannel_raw':
> drivers/rpmsg/virtio_rpmsg_bus.c:723: error: implicit declaration of function 'virtqueue_add_buf_gfp'
> make[2]: *** [drivers/rpmsg/virtio_rpmsg_bus.o] Error 1
> make[1]: *** [drivers/rpmsg] Error 2
> make: *** [drivers] Error 2
>
> Signed-off-by: Axel Lin <axel.lin@...il.com>
> ---
> I got the build error on linux-next 20111212.
> So this patch is against linux-next.

Thanks a lot for the heads up, Axel !

Stephen, can you please carry this patch in linux-next ?

Thanks!
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/