From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Navid Emamdoost <navid.emamdoost@gmail.com>
Cc: emamd001@umn.edu, smccaman@umn.edu, kjlu@umn.edu,
Benson Leung <bleung@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: null check create_singlethread_workqueue
Date: Thu, 19 Sep 2019 15:06:40 +0200 [thread overview]
Message-ID: <c2c9c9a0-98f0-2d1b-ecc7-7c4d03a141d7@collabora.com> (raw)
In-Reply-To: <20190911201100.11483-1-navid.emamdoost@gmail.com>
Hi,
On 11/9/19 22:10, Navid Emamdoost wrote:
> In cros_usbpd_logger_probe the return value of
> create_singlethread_workqueue may be null, it should be checked.
>
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> ---
Applied for 5.4, the patch went to linux-next some time ago, so sorry for late
notice.
Thanks,
Enric
> drivers/platform/chrome/cros_usbpd_logger.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/platform/chrome/cros_usbpd_logger.c b/drivers/platform/chrome/cros_usbpd_logger.c
> index 7c7b267626a0..c83397955cc3 100644
> --- a/drivers/platform/chrome/cros_usbpd_logger.c
> +++ b/drivers/platform/chrome/cros_usbpd_logger.c
> @@ -209,6 +209,9 @@ static int cros_usbpd_logger_probe(struct platform_device *pd)
> /* Retrieve PD event logs periodically */
> INIT_DELAYED_WORK(&logger->log_work, cros_usbpd_log_check);
> logger->log_workqueue = create_singlethread_workqueue("cros_usbpd_log");
> + if (!logger->log_workqueue)
> + return -ENOMEM;
> +
> queue_delayed_work(logger->log_workqueue, &logger->log_work,
> CROS_USBPD_LOG_UPDATE_DELAY);
>
>
prev parent reply other threads:[~2019-09-19 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 20:10 Navid Emamdoost
2019-09-19 13:06 ` Enric Balletbo i Serra [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=c2c9c9a0-98f0-2d1b-ecc7-7c4d03a141d7@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=emamd001@umn.edu \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=navid.emamdoost@gmail.com \
--cc=smccaman@umn.edu \
/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®