From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Joe Perches <joe@perches.com>
Cc: Peter H?we <PeterHuewe@gmx.de>,
tpmdd-devel@lists.sourceforge.net,
Ashley Lai <ashley@ashleylai.com>,
Leonidas Da Silva Barbosa <leosilva@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Rajiv Andrade <mail@srajiv.net>,
Sirrix AG <tpmdd@sirrix.com>
Subject: Re: [PATCH 1/2] tpm: Rename tpm.c to tpm-interface.c
Date: Sun, 6 Oct 2013 14:15:29 -0600 [thread overview]
Message-ID: <20131006201529.GA10426@obsidianresearch.com> (raw)
In-Reply-To: <1381089202.2081.157.camel@joe-AO722>
On Sun, Oct 06, 2013 at 12:53:22PM -0700, Joe Perches wrote:
> On Sun, 2013-10-06 at 13:38 -0600, Jason Gunthorpe wrote:
> > This is preparation for making the tpm module multi-file. kbuild does
> > not like having a .c file with the same name as a module. We wish to
> > keep the tpm module name so that userspace doesn't see this change.
>
> If that's true, and I don't believe it is,
> then Kbuild should be fixed instead.
>
> There are a lot of examples of .c files named
> the same as the directory they reside in.
That isn't the trouble, it is having a module named tpm, comprised of
tpm.c, tpm-foo.c, and tpm-bar.c
The issue is that assembling the tpm module uses tpm.o as an
intermediate file, and compiling tmp.c uses tpm.o as a intermediate
file - they conflict, things don't work right and make throws a
circular dependency warning.
The Makefile I started with looks like this:
obj-m += tpm.o
tpm-y := tpm.o tpm-foo.o tpm-bar.o
Is there some other solution?
In any event, this patch is part of a series that splits tpm.c up,
renaming it at this point in the series is to make kbuild work, but
at the end of the series it should be renamed anyhow :)
Regards,
Jason
prev parent reply other threads:[~2013-10-06 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 19:38 [PATCH 1/2] tpm: Rename tpm.c to tpm-interface.c Jason Gunthorpe
2013-10-06 19:53 ` Joe Perches
2013-10-06 20:15 ` Jason Gunthorpe [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=20131006201529.GA10426@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=PeterHuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=joe@perches.com \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@srajiv.net \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@sirrix.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