From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Tomeu Vizoso" <tomeu@tomeuvizoso.net>
Cc: "Oded Gabbay" <ogabbay@kernel.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<linux-kernel-mentees@lists.linux.dev>,
<skhan@linuxfoundation.org>, "kernel test robot" <lkp@intel.com>,
"dri-devel" <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH 0/2] accel/rocket: Fix build errors and sparse warning
Date: Sun, 03 Aug 2025 10:14:39 -0600 [thread overview]
Message-ID: <DBSXCWOKT4BE.1RD9LVC2CY12E@brighamcampbell.com> (raw)
In-Reply-To: <CAAObsKCUs0yn=S1PzGDKu8nNnTOkxqMMYzep-QhG00X1CY3DjA@mail.gmail.com>
On Sun Aug 3, 2025 at 9:33 AM MDT, Tomeu Vizoso wrote:
> thanks for the fixes. Will pick them up. Hope you don't mind if I
> change the subject of the first patch to something a bit more
> specific, such as:
>
> accel/rocket: Adapt to changes in drm/sched API
No, I don't mind at all. Go ahead and use your editorial discretion with
the shortlogs and commit messages. I'll put more thought into the patch
subject next time.
Thanks,
Brigham
prev parent reply other threads:[~2025-08-03 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 19:25 [PATCH 0/2] accel/rocket: Fix build errors and sparse warning Brigham Campbell
2025-08-02 19:25 ` [PATCH 1/2] accel/rocket: Fix Rockchip NPU compilation Brigham Campbell
2025-08-02 19:25 ` [PATCH 2/2] accel/rocket: Fix undeclared const rocket_pm_ops Brigham Campbell
2025-08-03 15:33 ` [PATCH 0/2] accel/rocket: Fix build errors and sparse warning Tomeu Vizoso
2025-08-03 16:14 ` Brigham Campbell [this message]
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=DBSXCWOKT4BE.1RD9LVC2CY12E@brighamcampbell.com \
--to=me@brighamcampbell.com \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ogabbay@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tomeu@tomeuvizoso.net \
/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