All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15736] Mesa3D is missing H.264/H.265 support
Date: Tue, 22 Aug 2023 05:49:16 +0000	[thread overview]
Message-ID: <bug-15736-163-BTNc96wkOs@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15736-163@https.bugs.busybox.net/>

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998@free.fr
             Status|NEW                         |RESOLVED
         Resolution|---                         |MOVED

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Tristan, All,

Thanks for the report.

Your patch is still pending, amongst the 340 other still pending patches:
    https://patchwork.ozlabs.org/project/buildroot/list/

We'll evntually get to it as tme permits. Opening a bug report will not
make the patch being considered faster, and will certainly not help
decrease the load...

So I'm closing this report.

Regards,
Yann E. MORIN.

-- 
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:[~2023-08-22  5:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  3:58 [Buildroot] [Bug 15736] New: Mesa3D is missing H.264/H.265 support bugzilla
2023-08-22  5:49 ` bugzilla [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-15736-163-BTNc96wkOs@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.