From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next 2012-04-25
Date: Wed, 25 Apr 2012 16:39:26 -0400 (EDT) [thread overview]
Message-ID: <20120425.163926.2209040699696617525.davem@davemloft.net> (raw)
In-Reply-To: <20120425191418.GC16900@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 25 Apr 2012 15:14:19 -0400
> This is another batch of updates intended for 3.5...
...
> Please let me know if there are problems!
There are:
>From 792545c7bc5d6b922d3778dc602e557d64c83551 Mon Sep 17 00:00:00 2001
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Date: Mon, 23 Apr 2012 19:55:48 -0700
Subject: [PATCH 88/88] libertas: include sched.h on firmware.c
Do not assume we have our subsystem including this for us,
at least for older kernels this is not true. Lets just be
explicit about this requirement for the usage of wake_up().
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
This is bogus, wake_up() is defined in linux/wait.h, the whole
point of the linux/sched.h split up is so that linux/sched.h
includes could be removed and replaced with actual dependencies.
Also, please don't accept any patches from Luis that add those
#undef pr_fmt things to the atheros drivers.
He tried to add it an ethernet driver, and I asked him to explain
exactly why he's doing and that if it's appropriate then it's
appropriate everywhere not just in a few specific drivers. He failed
to respond to me, and therefore failed to explain the situation and
address my concerned. And then I saw just today that he's submitting
the same patch to wireless drivers. That's not acceptable.
Thanks.
next prev parent reply other threads:[~2012-04-25 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:14 pull request: wireless-next 2012-04-25 John W. Linville
2012-04-25 20:39 ` David Miller [this message]
[not found] ` <20120425.163926.2209040699696617525.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2012-04-26 11:46 ` Luis R. Rodriguez
2012-04-26 18:41 ` John W. Linville
[not found] ` <20120425191418.GC16900-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-04-26 19:34 ` pull request: wireless-next 2012-04-26 John W. Linville
2012-04-26 20:06 ` David Miller
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=20120425.163926.2209040699696617525.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).