From: "Zhao\, Gang" <gamerh2o@gmail.com>
To: Michal Marek <michal.marek@matfyz.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kyungsik Lee <kyungsik.lee@lge.com>,
Markus Trippelsdorf <markus@trippelsdorf.de>
Subject: Re: [PATCH] .gitignore: ignore Module.symvers in all directories
Date: Thu, 17 Apr 2014 17:17:16 +0800 [thread overview]
Message-ID: <87eh0wz55v.fsf@gmail.com> (raw)
In-Reply-To: <20140416210826.GA20810@fiji.localdomain> (Michal Marek's message of "Wed, 16 Apr 2014 23:08:26 +0200")
On Wed, 2014-04-16 at 23:08:26 +0200, Michal Marek wrote:
> On Mon, Apr 14, 2014 at 02:56:15PM +0800, Zhao, Gang wrote:
>> When using `make M=/path/to/driver modules` to build a module, file
>> Module.symvers will be created in that directory, so it's better to
>> ignore it in all directories.
>>
>> Slightly reordered, let specific file names behind general ones.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Kyungsik Lee <kyungsik.lee@lge.com>
>> Cc: Markus Trippelsdorf <markus@trippelsdorf.de>
>> Signed-off-by: Zhao, Gang <gamerh2o@gmail.com>
>
> Note that the easier way to build a subtree of the kernel source is
>
> make path/to/driver/
>
Thanks for pointing out this.
> including the trailing /. But the M=... syntax seems so widespread that
> I have to apply this.
>
The M=... syntax is the first I learned to build a module. I think it's
popular because one can build out of tree drivers by using it(adding
C=...). As you said, it's better to use `make path/to/driver/` to build
in-tree drivers.
> BTW: there is really no need to CC the last N people who touched
> such a trivial file :).
>
./scripts/get_maintainer.pl doesn't return the maintainer of this
file. Maybe you can add this file to MAINTAINERS(telling you are the
maintainer), but it's really so trivial. :-)
> Michal
prev parent reply other threads:[~2014-04-17 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 6:56 [PATCH] .gitignore: ignore Module.symvers in all directories Zhao, Gang
2014-04-16 21:08 ` Michal Marek
2014-04-17 9:17 ` Zhao, Gang [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=87eh0wz55v.fsf@gmail.com \
--to=gamerh2o@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kyungsik.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=michal.marek@matfyz.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