From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Dave Airlie <airlied@gmail.com>,
Simona Vetter <simona.vetter@ffwll.ch>
Cc: Konstantin Sinyuk <sinyuk@gmail.com>,
<gregkh@linuxfoundation.org>, <ksummit@lists.linux.dev>,
Konstantin Sinyuk <konstantin.sinyuk@intel.com>,
Leon Romanovsky <leon@kernel.org>, <ogabbay@kernel.org>
Subject: Re: [TECH TOPIC] UALink driver upstreaming
Date: Fri, 12 Sep 2025 09:49:56 -0400 [thread overview]
Message-ID: <aMQlBBu-ieIk1T38@intel.com> (raw)
In-Reply-To: <CACRpkdZZdj1o++Z2tYVuHBkY_Tjypo=gu9srw=f9iL4rDJ4Jbw@mail.gmail.com>
On Fri, Sep 12, 2025 at 02:18:40PM +0200, Linus Walleij wrote:
> On Fri, Sep 12, 2025 at 2:07 PM Konstantin Sinyuk <sinyuk@gmail.com> wrote:
>
> > Longer term, as UAL adoption grows and multiple vendors hook into the
> > framework, the natural home would be a dedicated drivers/ual/, just as
> > CXL evolved into its own subsystem.
>
> If you already know there will be other things than accelerators there,
> so it's more like, i don't know, PCI or greybus, then put it into its own
> subsystem in drivers/ualink from day one, I think drivers/ual is a bit
> terse, the world is full och TLA:s already, also that is its actual name
> isn't it? Hard to miss if someone is looking for it.
>
> Your merges can still go through some submaintainer like Greg, or
> DRM, if they need some shepherding to start out. After all that's how
> drivers/accel is managed, through DRM.
I agree it should be drivers/ualink from day 1.
I like the idea of the flow through drm.
>
> Just my €0.01.
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2025-09-12 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 19:37 Sinyuk, Konstantin
2025-09-10 23:58 ` dan.j.williams
2025-09-11 5:13 ` Greg KH
[not found] ` <a70edcba-0ef7-4d0d-bc00-0e8519a458e8@intel.com>
2025-09-11 11:13 ` Konstantin Sinyuk
2025-09-11 10:59 ` Mimi Zohar
[not found] ` <DM3PR11MB86833A11AD52C01C9063FFE1E309A@DM3PR11MB8683.namprd11.prod.outlook.com>
2025-09-11 11:09 ` FW: " Konstantin Sinyuk
2025-09-11 15:19 ` Linus Walleij
[not found] ` <a74382d8-a2bf-4534-b0ee-a97d8faabf16@intel.com>
2025-09-11 18:10 ` Konstantin Sinyuk
2025-09-11 19:02 ` Leon Romanovsky
2025-09-12 7:22 ` Linus Walleij
2025-09-12 7:47 ` Greg KH
[not found] ` <0f876c7c-566b-476a-b590-d490d41d605c@intel.com>
2025-09-12 12:07 ` Konstantin Sinyuk
2025-09-12 12:18 ` Linus Walleij
2025-09-12 13:49 ` Rodrigo Vivi [this message]
2025-09-12 16:13 ` Matthew Brost
2025-09-13 19:11 ` Jason Gunthorpe
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=aMQlBBu-ieIk1T38@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin.sinyuk@intel.com \
--cc=ksummit@lists.linux.dev \
--cc=leon@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=ogabbay@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=sinyuk@gmail.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