netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: drt <drt@linux.vnet.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Lijun Pan <ljp@linux.ibm.com>,
	netdev@vger.kernel.org, sukadev@linux.ibm.com, drt@linux.ibm.com
Subject: Re: [PATCH net-next] ibmvnic: merge do_change_param_reset into do_reset
Date: Wed, 04 Nov 2020 13:56:09 -0800	[thread overview]
Message-ID: <63365b7e683e2c3b1b8e41c51668b401@linux.vnet.ibm.com> (raw)
In-Reply-To: <20201103150915.4411306e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On 2020-11-03 15:09, Jakub Kicinski wrote:
> On Sat, 31 Oct 2020 04:46:45 -0500 Lijun Pan wrote:
>> Commit b27507bb59ed ("net/ibmvnic: unlock rtnl_lock in reset so
>> linkwatch_event can run") introduced do_change_param_reset function to
>> solve the rtnl lock issue. Majority of the code in 
>> do_change_param_reset
>> duplicates do_reset. Also, we can handle the rtnl lock issue in 
>> do_reset
>> itself. Hence merge do_change_param_reset back into do_reset to clean 
>> up
>> the code.
>> 
>> Fixes: b27507bb59ed ("net/ibmvnic: unlock rtnl_lock in reset so 
>> linkwatch_event can run")
>> Signed-off-by: Lijun Pan <ljp@linux.ibm.com>
> 
> Applied, thanks!

Hi Jakub,

Thank you for applying this patch so promptly. However, I would like to 
ask that this patch be withdrawn.

1. It needs more time in testing.
2. There are a number of bug fix patches being tested. This patch would 
require rework of those patches.
3. As the lead maintainer for ibmvnic, I failed to communicate this to 
Lijun. I will do better going forward.

Please revert this commit. We will resubmit this patch later.

I sincerely apologize for any trouble this may have caused.

Regards,
Dany

  reply	other threads:[~2020-11-04 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31  9:46 [PATCH net-next] ibmvnic: merge do_change_param_reset into do_reset Lijun Pan
2020-11-03 23:09 ` Jakub Kicinski
2020-11-04 21:56   ` drt [this message]
2020-11-04 22:14     ` Jakub Kicinski
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15  8:30 Lijun Pan
2020-12-16 21:26 ` Jakub Kicinski
2021-01-06 21:35 Lijun Pan
2021-01-09 20:40 ` patchwork-bot+netdevbpf

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=63365b7e683e2c3b1b8e41c51668b401@linux.vnet.ibm.com \
    --to=drt@linux.vnet.ibm.com \
    --cc=drt@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=ljp@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).