From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Gortmaker <paul.gortmaker@windriver.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: Wed, 3 Aug 2011 14:35:11 +0900 [thread overview]
Message-ID: <20110803053510.GB16141@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110802043853.GH11811@windriver.com>
On Tue, Aug 02, 2011 at 12:38:54AM -0400, Paul Gortmaker wrote:
> 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
I'm not worried, I'm now perfectly aware of the source of the breakage.
My goal is to make sure that you're aware that there are other patches
for this stuff that have been submitted separately which you're likely
to collide with if you're fixing these issues yourself.
next prev parent reply other threads:[~2011-08-03 5:35 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
2011-08-03 5:35 ` Mark Brown [this message]
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=20110803053510.GB16141@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox