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 E5F61FF886F for ; Thu, 30 Apr 2026 07:16:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kernelnewbies.org; s=mail; h=Content-Transfer-Encoding:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:Cc: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=jkLqRPpI403d1OMJGq2c2BPZ38UmQbL23jAJhuas/oc=; b=lskiorpKOnbDWPDK2xjn3EJzUR tFKR1NHUx20ahf3eswEmUukVkk5OGlxVn3LEjdX3ywFfrSTmgQijSmXz/Ulom3gseLFJ6VjV6+nnf rYJ0K0iCMYr3EklfUANsZMxm2TWOmlXCoJV3T1qge4mhIXWiesPW6jGOy1us1bDEioivNBXL0T5sC LycGyLti44ZX+688xr2/hK+aEZkdSDfLqvcS06MzCx5vIXQLwY1kSAEuAHVHfidNtdLClrw6tnzG/ JTj1xllLVnj3o3iC9uc1WncxDaTFzhzzCmEVMI1/auH0xLARxQtdxvpcVF+b0Ux5UySNsadc/6kim snf6y95A==; Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.97.1) (envelope-from ) id 1wILdF-000000001ZI-1lKJ; Thu, 30 Apr 2026 03:16:21 -0400 Received: from fout-b3-smtp.messagingengine.com ([202.12.124.146]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1wILdE-000000001Z5-0ZZq for kernelnewbies@kernelnewbies.org; Thu, 30 Apr 2026 03:16:20 -0400 Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfout.stl.internal (Postfix) with ESMTP id 81C631D0005D; Thu, 30 Apr 2026 03:16:18 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Thu, 30 Apr 2026 03:16:18 -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=fm2; t=1777533378; x=1777619778; bh=LS8580a0gD XGAU8S9i3CoYgQ/OA927mYNVhAR5pEC/s=; b=Uhkbzr9bPrVQUJhIg352FDBssM /g8U7QKnei5uT94sEq/ylP+hZUf3iKii0wBbVmfD462/3A/IT6cOTtZhLQR6ROBa INJm80HAeh5r3whX9pIUXEc+uS2MHz4hjM/l+7hBA/QgDIuY7AFea/2+9ZqT26ot JB/UKtb71sozlIMqSxE+GAQ+xKzA8VTkwHB0qkLoJ5ZQ1Sa0Oq5uKHFP1zYMi0Vf 8/mbwUcAky7AbPtjDTm60DEIF/ZbgsjK+696Tql06NHRmKFnCNvNTAiTv+uCHtta Chf/38c9xGjIh7qA9reD0kJvXxtJptQUdEJP2u9hjjio134DM+9g4TI7QJww== 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-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1777533378; x=1777619778; bh=LS8580a0gDXGAU8S9i3CoYgQ/OA927mYNVh AR5pEC/s=; b=uum+lUirHz8O5XC8lepJepPubVSiGj4CzCtcT6aKJboqlAq6dXo 2biD30rLXDCehbf/4nzgWr8qomwT1HTK4YK8aHCY8a76Nv43I70jOGXY5CEU9pNP rsnDZv9CzoQbSORVEzjy9HoS5I1axX2r1tmcFO2KfmndNTmKse04T8i1gSl+WbS9 r31rfnEmErPSWuolJ5SsF/LEniCCKI5iPkD23BhqH1vHK7fpkqPi0OgJWly8NoVE RzaDUsihdJwQWAdtpJqyGoq1hz5m8WM3cxcYZlG39ZNDd1HKHTOqg87F5sTMqE/1 LRBI8BXZFFjcceDB3W+xsOjCuM1xr1e+pIw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdekieeilecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcumffj uceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeehgedvvedvle ejuefgtdduudfhkeeltdeihfevjeekjeeuhfdtueefhffgheekteenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtg homhdpnhgspghrtghpthhtohepiedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohep lhhinhhushdrphhrohgsvghrthesghhmrghilhdrtghomhdprhgtphhtthhopehpsghivg hljeesghhmrghilhdrtghomhdprhgtphhtthhopehkvghrnhgvlhhnvgifsghivghssehk vghrnhgvlhhnvgifsghivghsrdhorhhg X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 30 Apr 2026 03:16:17 -0400 (EDT) Date: Thu, 30 Apr 2026 09:15:39 +0200 From: Greg KH To: Linus Probert Subject: Re: Upstreaming - how to deal with vendor fork Message-ID: <2026043025-confined-paralyses-bb09@gregkh> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: Patryk , 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 Wed, Apr 29, 2026 at 07:42:14PM +0200, Linus Probert wrote: > On Wed Apr 29, 2026 at 3:27 PM CEST, Patryk wrote: > > Hi > > Some time ago I managed to upstream one bugfix, now I have more changes but > > I'm wondering how to approach this. > > > > Suppose that I have found a bug and prepared a fix. However, the bug and > > its solution has been found and tested on a custom board that is equipped > > with a particular buggy device. The problem is that I cannot simply use > > mainline/maintainer tree, build it, and run on my board as these source > > trees do not have support for my board, as I use SoC vendor fork (v6.12) > > supplied with their bsp with patches that add support for my board. > > > > It's not mine decision - obviously - me and my team would be very willing > > to use mainline but it would require some effort, time and obviously we > > would not get vendor support in case of some bugs (it happened mamy times). > > > > I can of course take the minimal set of patches for out board and apply > > them over mainline but e.g. now I have a bugfix for mainline driver...but > > in order to fully test it I need vendor changes as they did not upstream it > > yet. > > > > So at the end in order to test a bugfix on the mainline I would need to > > apply patches that add support for my board as well patches from vendor > > fork that add support for the rest of the functionality (not yet upstreamed > > by vendor) that I need in order to test the bugfix. > > > > Any sugestion on how to approach this? I have already few changes that > > could be applied to mainline but due to what I described above they're just > > waiting... > > > > Will be grateful for some sugestion. > > > > Best regards > > Patryk > > Hi Patryk, > > if your patches can't be applied without first applying the vendors > patches then there's not much you can do is there. Your fixes won't > apply. > > If your patches do apply to staging-next and they do fix your issue > isn't that enough to submit them? You should be able to explain how you > have confirmed the fixes even though it requires some steps to get > there. > > You can always submit a patch-tree to linux-staging with an RFC prefix > and you will get feedback based on that. Either you get a no or a yes. > Worth testing IMO. What does the staging tree have to do with this? confused, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies