From: Yunsheng Lin <linyunsheng@huawei.com>
To: "Eugenio Pérez" <eperezma@redhat.com>,
mst@redhat.com, linux-kernel@vger.kernel.org
Cc: Matthew Wilcox <willy@infradead.org>,
Jason Wang <jasowang@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH 0/2] tools/virtio: fix compilation
Date: Wed, 7 Jul 2021 11:18:56 +0800 [thread overview]
Message-ID: <38e101ff-c4aa-2a53-436e-f9710e575de1@huawei.com> (raw)
In-Reply-To: <20210706142632.670483-1-eperezma@redhat.com>
On 2021/7/6 22:26, Eugenio Pérez wrote:
> Virtio testing tools cannot build. Fixing.
>
>
>
> Comments are welcome, specially in case I missed use of stub lockdep.h.
>
>
>
> I couldn't try some of the tools, that already did not compile on 5.13:
>
> gpio, liblockdep, selftests, bpf, tracing.
This patchset fixes the compilation error explicitly.
My previous refactor patchset seems to fixes the compilation error
accidentally too.
Anyway it seems better to fix the compilation error explicitly.
>
>
>
> Eugenio Pérez (2):
>
> tools: Remove lockdep.h and its include from spinlock.h
>
> vringh: Include spinlock.h
>
>
>
> include/linux/vringh.h | 1 +
>
> tools/include/linux/spinlock.h | 2 --
>
> tools/testing/radix-tree/linux/lockdep.h | 11 -----------
>
> 3 files changed, 1 insertion(+), 13 deletions(-)
>
> delete mode 100644 tools/testing/radix-tree/linux/lockdep.h
>
>
>
prev parent reply other threads:[~2021-07-07 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 14:26 Eugenio Pérez
2021-07-06 14:26 ` [PATCH 1/2] tools: Remove lockdep.h and its include from spinlock.h Eugenio Pérez
2021-07-06 14:32 ` Matthew Wilcox
2021-07-06 14:26 ` [PATCH 2/2] vringh: Include spinlock.h Eugenio Pérez
2021-07-06 14:44 ` Stefano Garzarella
2021-07-07 3:18 ` Yunsheng Lin [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=38e101ff-c4aa-2a53-436e-f9710e575de1@huawei.com \
--to=linyunsheng@huawei.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®