All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Purushottam Kumar <purushottam27.kumar@lge.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] kmscube: Upgrade to latest revision
Date: Fri, 27 Sep 2024 16:25:16 +0200	[thread overview]
Message-ID: <5c5290c7-0535-4e58-9c36-83313336d068@cherry.de> (raw)
In-Reply-To: <OF2DE997E7.61C047EC-ON48258BA5.004E8C23-48258BA5.004E8C27@lge.com>

Hi Purushottam,

On 9/27/24 4:17 PM, Purushottam Kumar wrote:
> Hi,
> 
> Thanks for the quick response.
> Yes, for kirkstone branch need a separate commit but there gstreamer version is
> 1.20.7.
> Please ignore this patch i will share specific change commit for kmscube for
> master and kirskstone.
> 

I think this patch is fine for master and scarthgap? Is ther

For kirkstone, we probably want to bump + revert the patch that 
introduces a dependency version we cannot meet, or simply backport only 
the patches you're interested in in kirkstone?

Cheers,
Quentin


  reply	other threads:[~2024-09-27 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 10:53 [oe-core][PATCH] kmscube: Upgrade to latest revision Purushottam Choudhary
2024-09-27 11:18 ` Quentin Schulz
2024-09-27 14:17   ` Purushottam Kumar
2024-09-27 14:25     ` Quentin Schulz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-27 10:30 Purushottam Choudhary
2023-12-26 12:38 [PATCH] " Fabio Estevam
2024-01-08 16:21 ` [OE-core] " Martin Jansa
2024-01-08 17:01   ` Fabio Estevam
2024-01-08 17:25     ` Martin Jansa
2024-01-08 18:01       ` Fabio Estevam
2022-09-05  9:03 [OE-core] [PATCH] cracklib: upgrade 2.9.7 -> 2.9.8 Wang Mingyu
2022-09-05  9:03 ` [OE-core] [PATCH] kmscube: upgrade to latest revision Wang Mingyu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c5290c7-0535-4e58-9c36-83313336d068@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=purushottam27.kumar@lge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.