From: Jakub Kicinski <kuba@kernel.org>
To: Larysa Zaremba <larysa.zaremba@intel.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>, <davem@davemloft.net>,
<pabeni@redhat.com>, <edumazet@google.com>,
<andrew+netdev@lunn.ch>, <netdev@vger.kernel.org>,
<przemyslaw.kitszel@intel.com>, <aleksander.lobakin@intel.com>,
<sridhar.samudrala@intel.com>, <anjali.singhai@intel.com>,
<michal.swiatkowski@linux.intel.com>,
<maciej.fijalkowski@intel.com>, <emil.s.tantilov@intel.com>,
<madhu.chittim@intel.com>, <joshua.a.hay@intel.com>,
<jacob.e.keller@intel.com>, <jayaprakash.shanmugam@intel.com>,
<jiri@resnulli.us>, <horms@kernel.org>, <corbet@lwn.net>,
<richardcochran@gmail.com>, <linux-doc@vger.kernel.org>,
<tatyana.e.nikolova@intel.com>, <krzysztof.czurylo@intel.com>,
<jgg@ziepe.ca>, <leon@kernel.org>, <linux-rdma@vger.kernel.org>,
Samuel Salin <Samuel.salin@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [PATCH net-next v3 01/14] virtchnl: create 'include/linux/intel' and move necessary header files
Date: Thu, 21 May 2026 06:56:09 -0700 [thread overview]
Message-ID: <20260521065609.248c7009@kernel.org> (raw)
In-Reply-To: <ag7QUgfpM5UAAE2z@soc-5CG4396X81.clients.intel.com>
On Thu, 21 May 2026 11:28:50 +0200 Larysa Zaremba wrote:
> On Wed, May 20, 2026 at 05:52:01PM -0700, Jakub Kicinski wrote:
> > On Fri, 15 May 2026 15:44:25 -0700 Tony Nguyen wrote:
> > > include/linux/intel is vacant
> >
> > I don't see any other vendor directory under include/linux
>
> There are at least
>
> include/linux/mlx4, include/linux/mlx5 and include/linux/bnxt.
>
> Those are per-driver and not per-vendor, but intel ethernet has too many drivers
> to have separate folders for them.
>
> I just do not think this creates a precedent neccessarily.
You just said the other ones are for specific drivers.
> Folder structure is for you to decide as a maintainer, but it would be nice to
> have known about such doubts earlier.
I'd love to know if you any suggestions for improving the process.
Otherwise please keep your venting off list.
next prev parent reply other threads:[~2026-05-21 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260515224443.2772147-1-anthony.l.nguyen@intel.com>
2026-05-15 22:44 ` [PATCH net-next v3 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Tony Nguyen
2026-05-21 0:52 ` Jakub Kicinski
2026-05-21 9:28 ` Larysa Zaremba
2026-05-21 13:56 ` Jakub Kicinski [this message]
2026-05-22 11:08 ` Alexander Lobakin
2026-05-22 15:40 ` Jakub Kicinski
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=20260521065609.248c7009@kernel.org \
--to=kuba@kernel.org \
--cc=Samuel.salin@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jayaprakash.shanmugam@intel.com \
--cc=jgg@ziepe.ca \
--cc=jiri@resnulli.us \
--cc=joshua.a.hay@intel.com \
--cc=krzysztof.czurylo@intel.com \
--cc=larysa.zaremba@intel.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=madhu.chittim@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=sridhar.samudrala@intel.com \
--cc=tatyana.e.nikolova@intel.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