From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless 2013-06-06
Date: Wed, 12 Jun 2013 08:26:49 +0200 [thread overview]
Message-ID: <1371018409.8601.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130611.222706.1492583255605214982.davem@davemloft.net> (sfid-20130612_072751_104839_5F29BCA5)
On Tue, 2013-06-11 at 22:27 -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Thu, 6 Jun 2013 15:09:30 -0400
>
> > Johannes Berg (2):
> > mac80211: constify ieee802_11_parse_elems() argument
>
> Such cleanups are absolutely, positively, not appropriate at this
> time.
My other fix depends on this to not have a const warning. I can add a
cast to pretend the input isn't const at this point, but that seemed
like a bad idea as well.
johannes
next prev parent reply other threads:[~2013-06-12 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 19:09 pull request: wireless 2013-06-06 John W. Linville
[not found] ` <20130606190929.GB18827-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2013-06-12 5:27 ` David Miller
2013-06-12 6:26 ` Johannes Berg [this message]
2013-06-12 7:07 ` David Miller
2013-06-12 7:09 ` Johannes Berg
2013-06-12 7:21 ` David Miller
2013-06-12 7:24 ` Sujith Manoharan
2013-06-12 7:42 ` David Miller
[not found] ` <20130611.222706.1492583255605214982.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2013-06-12 14:30 ` John W. Linville
2013-06-12 15:09 ` pull request: wireless 2013-06-12 John W. Linville
2013-06-12 20:36 ` 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=1371018409.8601.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).