Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1186685
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build warnings after merge of the regmap tree |
| Date | 2015-07-17 12:40 +0200 |
| Message-ID | <pNbdD-2PM-5@gated-at.bofh.it> (permalink) |
| References | <pN5Bf-3cV-5@gated-at.bofh.it> <pNarg-1FW-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build warnings after merge of the regmap tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-07-17 06:40 +0200
Re: linux-next: build warnings after merge of the regmap tree Nariman Poushin <nariman@opensource.wolfsonmicro.com> - 2015-07-17 11:50 +0200
Re: linux-next: build warnings after merge of the regmap tree Mark Brown <broonie@kernel.org> - 2015-07-17 12:40 +0200
[PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Nariman Poushin <nariman@opensource.wolfsonmicro.com> - 2015-07-17 16:10 +0200
[PATCH 2/2] ASoC: wm5110: Use reg_sequence for multi_reg_write/register_patch Nariman Poushin <nariman@opensource.wolfsonmicro.com> - 2015-07-17 16:20 +0200
csiph-web