From: Christoph Hellwig <hch@lst.de>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] target: Fix tcm_mod_builder.py default EXTRA_CFLAGS
Date: Tue, 18 Jan 2011 22:47:26 +0100 [thread overview]
Message-ID: <20110118214726.GA13329@lst.de> (raw)
In-Reply-To: <1295387162.22813.454.camel@haakon2.linux-iscsi.org>
On Tue, Jan 18, 2011 at 01:46:02PM -0800, Nicholas A. Bellinger wrote:
> This is correct on the -I$(srctree)/include/, and I will drop this as
> well.. However with the current fabric module include layout (all .h
> living in drivers/target/$FABRIC_MOD), the latter bit is still required
> AFAICS to build.
No, there's no need. Just use ""-style includes and they'll always get
picked up in the local directory.
next prev parent reply other threads:[~2011-01-18 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 21:30 [PATCH] target: Fix tcm_mod_builder.py default EXTRA_CFLAGS Nicholas A. Bellinger
2011-01-18 21:36 ` Christoph Hellwig
2011-01-18 21:46 ` Nicholas A. Bellinger
2011-01-18 21:47 ` Christoph Hellwig [this message]
2011-01-18 22:03 ` Nicholas A. Bellinger
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=20110118214726.GA13329@lst.de \
--to=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
/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