From: "Krzysztof Wilczyński" <kw@linux.com>
To: phasta@kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bingbu Cao <bingbu.cao@linux.intel.com>
Subject: Re: [PATCH] PCI: Check BAR index for validity
Date: Wed, 5 Mar 2025 16:14:30 +0900 [thread overview]
Message-ID: <20250305071430.GA847772@rocinante> (raw)
In-Reply-To: <d667d29337c49ebebb82d69b12bd48cad66ce595.camel@mailbox.org>
Hello,
[...]
> Shall I send a v2 or do you want to rebase, Bjorn?
If the changes are relatively small, then you can send a patch top be
applied atop the existing branch. I will squash things as needed.
Otherwise, a v2.
> sry bout that.
No worries. Things happen. We can fix everything. :)
Krzysztof
next prev parent reply other threads:[~2025-03-05 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 14:31 [PATCH] PCI: Check BAR index for validity Philipp Stanner
2025-03-04 22:42 ` Bjorn Helgaas
2025-03-05 7:03 ` Philipp Stanner
2025-03-05 7:14 ` Krzysztof Wilczyński [this message]
2025-03-10 2:43 ` kernel test robot
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=20250305071430.GA847772@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=bingbu.cao@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=phasta@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