From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Ivan Vecera <ivecera@redhat.com>
Cc: Michal Jaron <michalx.jaron@intel.com>,
Kamil Maziarz <kamil.maziarz@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net v2] i40e: Fix not setting xps_cpus after reset
Date: Fri, 30 Sep 2022 08:07:51 -0700 [thread overview]
Message-ID: <23d35fdb-6f99-466f-a557-ccb044579bd1@intel.com> (raw)
In-Reply-To: <20220930132133.4d312070@p1.luc.cera.cz>
On 9/30/2022 4:21 AM, Ivan Vecera wrote:
> On Thu, 29 Sep 2022 08:54:39 -0700
> Tony Nguyen <anthony.l.nguyen@intel.com> wrote:
>
>> On 9/29/2022 8:47 AM, Tony Nguyen wrote:
>>> I'm not sure exactly where you are referring to when you say upstream,
>>> but it is still currently on the IWL trees [1].
>>
>> ...
>>
>>> [1]
>>> https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/?h=dev-queue&id=e312239075d77f11b45c3997a4e89153393c259d
>>
>> Sorry, gave the wrong link/commit. Should be:
>> https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/?h=dev-queue&id=aea4f7bb6c656b852771747538ca264b72967055
>
> Hmm, ok... it is now in next repo... I'm a little bit confused why the patch with Fixes: tag is present in next-queue repo.
> This is not a -next material or is it?
For net patches, they are applied to both trees to help minimize
conflicts when they get rebased into next. Here's the net link of it
[1], I just used the -next link as it's what I had handy.
Thanks,
Tony
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git/commit/?h=dev-queue&id=7670a1167933ca825bbe4d3614b6936e1a6f7c19
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-09-30 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 14:02 [Intel-wired-lan] [PATCH net v2] i40e: Fix not setting xps_cpus after reset Kamil Maziarz
2022-09-22 5:55 ` G, GurucharanX
2022-09-29 7:53 ` Ivan Vecera
2022-09-29 15:47 ` Tony Nguyen
2022-09-29 15:54 ` Tony Nguyen
2022-09-30 11:21 ` Ivan Vecera
2022-09-30 15:07 ` 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=23d35fdb-6f99-466f-a557-ccb044579bd1@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=kamil.maziarz@intel.com \
--cc=michalx.jaron@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