Re: [greybus-dev] Re: [PATCH linux-next] staging: greybus:using the

[Alex Elder <elder@linaro.org>]

On 8/3/22 1:30 AM, Greg KH wrote:
> On Wed, Aug 03, 2022 at 06:22:58AM +0000, cgel.zte@gmail.com wrote:
>> From: ye xingchen <ye.xingchen@zte.com.cn>
>>
>> Using pm_runtime_resume_and_get() to instade of  pm_runtime_get_sync
>> and pm_runtime_put_noidle.
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by:  <ye.xingchen@zte.com.cn>
>> ---
>>   drivers/greybus/core.c | 3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/greybus/core.c b/drivers/greybus/core.c
>> index e546c6431877..b9063e86534b 100644
>> --- a/drivers/greybus/core.c
>> +++ b/drivers/greybus/core.c
>> @@ -174,9 +174,8 @@ static int greybus_probe(struct device *dev)
>>   	if (!id)
>>   		return -ENODEV;
>>   
>> -	retval = pm_runtime_get_sync(&bundle->intf->dev);
>> +	retval = pm_runtime_resume_and_get(&bundle->intf->dev);
>>   	if (retval < 0) {
>> -		pm_runtime_put_noidle(&bundle->intf->dev);
>>   		return retval;
>>   	}
>>   
>> -- 
>> 2.25.1
> 
> Now this is just being silly.  Consider all future emails also dropped.


No Greg, please don't do this, or please undo this.

This happened because the original poster was not a subscriber to the
greybus-dev mailing list.  Such messages get held until someone (me)
releases them after picking them out from the mostly spam that is
caught and held.  I have been trying to do that daily lately but
it's still not enough to avoid this happening.

You were on the original addressee list.  So you got the message
immediately.  But the mailing list filter held it and sent it
again when I released it yesterday.  This is why you saw it the
second time.

Ye Xingchen had nothing to do with your receiving the message twice.

					-Alex

> greg k-h
> _______________________________________________
> greybus-dev mailing list -- greybus-dev@lists.linaro.org
> To unsubscribe send an email to greybus-dev-leave@lists.linaro.org