From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
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:48:53 +0100 [thread overview]
Message-ID: <1416430133.9374.29.camel@sipsolutions.net> (raw)
In-Reply-To: <546D01EC.8070808@broadcom.com>
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 ;-)
johannes
next prev parent reply other threads:[~2014-11-19 20:49 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 [this message]
2014-11-19 20:51 ` Arend van Spriel
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=1416430133.9374.29.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--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 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.