From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 03 Mar 2022 18:08:35 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nPowN-00GiL0-NH for lore@lore.pengutronix.de; Thu, 03 Mar 2022 18:08:35 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nPowN-0000MO-4R; Thu, 03 Mar 2022 18:08:35 +0100 Received: from mail.benfm.de ([85.214.16.47] helo=h2956758.stratoserver.net) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nPovY-0000MF-OU for ptxdist@pengutronix.de; Thu, 03 Mar 2022 18:07:45 +0100 Message-ID: <9e421142-d037-6b62-79c4-2a7a9a09d120@benfm.de> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benfm.de; s=2020; t=1646327263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LF/WPviFX+q8Nh+sXc8UD1LfCzL/HrEbaU7p0XSgwJQ=; b=b9EjGNUH/y/Nn7X8iUe9bs7Q5u+bDyr+t/Tj8guk/zkaMsA6SL7ba0jQR/aiYerhgvtZ0b tZYgyFPOk80phmO9JS2qXVmUrFzZqG8PPYBaQJ2ZB2R4rZf9gmmE6QjUfF73u0WUjHsPi3 1hTPXCNq91NjMWKfXbPwNgnatZEXkPpWZ/gg/OUWFduqWZWNCAOcEuwqZlrW/rW0powzju l/kVvJLudaU7IW9DX/e9sHcyKNTsUxpWRsdSEIy5+EQpwnSC6m5uZ1hCEl3dippdxE4eSH CKvA8ZoQ5xJya7oV/TkEfqE//mEio9aVDvErsVkPuOGrHKbLzsYk6IaL1y1xng== Date: Thu, 3 Mar 2022 18:07:43 +0100 MIME-Version: 1.0 Content-Language: en-US To: ptxdist@pengutronix.de References: <20220303134028.GN12709@pengutronix.de> <7ee003fb-e6c3-34d7-d9e2-d29279369b0c@t2data.com> From: Felix Mellmann In-Reply-To: <7ee003fb-e6c3-34d7-d9e2-d29279369b0c@t2data.com> Authentication-Results: ORIGINATING; auth=pass smtp.auth=flix@benfm.de smtp.mailfrom=flix.ptxdist@benfm.de X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-1.7 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: Re: [ptxdist] Patch series for package per project? X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false On 03.03.22 15:22, Christian Melki wrote: > > > On 3/3/22 2:40 PM, Michael Olbrich wrote: >> Hi, >> >> On Thu, Mar 03, 2022 at 10:17:07AM +0100, Christian Melki wrote: >>> I want to use the same bootloader (barebox) for various projects. >>> But patches are slightly different. series. doesn't seem to >>> work. >>> Have I missed something? I just assumed that per project patch >>> series for >>> packages would be possible. >>> I can see that kernel can steer the use of series file name, but how >>> does >>> that work for other packages? >>> >>> I can also see that there is search for various directory paths, but >>> nothing >>> regarding series.? >>> >>> It would be nice if I could use the same steering analogy as >>> _alternative. >> >> I'm not sure what you mean. Do you have multiple barebox packages in the >> same BSP? Or something else? >> > > Just one barebox version, but for different archs, with different > patchsets. I'd like the patches to live in the same place as they've > always done, i.e. under patches/package/... > But patches/package/series.$platform or similar does not seem to work? > Would it be an option to put the patches below each of the platformdirs? I ran into a similiar situation when starting to migrate to a different CPU platform. After a couple of years putting serveral "platformconfig" files within the same directory as "ptxconfig" I'm now using separate subdirs for each platform where separate sets of platform dependent patches are lying. Felix > Christian > >> Michael >> > > _______________________________________________ > ptxdist mailing list > ptxdist@pengutronix.de > To unsubscribe, send a mail with subject "unsubscribe" to > ptxdist-request@pengutronix.de _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de