From: Thor Thayer <thor.thayer@linux.intel.com>
To: Marek Vasut <marek.vasut@gmail.com>,
cyrille.pitchen@wedev4u.fr, dwmw2@infradead.org,
computersforpeace@gmail.com, boris.brezillon@free-electrons.com,
richard@nod.at
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: Allow Cadence QSPI support for ARM64
Date: Fri, 6 Oct 2017 10:04:25 -0500 [thread overview]
Message-ID: <d40be7de-0235-a11a-bb0a-899e3e410779@linux.intel.com> (raw)
In-Reply-To: <d7b8e1f7-b007-c6d1-bcb3-ea096f288a7c@gmail.com>
On 10/06/2017 10:00 AM, Marek Vasut wrote:
> On 10/06/2017 04:56 PM, Thor Thayer wrote:
>> gentle ping...
>>
>>
>> On 09/29/2017 11:07 AM, thor.thayer@linux.intel.com wrote:
>>> From: Thor Thayer <thor.thayer@linux.intel.com>
>>>
>>> Allow ARM64 support for the Cadence QSPI interface by
>>> adding ARM64 as a dependency.
>>>
>>> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
>
> Reviewed-by: Marek Vasut <marek.vasut@gmail.com>
>
> I presume it was tested on Stratix 10 ?
>
Yes, that is correct. Thanks for the review!
>>> ---
>>> drivers/mtd/spi-nor/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/mtd/spi-nor/Kconfig b/drivers/mtd/spi-nor/Kconfig
>>> index 69c638dd0484..f26aaa6d1430 100644
>>> --- a/drivers/mtd/spi-nor/Kconfig
>>> +++ b/drivers/mtd/spi-nor/Kconfig
>>> @@ -50,7 +50,7 @@ config SPI_ATMEL_QUADSPI
>>> config SPI_CADENCE_QUADSPI
>>> tristate "Cadence Quad SPI controller"
>>> - depends on OF && (ARM || COMPILE_TEST)
>>> + depends on OF && (ARM || ARM64 || COMPILE_TEST)
>>> help
>>> Enable support for the Cadence Quad SPI Flash controller.
>>>
>>
>
>
next prev parent reply other threads:[~2017-10-06 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 16:07 [PATCH] mtd: spi-nor: Allow Cadence QSPI support for ARM64 thor.thayer
2017-10-06 14:56 ` Thor Thayer
2017-10-06 15:00 ` Marek Vasut
2017-10-06 15:04 ` Thor Thayer [this message]
2017-10-10 16:30 ` Cyrille Pitchen
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=d40be7de-0235-a11a-bb0a-899e3e410779@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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