From: Steven Rostedt <rostedt@goodmis.org>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
yann.morin.1998@free.fr, artafinde@gmail.com,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] localmodconfig: Use Kbuild files too
Date: Mon, 10 Aug 2015 10:58:08 -0400 [thread overview]
Message-ID: <20150810105808.6571df03@gandalf.local.home> (raw)
In-Reply-To: <CAFLxGvzT11zSu2YDO5Hqr4se0icp=K1MGKhhGZgubVQbu55=mw@mail.gmail.com>
On Sat, 8 Aug 2015 14:47:32 +0200
Richard Weinberger <richard.weinberger@gmail.com> wrote:
> On Mon, Jul 27, 2015 at 12:06 AM, Richard Weinberger <richard@nod.at> wrote:
> > In kbuild it is allowed to define objects in files named "Makefile"
> > and "Kbuild".
> > Currently localmodconfig reads objects only from "Makefile"s and misses
> > modules like nouveau.
> >
> > Reported-and-tested-by: Leonidas Spyropoulos <artafinde@gmail.com>
> > Signed-off-by: Richard Weinberger <richard@nod.at>
> > ---
> > scripts/kconfig/streamline_config.pl | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/kconfig/streamline_config.pl b/scripts/kconfig/streamline_config.pl
> > index 9cb8522..f3d3fb4 100755
> > --- a/scripts/kconfig/streamline_config.pl
> > +++ b/scripts/kconfig/streamline_config.pl
> > @@ -137,7 +137,7 @@ my $ksource = ($ARGV[0] ? $ARGV[0] : '.');
> > my $kconfig = $ARGV[1];
> > my $lsmod_file = $ENV{'LSMOD'};
> >
> > -my @makefiles = `find $ksource -name Makefile 2>/dev/null`;
> > +my @makefiles = `find $ksource -name Makefile -or -name Kbuild 2>/dev/null`;
> > chomp @makefiles;
> >
> > my %depends;
> > --
>
> Ping?
>
Thanks, I'll take a look at this today.
-- Steve
prev parent reply other threads:[~2015-08-10 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 22:06 [PATCH] localmodconfig: Use Kbuild files too Richard Weinberger
2015-08-08 12:47 ` Richard Weinberger
2015-08-10 14:58 ` Steven Rostedt [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=20150810105808.6571df03@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=artafinde@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).