From: Johannes Berg <johannes@sipsolutions.net>
To: Stefan Agner <stefan@agner.ch>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nl80211: fix enumeration type
Date: Thu, 20 Apr 2017 09:22:06 +0200 [thread overview]
Message-ID: <1492672926.3109.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20170420065513.1930-1-stefan@agner.ch>
On Wed, 2017-04-19 at 23:55 -0700, Stefan Agner wrote:
> Use type enum nl80211_rate_info for bitrate information. This fixes
> a warning when compiling with clang:
> warning: implicit conversion from enumeration type 'enum
> nl80211_rate_info'
> to different enumeration type 'enum nl80211_attrs'
I'm pretty sure I just applied exactly these two patches very recently.
What made *two* people suddenly see this?
johannes
next prev parent reply other threads:[~2017-04-20 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 6:55 [PATCH] nl80211: fix enumeration type Stefan Agner
2017-04-20 7:22 ` Johannes Berg [this message]
[not found] ` <1492672926.3109.5.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2017-04-20 14:21 ` Stefan Agner
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=1492672926.3109.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@agner.ch \
/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).