From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 75D4BC3DA4A for ; Thu, 22 Aug 2024 09:12:21 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.97.1) (envelope-from ) id 1sh3rW-00000000155-01P9; Thu, 22 Aug 2024 05:12:10 -0400 Received: from fhigh3-smtp.messagingengine.com ([103.168.172.154]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1sh3rU-0000000014z-35RL for kernelnewbies@kernelnewbies.org; Thu, 22 Aug 2024 05:12:09 -0400 Received: from phl-compute-01.internal (phl-compute-01.nyi.internal [10.202.2.41]) by mailfhigh.nyi.internal (Postfix) with ESMTP id EC7141151AC0; Thu, 22 Aug 2024 05:12:07 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Thu, 22 Aug 2024 05:12:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1724317927; x=1724404327; bh=IVVWhEq1AM lMvI3UPLHyI1jk9nKuFRH/z4aHgnic4z0=; b=MZpWBTYDBXjgXru65GSZxgahR9 BPcsH3e0jO138NSperdOnhvxfSzRo4ZHEOkRHspl40+3bGgzCsY3sbAENRghODbC F1xozSeSC/2Axv0TUBj5QpERuo+7NCejHOTtzySXR2lswamFvdIWUgI4oPG2WJOh PQTyncrlOuT5ec4w6hlpW9WDOm+iiOScTG7UVSa666gOn5G8l+++VArfVdBMY52e H/btsL5d3CNHQiky1Zxnxqr3JMZ4CdcQ5l5REoC5mbARb4VxlvOp0t2Z6VA4bZe1 4ycwelqZV/uXv7FFMbxdbsTa0GEpOcGTKH5BvAhd38UD4knCQiZDrSSZcIhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1724317927; x=1724404327; bh=IVVWhEq1AMlMvI3UPLHyI1jk9nKu FRH/z4aHgnic4z0=; b=U9ZiaXo9pergXG507stmeJob0FRRHwEWkWaWKuuI65Ln T0II5/u9PrtRvg7OOSk1G3SMFgYVoXObQ3bZKaVjqQQuSF5dhwlfk6Gvei+uWeVF Lf8eM23M+iyRmarihXWUJNkIbvbMipqNsaxj7A3t/J+BYfBWDSi/lB/+0TEzWP2L 27LTZmqm/353HfkZJVwotqH2CINY9riSjoiDblrkJ32ZlUbQI6d8RaKhv9JrX9nj eHjO6aaBSFhc4Qg40jW1Ra1/XnUpt3947IdV5sNN3SAV9jy5RMSi0TVeAchWV53A jNAbhb3V5Nh5y7Je/Xdnk4pgtXUREC4n5RX9Tshkcw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddruddvtddguddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvden ucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrf grthhtvghrnhepheegvdevvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefh gfehkeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epghhrvghgsehkrhhorghhrdgtohhmpdhnsggprhgtphhtthhopeegpdhmohguvgepshhm thhpohhuthdprhgtphhtthhopehpsghivghljeesghhmrghilhdrtghomhdprhgtphhtth hopehkvghrnhgvlhhnvgifsghivghssehkvghrnhgvlhhnvgifsghivghsrdhorhhg X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 22 Aug 2024 05:12:06 -0400 (EDT) Date: Thu, 22 Aug 2024 17:12:02 +0800 From: Greg KH To: Patryk Biel Subject: Re: Separating driver and documentation changes Message-ID: <2024082218-exemplify-collected-ae2f@gregkh> References: <20240822082932.vlovfb2wfzkpy2dv@LAP470330.localdomain> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240822082932.vlovfb2wfzkpy2dv@LAP470330.localdomain> Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Thu, Aug 22, 2024 at 10:29:32AM +0200, Patryk Biel wrote: > Hi > I'm going to send a patch that extends existing driver with support for a new > variant of the existing device. The changes in the drivr code are rather > small, around 100 lines of code. Apart from the driver changes I > would like to also update Documentation/devicetree/bindings for this > driver to add the information about the new supported variant. Should I > split the changes and send them separately? If so, how can I make sure > that the documentation changes won't be merged to kernel source tree > until the drive's modifications are merged? (if ofc maintainer decides > to integrate them). Make it a patch series, first patch does the bindings change and the second does the driver change. You will find thousands of examples of people doing this on the development mailing lists, it's the preferred way. good luck! greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies