mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/jfs: fix error due to PF_* undeclared
Date: Fri, 08 Dec 2006 15:59:01 -0600	[thread overview]
Message-ID: <1165615141.8575.7.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <4579D941.9040607@student.ltu.se>

On Fri, 2006-12-08 at 22:29 +0100, Richard Knutsson wrote:
> Randy Dunlap wrote:
> > On Fri, 08 Dec 2006 19:56:20 +0100 Richard Knutsson wrote:

> >> Guess this is the desired fix, since including linux/sched.h in linux/freezer.h
> >> make little sense.
> >>     
> >
> > Why do you say that?  freezer.h is what uses those #defined values,
> > and freezer.h is what uses struct task_struct fields as well,
> > so it needs sched.h.
> >   
> Oh, an error of thought when I read the patch 
> 7dfb71030f7636a0d65200158113c37764552f93 made that statement. After more 
> checking, sched.h is apperarently included in suspend.h from swap.h so 
> the direct include of sched.h in most drivers was/is not nessecary.
> 
> Do you agree with the patch below then? This was how I first fixed it 
> but found it strange no-one hit it before, and from there it went on... 
> Thanks for the help. (Sign it?)

Randy had already submitted a similar patch to lkml.

http://marc.theaimsgroup.com/?l=linux-kernel&m=116561219801397&w=2

> ---
> 
> Compile-tested only.
> 
> 
> diff --git a/include/linux/freezer.h b/include/linux/freezer.h
> index 6e05e3e..f616c0c 100644
> --- a/include/linux/freezer.h
> +++ b/include/linux/freezer.h
> @@ -1,3 +1,4 @@
> +#include <linux/sched.h>
>  /* Freezer declarations */
> 
>  #ifdef CONFIG_PM

Thanks anyway,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2006-12-08 21:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 22:21 Linux 2.6.19 Linus Torvalds
2006-11-29 22:55 ` Romano Giannetti
2006-11-29 23:11 ` Randy Dunlap
2006-11-29 23:21   ` Alan
2006-11-29 23:15     ` Randy Dunlap
2006-11-29 23:25       ` Geraldo Netto
2006-11-29 23:32         ` Randy Dunlap
2006-11-29 23:31       ` Geraldo Netto
2006-11-29 23:52       ` Linus Torvalds
2006-11-30  0:56   ` Greg Norris
2006-11-30  1:08     ` Randy Dunlap
2006-11-30  2:20       ` Greg Norris
2006-11-30  1:49     ` Phil Oester
2006-11-30  2:15       ` David Miller
2006-11-30  2:22         ` Phil Oester
2006-11-30 20:30         ` Malte Schröder
2006-12-02  9:48           ` Malte Schröder
2006-11-30  0:26 ` Udo A. Steinberg
2006-11-30 21:15   ` Herbert Xu
2006-11-30 22:32     ` Udo A. Steinberg
2006-11-30 23:51       ` Herbert Xu
2006-11-30  8:01 ` Jindrich Makovicka
2006-12-02 19:54 ` Matthijs
2006-12-08 18:56 ` [PATCH] fs/jfs: fix error due to PF_* undeclared Richard Knutsson
2006-12-08 19:23   ` Randy Dunlap
2006-12-08 21:29     ` Richard Knutsson
2006-12-08 21:59       ` Dave Kleikamp [this message]
2006-12-11 14:47 ` Linux 2.6.19 Romano Giannetti
2006-12-11 20:38   ` Dominik Brodowski

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=1165615141.8575.7.camel@kleikamp.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=ricknu-0@student.ltu.se \
    --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®