On Wed, Apr 27, 2022 at 4:46 PM Piyush Malgujar <pmalgujar@xxxxxxxxxxx> wrote: > > Using irqsave/irqrestore locking variants to avoid any deadlock. > I see you'll be resending this anyway so would you mind providing an example of a deadlock that is possible with no-irqsave variants? Thanks. Bart > Signed-off-by: Piyush Malgujar <pmalgujar@xxxxxxxxxxx> > ---
Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- From: Bartosz Golaszewski <brgl@xxxxxxxx>
- Date: Mon, 2 May 2022 13:18:49 +0200
- In-reply-to: <20220427144620.9105-2-pmalgujar@marvell.com>
- References: <20220427144620.9105-1-pmalgujar@marvell.com> <20220427144620.9105-2-pmalgujar@marvell.com>
- Follow-Ups:
- Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- From: Piyush Malgujar
- Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- References:
- [PATCH 0/5] gpio: thunderx: Marvell GPIO changes.
- From: Piyush Malgujar
- [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- From: Piyush Malgujar
- [PATCH 0/5] gpio: thunderx: Marvell GPIO changes.
- Prev by Date: [PATCH v2] gpio: xilinx: add missing blank line after declarations
- Next by Date: Re: [PATCH] gpio: drop the SOC_VF610 dependency for GPIO_VF610
- Previous by thread: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- Next by thread: Re: [PATCH 1/5] gpio: thunderx: avoid potential deadlock
- Index(es):
 |