Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Konrad Dybcio <konradybcio@kernel.org>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	usb4-upstream@oss.qualcomm.com,
	Raghavendra Thoorpu <rthoorpu@qti.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v4 0/4] Prepwork for non-PCIe NHI/TBT hosts
Date: Wed, 20 May 2026 12:10:38 +0200	[thread overview]
Message-ID: <20260520101038.GE8580@black.igk.intel.com> (raw)
In-Reply-To: <20260515-topic-usb4_nonpcie_prepwork-v4-0-5c818378243e@oss.qualcomm.com>

Hi Konrad,

On Fri, May 15, 2026 at 02:38:40PM +0200, Konrad Dybcio wrote:
> Konrad Dybcio (4):
>       thunderbolt: Move pci_device out of tb_nhi
>       thunderbolt: Separate out common NHI bits
>       thunderbolt: Require nhi->ops be valid
>       thunderbolt: Add some more descriptive probe error messages

I was about to apply this one it does not apply anymore on top of my
thunderbolt.git/next. Can you rebase this on top of the latest next branch?

Thanks!

      parent reply	other threads:[~2026-05-20 10:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 12:38 [PATCH v4 0/4] Prepwork for non-PCIe NHI/TBT hosts Konrad Dybcio
2026-05-15 12:38 ` [PATCH v4 1/4] thunderbolt: Move pci_device out of tb_nhi Konrad Dybcio
2026-05-15 12:38 ` [PATCH v4 2/4] thunderbolt: Separate out common NHI bits Konrad Dybcio
2026-05-15 12:38 ` [PATCH v4 3/4] thunderbolt: Require nhi->ops be valid Konrad Dybcio
2026-05-15 12:38 ` [PATCH v4 4/4] thunderbolt: Add some more descriptive probe error messages Konrad Dybcio
2026-05-20 10:10 ` Mika Westerberg [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=20260520101038.GE8580@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rthoorpu@qti.qualcomm.com \
    --cc=usb4-upstream@oss.qualcomm.com \
    --cc=westeri@kernel.org \
    /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