From nobody Fri Nov 29 02:49:58 2024 Received: from mail-wr1-f43.google.com (mail-wr1-f43.google.com [209.85.221.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C28D714B967 for ; Wed, 25 Sep 2024 09:56:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.43 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727258209; cv=none; b=qRnaVooNYFY3u/2aOjZGQ5i/U5pDj5moLvEw6EXB9TMMYMbrCUTYZqLGmpZQ0HxpSJkvXBgLlSrDz4EVMxdGVa6ytnHzby1KjDfdYmGk/01F12woEGmZ7pq/9xV+Xdtb2155IIxPKwDYhWBEsHVkNZ0zJ2J+8Tu/Pa8uhTjwl78= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727258209; c=relaxed/simple; bh=xEng0ILGawkE/K9pQCc8vU14hShyRxs7UG8CXeYAF04=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=SIzNKGL43CHXglKTiCU95vEe26vhYI1ZATTN5PeCbjfOb6gKtgXoj2yQSsLnlMNI+iXkqSMIN93kMEipuzRyEBfoT7Xel7ZqUlJvK2cVRRnkbdHfASOqgZLTcJJ7pJqiSbTlQWGJ9kVuCb7UPtILkrxUf9wVg7YY11Jz/1EIRcc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=UU+VeMYL; arc=none smtp.client-ip=209.85.221.43 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="UU+VeMYL" Received: by mail-wr1-f43.google.com with SMTP id ffacd0b85a97d-37ccc5c7857so8094f8f.0 for ; Wed, 25 Sep 2024 02:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1727258206; x=1727863006; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=T4ek5g2WpaEArbed43Ic4SfAR8svgIoVtYNeQf4QZko=; b=UU+VeMYLsKSW3dHDi0FKe1s4pY5hRWuRRU5MRa1/NYaTEr2waUTYojM/YQa0omyZVV ZCe/qjquY0C6Eqqyvp/Cah2VT9nXP/R7fO38ejy9DCgXqJ7NEsWYaMTegssgVC4sJA0b KHOz+vGT1BZJvY6GXQtItjjPRc2aLS0rmsLLyXLPgZvw6RDcpAZbdV4KLgcW3BrqJNbl YGzURW2VCv38YbYi4npPXkS97ovidTp1YKp13tskr9B40k6O5q9hLpxkL9H9MBdtfo2i JF7okKVkknpkDiWhn7iTBGGBSXE5fz0npLNR6zHI/H8gyM3HCXbA7od+XGRZ5t8gHERz 8WTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727258206; x=1727863006; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=T4ek5g2WpaEArbed43Ic4SfAR8svgIoVtYNeQf4QZko=; b=UTKeDFTDj+pOGnUe1LaifQu4GR9PEiVD9069WfYE4R8tRl67orflLe2CLtuaEUbWdZ a8k1O1twG70KkEpVUCzMJCAiuP9Ad0GUs5BqziC6Y5TmkMF76hpleBxOX9k+XO37AxDc J3ie4Kitan6XBxa2c5PvjPyfZgMEVO8gW64F5jNFC/4NBwwT4F1sMKtCWvKehpOJQXv8 1GO/Omqex5kKKh112p2rh08vJVdkxPv6rBu8vnmYBm7VuGVPk9cdlHd4PsF2aORdRQvG 7W28R+NzT2jUewCcA+iuHkooEVto1pUlHv3YNjrAaUKTlDSurpUbJzr6HqlZ7TjIn79e G/0A== X-Forwarded-Encrypted: i=1; AJvYcCVFtspYcaf4PE+Gyr5j2V3cyuZc/Gx97bUyGy7xFZGUUsLr43ay2LIyp7FBChD9s44bOztSRuhBY1WoPEc=@vger.kernel.org X-Gm-Message-State: AOJu0YxX5JeUX11N32Q7O0GK8fDoi/F9qSXJOcCQQpitmUz/8YHVYWzw 0XvL52Hu0TsUqNpQHZr1208xnJHaRFNHZ5QFRYDeWJpNCUBcm/G4Iu036OYeeUM= X-Google-Smtp-Source: AGHT+IGSJhzwvWL9e+QqYHeRxVHO7r6yn25VxHi+gaz4ceL1fnx2qrMA8vQyjlnTr3Yrz+A2YPHONQ== X-Received: by 2002:a5d:64c8:0:b0:374:c2e9:28aa with SMTP id ffacd0b85a97d-37cc249efa7mr700119f8f.8.1727258205960; Wed, 25 Sep 2024 02:56:45 -0700 (PDT) Received: from krzk-bin.. ([178.197.211.167]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-37cbc2a8bcasm3559020f8f.9.2024.09.25.02.56.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Sep 2024 02:56:45 -0700 (PDT) From: Krzysztof Kozlowski To: Arnd Bergmann , Olof Johansson , soc@kernel.org, Jonathan Corbet , linux-arm-kernel@lists.infradead.org, workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski , Linus Walleij , Alexandre Belloni , Will Deacon , Kevin Hilman , Palmer Dabbelt , Geert Uytterhoeven , Conor Dooley , =?UTF-8?q?Heiko=20St=C3=BCbner?= Subject: [PATCH v2] Documentation/process: maintainer-soc: clarify submitting patches Date: Wed, 25 Sep 2024 11:56:35 +0200 Message-ID: <20240925095635.30452-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.43.0 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 Patches for SoCs are expected to be picked up by SoC submaintainers. The main SoC maintainers should be addressed only in few cases. Rewrite the section about maintainer handling to document above expectation. Signed-off-by: Krzysztof Kozlowski Cc: Linus Walleij Cc: Alexandre Belloni Cc: Will Deacon Cc: Kevin Hilman Cc: Palmer Dabbelt Cc: Geert Uytterhoeven Cc: Conor Dooley Cc: Heiko St=C3=BCbner Reviewed-by: Bagas Sanjaya Reviewed-by: Kevin Hilman Reviewed-by: Linus Walleij --- During our LPC ad-hoc BoF, we discussed improving Maintainer SoC docs and I think I volunteered to write something. The trouble is that whatever I won't write in my notes, escapes my memory. I believe this is what we discussed. Was there anything more to write/document? Changes in v2: 1. Fix missing closing ) (Conor). 2. Style changes (in point 3.). 3. Soften note that soc@kernel is not for discussing ("is usually not"). --- Documentation/process/maintainer-soc.rst | 42 +++++++++++++++++++++--- 1 file changed, 37 insertions(+), 5 deletions(-) diff --git a/Documentation/process/maintainer-soc.rst b/Documentation/proce= ss/maintainer-soc.rst index 12637530d68f..fe9d8bcfbd2b 100644 --- a/Documentation/process/maintainer-soc.rst +++ b/Documentation/process/maintainer-soc.rst @@ -30,10 +30,13 @@ tree as a dedicated branch covering multiple subsystems. The main SoC tree is housed on git.kernel.org: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/ =20 +Maintainers +----------- + Clearly this is quite a wide range of topics, which no one person, or even small group of people are capable of maintaining. Instead, the SoC subsys= tem -is comprised of many submaintainers, each taking care of individual platfo= rms -and driver subdirectories. +is comprised of many submaintainers (platform maintainers), each taking ca= re of +individual platforms and driver subdirectories. In this regard, "platform" usually refers to a series of SoCs from a given vendor, for example, Nvidia's series of Tegra SoCs. Many submaintainers o= perate on a vendor level, responsible for multiple product lines. For several re= asons, @@ -43,14 +46,43 @@ MAINTAINERS file. =20 Most of these submaintainers have their own trees where they stage patches, sending pull requests to the main SoC tree. These trees are usually, but = not -always, listed in MAINTAINERS. The main SoC maintainers can be reached vi= a the -alias soc@kernel.org if there is no platform-specific maintainer, or if th= ey -are unresponsive. +always, listed in MAINTAINERS. =20 What the SoC tree is not, however, is a location for architecture-specific= code changes. Each architecture has its own maintainers that are responsible f= or architectural details, CPU errata and the like. =20 +Submitting Patches for Given SoC +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +All typical platform related patches should be sent via SoC submaintainers +(platform-specific maintainers). This includes also changes to per-platfo= rm or +shared defconfigs (scripts/get_maintainer.pl might not provide correct +addresses in such case). + +Submitting Patches to the Main SoC Maintainers +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The main SoC maintainers can be reached via the alias soc@kernel.org only = in +following cases: + +1. There are no platform-specific maintainers. + +2. Platform-specific maintainers are unresponsive. + +3. Introducing a completely new SoC platform. Such new SoC work should be= sent + first to common mailing lists, pointed out by scripts/get_maintainer.pl= , for + community review. After positive community review, work should be sent= to + soc@kernel.org in one patchset containing new arch/foo/Kconfig entry, D= TS + files, MAINTAINERS file entry and optionally initial drivers with their + Devicetree bindings. The MAINTAINERS file entry should list new + platform-specific maintainers, who are going to be responsible for hand= ling + patches for the platform from now on. + +Note that the soc@kernel.org is usually not the place to discuss the patch= es, +thus work sent to this address should be already considered as acceptable = by +the community. + Information for (new) Submaintainers ------------------------------------ =20 --=20 2.43.0