From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/brltty: explicitly check if ioperm is available
Date: Fri, 29 Dec 2017 21:59:03 +0100 [thread overview]
Message-ID: <20171229215903.15ae85a3@windsurf.lan> (raw)
In-Reply-To: <20171229140641.13882-2-mlang@blind.guru>
Hello,
On Fri, 29 Dec 2017 15:06:41 +0100, Mario Lang wrote:
> ioperm, inb and outb are i386 specific functions usually
> not available on non-PC archs. Check if ioperm is available before
> trying to use it.
>
> Patch cherry-picked from upstream, can be removed when 5.6 is out.
>
> Fixes:
> http://autobuild.buildroot.net/results/f09974f2ba24319e55e578ece34bb2e7e8bb3c43
> http://autobuild.buildroot.net/results/7d502f280c46f0d1e2678140f9117fcc59bc2d7b
> Signed-off-by: Mario Lang <mlang@blind.guru>
> ---
> v2 fixes commit message and adds forgotten dependency on host-autoconf.
Like for PATCH 1/2, I've moved the patch back into package/brltty/,
since a per-version sub-directory is not needed. I've also added a
comment in the .mk file about why we're doing autoconf, and not an
autoreconf.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-29 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 14:06 [Buildroot] [PATCH v2 1/2] package/brltty: avoid spurious log messages while decoding scancodes Mario Lang
2017-12-29 14:06 ` [Buildroot] [PATCH v2 2/2] package/brltty: explicitly check if ioperm is available Mario Lang
2017-12-29 16:19 ` Thomas Petazzoni
2017-12-29 19:22 ` Mario Lang
2017-12-29 19:54 ` Thomas Petazzoni
2017-12-29 20:59 ` Thomas Petazzoni [this message]
2017-12-29 20:56 ` [Buildroot] [PATCH v2 1/2] package/brltty: avoid spurious log messages while decoding scancodes Thomas Petazzoni
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=20171229215903.15ae85a3@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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