From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] mfd: Provide MACRO to declare commonly defined MFD cell attributes
Date: Thu, 11 Feb 2016 09:46:23 +0000 [thread overview]
Message-ID: <20160211094623.GH3782@x1> (raw)
In-Reply-To: <56BC4DF9.7050402@nvidia.com>
On Thu, 11 Feb 2016, Laxman Dewangan wrote:
>
> On Thursday 11 February 2016 02:40 PM, Lee Jones wrote:
> >On Wed, 10 Feb 2016, Laxman Dewangan wrote:
> >
> >>On Wednesday 10 February 2016 09:08 PM, Lee Jones wrote:
> >>>mfd: Provide MACRO to declare commonly defined MFD cell attributes
> >>>Cc: Laxman Dewangan <ldewangan@nvidia.com>
> >>>Signed-off-by: Lee Jones <lee.jones@linaro.org>
> >>Build passed with this patch when using it.
> >>
> >>Acked-by: Laxman Dewangan <ldewangan@nvidia.com>
> >>
> >>Please let me know if you applying this. I am going to use the macro
> >>from this patch on max77620 series on next spin.
> >As you are the first user, just submit it as 0/1 of your set.
> >
>
> I saw that it is merged and available in linux-next 20160211.
> So it is fine to not submit this patch again and modify my patch
> assuming it is on tree.
I was going to handle that, but as you wish, either way is fine by
me.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-02-11 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 14:27 [PATCH] mfd: Provide MACRO to declare commonly defined MFD cell attributes Lee Jones
2016-02-09 15:20 ` Laxman Dewangan
2016-02-10 12:38 ` Laxman Dewangan
2016-02-10 15:38 ` [PATCH v2] " Lee Jones
2016-02-10 17:50 ` Laxman Dewangan
2016-02-11 9:10 ` Lee Jones
2016-02-11 9:01 ` Laxman Dewangan
2016-02-11 9:46 ` Lee Jones [this message]
2016-02-26 10:43 ` Andy Shevchenko
2016-02-10 15:39 ` [PATCH v2] mfd: ab8500: Provide a small example using new MFD cell MACROs Lee Jones
2016-02-15 9:58 ` Linus Walleij
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=20160211094623.GH3782@x1 \
--to=lee.jones@linaro.org \
--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).