[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM6PR04MB65756F8A881F88DBEDAB5F40FCF99@DM6PR04MB6575.namprd04.prod.outlook.com>
Date: Sun, 24 Apr 2022 11:52:52 +0000
From: Avri Altman <Avri.Altman@....com>
To: Bean Huo <huobean@...il.com>,
"ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"adrian.hunter@...el.com" <adrian.hunter@...el.com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "beanhuo@...ron.com" <beanhuo@...ron.com>,
stable <stable@...r.kernel.org>
Subject: RE: [PATCH v1 2/2] mmc: core: Allows to override the timeout value
for ioctl() path
>
> From: Bean Huo <beanhuo@...ron.com>
>
> Occasionally, user-land applications initiate longer timeout values for certain
> commands through ioctl() system call. But so far we are still using a fixed
> timeout of 10 seconds in mmc_poll_for_busy() on the ioctl() path, even if a
> custom timeout is specified in the userspace application. This patch allows
> custom timeout values to override this default timeout values on the ioctl
> path.
>
> Cc: stable <stable@...r.kernel.org>
> Signed-off-by: Bean Huo <beanhuo@...ron.com>
Acked-by: Avri Altman <avri.altman@....com>
Powered by blists - more mailing lists