From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] spidev_test: use the one from the kernel we build
Date: Mon, 13 Jul 2015 01:31:10 +0200 [thread overview]
Message-ID: <55A2F8BE.6020508@mind.be> (raw)
In-Reply-To: <1421696137-17377-1-git-send-email-vincent.stehle@freescale.com>
Hi Vincent,
We're doing a big patchwork cleanup and finally getting back at your patch.
On 01/19/15 20:35, Vincent Stehl? wrote:
> Add a configuration option to use the spidev_test.c from the Linux kernel we
> build. This allows to be perfectly consistent between spidev_test and the
> kernel in use.
The conclusion of the earlier discussion is that spidev_test should really only
be built together with the kernel, so you could remove the extra config option.
Note, if you do that, there may be a need for legacy handling otherwise a
.config which previously had SPIDEV_TEST but no kernel would suddenly loose the
SPIDEV_TEST.
However, there is also the new kernel-tools infra proposed by Romain, and this
change would fit into that approach perfectly. So if you resubmit, consider
using the kernel-tools infra.
Regards,
Arnout
>
> Signed-off-by: Vincent Stehl? <vincent.stehle@freescale.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-07-12 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 19:35 [Buildroot] [PATCH] spidev_test: use the one from the kernel we build Vincent Stehlé
2015-01-19 21:13 ` Yann E. MORIN
2015-01-19 21:32 ` Yann E. MORIN
2015-01-20 9:02 ` Vincent Stehlé
2015-07-12 23:31 ` Arnout Vandecappelle [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=55A2F8BE.6020508@mind.be \
--to=arnout@mind.be \
--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.