[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SJ0PR21MB13245A39F619F5C67A1D7BDEBFB42@SJ0PR21MB1324.namprd21.prod.outlook.com>
Date: Fri, 26 Jul 2024 06:02:10 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
CC: Nuno Das Neves <nunodasneves@...ux.microsoft.com>, KY Srinivasan
<kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>, "linux-hyperv@...r.kernel.org"
<linux-hyperv@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, Saurabh Singh Sengar <ssengar@...rosoft.com>,
"srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>
Subject: RE: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks
> From: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
> Sent: Thursday, July 25, 2024 10:27 PM
> [...]
> > > + ret = __cpuhp_setup_state_cpuslocked(CPUHP_AP_ONLINE_DYN,
> > > "hyperv/vmbus:online", false,
> > > + hv_synic_init, hv_synic_cleanup,
> > > false);
> > > + cpus_read_unlock();
> >
> > Add an empty line here to make it slightly more readable? :-)
>
> My personal preference was to have empty line as well here, but then I
> looked the
> other places in this file where we used cpus_read_unlock, hence I
> maintained that style consistent.
>
> Please let me know if you have strong opinion about this empty line, I can
> add in V2.
>
> - Saurabh
I have no strong opinion here :-)
Powered by blists - more mailing lists