From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-185.mta0.migadu.com (out-185.mta0.migadu.com [91.218.175.185]) (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 319BA2E62A9 for ; Tue, 2 Jun 2026 20:45:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780433103; cv=none; b=YvBi6j9JHUV4o4eoHlHk9L6Df7XBE5auVTWY8as41yyg65OrmKupUPKy5h2znWTwXuh7UwNjFAD9fN/uVBYt97JDiTI9D+5a640aXz28RBIgExvh4pkvW/UzOpioUetctcCCOEvgor++WsoWC4p8LJ80JDkjnDSnn6h6Jjj/pl4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780433103; c=relaxed/simple; bh=XOXieHT5BNwSL6lnj4StoJAGUsbJruWniToi9U2yReM=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=e+edqrnrnQhpnNL0Verco9hLMdaUKTJBMGtRyV9blTNx1bXtwVczXSJDx00ykU7qP3Od++BF/mRwjiTBHk+j+a0FgFZlxfd8QIzYDFV54aTQRLFoxKs335kWIlqjFRiFmSAMk41R0NQT2YfB/3tRmnNUW99HXFDvTxQrXA2MxJg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=IWfJDCNt; arc=none smtp.client-ip=91.218.175.185 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="IWfJDCNt" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1780433099; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GovdXnIkZYl5ihVwHTXq51twoG5NdKn4Swa4IYsN7Lc=; b=IWfJDCNtChn4jUMaQjUR6s5f3QFfMeubprBdbCuIMzDQa6zpwxiYD9jZpLzzFFLo898v8q rpuqIiQOY2gwQ3qgVxSmjNR2ckmcz2JKGqHUiqAIyjVGv6dXMf8AJh3cyb1XhpvUOydK40 72sfJksxSKoavtcXyzOHAMZ990xOals= From: Roman Gushchin To: Mauro Carvalho Chehab Cc: Derek Barbosa , Konstantin Ryabitsev , Jason Gunthorpe , Steven Rostedt , users@kernel.org, Linux Media Mailing List Subject: Re: Linking Patchwork with Sashiko? In-Reply-To: <20260602223936.27def657@foz.lan> (Mauro Carvalho Chehab's message of "Tue, 2 Jun 2026 22:39:36 +0200") References: <20260530103004.6fe2ffa7@foz.lan> <7E971C76-0568-43EF-9EE7-C8DB78C45CA1@linux.dev> <20260530200017.0fe7f685@foz.lan> <20260530204945.22ac92c6@foz.lan> <20260530205351.19847fc8@foz.lan> <7ia4tsrkn1k4.fsf@castle.c.googlers.com> <20260602223936.27def657@foz.lan> Date: Tue, 02 Jun 2026 20:44:39 +0000 Message-ID: <7ia4jysgvfig.fsf@castle.c.googlers.com> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT Mauro Carvalho Chehab writes: > On Tue, 02 Jun 2026 20:13:15 +0000 > Roman Gushchin wrote: > >> Derek Barbosa writes: >> >> > On Sat, May 30, 2026 at 08:53:51PM +0200, Mauro Carvalho Chehab wrote: >> >> >> >> In time: problematic in the sense that the first project that >> >> picked it is likely the patch "owner": the token will require >> >> maintainership on such project. >> >> >> >> In practice it would mean that the token used on patchwork instances >> >> with multiple Kernel projects may need maintainers permission on all >> >> such projects, as otherwise patchwork update will fail. >> >> >> >> Thanks, >> >> Mauro >> >> >> > >> > Hi Mauro, >> > >> > Just to recap the the thread, to confirm that I am following it correctly: >> > >> > - Patchwork only supports a single URL mask for message-ID lookup (lore or >> > sashiko). Adding a sashiko link would require diverging from >> > upstream. >> >> Is it something we can change upstream? > > No idea. I suspect a change like that will require change patches database > and use Django's migration logic to touch its database. > > However, at least for me, I can't see any value of being able search for a > patch based on Sashiko's message ID. > >> > - pw_tools is a workaround solution to get/set status on patchwork via bot-mail >> > parsing. pw tokens also have broad permission scope. >> > >> > which that leaves us with two "methods" of integration: >> > >> > 1. The Sashiko daemon calls the pw_tools script directly to update the status. >> > 2. Sashiko sends a single-per-patch-email with parseable "status" to a mailing >> > list, where some running daemon will pickup the mail. >> >> This feels a bit hacky. > > The alternative that would be acceptable, at least on media, is if > one would add support on patchwork to have a separate permission just > for checks update. Agree, it feels like the best way forward. > Granting full maintainership control to external bots sounds too risky > for my taste. Agree. I'd strongly prefer Sashiko to not have it.