From: Jarek Poplawski <jarkao2@gmail•com>
To: unlisted-recipients:; (no To-header on input)
Cc: Manuel Prinz <manuel@debian•org>, netdev@vger•kernel.org
Subject: Re: [Fwd: Re: Bug#538372: header failure including netlink.h (or uio.h)]
Date: Tue, 29 Sep 2009 21:21:05 +0200 [thread overview]
Message-ID: <4AC25E21.7050407@gmail.com> (raw)
In-Reply-To: <20090929092727.GA7025@ff.dom.local>
Jarek Poplawski wrote, On 09/29/2009 11:27 AM:
> On 28-09-2009 13:24, Manuel Prinz wrote:
>> Hi everyone,
>>
>> I'm forwarding this bug in Debian (http://bugs.debian.org/538372) as
>> requested by the Debian kernel team. A patch is available. Applying just
>> the first hunk fixes the issue for me. I've not enough kernel knowledge
>> to judge if this fix is a proper solution, though.
>>
>> It would be really great if someone could have a look at it. Thanks in
>> advance! (And please CC me in replies. Thanks!)
>
> I've tried it with current include/linux and it works OK. Replacing
> uio.h on Debian really was not enough, but it looks like missing
> compiler.h entries could be the reason. Otherwise, please send your
> compile error log.
Hmm... Probably you noticed it yourself, so a little update for the
record. My method wasn't the proper way, but repeating it with
sanitized headers from the current kernel works even better: replacing
Debian's uio.h only seems to be enough yet.
Jarek P.
prev parent reply other threads:[~2009-09-29 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 11:24 [Fwd: Re: Bug#538372: header failure including netlink.h (or uio.h)] Manuel Prinz
2009-09-29 9:27 ` Jarek Poplawski
2009-09-29 19:21 ` Jarek Poplawski [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=4AC25E21.7050407@gmail.com \
--to=jarkao2@gmail$(echo .)com \
--cc=manuel@debian$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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