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 9161] New: modsetting patch not applied to xserver 1.18.4
Date: Wed, 10 Aug 2016 08:51:13 +0000	[thread overview]
Message-ID: <bug-9161-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9161
           Summary: modsetting patch not applied to xserver 1.18.4
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: develop at manuel-voegele.de
                CC: buildroot at uclibc.org
  Target Milestone: ---

The "modesettings-needs-dri2" patch isn't applied to the xserver version 1.18.4
in buildroot 2016.08-rc1

I managed to hotfix this locally by renaming
"package/x11r7/xserver_xorg-server/1.18.3" to "1.18.4". However the commit
which introduced this directory (bb6bd531c97734b7be2ec24670771dc10aef1791)
mentions that this patch has to be applied to all versions >= 1.17.2. Since
version 1.17.4 was added in this release there might be additional steps
required to ensure both versions will be patched.

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

             reply	other threads:[~2016-08-10  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  8:51 bugzilla at busybox.net [this message]
2016-08-10 13:15 ` [Buildroot] [Bug 9161] modsetting patch not applied to xserver 1.18.4 bugzilla at busybox.net
2016-08-10 13:20 ` bugzilla at busybox.net

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-9161-163@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