> -----Original Message-----
> From: Intel-wired-lan <[email protected]> On Behalf Of
> Larysa Zaremba
> Sent: Monday, November 17, 2025 5:49 AM
> To: [email protected]; Nguyen, Anthony L
> <[email protected]>
> Cc: Lobakin, Aleksander <[email protected]>; Samudrala, Sridhar
> <[email protected]>; Singhai, Anjali <[email protected]>;
> Michal Swiatkowski <[email protected]>; Zaremba, Larysa
> <[email protected]>; Fijalkowski, Maciej
> <[email protected]>; Tantilov, Emil S <[email protected]>;
> Chittim, Madhu <[email protected]>; Hay, Joshua A
> <[email protected]>; Keller, Jacob E <[email protected]>;
> Shanmugam, Jayaprakash <[email protected]>;
> Wochtman, Natalia <[email protected]>; Jiri Pirko
> <[email protected]>; David S. Miller <[email protected]>; Eric Dumazet
> <[email protected]>; Jakub Kicinski <[email protected]>; Paolo Abeni
> <[email protected]>; Simon Horman <[email protected]>; Jonathan
> Corbet <[email protected]>; Richard Cochran <[email protected]>;
> Kitszel, Przemyslaw <[email protected]>; Andrew Lunn
> <[email protected]>; [email protected]; linux-
> [email protected]; [email protected]; Czurylo, Krzysztof
> <[email protected]>
> Subject: [Intel-wired-lan] [PATCH iwl-next v5 01/15] virtchnl: create
> 'include/linux/intel' and move necessary header files
>
> From: Victor Raj <[email protected]>
>
> include/linux/net houses a single folder "intel", meanwhile
> include/linux/intel
> is vacant. On top of that, it would be useful to place all iavf headers
> together
> with other intel networking headers.
>
> Move abovementioned intel header files into new folder include/linux/intel.
> Also, assign new folder to both intel and general networking maintainers.
>
> Suggested-by: Alexander Lobakin <[email protected]>
> Reviewed-by: Sridhar Samudrala <[email protected]>
> Signed-off-by: Victor Raj <[email protected]>
> Signed-off-by: Larysa Zaremba <[email protected]>
> ---
Tested-by: Samuel Salin <[email protected]>
