Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11851] Support for Google Coral devboard
Date: Fri, 10 May 2019 07:43:06 +0000	[thread overview]
Message-ID: <bug-11851-163-yqfox3opDC@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11851-163@https.bugs.busybox.net/>

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

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for the suggestion. Howevr, this is not really a bug report or an
enhancement on which there's much we can do: if somebody has access to this
hardware platform, and is interested in adding a defconfig for it in Buildroot,
it will be done. But without this, this bug would be sitting in our bug tracker
for ages, without us being able to do anything about it.

Perhaps you could consider sponsoring this HW platform to one of the Buildroot
developers, or alternatively adding a Buildroot configuration for this HW
platform yourself ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      reply	other threads:[~2019-05-10  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 12:19 [Buildroot] [Bug 11851] New: Support for Google Coral devboard bugzilla at busybox.net
2019-05-10  7:43 ` bugzilla at busybox.net [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=bug-11851-163-yqfox3opDC@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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