From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 63381] cpumask.h error
Date: Tue, 22 Oct 2013 19:23:07 +0000 [thread overview]
Message-ID: <bug-63381-58281-zt4w6SGVBg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-63381-58281@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=63381
--- Comment #2 from DarinV <darin.vancoevering@gmail.com> ---
2.6.27.57 patches for bootsplash and squashfs 3. No issues building with
the 3.8.3 version and it is for x86. Mainline with only those 2 patches as
I built my own kernel for the SuperGamer Distro. What changed going from
the 3.8.3 to the 3.9 versions? I may have to build the the drivers with
stock kernel then build the kernel last with patches but was hoping I
didn't have to.
On Mon, Oct 21, 2013 at 10:46 AM, <bugzilla-daemon@bugzilla.kernel.org>wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=63381
>
> Hauke Mehrtens <hauke@hauke-m.de> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |hauke@hauke-m.de
>
> --- Comment #1 from Hauke Mehrtens <hauke@hauke-m.de> ---
> What kernel are you compiling against? We only test this with mainline
> kernels,
> but when you have a patched kernel like one provided by distributions like
> RedHat, they contain many patches which are conflicting with backports.
>
> Are you compiling for x86 or for some other arch?
>
> --
> You are receiving this mail because:
> You reported the bug.
>
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-10-22 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 5:32 [Bug 63381] New: cpumask.h error bugzilla-daemon
2013-10-21 10:46 ` [Bug 63381] " bugzilla-daemon
2013-10-22 19:23 ` bugzilla-daemon [this message]
2013-10-23 18:32 ` bugzilla-daemon
2013-11-24 21:35 ` bugzilla-daemon
2013-11-25 23:01 ` bugzilla-daemon
2014-07-28 3:33 ` bugzilla-daemon
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-63381-58281-zt4w6SGVBg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox