From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpout-02.galae.net (smtpout-02.galae.net [185.246.84.56]) (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 1D6AB2D8796; Thu, 29 Jan 2026 18:38:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.84.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769711934; cv=none; b=KQclXfjs9Skt+E5Xs/ZB9dEzo5E3lTuBrSdkiqYueLCUZpdDUwRM3r002UuxwZklVdOiZmy6GtUp08MpLqrJDZqM1ZkpmRq0x6dSLVZtQzYkaPY3DAad0ggLfU8m3GKwQDgSRkY0ow36km9AGoHTCVi94U9ydNga53TS2RDuu8k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769711934; c=relaxed/simple; bh=RgHO2pkUFSgU4t4TLGPUHZGx0S+toOfJKk5R7JzVOLQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=SftbRDT/HELzbGumvh5hS778r9/eQEAsNJOd76CUAZJR3yjx3BCmLSYd8SPPEdBXYYEaxCq7pvZsdSaDi3Nj4yRrk527VobVEzMk9RgUwzxcNcKsL6/o2snOe9MVr3CT9KwRjMciIQBYqdBt5VkvZut+Y29ifi5UuQXJOq6xFWY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=rVP9e3X6; arc=none smtp.client-ip=185.246.84.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="rVP9e3X6" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-02.galae.net (Postfix) with ESMTPS id 7F1A41A2B11; Thu, 29 Jan 2026 18:38:50 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 3655D60746; Thu, 29 Jan 2026 18:38:50 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 7C38B119A880F; Thu, 29 Jan 2026 19:38:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1769711929; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=RgHO2pkUFSgU4t4TLGPUHZGx0S+toOfJKk5R7JzVOLQ=; b=rVP9e3X6fXoClBPXCPhoP7BSYBOtTcPNHLgyBvFkcaicQTSZ0X0uowXMx/DwvhujyBREpm fM5v7tqFldp6J7Cn93HyKBwUnqXk4BrKLsUg5K87idhTveUn7IRgN/EUjdO8WkmSqaEG6i vex6a/y9FF6tTS7uRdHB3gOZsiYfRlRCJRK6bW9JmBnuRLtuNHhD29JcU7NZNdmnrihzEz +ndD/0mw6cMsrLB3WRoRxXWJfOyKCb67+fpOoCvWfkXPrOXjezr4+bgZcou+qTXRpuRhVS u4X4sGxLpGazqSh7p6CemlnAPcdR429XWDjVSOL4odcVglWaaiSeYmLT5tH59A== From: Miquel Raynal To: Bjorn Andersson Cc: Konrad Dybcio , Junhao Xie , Konrad Dybcio , Richard Weinberger , Vignesh Raghavendra , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, Xilin Wu Subject: Re: [PATCH v2 0/2] mtd: devices: Qualcomm SCM storage support In-Reply-To: (Bjorn Andersson's message of "Wed, 28 Jan 2026 14:31:33 -0600") References: <20260126-scm-storage-v2-v2-0-fa045c7e7699@radxa.com> <875x8ln7tk.fsf@bootlin.com> User-Agent: mu4e 1.12.7; emacs 30.2 Date: Thu, 29 Jan 2026 19:38:44 +0100 Message-ID: <87fr7ol0wb.fsf@bootlin.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Last-TLS-Session-Version: TLSv1.3 Hello Bjorn, >> If I may, I even skipped the mail entirely because it was not about mtd >> in the end. There is a single big patch labelled "firmware: qcom:". I >> believe the series would better be split in smaller chunks. Typically >> one for the storage support and another one for the firmware part, at >> least. >>=20 > > The firmware patch adds wrappers for the secure world interface, which > without the MTD driver will lack consumers of the API - i.e. I'd prefer > not to pick that part, or parts thereof, alone. Yes, I understand. > So I think it does make sense to introduce the two parts together in one > series (if you have any requests for splitting the MTD patch up in any > way I have no objections). > > This leaves us with the practical problem of getting it merged, which I > believe would best be handled by me picking the firmware patch and > sharing this in an immutable branch with you, once we're happy with the > set (which won't be for 6.20). Works for me! I'll send a minor review with a couple of comments, but we can apply this close after next -rc1, if you are good with the fw part. Thanks, Miqu=C3=A8l