From: Aaron Komisar <aaron.komisar@tandemg.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Wan-Hua Chang <winnie.chang@cypress.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>,
"chi-hsien.lin@cypress.com" <chi-hsien.lin@cypress.com>
Subject: Re: [PATCH] Updating id field in backports genl family
Date: Tue, 12 Jun 2018 12:10:36 +0000 [thread overview]
Message-ID: <AM4PR0202MB2916BC5C05FC8D9A2DB041EBF87F0@AM4PR0202MB2916.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <6bbc4985-0a18-80f5-2a52-6bc04f27af3a@cypress.com>
On 6/12/2018 4:50, Chi-hsien Lin wrote:
>On 06/11/2018 8:25, Johannes Berg wrote:
>> On Mon, 2018-06-11 at 05:29 -0500, Wan-Hua Chang wrote:
>>> Hi,
>>>
>>> I see the patch causes compiling error becasue family->family is not
>>> found when LINUX_VERSION >=3D 3.13
>>>
>>> backports/backport/backport-include/genetlink.h
>>> struct backport_genl_fmaily is only defined when LINUX_VERSION < 3.13
>>>
I built backports-output for recent kernels (4.4.92, for example) and didn'=
t get any compilation errors.
Which version are you using?
>>>
>>> And in backports/backport/compat/backport-3.13.c line 127
>>>
>>> family->id =3D family->family.id
>>>
>>> it looks like this line has done what the patch want to do. Is the
>>> comprehension correct?
This line does update family id, but it gets **copy**->family.
copy->family.id in backport-4.12.c is changed, but family->family.id remain=
s unchanged.
>>=20
>> I guess we have to put an ifdef around this ...
>>=20
>> Aaron?
>
>Hi Aaron,
>
>As Wan-Hua mentioned, it looks like backport-3.13.c line 127 syncs back=20
>the id for backport_genl_family structure for kernel < 3.13 already.
>
>Could you please share more details about the failure you saw without=20
>this change? What's the kernel version you used?
>
I am using target kernel version 3.10.104.
The problem I saw was that a driver using family id after calling genl_regi=
ster_family would always get 0 instead of the actual value.
>
>Regards,
>Chi-hsien Lin
>
>>=20
>> johannes
> .
>=20
Aaron
=
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-06-12 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 10:29 [PATCH] Updating id field in backports genl family Wan-Hua Chang
2018-06-11 12:25 ` Johannes Berg
2018-06-12 1:50 ` Chi-Hsien Lin
2018-06-12 12:10 ` Aaron Komisar [this message]
2018-06-13 10:30 ` Wan-Hua Chang
2018-06-21 10:12 ` Wan-Hua Chang
2018-06-21 14:14 ` Aaron Komisar
2018-06-21 14:17 ` Johannes Berg
2018-06-25 16:40 ` Johannes Berg
2018-06-26 6:07 ` Wan-Hua Chang
2018-06-26 6:54 ` Aaron Komisar
-- strict thread matches above, loose matches on Subject: below --
2018-05-24 10:57 Aaron Komisar
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=AM4PR0202MB2916BC5C05FC8D9A2DB041EBF87F0@AM4PR0202MB2916.eurprd02.prod.outlook.com \
--to=aaron.komisar@tandemg.com \
--cc=backports@vger.kernel.org \
--cc=chi-hsien.lin@cypress.com \
--cc=johannes@sipsolutions.net \
--cc=winnie.chang@cypress.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).