From nobody Mon Apr 6 12:52:10 2026 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 DFE6B35B63C for ; Thu, 19 Mar 2026 11:00:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773918011; cv=none; b=r0rTFtrIbZutcFB+raqB66dsKsod8VnkZUZ2NqEguWSBI3T6OAn+yLy3sVAlDlY5FUNHjcINFDZvr2q6NlJguAW8zeiTPsOiRC+m4NWnEIqikvIYz53F6WYa+2BTX2LruvRtT8u1esYpGzF/4c13ieV60JevKgZ1ZY4AnzUKJNs= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773918011; c=relaxed/simple; bh=s4yz1qknYsovhomq/cNB/wPtjPAk3MtjAzmSsKjp3rs=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=JprIOS+RWp7yR2tnNr4aXalKFcKGBT3uYvyuVogIijFyVaTbdsxRgLx3cUg9yF0PleyMsyC2BDUla+INwiOO5/R4AsaDvUWWAyri61VxnHpUpGXT38IWYl2mF+M5vXB7zGFDV+LNJkK+KG1Z/h7wCY38b46ZHa1ofd7asn6dXJU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=ifO6TAC7; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="ifO6TAC7" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-transfer-encoding; s=k1; bh=9wsX/1VG+KmMW/70MpWHcnfgt2pNqZbpfdvHVMNyqlE=; b=ifO6TA C7ICH7HTIW63VvIKZ6uBii5nFv7jCinL5igQFeTNVTeUmq0uSnBf3OYfRe9mlXS6 +jXts4fsjfSkulz40II5VT768Zz0N1FBsyimwsP82NBsd+sEKC85fC9pxaDd3eIL b/2qNELNHWZ2dbOPEOUnCw2/bykfjfn3xrGmJUIRUfRvB/Wu+gyY1tau6fKFGeUl 4Gsq0m+WtPnaSWQAbvKLz0BxGA2r3eVfUSUHWpCM/a0wXzXWi2lRST0RKGJO7GQN s1vR6I/tNkW6l1A6/N84XZHm6bebGrwUYIMxW8z8LeGk8LzEEEanwD/ZPv5pgnp9 dT2mH2b/ACw/Gi0A== Received: (qmail 1099480 invoked from network); 19 Mar 2026 11:59:53 +0100 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 19 Mar 2026 11:59:53 +0100 X-UD-Smtp-Session: l3s3148p1@uP/Ud15N2t0gAwDPXzF+ANZpdrMKUeLI From: Wolfram Sang To: linux-renesas-soc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Wolfram Sang , Linus Walleij , Andy Shevchenko Subject: [PATCH v5 02/15] hwspinlock: remove now unused pdata from header file Date: Thu, 19 Mar 2026 11:59:24 +0100 Message-ID: <20260319105947.6237-3-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.51.0 In-Reply-To: <20260319105947.6237-1-wsa+renesas@sang-engineering.com> References: <20260319105947.6237-1-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The last user turned out to be obsolete and was removed. Remove the unused struct now, too. Signed-off-by: Wolfram Sang Reviewed-by: Linus Walleij Acked-by: Andy Shevchenko --- include/linux/hwspinlock.h | 28 ---------------------------- 1 file changed, 28 deletions(-) diff --git a/include/linux/hwspinlock.h b/include/linux/hwspinlock.h index f35b42e8c5de..74b91244fe0e 100644 --- a/include/linux/hwspinlock.h +++ b/include/linux/hwspinlock.h @@ -25,34 +25,6 @@ struct hwspinlock; struct hwspinlock_device; struct hwspinlock_ops; =20 -/** - * struct hwspinlock_pdata - platform data for hwspinlock drivers - * @base_id: base id for this hwspinlock device - * - * hwspinlock devices provide system-wide hardware locks that are used - * by remote processors that have no other way to achieve synchronization. - * - * To achieve that, each physical lock must have a system-wide id number - * that is agreed upon, otherwise remote processors can't possibly assume - * they're using the same hardware lock. - * - * Usually boards have a single hwspinlock device, which provides several - * hwspinlocks, and in this case, they can be trivially numbered 0 to - * (num-of-locks - 1). - * - * In case boards have several hwspinlocks devices, a different base id - * should be used for each hwspinlock device (they can't all use 0 as - * a starting id!). - * - * This platform data structure should be used to provide the base id - * for each device (which is trivially 0 when only a single hwspinlock - * device exists). It can be shared between different platforms, hence - * its location. - */ -struct hwspinlock_pdata { - int base_id; -}; - #ifdef CONFIG_HWSPINLOCK =20 int hwspin_lock_register(struct hwspinlock_device *bank, struct device *de= v, --=20 2.51.0