From: Jacob Keller <jacob.e.keller@intel.com>
To: "Samal, Anil" <anil.samal@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Pepiak, Leszek" <leszek.pepiak@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
"Czapnik, Lukasz" <lukasz.czapnik@intel.com>
Subject: Re: [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC
Date: Mon, 10 Jun 2024 11:57:55 -0700 [thread overview]
Message-ID: <edd6f59b-b0ab-4623-86e2-865acf90cb8f@intel.com> (raw)
In-Reply-To: <DS7PR11MB6037D67A617D1C6FC667EEF799C42@DS7PR11MB6037.namprd11.prod.outlook.com>
On 6/8/2024 11:14 AM, Samal, Anil wrote:
> Hi Jacob,
> Can you please help me with the branch name that I should rebase?
> Last time I rebased to "dev-queue" branch of "git clone git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git".
>
> Let me know, if I should use a different branch for rebasing.
>
> Thanks
> Anil
>
That is typically the correct branch. I suspect what happened is that
other work got applied to this branch between when you fetched and when
you sent the work. (Or possibly between when you sent and when I tried
to apply).
next prev parent reply other threads:[~2024-06-10 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:51 [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC Anil Samal
2024-05-24 13:51 ` [PATCH iwl-next v3 1/3] ice: Extend Sideband Queue command to support flags Anil Samal
2024-05-24 20:43 ` [Intel-wired-lan] " Paul Menzel
2024-05-24 21:12 ` Jacob Keller
2024-05-24 13:51 ` [PATCH iwl-next v3 2/3] ice: Implement driver functionality to dump fec statistics Anil Samal
2024-05-24 13:51 ` [PATCH iwl-next v3 3/3] ice: Implement driver functionality to dump serdes equalizer values Anil Samal
2024-06-24 16:28 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-05-24 21:11 ` [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC Jacob Keller
2024-06-08 18:14 ` Samal, Anil
2024-06-10 18:57 ` Jacob Keller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 12:58 Anil Samal
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=edd6f59b-b0ab-4623-86e2-865acf90cb8f@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anil.samal@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=leszek.pepiak@intel.com \
--cc=lukasz.czapnik@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).