public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Jan-Simon Möller" <jsmoeller@linuxfoundation.org>,
	"akash hadke" <akash.hadke27@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: akash hadke <akash.hadke@kpit.com>
Subject: Re: [oe-core][master][PATCH] busybox: Use ISO 13400 timings in zcip
Date: Thu, 15 Feb 2024 15:21:50 +0000	[thread overview]
Message-ID: <6aafdf6c32502cc814d08437da838790dfbe5e28.camel@linuxfoundation.org> (raw)
In-Reply-To: <2143322.9o76ZdvQCi@arbeit>

On Thu, 2024-02-15 at 16:06 +0100, Jan-Simon Möller wrote:
> Am Freitag, 9. Februar 2024, 15:17:13 CET schrieb Richard Purdie via 
> lists.openembedded.org:
> > On Wed, 2024-02-07 at 13:21 +0530, akash hadke wrote:
> > 
> > I think a few of us are torn on this. If it were accepted upstream, I'd
> > probably take it. Whilst it is still pending, I'm less sure.
> > 
> > Having "embedded" targeted features in OE-Core is desirable in many
> > ways. In this case the target usage is probably quite niche.
> > 
> > I'd like to see if anyone else would find this useful? Does AGL want to
> > use this for example?
> 
> We (AGL) would wait for upstream busybox feedback to 
> http://lists.busybox.net/pipermail/busybox/2024-February/090611.html 
> 
> And go from there.

Thanks, in that case I think OE-Core will follow on that as I don't
think this is going to be enabled to tested in most of our userbase.

Cheers,

Richard


      parent reply	other threads:[~2024-02-15 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  7:51 [oe-core][master][PATCH] busybox: Use ISO 13400 timings in zcip Akash Hadke
2024-02-07 11:28 ` Alexander Kanavin
2024-02-07 12:20   ` [master][PATCH] " akash hadke
2024-02-07 12:39     ` [OE-core] " Alexander Kanavin
2024-02-09 14:17 ` [oe-core][master][PATCH] " Richard Purdie
     [not found]   ` <2143322.9o76ZdvQCi@arbeit>
2024-02-15 15:21     ` Richard Purdie [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=6aafdf6c32502cc814d08437da838790dfbe5e28.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akash.hadke27@gmail.com \
    --cc=akash.hadke@kpit.com \
    --cc=jsmoeller@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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