From: "Kuppuswamy, Sathyanarayanan" <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] drivers: base: Fix NULL pointer exception in __platform_driver_probe()
Date: Tue, 28 Apr 2020 12:24:05 -0700 [thread overview]
Message-ID: <2c0c2e54-a385-c4ce-da29-0f84454cce55@linux.intel.com> (raw)
In-Reply-To: <20200428190337.GA1719585@kroah.com>
Hi Greg,
On 4/28/20 12:03 PM, Greg KH wrote:
> On Wed, Apr 08, 2020 at 02:40:03PM -0700, sathyanarayanan.kuppuswamy@linux.intel.com wrote:
>> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>>
>> If platform bus driver registration is failed then,
>
> How is your platform driver registration failing? What caused that, is
> it an in-kernel problem with something? How can it be triggered?
In my case I triggered it intentionally. For one of our internal
project we want to strictly control the number of drivers/devices
allowed in kernel. To verify the feasibility of adding above support,
I intentionally failed few bus drivers and checked the behavior. In
one of those tests I hence came across the mentioned issue.
In any case, platform bus driver registration failure is a valid case
right ? Any issue we notice when this happens needs to be handled right?
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2020-04-28 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 21:40 [PATCH v1 1/1] drivers: base: Fix NULL pointer exception in __platform_driver_probe() sathyanarayanan.kuppuswamy
2020-04-28 19:03 ` Greg KH
2020-04-28 19:24 ` Kuppuswamy, Sathyanarayanan [this message]
2020-04-29 7:47 ` Greg KH
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=2c0c2e54-a385-c4ce-da29-0f84454cce55@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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