From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/brltty: avoid spurious log messages while decoding scancodes
Date: Fri, 29 Dec 2017 21:56:58 +0100 [thread overview]
Message-ID: <20171229215658.5f288a24@windsurf.lan> (raw)
In-Reply-To: <20171229140641.13882-1-mlang@blind.guru>
Hello,
On Fri, 29 Dec 2017 15:06:40 +0100, Mario Lang wrote:
> +++ b/package/brltty/5.5/0001-Prevent-scancodes-from-generating-spurious-log-messa.patch
This patch shouldn't have been in the 5.5/ sub-folder. Indeed, using
per-version sub-directories for patches is only useful for packages
that support multiple versions, which isn't the case of brltty.
So I've moved the patch in package/brltty/ and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-29 20:56 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
2017-12-29 20:56 ` Thomas Petazzoni [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=20171229215658.5f288a24@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