mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: colin@colino.net, benh@kernel.crashing.org,
	linux-kernel@vger.kernel.org, debian-powerpc@lists.debian.org,
	torvalds@osdl.org
Subject: Re: 2.6.12-rc3 cpufreq compile error on ppc32
Date: Fri, 29 Apr 2005 06:26:04 -0700	[thread overview]
Message-ID: <20050429062604.536cb193.akpm@osdl.org> (raw)
In-Reply-To: <20050429131519.GA6158@infradead.org>

Christoph Hellwig <hch@infradead.org> wrote:
>
> On Mon, Apr 25, 2005 at 10:20:39PM +0200, Colin Leroy wrote:
>  > > > One of Ben's patches ("ppc32: Fix cpufreq problems") went in 2.6.12-
>  > > > rc3, but it depended on another patch that's still in -mm only: 
>  > > > add-suspend-method-to-cpufreq-core.patch
>  > > > 
>  > > > In addition to this, there's a third patch in -mm that fixes
>  > > > warnings and line length to the previous patch, but it doesn't
>  > > > apply cleanly anymore. It's named add-suspend-method-to-cpufreq-
>  > > > core-warning-fix.patch
>  > > 
>  > > Yup, please, Andrew, get those 2 to Linus.
>  > 
>  > Just a heads-up : I didn't see these go into the git tree?
> 
>  still not in.  Linus, can you please put in the patch below from benh?
> 
> 
>  Index: linux-work/drivers/cpufreq/cpufreq.c

This patch is missing a warning fix.  I'll send the correct one.

      reply	other threads:[~2005-04-29 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21  7:26 Colin Leroy
2005-04-22  0:17 ` Benjamin Herrenschmidt
2005-04-25 20:20   ` Colin Leroy
2005-04-29 13:15     ` Christoph Hellwig
2005-04-29 13:26       ` Andrew Morton [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=20050429062604.536cb193.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=colin@colino.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®