linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Michal Marek <mmarek@suse.com>, <linux-kernel@vger.kernel.org>,
	<linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] staging: drop kbuild workaround dummy module from top dir
Date: Wed, 9 Dec 2015 16:06:10 -0500	[thread overview]
Message-ID: <20151209210609.GR22885@windriver.com> (raw)
In-Reply-To: <20151118175330.GA5988@kroah.com>

[Re: [PATCH] staging: drop kbuild workaround dummy module from top dir] On 18/11/2015 (Wed 09:53) Greg Kroah-Hartman wrote:

> On Wed, Nov 18, 2015 at 06:45:11PM +0100, Michal Marek wrote:
> > Dne 17.11.2015 v 01:58 Paul Gortmaker napsal(a):
> > > This is essentially a revert of 86f69fe9c069dd8608d238581eea259caa1dfc99
> > > ("Staging: workaround build system bug"), but to call it a revert would
> > > imply it was wrong -- rather it seems more like it is just no longer
> > > required anymore.
> > 
> > Acked-by: Michal Marek <mmarek@suse.com>
> > 
> > In fact, I can't even reproduce the original bug with 2.6.27 + the
> > initial staging series. I also do not remember any fix for such bug in
> > the recent years. 4b024242e8a4 ("kbuild: Fix linking error built-in.o no
> > such file or directory") is related, but fixing a different problem.
> 
> I can't remember the issue at the moment either, but it was a problem
> with some sort of config, I'll queue this up and see if anything breaks
> :)

Did you detect any fallout?  Just wondering since I didn't see it loop
around in linux-next via staging #staging-next yet...

Thanks,
Paul.
--

> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2015-12-09 21:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  0:58 [PATCH] staging: drop kbuild workaround dummy module from top dir Paul Gortmaker
2015-11-18 17:45 ` Michal Marek
2015-11-18 17:53   ` Greg Kroah-Hartman
2015-12-09 21:06     ` Paul Gortmaker [this message]
2016-02-08  2:40       ` Greg Kroah-Hartman

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=20151209210609.GR22885@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.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).