From: Gyorgy Sarvari <skandigraun@gmail.com>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: openembedded-devel@lists.openembedded.org,
linux-kernel@vger.kernel.org,
"Signed-off-by: Patrick Rudolph" <patrick.rudolph@9elements.com>
Subject: Re: [oe] [meta-oe][PATCH] meta-openembedded: flashrom: Update to v1.4.0
Date: Wed, 12 Mar 2025 18:04:56 +0100 [thread overview]
Message-ID: <356a4c72-2155-47ef-9ee1-180b861b94b1@gmail.com> (raw)
In-Reply-To: <CABqG17hBviQ64jXgZ1fa5+ir37YPyK62LZvMgrSGADOxSTFo-w@mail.gmail.com>
On 12.03.25 17:56, Naresh Solanki wrote:
> Hi
>
> On Wed, 12 Mar 2025 at 22:09, Gyorgy Sarvari <skandigraun@gmail.com> wrote:
>> On 12.03.25 17:03, Naresh Solanki wrote:
>>> Hi Gyorgy,
>>>
>>> On Wed, 12 Mar 2025 at 19:47, Gyorgy Sarvari <skandigraun@gmail.com> wrote:
>>>> On 12.03.25 12:19, Naresh Solanki via lists.openembedded.org wrote:
>>>>> -Upstream-Status: Submitted [https://review.coreboot.org/c/flashrom/+/51960]
>>>>> -Signed-off-by: Khem Raj <raj.khem@gmail.com>
>>>>> -Change-Id: I55c4e8529d36f0850dd56441c3fb8602c5d889fd
>>>>> +Upstream-Status: Inactive-Upstream
>>>> Is that really the case? I mean it is just being updated to a new
>>>> version, it doesn't look that inactive. That PR seems to be abandoned by
>>>> the submitter at the first superficial sight, is this not the case?
>>> Yes. its being inactive for long time.
>> The last commit date in the main branch of
>> https://review.coreboot.org/flashrom is "Sat Mar 1 19:19:16 2025 +1100"
>> - less than 2 weeks ago, with last release just before Christmas. It's
>> not as busy as Yocto, but doesn't look abandoned.
>>
>> Or am I looking at a wrong repo?
> Your right.
> I can work on flashrom 1.5.1 release. Please let me know.
>
> Thanks,
> Naresh
I was mostly interested about the Upstream-Status, thank you for the
confirmation.
I have no strong opinion about the new version - please do as you see it
fit.
>>>>> +
>>>>> +EXTRA_OEMESON="-Dbash_completion=disabled -Dtests=disabled"
>>>> Nitpick: Could you please fix the whitespaces around the equal sign?
>>> Sure.
>>>
>>> Regards,
>>> Naresh
prev parent reply other threads:[~2025-03-12 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 11:19 Naresh Solanki
2025-03-12 14:02 ` [oe] " Fabio Estevam
2025-03-12 14:07 ` Naresh Solanki
2025-03-12 16:18 ` Naresh Solanki
2025-03-12 14:17 ` Gyorgy Sarvari
2025-03-12 14:29 ` Naresh Solanki
2025-03-12 16:03 ` Naresh Solanki
2025-03-12 16:39 ` Gyorgy Sarvari
2025-03-12 16:56 ` Naresh Solanki
2025-03-12 17:04 ` Gyorgy Sarvari [this message]
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=356a4c72-2155-47ef-9ee1-180b861b94b1@gmail.com \
--to=skandigraun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=patrick.rudolph@9elements.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®