From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2008-07-14
Date: Tue, 15 Jul 2008 12:38:58 -0400 [thread overview]
Message-ID: <20080715163858.GA557@tuxdriver.com> (raw)
In-Reply-To: <20080715092431.d288d0e8.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Tue, Jul 15, 2008 at 09:24:31AM -0700, Randy Dunlap wrote:
> On Tue, 15 Jul 2008 09:48:49 -0400 John W. Linville wrote:
> > commit 6ef307bc561911c8cdda98ef3896b5982b602a43
> > Author: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> > Date: Thu Jul 3 13:52:18 2008 -0700
> >
> > mac80211: fix lots of kernel-doc
> >
> > Fix more than 50 kernel-doc warnings in ieee80211/mac80211 kernel-doc notati
> > Fix a few typos also.
> >
> > Note: Some fields are marked as TBD and need to have their description
> > corrected.
> >
> > Signed-off-by: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> > Signed-off-by: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
>
>
> Yes, that's in the wireless-next-2.6 git tree:
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=6ef307bc561911c8cdda98ef3896b5982b602a43
>
> and this was a pull request, possibly even the last(?) pull, for wireless-next-2.6
> for 2.6.27, according to the email intro. So please tell me what I can
> expect for this mac80211 kernel-doc patch. Thanks.
We spoke off-line, but just for the public record that commit was
already pulled into net-next-2.6.
Hth!
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-15 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:23 pull request: wireless-next-2.6 2008-07-14 John W. Linville
[not found] ` <20080714192302.GA2541-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-07-14 20:29 ` Randy Dunlap
2008-07-15 13:48 ` John W. Linville
[not found] ` <20080715134849.GA24361-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-07-15 16:24 ` Randy Dunlap
[not found] ` <20080715092431.d288d0e8.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-07-15 16:38 ` John W. Linville [this message]
2008-07-15 3:45 ` David Miller
[not found] ` <20080714.204532.116542087.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-07-15 7:43 ` Johannes Berg
[not found] ` <1216107805.23746.14.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-07-15 8:09 ` [PATCH] wireless: fix warnings from QoS patch Johannes Berg
[not found] ` <1216109364.23746.17.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-07-15 9:09 ` David Miller
2008-07-16 12:49 ` pull request: wireless-next-2.6 2008-07-14 Tomas Winkler
2008-07-16 20:00 ` David Miller
2008-07-16 20:05 ` 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=20080715163858.GA557@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.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).