dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	dafna@fastmail.com, linux-doc@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, ogabbay@kernel.org,
	dri-devel@lists.freedesktop.org, quic_ajitpals@quicinc.com,
	quic_pkanojiy@quicinc.com, stanislaw.gruszka@linux.intel.com,
	quic_carlv@quicinc.com,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH v3 8/8] MAINTAINERS: Add entry for QAIC driver
Date: Fri, 17 Mar 2023 15:04:51 +0100	[thread overview]
Message-ID: <20230317140451.uywz7szrzvusyrjy@houat> (raw)
In-Reply-To: <daa3100e-8f5b-8dbb-297f-ca3a87b44a97@quicinc.com>

On Thu, Mar 16, 2023 at 11:04:05AM -0600, Jeffrey Hugo wrote:
> On 3/14/2023 3:59 AM, Jacek Lawrynowicz wrote:
> > Hi
> > 
> > On 06.03.2023 22:34, Jeffrey Hugo wrote:
> > > Add MAINTAINERS entry for the Qualcomm Cloud AI 100 driver.
> > > 
> > > Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> > > Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
> > > Reviewed-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
> > > ---
> > >   MAINTAINERS | 9 +++++++++
> > >   1 file changed, 9 insertions(+)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index b0db911..feb2974 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -17253,6 +17253,15 @@ F:	Documentation/devicetree/bindings/clock/qcom,*
> > >   F:	drivers/clk/qcom/
> > >   F:	include/dt-bindings/clock/qcom,*
> > > +QUALCOMM CLOUD AI (QAIC) DRIVER
> > > +M:	Jeffrey Hugo <quic_jhugo@quicinc.com>
> > > +L:	linux-arm-msm@vger.kernel.org
> > > +L:	dri-devel@lists.freedesktop.org
> > > +S:	Supported
> > > +F:	Documentation/accel/qaic/
> > > +F:	drivers/accel/qaic/
> > > +F:	include/uapi/drm/qaic_accel.h
> > 
> > Aren't you missing repo link?
> > T:	git git://anongit.freedesktop.org/drm/drm-misc
> 
> Maarten/Maxime/Thomas are we ok to follow the iVPU example and use drm-misc
> for this, or would a separate tree be preferred?

Yeah, please go ahead with drm-misc

Do you have commit rights?

Maxime

  reply	other threads:[~2023-03-17 14:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 21:33 [PATCH v3 0/8] QAIC accel driver Jeffrey Hugo
2023-03-06 21:33 ` [PATCH v3 1/8] accel/qaic: Add documentation for AIC100 accelerator driver Jeffrey Hugo
2023-03-13 12:47   ` Jacek Lawrynowicz
2023-03-06 21:33 ` [PATCH v3 2/8] accel/qaic: Add uapi and core driver file Jeffrey Hugo
2023-03-13 13:21   ` Jacek Lawrynowicz
2023-03-13 17:37     ` Jeffrey Hugo
2023-03-14  9:55       ` Jacek Lawrynowicz
2023-03-14 15:41         ` Jeffrey Hugo
2023-03-06 21:33 ` [PATCH v3 3/8] accel/qaic: Add MHI controller Jeffrey Hugo
2023-03-13 13:39   ` Jacek Lawrynowicz
2023-03-13 17:45     ` Jeffrey Hugo
2023-03-06 21:33 ` [PATCH v3 4/8] accel/qaic: Add control path Jeffrey Hugo
2023-03-14 10:29   ` Jacek Lawrynowicz
2023-03-14 17:26     ` Jeffrey Hugo
2023-03-15 21:50       ` Jeffrey Hugo
2023-03-06 21:34 ` [PATCH v3 5/8] accel/qaic: Add datapath Jeffrey Hugo
2023-03-14 10:58   ` Jacek Lawrynowicz
2023-03-14 17:48     ` Jeffrey Hugo
2023-03-06 21:34 ` [PATCH v3 6/8] accel/qaic: Add mhi_qaic_cntl Jeffrey Hugo
2023-03-14 12:19   ` Jacek Lawrynowicz
2023-03-14 18:26     ` Jeffrey Hugo
2023-03-06 21:34 ` [PATCH v3 7/8] accel/qaic: Add qaic driver to the build system Jeffrey Hugo
2023-03-13 13:25   ` Jacek Lawrynowicz
2023-03-06 21:34 ` [PATCH v3 8/8] MAINTAINERS: Add entry for QAIC driver Jeffrey Hugo
2023-03-14  9:59   ` Jacek Lawrynowicz
2023-03-14 16:02     ` Jeffrey Hugo
2023-03-16 17:04     ` Jeffrey Hugo
2023-03-17 14:04       ` Maxime Ripard [this message]
2023-03-17 15:46         ` Jeffrey Hugo
2023-03-20  7:03           ` Oded Gabbay
2023-03-10 10:02 ` [PATCH v3 0/8] QAIC accel driver Stanislaw Gruszka

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=20230317140451.uywz7szrzvusyrjy@houat \
    --to=maxime@cerno.tech \
    --cc=dafna@fastmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=quic_ajitpals@quicinc.com \
    --cc=quic_carlv@quicinc.com \
    --cc=quic_jhugo@quicinc.com \
    --cc=quic_pkanojiy@quicinc.com \
    --cc=stanislaw.gruszka@linux.intel.com \
    --cc=tzimmermann@suse.de \
    /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).