[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150717164513.GR16517@opensource.wolfsonmicro.com>
Date: Fri, 17 Jul 2015 17:45:13 +0100
From: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To: Nariman Poushin <nariman@...nsource.wolfsonmicro.com>
Cc: Mark Brown <broonie@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
Subject: Re: linux-next: build warnings after merge of the regmap tree
On Fri, Jul 17, 2015 at 04:29:55PM +0100, Nariman Poushin wrote:
> 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
If you include myself and Richard Fitzgerald
(rf@...nsource.wolfsonmicro.com) one of us will pick things up if
there are any issues.
Thanks,
Charles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists