From: Don Zickus <dzickus@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] staging: unisys: remove some dead code
Date: Thu, 07 Jan 2016 15:47:47 +0000 [thread overview]
Message-ID: <20160107154747.GG152924@redhat.com> (raw)
In-Reply-To: <20160107093413.GA27186@mwanda>
On Thu, Jan 07, 2016 at 12:34:13PM +0300, Dan Carpenter wrote:
> queue_delayed_work() returns bool, not negative error codes. It returns
> false if the work has already been queued or true otherwise. Since
> we don't care about that, we can just remove the test.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Don Zickus <dzickus@redhat.com>
>
> diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c
> index 07594f4..ff2bd077 100644
> --- a/drivers/staging/unisys/visorbus/visorchipset.c
> +++ b/drivers/staging/unisys/visorbus/visorchipset.c
> @@ -2310,13 +2310,8 @@ visorchipset_init(struct acpi_device *acpi_device)
> }
> most_recent_message_jiffies = jiffies;
> poll_jiffies = POLLJIFFIES_CONTROLVMCHANNEL_FAST;
> - rc = queue_delayed_work(periodic_controlvm_workqueue,
> - &periodic_controlvm_work, poll_jiffies);
> - if (rc < 0) {
> - POSTCODE_LINUX_2(QUEUE_DELAYED_WORK_PC,
> - DIAG_SEVERITY_ERR);
> - goto cleanup;
> - }
> + queue_delayed_work(periodic_controlvm_workqueue,
> + &periodic_controlvm_work, poll_jiffies);
>
> visorchipset_platform_device.dev.devt = major_dev;
> if (platform_device_register(&visorchipset_platform_device) < 0) {
next prev parent reply other threads:[~2016-01-07 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:34 [patch] staging: unisys: remove some dead code Dan Carpenter
2016-01-07 15:47 ` Don Zickus [this message]
2016-01-12 16:26 ` Ben Romer
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=20160107154747.GG152924@redhat.com \
--to=dzickus@redhat.com \
--cc=kernel-janitors@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).