From: Valdis.Kletnieks@vt.edu
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: [RFC 3/7] kconfig/check.sh: prepare for generic check
Date: Tue, 05 Jul 2011 18:37:54 -0400 [thread overview]
Message-ID: <62528.1309905474@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 01 Jul 2011 21:47:35 EDT." <1309571259-15241-4-git-send-email-lacombar@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
On Fri, 01 Jul 2011 21:47:35 EDT, Arnaud Lacombe said:
> diff --git a/scripts/kconfig/check.sh b/scripts/kconfig/check.sh
Can this be check_libs.sh or similar, to better indicate the function?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-07-05 22:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 19:16 [RFC] Kconfig library check merge Arnaud Lacombe
2011-07-01 14:11 ` Michal Marek
2011-07-02 0:33 ` Arnaud Lacombe
2011-07-02 1:47 ` [RFC 0/7] " Arnaud Lacombe
2011-07-02 1:47 ` [RFC 1/7] kconfig/Makefile: add pretty printer for moc(1) Arnaud Lacombe
2011-07-02 1:47 ` [RFC 2/7] kconfig/Makefile: ensure `conf' appears last in `hostprogs-y' Arnaud Lacombe
2011-07-02 1:47 ` [RFC 3/7] kconfig/check.sh: prepare for generic check Arnaud Lacombe
2011-07-05 22:37 ` Valdis.Kletnieks [this message]
2011-07-05 22:48 ` Arnaud Lacombe
2011-07-02 1:47 ` [RFC 4/7] kconfig: move QT checks to `scripts/kconfig/check.sh' Arnaud Lacombe
2011-07-02 1:47 ` [RFC 5/7] kconfig: move GTK " Arnaud Lacombe
2011-07-02 1:47 ` [RFC 6/7] kconfig: move ncurses " Arnaud Lacombe
2011-07-02 1:47 ` [RFC 7/7] kconfig: add stub for nconf checks Arnaud Lacombe
2011-07-18 19:03 ` [RFC 0/7] Kconfig library check merge Arnaud Lacombe
2011-07-19 13:06 ` Michal Marek
2011-08-16 5:29 ` Arnaud Lacombe
2011-08-19 14:02 ` Michal Marek
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=62528.1309905474@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®