All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tslib: needs kernel headers 3.12
Date: Fri, 20 Jan 2017 05:35:51 +0200	[thread overview]
Message-ID: <20170120033551.4cpamcz63irneymp@tarshish> (raw)
In-Reply-To: <20170120112630.557f297d@free-electrons.com>

Hi Thomas,

On Fri, Jan 20, 2017 at 11:26:30AM +1100, Thomas Petazzoni wrote:
> On Thu, 19 Jan 2017 14:50:47 +0200, Baruch Siach wrote:
> > Kernel headers 3.12+ are required since tslib version 1.3.
> > 
> > https://github.com/kergoth/tslib/blob/master/README.markdown
> > 
> > Update tslib reverse dependencies.
> > 
> > Fixes:
> > http://autobuild.buildroot.net/results/28d/28df38e2a042f1b5940bf35c18334ebf8810a348/
> > http://autobuild.buildroot.net/results/c38/c383cfee3673aa9fba36a86f1e68de63413c2987/
> > http://autobuild.buildroot.net/results/6dd/6ddb2cd9f4f41ee03dc10a73422ad37070811732/
> > 
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> 
> Isn't this a bit annoying for people using tslib on kernel olders than
> 3.12 ? Isn't there a simpler patch to tslib to avoid depending on
> headers >= 3.12 ?

The present build failure seems to be easy to fix by skipping the ts_uinput 
tool on pre 3.12 kernels. But since upstream explicitly states that 3.12 is 
the oldest supported kernel (see commit message link) we are on our own here.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  reply	other threads:[~2017-01-20  3:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 12:50 [Buildroot] [PATCH] tslib: needs kernel headers 3.12 Baruch Siach
2017-01-19 14:03 ` Peter Korsgaard
2017-01-20  0:26 ` Thomas Petazzoni
2017-01-20  3:35   ` Baruch Siach [this message]
2017-01-20 13:46     ` Peter Korsgaard
2017-01-25  9:24       ` Martin Kepplinger

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=20170120033551.4cpamcz63irneymp@tarshish \
    --to=baruch@tkos.co.il \
    --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 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.