Re: [PATCH 5/6] compat-drivers: add import to fix compile error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 29, 2012 at 11:50 AM, Hauke Mehrtens <hauke@xxxxxxxxxx> wrote:
> On 11/29/2012 08:25 PM, Luis R. Rodriguez wrote:
>> On Wed, Nov 28, 2012 at 3:07 PM, Hauke Mehrtens <hauke@xxxxxxxxxx> wrote:
>>> On kernel version <= 2.6.28, I saw the following compile error without
>>> this patch:
>>>
>>> /net/wireless/util.c: In function ‘cfg80211_get_p2p_attr’:
>>> /net/wireless/util.c:1120:4: error: implicit declaration of function
>>> ‘get_unaligned_le16’ [-Werror=implicit-function-declaration]
>>>
>>> Signed-off-by: Hauke Mehrtens <hauke@xxxxxxxxxx>
>>> ---
>>>  patches/network/06-header-changes.patch |   10 ++++++++++
>>>  patches/network/30-bridge-port.patch    |    2 +-
>>>  2 files changed, 11 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/patches/network/06-header-changes.patch b/patches/network/06-header-changes.patch
>>> index cd587cd..5da05c0 100644
>>> --- a/patches/network/06-header-changes.patch
>>> +++ b/patches/network/06-header-changes.patch
>>> @@ -125,3 +125,13 @@ cases.
>>>
>>>   #define USB_VERSION   "1.0"
>>>
>>> +--- a/net/wireless/util.c
>>> ++++ b/net/wireless/util.c
>>> +@@ -10,6 +10,7 @@
>>> + #include <net/cfg80211.h>
>>> + #include <net/ip.h>
>>> + #include <net/dsfield.h>
>>> ++#include <asm/unaligned.h>
>>
>> Interesting, I wonder if we should just get a compat header to add
>> this therefore not requiring any patching.
>
> Probably some of the header files included also include asm/unaligned.h
> on kernel versions > 2.6.28. You could add all the includes added in
> this patch to compat-X.h to get rid of this entire patch, but this will
> increase the risk of name clashes.

True.. I'll merge in for now and we can later try adding it and test
compiling, if we get no classes then we can move it upstream.

>>> + #include "core.h"
>>> + #include "rdev-ops.h"
>>> +
>>> diff --git a/patches/network/30-bridge-port.patch b/patches/network/30-bridge-port.patch
>>> index b4106b7..a426274 100644
>>> --- a/patches/network/30-bridge-port.patch
>>> +++ b/patches/network/30-bridge-port.patch
>>> @@ -23,7 +23,7 @@ compat-drivers.
>>>
>>>  --- a/net/wireless/util.c
>>>  +++ b/net/wireless/util.c
>>> -@@ -812,7 +812,7 @@ int cfg80211_change_iface(struct cfg8021
>>> +@@ -813,7 +813,7 @@ int cfg80211_change_iface(struct cfg8021
>>>                 return -EOPNOTSUPP;
>>>
>>
>> This hunk does not seem to be relevant so I'll discard it.
>
> The offset of this change in the patch changed because of the additional
> header being added in the previous patch. I am always refreshing the
> patches after doing some changes to them to make all apply cleanly.

Got it, I'd prefer we keep refreshes separate if possible given that I
think it'd be good we can keep track of automatic refreshes Vs manual
fixes required on patches between two releases. I'm a statistics
junky, but do think this can help in the long run to separate and
analyze the different types of changes required to keep doing
backporting.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe backports" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux