From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Daniel Halperin <dhalperi@cs.washington.edu>,
Ingo Molnar <mingo@elte.hu>,
"Guy, Wey-Yi" <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Undefined TASK_INTERRUPTIBLE (Was: Re: [PATCH 1/3] iwlwifi: move rx handlers code to iwl-rx.c)
Date: Mon, 7 Mar 2011 14:12:17 +0100 [thread overview]
Message-ID: <20110307131217.GA9571@redhat.com> (raw)
In-Reply-To: <1299489602.2308.1.camel@twins>
On Mon, Mar 07, 2011 at 10:20:02AM +0100, Peter Zijlstra wrote:
> On Mon, 2011-03-07 at 09:12 +0100, Stanislaw Gruszka wrote:
> >
> > But perhaps we need a more generic fix in wait.h for the future. Maybe
> > we should decouple definitions of TASK_INTERRUPTIBLE and friends from
> > sched.h into separate header and include that header in wait.h as
> > well?
>
> No! That only makes the mess worse, the only sane option is to fix
> things so that wait.h can include sched.h and that is non-trivial.
I was not aware of recent discussion
http://marc.info/?t=129829886000004&r=1&w=2
prev parent reply other threads:[~2011-03-07 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:51 [PATCH 1/3] iwlwifi: move rx handlers code to iwl-rx.c Stanislaw Gruszka
2011-03-04 16:51 ` [PATCH 2/3] iwlwifi: cleanup iwl_good_plcp_health Stanislaw Gruszka
2011-03-04 16:47 ` Guy, Wey-Yi
2011-03-04 16:51 ` [PATCH 3/3] iwlwifi: avoid too frequent recover from statistics Stanislaw Gruszka
2011-03-04 16:46 ` Guy, Wey-Yi
2011-03-04 16:52 ` [PATCH 1/3] iwlwifi: move rx handlers code to iwl-rx.c Guy, Wey-Yi
2011-03-06 21:34 ` Guy, Wey-Yi
2011-03-06 23:47 ` Daniel Halperin
2011-03-07 8:12 ` Undefined TASK_INTERRUPTIBLE (Was: Re: [PATCH 1/3] iwlwifi: move rx handlers code to iwl-rx.c) Stanislaw Gruszka
2011-03-07 9:20 ` Peter Zijlstra
2011-03-07 13:12 ` Stanislaw Gruszka [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=20110307131217.GA9571@redhat.com \
--to=sgruszka@redhat.com \
--cc=dhalperi@cs.washington.edu \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=wey-yi.w.guy@intel.com \
/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.