From: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Subject: Re: linux-next: build warnings after merge of the regmap tree
Date: Fri, 17 Jul 2015 16:29:55 +0100 [thread overview]
Message-ID: <20150717152955.GI21939@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150717103450.GJ11162@sirena.org.uk>
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
> On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
>
> > What is the best course of action here? I am more than happy to help with
> > whatever is needed but unsure of the etiquette here and also not sure
> > what I can do.
>
> > Clearly there are some clients that need updating but they were not
> > present in the regmap tree, so is the correct thing to do to merge
> > in the mfd and sound-asoc tree and provide a fixup commit?
>
> > Just let me know and I am happy to do whatever is deemed correct.
>
> Please send patches fixing the problems you have introduced.
I have sent the patches to fix the build errors you found Stephen.
Just wanted to let you guys know I will be on vacation for 1 week,
so if there are any issues they might not be addressed until then.
Thanks
Nariman
next prev parent reply other threads:[~2015-07-17 15:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 4:39 linux-next: build warnings after merge of the regmap tree Stephen Rothwell
2015-07-17 9:44 ` Nariman Poushin
2015-07-17 10:34 ` Mark Brown
2015-07-17 14:09 ` [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Nariman Poushin
2015-07-17 17:57 ` Mark Brown
2015-07-20 1:59 ` Stephen Rothwell
2015-09-05 14:08 ` Geert Uytterhoeven
2015-09-18 3:50 ` Stephen Rothwell
2015-09-18 8:33 ` Charles Keepax
2015-09-18 10:25 ` Mark Brown
2015-07-17 14:11 ` [PATCH 2/2] ASoC: wm5110: Use reg_sequence for multi_reg_write/register_patch Nariman Poushin
2015-07-17 15:29 ` Nariman Poushin [this message]
2015-07-17 16:45 ` linux-next: build warnings after merge of the regmap tree Charles Keepax
-- strict thread matches above, loose matches on Subject: below --
2013-03-27 4:47 Stephen Rothwell
2013-03-27 10:24 ` Mark Brown
2013-03-27 10:35 ` Stephen Rothwell
2011-08-09 3:21 Stephen Rothwell
2011-08-09 15:01 ` 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=20150717152955.GI21939@opensource.wolfsonmicro.com \
--to=nariman@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rf@opensource.wolfsonmicro.com \
--cc=sfr@canb.auug.org.au \
/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).