From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Larysa Zaremba <larysa.zaremba@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH] ice: Unbind the workqueue
Date: Mon, 7 Oct 2024 14:42:06 -0700 [thread overview]
Message-ID: <0f4a2226-b4c1-3440-12c4-19ed36e02979@intel.com> (raw)
In-Reply-To: <ZwO4CrZ_c92ZUseg@localhost.localdomain>
On 10/7/2024 3:29 AM, Frederic Weisbecker wrote:
> Le Mon, Sep 23, 2024 at 11:28:20AM -0700, Tony Nguyen a écrit :
...
>>> Thank you for the patch, it would make sense for our iwl-next tree,
>>> with such assumption:
>>> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
>>>
>>> @Tony, do you want it resent with target tree in the subject?
>>
>> No, I can apply this as-is but please remember to designate a tree for
>> future patches.
>
> Sorry I didn't know about any tree. I can't even find where iwl-next is
> hosted.
The information is here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n11413
For bug fixes, net-queue tree is used and next-queue for other content
(dev-queue branch for both).
I did find that I crossed this patch with another and found that the
initial send of this did not include the Intel Wired LAN list. I'll
resend the patch to include the proper list so that patchworks can pick
this up.
Thanks,
Tony
prev parent reply other threads:[~2024-10-07 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 22:24 Frederic Weisbecker
2024-09-23 8:57 ` Przemek Kitszel
2024-09-23 18:28 ` Tony Nguyen
2024-10-07 10:29 ` Frederic Weisbecker
2024-10-07 21:42 ` Tony Nguyen [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=0f4a2226-b4c1-3440-12c4-19ed36e02979@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=frederic@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=przemyslaw.kitszel@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
all inboxes | Powered by JetHome®