From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>,
<brcm80211-dev-list@broadcom.com>,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] brcmfmac: don't include linux/unaligned/access_ok.h
Date: Wed, 19 Nov 2014 21:51:58 +0100 [thread overview]
Message-ID: <546D02EE.7030602@broadcom.com> (raw)
In-Reply-To: <1416430133.9374.29.camel@sipsolutions.net>
On 11/19/14 21:48, Johannes Berg wrote:
> On Wed, 2014-11-19 at 21:47 +0100, Arend van Spriel wrote:
>> On 11/19/14 21:42, Johannes Berg wrote:
>>> On Wed, 2014-11-19 at 21:36 +0100, Arend van Spriel wrote:
>>>> On 11/19/14 21:18, Johannes Berg wrote:
>>>>> From: Johannes Berg<johannes.berg@intel.com>
>>>>>
>>>>> This is a specific implementation,<asm/unaligned.h> is the
>>>>> multiplexer that has the arch-specific knowledge of which
>>>>> of the implementations needs to be used, so include that.
>>>>
>>>> Thanks, Johannes
>>>>
>>>> Maybe it would be good to mention this was found by kbuild test robot.
>>>
>>> Yeah, maybe. It was more or less by accident though :-)
>>
>> accidents happen. The pcie stuff was added in 3.17 so my question to
>> John is whether this can go into 3.18 and stable.
>
> Could be considered, I guess you can resend the patch with appropriate
> tags? I just want wireless-next to not complain about my patch ;-)
Yeah, I also hate it when that happens. I will resend it.
Regards,
Arend
> johannes
>
prev parent reply other threads:[~2014-11-19 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 20:18 [PATCH] brcmfmac: don't include linux/unaligned/access_ok.h Johannes Berg
2014-11-19 20:36 ` Arend van Spriel
2014-11-19 20:42 ` Johannes Berg
2014-11-19 20:47 ` Arend van Spriel
2014-11-19 20:48 ` Johannes Berg
2014-11-19 20:51 ` Arend van Spriel [this message]
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=546D02EE.7030602@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).