linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info()
Date: Thu, 1 Sep 2016 14:23:29 +0200	[thread overview]
Message-ID: <20160901122329.GA4367@lunn.ch> (raw)
In-Reply-To: <20160901093904.26564-1-sr@denx.de>

Hi Stefan

> +	/*
> +	 * On all ARM32 MVEBU platforms with MBus support, this stub
> +	 * function will not get called. The real function from the
> +	 * MBus driver is called instead. ARM64 MVEBU platforms like
> +	 * the Armada 3700 could do use the mv_xor device which calls

could us, or do us, but not both.

Thanks
	Andrew

      parent reply	other threads:[~2016-09-01 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  9:39 [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() Stefan Roese
2016-09-01  9:39 ` [PATCH 2/2 v4] dmaengine: mv_xor: Add support for IO (PCIe) src/dst areas Stefan Roese
2016-09-01 11:31 ` [PATCH 1/2 v2] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() kbuild test robot
2016-09-01 12:23 ` Andrew Lunn [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=20160901122329.GA4367@lunn.ch \
    --to=andrew@lunn.ch \
    --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;
as well as URLs for NNTP newsgroup(s).