On Thu, Sep 14, 2017 at 10:56 AM, wrote:
Hi Matthew,
>
> Hi Alan,
>
> s/mixxed/mixed/
>
OK, I'll fix that.
Alan
> On Wed, 13 Sep 2017, Alan Tull wrote:
>
>> The fpga menuconfig has gotten messy. The bridges and managers are
>> mixxed together.
>>
>> *
On Thu, Sep 14, 2017 at 10:56 AM, wrote:
Hi Matthew,
>
> Hi Alan,
>
> s/mixxed/mixed/
>
OK, I'll fix that.
Alan
> On Wed, 13 Sep 2017, Alan Tull wrote:
>
>> The fpga menuconfig has gotten messy. The bridges and managers are
>> mixxed together.
>>
>> * Separate the bridges and things
Hi Alan,
s/mixxed/mixed/
On Wed, 13 Sep 2017, Alan Tull wrote:
The fpga menuconfig has gotten messy. The bridges and managers are
mixxed together.
* Separate the bridges and things dependent on CONFIG_FPGA_BRIDGE
from the managers.
* Group the managers by vendor in order that they were
Hi Alan,
s/mixxed/mixed/
On Wed, 13 Sep 2017, Alan Tull wrote:
The fpga menuconfig has gotten messy. The bridges and managers are
mixxed together.
* Separate the bridges and things dependent on CONFIG_FPGA_BRIDGE
from the managers.
* Group the managers by vendor in order that they were
The fpga menuconfig has gotten messy. The bridges and managers are
mixxed together.
* Separate the bridges and things dependent on CONFIG_FPGA_BRIDGE
from the managers.
* Group the managers by vendor in order that they were added
to the kernel.
The following is what the menuconfig ends up
The fpga menuconfig has gotten messy. The bridges and managers are
mixxed together.
* Separate the bridges and things dependent on CONFIG_FPGA_BRIDGE
from the managers.
* Group the managers by vendor in order that they were added
to the kernel.
The following is what the menuconfig ends up
6 matches
Mail list logo