From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 011.lax.mailroute.net (011.lax.mailroute.net [199.89.1.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 818F0374E5A; Fri, 10 Jul 2026 13:40:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=199.89.1.14 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783690852; cv=none; b=RKDghwdkqkve4LyoUNY7pTLC7OB3Bn48WwXPlXxDnPEdruN5Ym6uY4rLAaldX0a5BA+pwmX+nRCS/dpIDvbq8IL1ii85PjXrNS2Xa9Si9T3OCdV3FL3rDKHOtsWIckgXAEhSj5KozNwhh+QyN25oSFz0r25EFKZ+H6KObADsKkU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783690852; c=relaxed/simple; bh=ANhHVphqp97jTNeKfP4QFxWLoHszJCOkWdXOHXSFUSM=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=DSIHIU9TGjqHFCnwlbC4ospd//nXO0cCwasP5lMQ/wZG59zEUMr/+9zX0R7PrrtwRrO2aPiELgDSiMGSI1wl5vLP8Ax7WI0uEYyWg27IR4Ik5Js/8bN+Bgxxk5Dvd49ZSo8RfA1xIVpCXnb79ZN+eaMA7pLUjNETkd7tZdIKk6s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org; spf=pass smtp.mailfrom=acm.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b=Dci6QSne; arc=none smtp.client-ip=199.89.1.14 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=acm.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=acm.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=acm.org header.i=@acm.org header.b="Dci6QSne" Received: from localhost (localhost [127.0.0.1]) by 011.lax.mailroute.net (Postfix) with ESMTP id 4gxXz03VTqz1XM2FS; Fri, 10 Jul 2026 13:40:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:content-language:references:subject:subject :user-agent:mime-version:date:date:message-id:received:received; s=mr01; t=1783690839; x=1786282840; bh=ANhHVphqp97jTNeKfP4QFxWL oHszJCOkWdXOHXSFUSM=; b=Dci6QSne847wokYf2isHg1NheXKYYVC7b4U9Uh+P r5Kj7bAMeHLK8SiafycqFC9selkSN2uHbKsmYmvuhK3b7yhL5JR5luRdPuvBqEMW WfdORovLt7eobhcxx+Yb/z1S6k1aK9nlcDBIpVqIDTh4SWXvnUKCGERvULMdA8J+ FL9xUFONAkCS2AiUiOA4tMIFJoST7dgBhzLWpdI3BaDTRCumn7ZdsZW8PFJfAHE1 iD4Z+uVkF954iIV/iRhhWj5BSKS0BFThxOW56B2tluSGPvYDlsurmFMRlxer8pGn JuBdlAtEfRsHvR9dCK4Uj+rhqwWnJMMZ3d1rcb4aFCHG8g== X-Virus-Scanned: by MailRoute Received: from 011.lax.mailroute.net ([127.0.0.1]) by localhost (011.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id 9JDeUorXncFP; Fri, 10 Jul 2026 13:40:39 +0000 (UTC) Received: from [192.168.50.14] (c-73-231-117-72.hsd1.ca.comcast.net [73.231.117.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: bvanassche@acm.org) by 011.lax.mailroute.net (Postfix) with ESMTPSA id 4gxXyp62xKz1XM5jn; Fri, 10 Jul 2026 13:40:34 +0000 (UTC) Message-ID: Date: Fri, 10 Jul 2026 06:40:32 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] scsi: ufs: Allows the driver to choose the interrupt handler type To: Kui Sun , Alim Akhtar , Avri Altman , "James E . J . Bottomley" , "Martin K . Petersen" Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, rain.zhang@unisoc.com, yuelin.tang@unisoc.com, wenchao.chen@unisoc.com, cixi.geng@linux.dev, =?UTF-8?Q?Andr=C3=A9_Draszik?= References: <20260710065948.467514-1-kui.sun@unisoc.com> Content-Language: en-US From: Bart Van Assche In-Reply-To: <20260710065948.467514-1-kui.sun@unisoc.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 7/9/26 11:59 PM, Kui Sun wrote: > This capability allows the host controller driver to choose whether > To register interrupts in a threaded manner or in a > Standard (non-threaded) manner A patch description should not only explain what has been changed but also why. Why do you want to make this change? Why do you want to change the default behavior from threaded to not threaded? Bart.