Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Sakib Sajal <sakib.sajal@windriver.com>,
	Randy MacLeod <rwmacleod@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31
Date: Tue, 21 Jul 2020 12:07:21 -0700	[thread overview]
Message-ID: <f1bb6b95-5de6-e99f-347a-834c0ebd213a@gmail.com> (raw)
In-Reply-To: <0ebff3d6-7325-5263-9ebe-760bc25e8e3b@gmail.com>



On 7/21/20 12:01 PM, Khem Raj wrote:
> 
> 
> On 7/21/20 11:54 AM, Sakib Sajal wrote:
>>
>> On 2020-07-21 2:11 p.m., Randy MacLeod wrote:
>>> Hi Sakib,
>>>
>>> Did you check this busybox fix against musl? I forgot to ask you this 
>>> when
>>> you showed me this patch yesterday.
>>>
>>> Randy
>>
>> Yes, I built core-image-minimal with musl and everything was fine.
>>
> 
> build alone would not be sufficient, runtime testing would be required 
> too. The patch however seems ok to me. Also send it upstream to bb ml as 
> well for review

oh there already is another patch proposed here [1]

[1] http://lists.busybox.net/pipermail/busybox/2020-July/088133.html

  reply	other threads:[~2020-07-21 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 18:00 [dunfell][PATCH] busybox: make hwclock compatible with glibc 2.31 Sakib Sajal
2020-07-21 18:11 ` [OE-core] " Randy MacLeod
2020-07-21 18:54   ` Sakib Sajal
2020-07-21 19:01     ` Khem Raj
2020-07-21 19:07       ` Khem Raj [this message]
2020-07-21 19:10       ` Sakib Sajal
2020-07-21 18:32 ` ✗ patchtest: failure for busybox: make hwclock compatible with glibc 2.31 (rev2) Patchwork

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=f1bb6b95-5de6-e99f-347a-834c0ebd213a@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rwmacleod@gmail.com \
    --cc=sakib.sajal@windriver.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