All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: mmarek@suse.com, linux-kbuild@vger.kernel.org,
	ming.lei@canonical.com, gregkh@linuxfoundation.org, teg@jklm.no,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: [PATCH v2] firmware/Makefile: force recompilation if makefile changes
Date: Tue, 14 Feb 2017 20:34:15 +0100	[thread overview]
Message-ID: <20170214193415.GY24047@wotan.suse.de> (raw)
In-Reply-To: <20170206220352.GB24047@wotan.suse.de>

On Mon, Feb 06, 2017 at 11:03:52PM +0100, Luis R. Rodriguez wrote:
> On Mon, Jan 23, 2017 at 07:07:27AM -0800, Luis R. Rodriguez wrote:
> > If you modify the target asm we currently do not force the
> > recompilation of the firmware files. The target asm is in
> > the firmware/Makefile, peg this file as a dependency to
> > require re-compilation of firmware targets when the asm
> > changes.
> > 
> > Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
> > ---
> > 
> > Michal,
> > 
> > I had this patch as part of my linker table series [0] but have split it
> > off as its a small atomic separate change and can go in separately. Greg
> > prefers this be reviewed by the kbuild tree so sending it your way.
> > This v2 has no modifications, just resending it to the kbuild tree.
> > 
> > [0] https://lkml.kernel.org/r/20170115211057.17167-1-mcgrof@kernel.org
> 
> *Poke*

*Re-poke*

 Luis

  reply	other threads:[~2017-02-14 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 17:31 [PATCH] firmware/Makefile: force recompilation if makefile changes Luis R. Rodriguez
2017-01-19 10:15 ` Greg KH
2017-01-23 14:59   ` Luis R. Rodriguez
2017-01-23 15:02     ` Greg KH
2017-01-23 15:04       ` Luis R. Rodriguez
2017-01-23 15:07 ` [PATCH v2] " Luis R. Rodriguez
2017-02-06 22:03   ` Luis R. Rodriguez
2017-02-14 19:34     ` Luis R. Rodriguez [this message]
2017-02-21 19:38       ` Luis R. Rodriguez
2017-03-11  5:37   ` Masahiro Yamada
2017-03-15  0:53     ` Luis R. Rodriguez
2017-03-16 17:43       ` Masahiro Yamada
2017-03-16 17:55         ` Luis R. Rodriguez
2017-03-18 13:32           ` Masahiro Yamada

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=20170214193415.GY24047@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=mmarek@suse.com \
    --cc=teg@jklm.no \
    /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.