[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170810085823.8B48E601D8@smtp.codeaurora.org>
Date: Thu, 10 Aug 2017 08:58:23 +0000 (UTC)
From: Kalle Valo <kvalo@...eaurora.org>
To: Arvind Yadav <arvind.yadav.cs@...il.com>
Cc: petkan@...leusys.com, arend.vanspriel@...adcom.com,
franky.lin@...adcom.com, wright.feng@...ress.com,
hante.meuleman@...adcom.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com, brcm80211-dev-list@...ress.com
Subject: Re: [v2,06/20] brcm80211: constify usb_device_id
Arvind Yadav <arvind.yadav.cs@...il.com> wrote:
> usb_device_id are not supposed to change at runtime. All functions
> working with usb_device_id provided by <linux/usb.h> work with
> const usb_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@...il.com>
Does not apply to wireless-drivers-next:
error: Failed to merge in the changes.
Applying: brcm80211: constify usb_device_id
Using index info to reconstruct a base tree...
M drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c
Falling back to patching base and 3-way merge...
Auto-merging drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c
CONFLICT (content): Merge conflict in drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c
Patch failed at 0001 brcm80211: constify usb_device_id
The copy of the patch that failed is found in: .git/rebase-apply/patch
Patch set to Changes Requested.
--
https://patchwork.kernel.org/patch/9890985/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists