Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\s+0\/4\]\s+Fix\s+W\=1\s+compilation\s+warnings\s+in\s+net\/\*\s+folder\s*$/: 5 ]

Total 5 documents matching your query.

1. Re: [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder (score: 1)
Author: Leon Romanovsky <leon@xxxxxxxxxx>
Date: Tue, 2 Feb 2021 17:54:09 +0200
No problem. I'm receiving them either.
/html/lvs-devel/2021-02/msg00009.html (12,399 bytes)

2. Re: [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder (score: 1)
Author: Eric Dumazet <edumazet@xxxxxxxxxx>
Date: Tue, 2 Feb 2021 15:59:38 +0100
Send this to net-next As I stated, we never enforce W=1 compilation rule. I understand we might want that for _future_ kernels. I do receive a copy of all backports in my mailbox, whenever I am tagge
/html/lvs-devel/2021-02/msg00008.html (12,522 bytes)

3. Re: [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder (score: 1)
Author: Leon Romanovsky <leon@xxxxxxxxxx>
Date: Tue, 2 Feb 2021 16:57:24 +0200
I added because Jakub has checker that looks for Fixes lines in "net" patches. It is automatic. Thanks
/html/lvs-devel/2021-02/msg00007.html (11,084 bytes)

4. Re: [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder (score: 1)
Author: Eric Dumazet <edumazet@xxxxxxxxxx>
Date: Tue, 2 Feb 2021 15:34:37 +0100
Ok, but we never had a strong requirement about W=1, so adding Fixes: tag is adding unnecessary burden to stable teams all around the world.
/html/lvs-devel/2021-02/msg00005.html (11,367 bytes)

5. [PATCH net 0/4] Fix W=1 compilation warnings in net/* folder (score: 1)
Author: Leon Romanovsky <leon@xxxxxxxxxx>
Date: Tue, 2 Feb 2021 15:55:40 +0200
Hi, This short series fixes W=1 compilation warnings which I experienced when tried to compile net/* folder. Thanks Leon Romanovsky (4): ipv6: silence compilation warning for non-IPV6 builds ipv6: mo
/html/lvs-devel/2021-02/msg00001.html (11,235 bytes)


This search system is powered by Namazu