All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14766] package dhcp on buildroot 2022.02.1 failed
Date: Tue, 19 Apr 2022 13:11:39 +0000	[thread overview]
Message-ID: <bug-14766-163-dmRgm2uTLc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14766-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=14766

Jörg Hering <joerg.hering@macgregor.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |blocker
             Target|                            |aarch64 processor (NXP
                   |                            |LS1046A)
                 CC|                            |joerg.hering@macgregor.com
               Host|                            |5.13.0-39-generic
                   |                            |#44~20.04.1-Ubuntu SMP Thu
                   |                            |Mar 24 16:43:35 UTC 2022
                   |                            |x86_64 x86_64 x86_64
                   |                            |GNU/Linux

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-04-19 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 11:30 [Buildroot] [Bug 14766] New: package dhcp on buildroot 2022.02.1 failed bugzilla
2022-04-19 13:11 ` bugzilla [this message]
2022-05-08 11:32 ` [Buildroot] [Bug 14766] " bugzilla
2022-05-08 12:01 ` bugzilla
2022-05-30  6:42 ` bugzilla

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=bug-14766-163-dmRgm2uTLc@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 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.