public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: drivers changes for v4.2
Date: Sat, 30 May 2015 17:36:51 +0200	[thread overview]
Message-ID: <5569D913.4030406@free-electrons.com> (raw)
In-Reply-To: <20150530141210.GE13641@io.lakedaemon.net>

Hi Jason,

On 30/05/2015 16:12, Jason Cooper wrote:
> Hey Gregory,
> 
> On Fri, May 29, 2015 at 11:52:01PM +0200, Gregory CLEMENT wrote:
>> Hi,
>>
>> Here is the first pull request for drivers for mvebu for v4.2.
>> It depends on the mvebu/fixes branch which have been merged in the
>> mvebu/drivers branch
>>
>> Gregory
>>
>> The following changes since commit 885dbd154b2f2ee305cec6fd0a162e1a77ae2b06:
>>
>>   Revert "bus: mvebu-mbus: make sure SDRAM CS for DMA don't overlap the MBus bridge window" (2015-05-28 11:14:31 +0200)
>>
>> are available in the git repository at:
>>
>>   git://git.infradead.org/linux-mvebu.git tags/mvebu-drivers-4.2
>>
>> for you to fetch changes up to bfa1ce5f38938cc9e6c7f2d1011f88eba2b9e2b2:
>>
>>   bus: mvebu-mbus: add mv_mbus_dram_info_nooverlap() (2015-05-28 12:21:08 +0200)
>>
>> ----------------------------------------------------------------
>> mvebu drivers change for 4.2
>>
>> mvebu-mbus: add mv_mbus_dram_info_nooverlap() needed for the new
>> Marvell crypto driver
>>
>> ----------------------------------------------------------------
>> Thomas Petazzoni (1):
>>       bus: mvebu-mbus: add mv_mbus_dram_info_nooverlap()
>>
>>  drivers/bus/mvebu-mbus.c | 117 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  include/linux/mbus.h     |   5 +++++
>>  2 files changed, 122 insertions(+)
>>
> 
> I don't see this in mvebu/for-next...  Not earth shattering, just mentioning
> it.  This commit is adding a new function with no callers, so the chances of
> conflicts / build failures is minimal.

Usually as soon as I apply a patch set, I also merge the branch in
mvebu/for-next and I push it on infradead. However it is still possible
that I forgot to push it. So I checked and this patch is part of mvebu/for-next:
http://git.infradead.org/linux-mvebu.git/commit/bfa1ce5f38938cc9e6c7f2d1011f88eba2b9e2b2

And it was even pulled in linux-next:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=bfa1ce5f38938cc9e6c7f2d1011f88eba2b9e2b2

So this time we are fine, but thanks for having a look on it.

Gregory

> 
> thx,
> 
> Jason.
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2015-05-30 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 21:52 [GIT PULL] ARM: mvebu: drivers changes for v4.2 Gregory CLEMENT
2015-05-30 14:12 ` Jason Cooper
2015-05-30 15:36   ` Gregory CLEMENT [this message]
2015-05-30 16:04     ` Jason Cooper
2015-06-01 15:36 ` Arnd Bergmann

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=5569D913.4030406@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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