From: Ray Jui <ray.jui@broadcom.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Wei Yongjun <weiyongjun1@huawei.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH -next] pinctrl: nsp: fix potential NULL dereference in nsp_pinmux_probe()
Date: Wed, 11 Jul 2018 10:18:14 -0700 [thread overview]
Message-ID: <8bbcafd2-db6d-a316-1d15-6af40771d1b6@broadcom.com> (raw)
In-Reply-To: <15d64c26-f2c3-e3bb-2768-e5c9726cde49@arm.com>
On 7/11/2018 10:14 AM, Sudeep Holla wrote:
>
>
> On 11/07/18 18:11, Ray Jui wrote:
>>
>>
>
> [...]
>
>>
>> I meant there's a reason why xxx_resource was not used, which is most
>> likely due to some resource conflict with another driver on NSP.
>>
>
> Ah OK, sorry for the noise then.
>
Not a noise at all. Helpful discussion.
Thanks!
Ray
next prev parent reply other threads:[~2018-07-11 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 12:34 [PATCH -next] pinctrl: nsp: fix potential NULL dereference in nsp_pinmux_probe() Wei Yongjun
2018-07-11 16:48 ` Ray Jui
2018-07-11 16:56 ` Ray Jui
2018-07-11 17:01 ` Sudeep Holla
2018-07-11 17:11 ` Ray Jui
2018-07-11 17:14 ` Sudeep Holla
2018-07-11 17:18 ` Ray Jui [this message]
2018-07-13 7:46 ` Linus Walleij
2018-07-13 16:53 ` Ray Jui
2018-07-14 10:49 ` Linus Walleij
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=8bbcafd2-db6d-a316-1d15-6af40771d1b6@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jonmason@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=sudeep.holla@arm.com \
--cc=weiyongjun1@huawei.com \
/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