From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v3] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info()
Date: Wed, 14 Sep 2016 19:15:59 +0530 [thread overview]
Message-ID: <20160914134559.GM13920@localhost> (raw)
In-Reply-To: <8760pyd41s.fsf@free-electrons.com>
On Wed, Sep 14, 2016 at 03:06:07PM +0200, Gregory CLEMENT wrote:
> Hi,
>
> On lun., sept. 05 2016, Stefan Roese <sr@denx.de> wrote:
>
> > This patch provides a stub function for mvebu_mbus_get_io_win_info(),
> > which will be used for all non-Orion (ARM32 MVEBU) platforms for
> > compile test coverage.
> >
> > On such platforms this function will return an error so that drivers
> > might detect a potential problem.
>
> Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>
> Vinod, if you happy with the second patch of the series you can apply
> both patches on your tree. It will allow to keep the bisactibility, and
> as I didn't have any commit modifying these file in my trees it won't
> generate merge conflict.
Okay, somehow I dont see this in my queue. Can you guys pls resend.
Thanks
--
~Vinod
next prev parent reply other threads:[~2016-09-14 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:24 [PATCH 1/2 v3] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() Stefan Roese
2016-09-05 7:25 ` [PATCH 2/2 v5] dmaengine: mv_xor: Add support for IO (PCIe) src/dst areas Stefan Roese
2016-09-14 13:06 ` [PATCH 1/2 v3] bus: mvebu-mbus: Provide stub function for mvebu_mbus_get_io_win_info() Gregory CLEMENT
2016-09-14 13:45 ` Vinod Koul [this message]
2016-09-15 5:36 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2016-09-15 5:37 Stefan Roese
2016-09-15 15:44 ` Vinod Koul
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=20160914134559.GM13920@localhost \
--to=vinod.koul@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.