From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
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: Sun, 7 Feb 2016 18:40:24 -0800 [thread overview]
Message-ID: <20160208024024.GA14842@kroah.com> (raw)
In-Reply-To: <20151209210609.GR22885@windriver.com>
On Wed, Dec 09, 2015 at 04:06:10PM -0500, Paul Gortmaker wrote:
> [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...
Sorry, it now just got applied, got way behind on patches :(
prev parent reply other threads:[~2016-02-08 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 0:58 Paul Gortmaker
2015-11-18 17:45 ` Michal Marek
2015-11-18 17:53 ` Greg Kroah-Hartman
2015-12-09 21:06 ` Paul Gortmaker
2016-02-08 2:40 ` Greg Kroah-Hartman [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=20160208024024.GA14842@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=paul.gortmaker@windriver.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
Powered by JetHome