From: Alan Cooper <alcooperx@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>,
Felipe Balbi <balbi@kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: Conflicting PCI ID in bdc driver
Date: Wed, 13 Jan 2021 15:07:03 -0500 [thread overview]
Message-ID: <CAOGqxeWYcsQMRfGQeefufriba33hZ7__g+77dzwE=kT=csWywA@mail.gmail.com> (raw)
In-Reply-To: <X/7KJ1gbcnQDUWx3@kroah.com>
Just to be clear, I'm only interested in removing the bdc_pci.c file
and not the rest of the BDC driver.
I talked to the hardware engineer that designed the BDC core and he
said that there were only a few of these PCIe/FPGA boards. They were
used for development until the BDC core was added to various ARM SoC's
as a memory mapped platform bus controller. The original PCIe boards
are no longer in existence.
Al
On Wed, Jan 13, 2021 at 5:22 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jan 12, 2021 at 02:51:05PM -0500, Alan Cooper wrote:
> > I just checked with the hardware engineer that designed the BDC core.
> > The BDC PCI driver was used with an FPGA/PCIe board for design
> > verification and no one should be using this driver. I'll send a patch
> > that will remove this driver.
>
> Based on the recent patches for this driver on the mailing list, are you
> sure that no one is using this? We can't delete a driver that people
> are using.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-01-13 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 19:34 Conflicting PCI ID in bdc driver Patrik Jakobsson
2021-01-11 20:30 ` Greg Kroah-Hartman
2021-01-11 22:02 ` Patrik Jakobsson
2021-01-12 1:06 ` Alan Cooper
2021-01-12 8:42 ` Patrik Jakobsson
2021-01-12 8:58 ` Greg Kroah-Hartman
2021-01-12 19:51 ` Alan Cooper
2021-01-13 10:23 ` Greg Kroah-Hartman
2021-01-13 20:07 ` Alan Cooper [this message]
2021-01-14 7:49 ` Greg Kroah-Hartman
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='CAOGqxeWYcsQMRfGQeefufriba33hZ7__g+77dzwE=kT=csWywA@mail.gmail.com' \
--to=alcooperx@gmail.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.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.