From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hansg@kernel.org>,
Stuart Hayes <stuart.w.hayes@gmail.com>
Subject: Re: [PATCH v4 0/5] platform/x86: dell_rbu: Packet data fixes
Date: Mon, 07 Jul 2025 16:11:32 +0300 [thread overview]
Message-ID: <175189389223.4826.12947270597345917208.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250609184659.7210-1-stuart.w.hayes@gmail.com>
On Mon, 09 Jun 2025 13:46:54 -0500, Stuart Hayes wrote:
> Make fixes related to packet data list and buffers, and fix a sparse
> warning.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/5] platform/x86: dell_rbu: Fix lock context warning
(no commit info)
[2/5] platform/x86: dell_rbu: Fix list usage
(no commit info)
[3/5] platform/x86: dell_rbu: Remove unused struct
commit: 56036d6af41a473a8129fc960a5ab3673eda13d5
[4/5] platform/x86: dell_rbu: Stop overwriting data buffer
(no commit info)
[5/5] platform/x86: dell_rbu: Bump version
(no commit info)
--
i.
prev parent reply other threads:[~2025-07-07 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 18:46 Stuart Hayes
2025-06-09 18:46 ` [PATCH v4 1/5] platform/x86: dell_rbu: Fix lock context warning Stuart Hayes
2025-06-09 18:46 ` [PATCH v4 2/5] platform/x86: dell_rbu: Fix list usage Stuart Hayes
2025-06-09 18:46 ` [PATCH v4 3/5] platform/x86: dell_rbu: Remove unused struct Stuart Hayes
2025-06-10 7:52 ` Ilpo Järvinen
2025-06-09 18:46 ` [PATCH v4 4/5] platform/x86: dell_rbu: Stop overwriting data buffer Stuart Hayes
2025-06-09 18:46 ` [PATCH v4 5/5] platform/x86: dell_rbu: Bump version Stuart Hayes
2025-07-07 13:11 ` Ilpo Järvinen [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=175189389223.4826.12947270597345917208.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stuart.w.hayes@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
all inboxes | Powered by JetHome®