From: Bjorn Helgaas <helgaas@kernel.org>
To: Ren Zhijie <renzhijie2@huawei.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jon Mason <jdmason@kudzu.us>,
kishon@ti.com, lpieralisi@kernel.org, kw@linux.com,
bhelgaas@google.com, Frank.Li@nxp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] PCI: endpoint: Fix Kconfig dependency
Date: Fri, 15 Jul 2022 16:24:11 -0500 [thread overview]
Message-ID: <20220715212411.GA1192563@bhelgaas> (raw)
In-Reply-To: <cdaf434f-90d5-696f-2a60-5946ecefcf0b@huawei.com>
On Sat, Jul 09, 2022 at 10:50:53AM +0800, Ren Zhijie wrote:
> Hi, Bjorn and jon
>
> Just a friendly ping ...
>
> Is this patch be merged or squashed?
Jon has to take care of this because I don't have the VNTB patches in
my tree.
> > > > > > drivers/pci/endpoint/functions/Kconfig | 1 +
> > > > > > 1 file changed, 1 insertion(+)
> > > > > >
> > > > > > diff --git a/drivers/pci/endpoint/functions/Kconfig b/drivers/pci/endpoint/functions/Kconfig
> > > > > > index 362555b024e8..9beee4f0f4ee 100644
> > > > > > --- a/drivers/pci/endpoint/functions/Kconfig
> > > > > > +++ b/drivers/pci/endpoint/functions/Kconfig
> > > > > > @@ -29,6 +29,7 @@ config PCI_EPF_NTB
> > > > > > config PCI_EPF_VNTB
> > > > > > tristate "PCI Endpoint NTB driver"
> > > > > > depends on PCI_ENDPOINT
> > > > > > + depends on NTB
> > > > > > select CONFIGFS_FS
> > > > > > help
> > > > > > Select this configuration option to enable the Non-Transparent
next prev parent reply other threads:[~2022-07-15 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 1:19 [PATCH -next] PCI: endpoint: Fix Kconfig dependency Ren Zhijie
2022-06-27 19:57 ` Bjorn Helgaas
2022-06-27 20:07 ` Bjorn Helgaas
2022-06-27 20:25 ` Bjorn Helgaas
2022-06-29 18:51 ` Randy Dunlap
2022-07-09 2:50 ` Ren Zhijie
2022-07-15 21:24 ` Bjorn Helgaas [this message]
2022-08-12 14:06 ` Jon Mason
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=20220715212411.GA1192563@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=jdmason@kudzu.us \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rdunlap@infradead.org \
--cc=renzhijie2@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.