[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5886f4ff-d6be-4804-8c76-c431946128a5@stanley.mountain>
Date: Thu, 20 Feb 2025 08:50:07 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: "Karan Tilak Kumar (kartilak)" <kartilak@...co.com>
Cc: "oe-kbuild@...ts.linux.dev" <oe-kbuild@...ts.linux.dev>,
"lkp@...el.com" <lkp@...el.com>,
"oe-kbuild-all@...ts.linux.dev" <oe-kbuild-all@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"Sesidhar Baddela (sebaddel)" <sebaddel@...co.com>,
"Gian Carlo Boffa (gcboffa)" <gcboffa@...co.com>,
"Arulprabhu Ponnusamy (arulponn)" <arulponn@...co.com>,
"Arun Easi (aeasi)" <aeasi@...co.com>
Subject: Re: drivers/scsi/fnic/fdls_disc.c:263
fdls_schedule_oxid_free_retry_work() warn: inconsistent indenting
On Thu, Feb 20, 2025 at 03:10:26AM +0000, Karan Tilak Kumar (kartilak) wrote:
> On Saturday, February 15, 2025 1:03 PM, Karan Tilak Kumar (kartilak) wrote:
> >
> > On Friday, February 14, 2025 7:03 AM, Dan Carpenter <dan.carpenter@...aro.org> wrote:
> > >
> > > On Fri, Feb 14, 2025 at 05:42:25PM +0300, Dan Carpenter wrote:
> > > >
> > > > I guess we can't call schedule_delayed_work() without holding the
> > > > spin_lock? It's a strange thing.
> > >
> > > Actually, I see now that we're just dropping the lock to avoid a sleeping
> > > in atomic warning with the GFP_ATOMIC allocation... I bet you could make
> > > the code under the lock much smaller. Just the test_and_clear_bit() stuff
> > > basically.
> > >
> > > regards,
> > > dan carpenter
>
> The window can be further reduced by adding the lock/unlock around the list_add_tail. But this looks good too.
>
Could you send the patch for this. I don't know the code that well and
can't test it.
regards,
dan carpenter
Powered by blists - more mailing lists