mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	"s.shtylyov@omp.ru" <s.shtylyov@omp.ru>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH net-next v3 5/6] net: ravb: Do not apply features to hardware if the interface is down
Date: Tue, 13 Feb 2024 20:55:24 +0200	[thread overview]
Message-ID: <81ca7397-3f00-431d-aea4-c30c363a90e6@tuxon.dev> (raw)
In-Reply-To: <368ca0a8-a005-4371-a959-297fd4f58cb1@tuxon.dev>



On 13.02.2024 13:07, claudiu beznea wrote:
>>> @@ -2566,15 +2566,23 @@ static int ravb_set_features(struct net_device
>>> *ndev,  {
>>>  	struct ravb_private *priv = netdev_priv(ndev);
>>>  	const struct ravb_hw_info *info = priv->info;
>>> -	int ret;
>>> +	struct device *dev = &priv->pdev->dev;
>>> +	int ret = 0;
>>> +
>>> +	pm_runtime_get_noresume(dev);
>>> +
>>> +	if (!pm_runtime_active(dev))
>>> +		goto out_set_features;
>> This can be simplified, which avoids 1 goto statement and
>> Unnecessary ret initialization. I am leaving to you and Sergey.
>>
>> 	if (!pm_runtime_active(dev))
>> 		ret = 0;
>> 	else
>> 		ret = info->set_feature(ndev, features);
>>
>> 	pm_runtime_put_noidle(dev);
>> 	if (ret)
>> 		goto err;
>>
>> 	ndev->features = features;
>>
>> err:
>> 	return ret;
>>
> I find it a bit difficult to follow this way.

Looking again at it, your version seems better.

  parent reply	other threads:[~2024-02-13 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  9:41 [PATCH net-next v3 0/6] net: ravb: Add runtime PM support (part 2) Claudiu
2024-02-13  9:41 ` [PATCH net-next v3 1/6] net: ravb: Get rid of the temporary variable irq Claudiu
2024-02-13  9:41 ` [PATCH net-next v3 2/6] net: ravb: Keep the reverse order of operations in ravb_close() Claudiu
2024-02-13  9:41 ` [PATCH net-next v3 3/6] net: ravb: Return cached statistics if the interface is down Claudiu
2024-02-13  9:41 ` [PATCH net-next v3 4/6] net: ravb: Move the update of ndev->features to ravb_set_features() Claudiu
2024-02-13 19:36   ` Sergey Shtylyov
2024-02-13 19:58     ` Sergey Shtylyov
2024-02-13 19:52   ` Sergey Shtylyov
2024-02-14  5:45     ` claudiu beznea
2024-02-13  9:41 ` [PATCH net-next v3 5/6] net: ravb: Do not apply features to hardware if the interface is down Claudiu
2024-02-13 10:13   ` Biju Das
2024-02-13 11:07     ` claudiu beznea
2024-02-13 11:39       ` Biju Das
2024-02-13 18:55       ` claudiu beznea [this message]
2024-02-13 19:48   ` Sergey Shtylyov
2024-02-13  9:41 ` [PATCH net-next v3 6/6] net: ravb: Add runtime PM support Claudiu

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=81ca7397-3f00-431d-aea4-c30c363a90e6@tuxon.dev \
    --to=claudiu.beznea@tuxon.dev \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=s.shtylyov@omp.ru \
    /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®