From: David Miller <davem@davemloft.net>
To: julian.calaby@gmail.com
Cc: torvalds@linux-foundation.org, keithp@keithp.com,
linux-wireless@vger.kernel.org, zajec5@gmail.com
Subject: Re: MBA resume wedge due to wireless fixed yet?
Date: Mon, 16 Jan 2012 20:17:03 -0500 (EST) [thread overview]
Message-ID: <20120116.201703.109506071619281024.davem@davemloft.net> (raw)
In-Reply-To: <CAGRGNgUhGs+30WpppKvH110qBMcSss3xKEoNH_Tv+ZEoKWRJhg@mail.gmail.com>
From: Julian Calaby <julian.calaby@gmail.com>
Date: Tue, 17 Jan 2012 12:09:03 +1100
> Hi,
>
> On Tue, Jan 17, 2012 at 11:57, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Mon, Jan 16, 2012 at 4:37 PM, Julian Calaby <julian.calaby@gmail.com> wrote:
>>> Hi all,
>>>
>>> I have a stupid question:
>>>
>>> On Tue, Jan 17, 2012 at 10:56, Linus Torvalds
>>> <torvalds@linux-foundation.org> wrote:
>>>> I have patches, but haven't committed them because I was kind of
>>>> expecting them to go through the wireless tree.
>>>
>>> Then why were these patches never posted to linux-wireless?
>>
>> They were posted to at least netdev, they were cc'd to the top-level
>> maintainers (both David and Linville), and the maintainers of the
>> driver itself.
>
> I noticed all the names for the driver maintainers but my eyes must
> have skipped over David and Linville.
I poked John and told him he needs to integrate those changes ASAP.
next prev parent reply other threads:[~2012-01-17 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86wr8rfbpf.fsf@sumi.keithp.com>
2012-01-16 23:56 ` MBA resume wedge due to wireless fixed yet? Linus Torvalds
2012-01-17 0:37 ` Julian Calaby
2012-01-17 0:57 ` Linus Torvalds
2012-01-17 1:09 ` Julian Calaby
2012-01-17 1:17 ` David Miller [this message]
2012-01-17 1:19 ` Linus Torvalds
2012-01-17 14:48 ` John W. Linville
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=20120116.201703.109506071619281024.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=julian.calaby@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zajec5@gmail.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 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).