From: Anatolij Gustschin <agust@denx.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Moritz Fischer <mdf@kernel.org>,
atull@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpga-manager: altera-ps-spi: preserve nCONFIG state
Date: Mon, 16 Apr 2018 10:34:22 +0200 [thread overview]
Message-ID: <20180416103422.5229b5fe@crub> (raw)
In-Reply-To: <20180416081008.GA31469@kroah.com>
On Mon, 16 Apr 2018 10:10:08 +0200
Greg KH gregkh@linuxfoundation.org wrote:
...
>> as discussed. Can you please take this bugfix for 4.17?
>> I rebased it against next.
>
>Is it also needed in any older kernel versions?
It is needed in versions starting from v4.14.
thanks,
Anatolij
prev parent reply other threads:[~2018-04-16 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 18:33 [PATCH] fpga-manager: altera-ps-spi: preserve nCONFIG state Moritz Fischer
2018-04-16 8:10 ` Greg KH
2018-04-16 8:34 ` Anatolij Gustschin [this message]
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=20180416103422.5229b5fe@crub \
--to=agust@denx.de \
--cc=atull@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@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;
as well as URLs for NNTP newsgroup(s).