From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux ARM MSM <linux-arm-msm@vger.kernel.org>,
Linux DRI Development <dri-devel@lists.freedesktop.org>
Cc: Carl Vanderlip <carl.vanderlip@oss.qualcomm.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Youssef Samir <youssef.abdulrahman@oss.qualcomm.com>,
Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>,
Zack McKevitt <zachary.mckevitt@oss.qualcomm.com>,
Aswin Venkatesan <aswivenk@qti.qualcomm.com>
Subject: Re: [PATCH 0/2] accel/qaic documentation fixes
Date: Tue, 11 Nov 2025 06:15:54 +0700 [thread overview]
Message-ID: <aRJyKlRkihq1OcGk@archie.me> (raw)
In-Reply-To: <e44c8f40-b6ff-4369-8d86-ded225b41544@oss.qualcomm.com>
On Mon, Nov 10, 2025 at 11:54:59AM -0700, Jeff Hugo wrote:
> Thank you for the fixes. Yet again I am impressed by having your fixes in my
> inbox before I even see the reports.
>
> I'll get these merged to drm-misc-next where the offending issues currently
> reside. I anticipate getting that done later today.
Thank you for the compliment!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-11-10 23:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 3:59 [PATCH 0/2] accel/qaic documentation fixes Bagas Sanjaya
2025-11-10 3:59 ` [PATCH 1/2] accel/qaic: Separate DBC_STATE_* definition list Bagas Sanjaya
2025-11-10 5:52 ` Randy Dunlap
2025-11-10 18:49 ` Jeff Hugo
2025-11-10 3:59 ` [PATCH 2/2] accel/qaic: Format DBC states table in sysfs ABI documentation Bagas Sanjaya
2025-11-10 5:52 ` Randy Dunlap
2025-11-10 18:50 ` Jeff Hugo
2025-11-10 18:54 ` [PATCH 0/2] accel/qaic documentation fixes Jeff Hugo
2025-11-10 23:15 ` Bagas Sanjaya [this message]
2025-11-10 21:56 ` Jeff Hugo
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=aRJyKlRkihq1OcGk@archie.me \
--to=bagasdotme@gmail.com \
--cc=aswivenk@qti.qualcomm.com \
--cc=carl.vanderlip@oss.qualcomm.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_pkanojiy@quicinc.com \
--cc=youssef.abdulrahman@oss.qualcomm.com \
--cc=zachary.mckevitt@oss.qualcomm.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).