similar to: [PATCH] virtio-mmio: Cocci spatch "ptr_ret.spatch"

Used PTR_RET function instead of IS_ERR and PTR_ERR. Patch found using coccinelle. Signed-off-by: Alexandru Gheorghiu <gheorghiuandru at gmail.com> --- drivers/virtio/virtio_mmio.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c index 1ba0d68..d1e664f 100644 --- a/drivers/virtio/virtio_mmio.c +++

Used PTR_RET function instead of IS_ERR and PTR_ERR. Patch found using coccinelle. Signed-off-by: Alexandru Gheorghiu <gheorghiuandru at gmail.com> --- drivers/virtio/virtio_mmio.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c index 1ba0d68..d1e664f 100644 --- a/drivers/virtio/virtio_mmio.c +++

Fix ptr_ret.cocci warnings: drivers/virtio/virtio_mmio.c:653:1-3: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Signed-off-by: Vasyl Gomonovych <gomonovych at gmail.com> --- drivers/virtio/virtio_mmio.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

Fix ptr_ret.cocci warnings: drivers/virtio/virtio_mmio.c:653:1-3: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Signed-off-by: Vasyl Gomonovych <gomonovych at gmail.com> --- drivers/virtio/virtio_mmio.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- Hi Rusty, As the param changes are in now, could you queue this long-time-forgotten patch for 3.5? Cheers! Pawel PS. Congratulations once again and see

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- Hi Rusty, As the param changes are in now, could you queue this long-time-forgotten patch for 3.5? Cheers! Pawel PS. Congratulations once again and see

This uses PTR_RET instead of IS_ERR and PTR_ERR in order to increase readability. Signed-off-by: Silviu-Mihai Popescu <silviupopescu1990 at gmail.com> --- net/bridge/netfilter/ebtable_broute.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/net/bridge/netfilter/ebtable_broute.c b/net/bridge/netfilter/ebtable_broute.c index 40d8258..70f656c 100644 ---

drivers/virtio/virtio_mmio.c: In function ?vm_cmdline_set?: drivers/virtio/virtio_mmio.c:535:4: warning: format ?%u? expects argument of type ?unsigned int *?, but argument 4 has type ?resource_size_t *? [-Wformat] Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: virtualization at lists.linux-foundation.org Signed-off-by: Lee Jones <lee.jones at linaro.org> ---

drivers/virtio/virtio_mmio.c: In function ?vm_cmdline_set?: drivers/virtio/virtio_mmio.c:535:4: warning: format ?%u? expects argument of type ?unsigned int *?, but argument 4 has type ?resource_size_t *? [-Wformat] Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: virtualization at lists.linux-foundation.org Signed-off-by: Lee Jones <lee.jones at linaro.org> ---

From: Bjorn Helgaas <bhelgaas at google.com> The "virtio_mmio.device=" command line argument allows a user to specify the size, address, and IRQ of a virtio device. Previously the only requirement for the IRQ was that it be an unsigned integer. Zero is an unsigned integer but an invalid IRQ number, and after a85a6c86c25be ("driver core: platform: Clarify that IRQ 0 is

From: Bjorn Helgaas <bhelgaas at google.com> The "virtio_mmio.device=" command line argument allows a user to specify the size, address, and IRQ of a virtio device. Previously the only requirement for the IRQ was that it be an unsigned integer. Zero is an unsigned integer but an invalid IRQ number, and after a85a6c86c25be ("driver core: platform: Clarify that IRQ 0 is

On 2020/7/2 ??6:10, Bjorn Helgaas wrote: > From: Bjorn Helgaas <bhelgaas at google.com> > > The "virtio_mmio.device=" command line argument allows a user to specify > the size, address, and IRQ of a virtio device. Previously the only > requirement for the IRQ was that it be an unsigned integer. > > Zero is an unsigned integer but an invalid IRQ number, and

Use ARRAY_SIZE macro, rather than explicitly coding some variant of it yourself. Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\) /ARRAY_SIZE(\1)/g' and manual check/verification. Signed-off-by: Thomas Meyer <thomas at m3y3r.de> --- diff --git

Commit-ID: 2931607d8156b4a725d485d2d0bb0cc5aa90e556 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=2931607d8156b4a725d485d2d0bb0cc5aa90e556 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Jan 2019 04:13:18 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] Kbuild.install: Copy UAPI

In fixing how we deal with bad inodes, we had a regression in the orphan cleanup code, since it expects to get a bad inode back. So fix it to deal with getting -ESTALE back by deleting the orphan item manually and moving on. Thanks, Reported-by: Simon Kirby <sim@hostway.ca> Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/inode.c | 36

Hi, thank you, Andrea, for the forward. On 07/13/17 10:19, Andrea Bolognani wrote: > -------- Forwarded Message -------- > From: Thomas Meyer <thomas@m3y3r.de> > To: libvirt-users@redhat.com > Subject: [libvirt-users] UEFI NVRAM variables > Date: Wed, 12 Jul 2017 07:49:43 +0200 > >> Hi, >> >> how do I set the BootOrder variable in an NVRAM file for UEFI

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48,1K at 0x1001e000:74 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- drivers/virtio/Kconfig | 25 ++++++ drivers/virtio/virtio_mmio.c | 170 +++++++++++++++++++++++++++++++++++++++++- 2 files

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48,1K at 0x1001e000:74 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- drivers/virtio/Kconfig | 25 ++++++ drivers/virtio/virtio_mmio.c | 170 +++++++++++++++++++++++++++++++++++++++++- 2 files

The kbuild test bot complained about a new coccinelle warning nearby, which sparked a discussion about the assignment to 'memory' inside of the conditional expression. See Link below for the original post. Fix the assignment to silence the coccinelle warning and also make the code look a little nicer. Link: https://lists.freedesktop.org/archives/nouveau/2017-November/029242.html

On Mon, Jan 15, 2018 at 01:47:07PM +0100, Julia Lawall wrote: > From: Fengguang Wu <fengguang.wu at intel.com> > > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and > drm_*_unreference() helpers. > > Generated by: scripts/coccinelle/api/drm-get-put.cocci > > Signed-off-by: Fengguang Wu <fengguang.wu at intel.com> > Signed-off-by: