All of lore.kernel.org
 help / color / mirror / Atom feed
From: matt mooney <mfm@muteddisk.com>
To: T Dent <tdent48227@gmail.com>
Cc: matt mooney <mfmooney@gmail.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 00/21] Staging: cleaned up makefiles cflag lines
Date: Fri, 24 Sep 2010 20:51:08 +0000	[thread overview]
Message-ID: <20100924205108.GA8191@haskell.muteddisk.com> (raw)
In-Reply-To: <AANLkTin1YfwwVcDNUBsi34iYC6HA5Y6+uOFZN=+Q2hqs@mail.gmail.com>

On 16:39 Fri 24 Sep     , T Dent wrote:
> On 9/24/10, matt mooney <mfmooney@gmail.com> wrote:
> > On Fri, Sep 24, 2010 at 11:25 AM, T Dent <tdent48227@gmail.com> wrote:
> >> I changed every makefile in the staging directory to use the proper
> >> ccflags-y option instead of EXTRA_CFLAGS. It builds also :) .
> >
> > Um, you didn't do a lot of these right. Maybe you should look into why
> > the change was made in the first place. For semantic reasons, I was
> > also changing the first assignment to ":=" from "+=".
> 
> I can resend them with the a small modification to the patch files if you want.

After looking at more of them, my "a lot" was a little bit of an
overstatement. The first few I randomly looked at happen to use the incorrect
pattern, but most are simple without relying on a variable. Yeah, I think you
should resubmit with a "[PATCH v2]." The pattern is:

ifeq ($(FOO),y)
     EXTRA_CFLAGS := <flags>
endif

changes to:

ccflags-$(FOO) := <flags>

Also, the rest of the kernel tree has been done except drivers/media; however, I
am going to email them in a little bit asking if some consolidation is possible
due to every driver there relying on a few flags. So thanks for the help (though
is was a good thing I was saving staging for last)!

-mfm


WARNING: multiple messages have this Message-ID (diff)
From: matt mooney <mfm@muteddisk.com>
To: T Dent <tdent48227@gmail.com>
Cc: matt mooney <mfmooney@gmail.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 00/21] Staging: cleaned up makefiles cflag lines
Date: Fri, 24 Sep 2010 13:51:08 -0700	[thread overview]
Message-ID: <20100924205108.GA8191@haskell.muteddisk.com> (raw)
In-Reply-To: <AANLkTin1YfwwVcDNUBsi34iYC6HA5Y6+uOFZN=+Q2hqs@mail.gmail.com>

On 16:39 Fri 24 Sep     , T Dent wrote:
> On 9/24/10, matt mooney <mfmooney@gmail.com> wrote:
> > On Fri, Sep 24, 2010 at 11:25 AM, T Dent <tdent48227@gmail.com> wrote:
> >> I changed every makefile in the staging directory to use the proper
> >> ccflags-y option instead of EXTRA_CFLAGS. It builds also :) .
> >
> > Um, you didn't do a lot of these right. Maybe you should look into why
> > the change was made in the first place. For semantic reasons, I was
> > also changing the first assignment to ":=" from "+=".
> 
> I can resend them with the a small modification to the patch files if you want.

After looking at more of them, my "a lot" was a little bit of an
overstatement. The first few I randomly looked at happen to use the incorrect
pattern, but most are simple without relying on a variable. Yeah, I think you
should resubmit with a "[PATCH v2]." The pattern is:

ifeq ($(FOO),y)
     EXTRA_CFLAGS := <flags>
endif

changes to:

ccflags-$(FOO) := <flags>

Also, the rest of the kernel tree has been done except drivers/media; however, I
am going to email them in a little bit asking if some consolidation is possible
due to every driver there relying on a few flags. So thanks for the help (though
is was a good thing I was saving staging for last)!

-mfm


  reply	other threads:[~2010-09-24 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 18:25 [PATCH 00/21] Staging: cleaned up makefiles cflag lines T Dent
2010-09-24 18:25 ` T Dent
2010-09-24 19:31 ` matt mooney
2010-09-24 19:31   ` matt mooney
2010-09-24 20:39   ` T Dent
2010-09-24 20:39     ` T Dent
2010-09-24 20:51     ` matt mooney [this message]
2010-09-24 20:51       ` matt mooney
2010-09-24 21:12       ` T Dent
2010-09-24 21:12         ` T Dent

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=20100924205108.GA8191@haskell.muteddisk.com \
    --to=mfm@muteddisk.com \
    --cc=greg@kroah.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfmooney@gmail.com \
    --cc=tdent48227@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.