linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: stfrench@microsoft.com, linux-cifs@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: cifs: Fix tracing build error with O=
Date: Thu, 20 Jun 2019 21:36:16 +0800	[thread overview]
Message-ID: <20190620133616.dajrd37b73k3v3kx@gondor.apana.org.au> (raw)
In-Reply-To: <CAK7LNAQrdkUYzDVEf5SERiNVquAyEjTrTL3tqw=1VGq=yumYUw@mail.gmail.com>

On Thu, Jun 20, 2019 at 09:56:53PM +0900, Masahiro Yamada wrote:
>
> > But it doesn't work with O=:
> >
> > $ rm -rf build-compile/fs/cifs
> > $ make O=build-compile fs/cifs
> > make[1]: Entering directory '/home/herbert/src/build/kernel/test/build-compile'
> > make[1]: Nothing to be done for '../fs/cifs'.
> > make[1]: Leaving directory '/home/herbert/src/build/kernel/test/build-compile'
> > $
> 
> You missed the trailing slash.
> 
> I suggested 'fs/cifs/' instead of 'fs/cifs'

Aha, that indeed works.  Thanks!
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2019-06-20 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  6:40 cifs: Fix tracing build error with O= Herbert Xu
2019-06-20  6:54 ` yamada.masahiro
2019-06-20  7:58   ` Herbert Xu
2019-06-20 11:56     ` Masahiro Yamada
2019-06-20 12:47       ` Herbert Xu
2019-06-20 12:56         ` Masahiro Yamada
2019-06-20 13:36           ` Herbert Xu [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=20190620133616.dajrd37b73k3v3kx@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=hch@lst.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stfrench@microsoft.com \
    --cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).