From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] i2c-tools: install devt headers to staging dir
Date: Mon, 26 Sep 2016 22:17:50 +0200 [thread overview]
Message-ID: <87r3862z69.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <6fa984a3-83e4-3ea5-8841-88b2db197ebc@mind.be> (Arnout Vandecappelle's message of "Mon, 26 Sep 2016 12:21:02 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>> Sorry for having missed that one ! Sadly, the same problem will occur
>> with my patch.
>> I have currently no idea how to solve that and still trying to figure
>> out how it can works on debian systems with libi2c-dev package installed.
>> So meanwhile you can forget about my patch.
> I guess Debian doesn't have packages that include both i2c.h and i2c-dev.h.
> libsoc, for example, doesn't exist in Debian.
> I guess the solution would be for i2c-tools to #include or #include_next the
> relevant kernel headers, instead of redefining. Or to have both i2c.h and
> i2c-dev.h so that both kernel headers end up being overwritten.
Does the i2c-tools version of this file add anything important on top of
the Linux headers? The i2c /dev interface afaik hasn't changed in MANY
years.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-09-26 20:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 14:06 [Buildroot] [PATCH] i2c-tools: install devt headers to staging dir julien.boibessot at free.fr
2016-09-23 21:18 ` Arnout Vandecappelle
2016-09-26 20:19 ` Peter Korsgaard
2016-09-24 14:18 ` Thomas Petazzoni
2016-09-26 8:56 ` Julien Boibessot
2016-09-26 10:21 ` Arnout Vandecappelle
2016-09-26 20:17 ` Peter Korsgaard [this message]
2016-09-27 3:57 ` Baruch Siach
2016-09-28 8:24 ` Julien Boibessot
2016-09-28 8:52 ` Peter Korsgaard
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=87r3862z69.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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