From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Dave Jones <davej@redhat.com>, <linux-kernel@vger.kernel.org>,
<patches@opensource.wolfsonmicro.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change
Date: Tue, 2 Aug 2011 00:38:54 -0400 [thread overview]
Message-ID: <20110802043853.GH11811@windriver.com> (raw)
In-Reply-To: <20110801002933.GB20641@opensource.wolfsonmicro.com>
[Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change] On 01/08/2011 (Mon 09:29) Mark Brown wrote:
> On Sat, Jul 30, 2011 at 01:44:25PM -0400, Paul Gortmaker wrote:
> > On 11-07-29 11:19 AM, Mark Brown wrote:
>
> > > Some header change has removed an implicit include of module.h, breaking
> > > the build due to the use of THIS_MODULE. Fix that.
>
> > Thanks, I'll apply it to the module.h cleanup branch that is soaking
> > in linux-next.
>
> There's a bunch of other changes fixing issues with this floating around
> - Randy Dunlap sent something for a regulator driver the other day and
> I've got a couple of other Samsung patches I sent on the basis that this
> must have been caused by a change in the Samsung headers.
It is all taken care of, so you don't have to worry. It isn't a change
specific to any Samsung headers. If you are interested to know the
background of what is being changed and why, this is a good start.
https://lkml.org/lkml/2011/5/27/459
https://lkml.org/lkml/2011/7/28/12
Thanks,
Paul.
next prev parent reply other threads:[~2011-08-02 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:19 [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change Mark Brown
2011-07-30 17:44 ` Paul Gortmaker
2011-08-01 0:29 ` Mark Brown
2011-08-02 4:38 ` Paul Gortmaker [this message]
2011-08-03 5:35 ` Mark Brown
2011-08-03 15:28 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2011-07-29 14:26 Mark Brown
2011-07-29 14:48 ` Dave Jones
2011-07-29 15:01 ` Mark Brown
2011-07-29 15:08 ` Dave Jones
2011-07-29 15:13 ` Mark Brown
2011-07-29 15:16 ` Dave Jones
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=20110802043853.GH11811@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rdunlap@xenotime.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 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.