| commit | 9406e0d97ec1923b261b40f11667145fb29e89de | |
| author | Philippe Mathieu-Daudé <philmd@redhat.com> | |
| Tue, 22 Sep 2020 08:38:19 +0000 (22 10:38 +0200) | ||
| committer | Stefan Hajnoczi <stefanha@redhat.com> | |
| Mon, 5 Oct 2020 08:35:52 +0000 (5 09:35 +0100) | ||
| tree | 874c28151bc897aa9e0599f585b84ae71be8df3a | treesnapshot (tar.gz zip) |
| parent | 37d7a45abdfa7376ba04dc68ccc331a5b406d672 | commitdiff |
block/nvme: Drop NVMeRegs structure, directly use NvmeBar
NVMeRegs only contains NvmeBar. Simplify the code by using NvmeBar
directly.
This triggers a checkpatch.pl error:
ERROR: Use of volatile is usually wrong, please add a comment
#30: FILE: block/nvme.c:691:
+ volatile NvmeBar *regs;
This is a false positive as in our case we are using I/O registers,
so the 'volatile' use is justified.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20200922083821.578519-5-philmd@redhat.com>
NVMeRegs only contains NvmeBar. Simplify the code by using NvmeBar
directly.
This triggers a checkpatch.pl error:
ERROR: Use of volatile is usually wrong, please add a comment
#30: FILE: block/nvme.c:691:
+ volatile NvmeBar *regs;
This is a false positive as in our case we are using I/O registers,
so the 'volatile' use is justified.
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20200922083821.578519-5-philmd@redhat.com>
| block/nvme.c | diffblobblamehistory |