From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, johannes@sipsolutions.net,
linux-next@vger.kernel.org
Subject: Re: linux-next: new warnings
Date: Thu, 6 Nov 2008 08:30:02 -0500 [thread overview]
Message-ID: <20081106133001.GA14184@tuxdriver.com> (raw)
In-Reply-To: <20081105.200901.00689398.davem@davemloft.net>
On Wed, Nov 05, 2008 at 08:09:01PM -0800, David Miller wrote:
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 6 Nov 2008 14:25:14 +1100
>
> > Hi all,
> >
> > Commit 7a5158ef8da70fdedeb0530faaa8128aa645be3c ("mac80211: fix short
> > slot handling") added this:
> >
> > /* XXX: remove all this once drivers stop trying to use it */
> > static inline int __deprecated __IEEE80211_CONF_SHORT_SLOT_TIME(void)
> > .
> > .
> > #define IEEE80211_CONF_SHORT_SLOT_TIME (__IEEE80211_CONF_SHORT_SLOT_TIME())
> >
> > to include/net/mac80211.h. I was wondering if any thought was given to
> > getting rid of the (currently 4) in tree uses of
> > IEEE80211_CONF_SHORT_SLOT_TIME before doing this so that we don't have
> > even more new warnings from the kernel build.
> >
> > The least that could be done is to clean them up now ...
>
> John Linville told me that these warnings would show up because
> of one of his merges and that he also has the patches pending
> to get rid of them as well.
>
> Please just ignore them for now.
Yes, sorry for the delay. I've been down with pneumonia all week. :-(
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-11-06 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 3:25 linux-next: new warnings Stephen Rothwell
2008-11-06 4:09 ` David Miller
2008-11-06 4:30 ` Stephen Rothwell
2008-11-06 13:30 ` John W. Linville [this message]
2008-11-06 23:38 ` Stephen Rothwell
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=20081106133001.GA14184@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.