linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jody McIntyre <scjody@modernduck.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux1394-user@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ieee1394: allow building with absolute SUBDIRS path
Date: Tue, 31 Jan 2006 00:21:01 -0500	[thread overview]
Message-ID: <20060131052101.GC9667@conscoop.ottawa.on.ca> (raw)
In-Reply-To: <1138234743.10202.3.camel@localhost>

On Thu, Jan 26, 2006 at 01:19:03AM +0100, Johannes Berg wrote:
> This patch allows building the modules with an absolute SUBDIRS path,
> especially for building them out of tree.

Applied, thanks.

Does anyone else feel like killing oui.c?

> Signed-Off-By: Johannes Berg <johannes@sipsolutions.net>

Minor nit: This should be Signed-off-by:

I doubt anyone cares :)

Cheers,
Jody

> 
> --- a/drivers/ieee1394/Makefile
> +++ b/drivers/ieee1394/Makefile
> @@ -18,7 +19,7 @@ obj-$(CONFIG_IEEE1394_AMDTP) += amdtp.o
>  obj-$(CONFIG_IEEE1394_CMP) += cmp.o
>  
>  quiet_cmd_oui2c = OUI2C   $@
> -      cmd_oui2c = $(CONFIG_SHELL) $(srctree)/$(src)/oui2c.sh < $< > $@
> +      cmd_oui2c = $(CONFIG_SHELL) $(src)/oui2c.sh < $< > $@
>  
>  targets := oui.c
>  $(obj)/oui.o: $(obj)/oui.c
> 



-- 

  parent reply	other threads:[~2006-01-31  5:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26  0:19 [PATCH] ieee1394: allow building with absolute SUBDIRS path Johannes Berg
2006-01-26 22:28 ` Stefan Richter
2006-01-27 11:31   ` Johannes Berg
2006-01-31  5:21 ` Jody McIntyre [this message]
2006-01-31 20:19   ` ieee1394/oui.db (was Re: [PATCH] ieee1394: allow building with absolute SUBDIRS path) Stefan Richter
2006-02-04  4:08     ` Jody McIntyre
     [not found]     ` <1138739715.4456.302.camel@grayson>
2006-02-04  8:54       ` Stefan Richter

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=20060131052101.GC9667@conscoop.ottawa.on.ca \
    --to=scjody@modernduck.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-user@lists.sourceforge.net \
    /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).