From: vigneshr@ti•com (Vignesh R)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v5 4/5] ARM: dts: DRA7: add entry for qspi mmap region
Date: Fri, 18 Dec 2015 11:20:44 +0530 [thread overview]
Message-ID: <56739EB4.6040804@ti.com> (raw)
In-Reply-To: <20151217184557.GC23396@atomide.com>
On 12/18/2015 12:15 AM, Tony Lindgren wrote:
> * Rob Herring <robh@kernel•org> [151211 07:10]:
>> On Fri, Dec 11, 2015 at 09:39:59AM +0530, Vignesh R wrote:
>>> Add qspi memory mapped region entries for DRA7xx based SoCs. Also,
>>> update the binding documents for the controller to document this change.
>>>
>>> Signed-off-by: Vignesh R <vigneshr@ti•com>
>>
>> Acked-by: Rob Herring <robh@kernel•org>
>
> Vignes, are patches 4 and 5 safe to apply separately already or
> do things break if we do that?
Yes, 4 and 5 can be applied separately w/o driver changes.
--
Regards
Vignesh
next prev parent reply other threads:[~2015-12-18 5:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 4:09 [PATCH v5 0/5] Add memory mapped read support for ti-qspi Vignesh R
2015-12-11 4:09 ` [PATCH v5 1/5] spi: introduce accelerated read support for spi flash devices Vignesh R
2015-12-11 4:09 ` [PATCH v5 2/5] spi: spi-ti-qspi: add mmap mode read support Vignesh R
2015-12-11 4:09 ` [PATCH v5 3/5] mtd: devices: m25p80: add support for mmap read request Vignesh R
2016-02-09 19:36 ` Mark Brown
2016-02-11 5:33 ` Vignesh R
2016-02-12 22:37 ` Mark Brown
2016-02-16 8:00 ` Vignesh R
2016-02-16 12:38 ` Mark Brown
2016-02-17 16:11 ` R, Vignesh
2016-02-24 12:21 ` Vignesh R
2015-12-11 4:09 ` [PATCH v5 4/5] ARM: dts: DRA7: add entry for qspi mmap region Vignesh R
2015-12-11 15:09 ` Rob Herring
2015-12-17 18:45 ` Tony Lindgren
2015-12-18 5:50 ` Vignesh R [this message]
2015-12-18 16:42 ` Tony Lindgren
2015-12-11 4:10 ` [PATCH v5 5/5] ARM: dts: AM4372: " Vignesh R
2015-12-21 12:03 ` [PATCH v5 0/5] Add memory mapped read support for ti-qspi Vignesh R
2016-01-05 5:20 ` Vignesh R
2016-01-05 18:19 ` Mark Brown
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=56739EB4.6040804@ti.com \
--to=vigneshr@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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