Re: [PATCH 1/2] regmap: only call custom reg_update_bits() if reg is marked volatile

From
Mark Brown <broonie@kernel.org>
Date
2015-10-06 13:39:55
Also in
lkml
Reply to
Jon Ringle, 2015-10-06
On Tue, Oct 06, 2015 at 08:50:43AM -0400, Jon Ringle wrote:
4) David should then merge the regmap for-next branch into net-next
What I generally do (and what's best practice in general for cross tree
work) is apply patches on topic branches and then create a signed tag
for anything that's being merged into another tree.  That both means
we've got a signed tag for the chain of trust in the code and means that
only the specific dependency gets pulled into other trees rather than
everything that's queued.  Minimising what's pulled in makes pull
requests look cleaner and avoids noise from in development code
appearing in other trees (eg, any bugs in other code that's not quite
ready won't get merged).

In my specific trees nobody should ever merge my for-FOO branches,
they're rebuilt frequently - the topic branches are fast forward only
and intended for that (though like I say a signed tag is best).  Linus
complains about keeping the for-FOO branches fast forward
only.
5) I will submit a new patch to net-next for the encx24j600 driver
that should build against the regmap changes
Sound like a good plan?
Makes sense to me modulo the signed tag thing above.

Attachments

Thread (10 messages) 10 messages, 4 authors, last reply 2015-10-06
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help