From: Daniel Vetter <daniel@ffwll.ch>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Cc: Jeffrey Hugo <quic_jhugo@quicinc.com>,
daniel@ffwll.ch, sfr@canb.auug.org.au, mani@kernel.org,
greg@kroah.com, ogabbay@kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, quic_pkanojiy@quicinc.com,
linux-next@vger.kernel.org, jacek.lawrynowicz@linux.intel.com,
airlied@redhat.com
Subject: Re: [PATCH] Revert "accel/qaic: Add mhi_qaic_cntl"
Date: Thu, 13 Apr 2023 10:49:29 +0200 [thread overview]
Message-ID: <ZDfCGXPCFkb20jNW@phenom.ffwll.local> (raw)
In-Reply-To: <20230412140542.GA3141290@linux.intel.com>
On Wed, Apr 12, 2023 at 04:05:42PM +0200, Stanislaw Gruszka wrote:
> On Wed, Apr 12, 2023 at 07:57:44AM -0600, Jeffrey Hugo wrote:
> > This reverts commit 566fc96198b4bb07ca6806386956669881225271.
> >
> > This exposes a userspace API that is still under debate. Revert the
> > change before the uAPI gets exposed to avoid making a mistake. QAIC is
> > otherwise still functional.
> >
> > Suggested-by: Daniel Vetter <daniel@ffwll.ch>
> > Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> > Reviewed-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
> Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
I think Ack from Oded would be good (but iirc there's some holidays going
on), but I guess Greg's is good enough. Can you pls push this to
drm-misc-next-fixes (it's open now for merge window fixes) since Jeff
isn't set up yet?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-04-13 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:57 [PATCH] Revert "accel/qaic: Add mhi_qaic_cntl" Jeffrey Hugo
2023-04-12 14:00 ` Jeffrey Hugo
2023-04-12 14:27 ` Daniel Vetter
2023-04-12 14:05 ` Stanislaw Gruszka
2023-04-13 8:49 ` Daniel Vetter [this message]
2023-04-13 10:15 ` Jacek Lawrynowicz
2023-04-12 17:15 ` Greg KH
2023-04-13 8:52 ` Daniel Vetter
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=ZDfCGXPCFkb20jNW@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mani@kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=quic_pkanojiy@quicinc.com \
--cc=sfr@canb.auug.org.au \
--cc=stanislaw.gruszka@linux.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;
as well as URLs for NNTP newsgroup(s).