[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3c40d1758b4ad0a71f826c5423ea4eeb@sw-optimization.com>
Date: Mon, 12 Nov 2018 08:59:58 +0100
From: Eric Schwarz <eas@...optimization.com>
To: Alan Tull <atull@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Moritz Fischer <mdf@...nel.org>, linux-kernel@...r.kernel.org,
linux-fpga@...r.kernel.org
Subject: Re: [PATCH 0/4] patches for FPGA
Hello Alan,
Am 07.11.2018 18:51, schrieb Alan Tull:
> Hi Greg,
>
> Please take these four small fpga fixes patches. They
> have been reviewed on the mailing list and apply
> cleanly on current linux-next and char-misc-testing.
>
> Thanks,
> Alan
>
> Anatolij Gustschin (1):
> fpga: altera-cvp: fix 'bad IO access' on x86_64
>
> Andreas Puhm (1):
> fpga: altera-cvp: Fix registration for CvP incapable devices
>
> Mike Looijmans (1):
> zynq-fpga: Only route PR via PCAP when required
>
> YueHaibing (1):
> fpga: dfl: fme: remove set but not used variable 'priv'
>
> drivers/fpga/altera-cvp.c | 15 +++++++++++++--
> drivers/fpga/dfl-fme-pr.c | 2 --
> drivers/fpga/zynq-fpga.c | 4 ++++
> 3 files changed, 17 insertions(+), 4 deletions(-)
How is the backporting strategy for FPGA manager related bugfixes and
drivers?
Best regards
Eric
Powered by blists - more mailing lists