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: Wed, 3 Aug 2011 11:28:19 -0400 [thread overview]
Message-ID: <20110803152819.GK16484@windriver.com> (raw)
In-Reply-To: <20110803053510.GB16141@opensource.wolfsonmicro.com>
[Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change] On 03/08/2011 (Wed 14:35) Mark Brown wrote:
> 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.
As long as commits end up in Linus' tree directly or in one of the
queues that are a part of the linux-next infrastructure, we have good
visibility of any conflicts thanks to Stephen R's work with next.
Paul.
next prev parent reply other threads:[~2011-08-03 15:28 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
2011-08-03 15:28 ` Paul Gortmaker [this message]
-- 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=20110803152819.GK16484@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.