From: Peter Foley <pefoley2@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c
Date: Fri, 29 Apr 2011 18:38:12 -0400 [thread overview]
Message-ID: <4DBB3DD4.9000000@verizon.net> (raw)
This patchset moves scripts/basic/docproc to scripts/docproc.
This causes docproc to only be built for *doc targets rather than every
time the kernel is compiled.
Patches also attached as requested by Michal Marek.
Thanks,
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Foley <pefoley2@verizon.net>
To: <linux-kernel@vger.kernel.org>
Cc: <linux-kbuild@vger.kernel.org>, Michal Marek <mmarek@suse.cz>
Subject: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c
Date: Fri, 29 Apr 2011 18:38:12 -0400 [thread overview]
Message-ID: <4DBB3DD4.9000000@verizon.net> (raw)
This patchset moves scripts/basic/docproc to scripts/docproc.
This causes docproc to only be built for *doc targets rather than every
time the kernel is compiled.
Patches also attached as requested by Michal Marek.
Thanks,
Peter
next reply other threads:[~2011-04-29 22:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:38 Peter Foley [this message]
2011-04-29 22:38 ` [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c Peter Foley
2011-04-29 22:46 ` Randy Dunlap
2011-04-29 22:46 ` Randy Dunlap
2011-04-29 23:00 ` Michal Marek
2011-04-29 23:02 ` Randy Dunlap
2011-04-29 23:15 ` Peter Foley
2011-04-29 23:15 ` Peter Foley
2011-04-29 23:09 ` Peter Foley
2011-04-29 23:09 ` Peter Foley
2011-04-29 23:18 ` Randy Dunlap
2011-04-29 23:18 ` Randy Dunlap
2011-04-30 0:30 ` Peter Foley
2011-04-30 0:30 ` Peter Foley
2011-04-29 23:22 ` Arnaud Lacombe
2011-04-29 22:59 ` Randy Dunlap
2011-04-29 22:59 ` Randy Dunlap
2011-04-29 23:00 ` Randy Dunlap
2011-04-29 23:00 ` Randy Dunlap
2011-04-29 23:04 ` Randy Dunlap
2011-04-29 23:04 ` Randy Dunlap
2011-05-02 20:55 ` 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=4DBB3DD4.9000000@verizon.net \
--to=pefoley2@verizon.net \
--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 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.