From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 0/5] kbuild: Clean-up and bug fixes of scripts/Makefile.host
Date: Fri, 6 Jun 2014 15:25:54 +0200 [thread overview]
Message-ID: <20140606132553.GA4961@ravnborg.org> (raw)
In-Reply-To: <1402018263-30670-1-git-send-email-yamada.m@jp.panasonic.com>
On Fri, Jun 06, 2014 at 10:30:58AM +0900, Masahiro Yamada wrote:
>
> Masahiro Yamada (5):
> kbuild: fix a typo in scripts/Makefile.host
> kbuild: fix a bug of C++ host program handling
> kbuild: clean up scripts/Makefile.host
> kbuild: clean-up and bug fix of scripts/Makefile.host
> kbuild: create directory of .o files from shlib-objs notation
All bug-fixes looks good.
But rahter than fixing this please consider if
we can drop the features.
The shlib stuff is for example no longer used and should be deleted.
Do we have any host progrs where we need to create directories as
is fixed in these patches?
If not then rip it out too.
Anthing that can make all this simpler is good.
Sam
next prev parent reply other threads:[~2014-06-06 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:30 [PATCH 0/5] kbuild: Clean-up and bug fixes of scripts/Makefile.host Masahiro Yamada
2014-06-06 1:30 ` [PATCH 1/5] kbuild: fix a typo in scripts/Makefile.host Masahiro Yamada
2014-06-06 1:31 ` [PATCH 2/5] kbuild: fix a bug of C++ host program handling Masahiro Yamada
2014-06-06 1:31 ` [PATCH 3/5] kbuild: clean up scripts/Makefile.host Masahiro Yamada
2014-06-06 1:31 ` [PATCH 4/5] kbuild: clean-up and bug fix of scripts/Makefile.host Masahiro Yamada
2014-06-06 1:31 ` [PATCH 5/5] kbuild: create directory of .o files from shlib-objs notation Masahiro Yamada
2014-06-06 13:25 ` Sam Ravnborg [this message]
2014-06-09 4:29 ` [PATCH 0/5] kbuild: Clean-up and bug fixes of scripts/Makefile.host Masahiro Yamada
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=20140606132553.GA4961@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.m@jp.panasonic.com \
/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