Messages in this thread | | | Date | Mon, 4 Sep 2017 21:36:43 +0200 | From | Peter Zijlstra <> | Subject | Re: [tip:locking/core] locking/refcount: Create unchecked atomic_t implementation |
| |
On Mon, Sep 04, 2017 at 08:34:44PM +0300, Alexey Dobriyan wrote: > On Mon, Sep 04, 2017 at 02:37:24PM +0200, Peter Zijlstra wrote: > > - once.o refcount.o usercopy.o errseq.o > > -obj-y += string_helpers.o > > + once.o usercopy.o errseq.o string_helpers.o hexdump.o kstrtox.o > > + > > +obj-$(CONFIG_REFCOUNT_FULL) += refcount.o > > obj-$(CONFIG_TEST_STRING_HELPERS) += test-string_helpers.o > > -obj-y += hexdump.o > > obj-$(CONFIG_TEST_HEXDUMP) += test_hexdump.o > > -obj-y += kstrtox.o > > File per line so everything is not lumped together even if it is obj-y.
If that is policy mass convert everything and be done with it. Otherwise I'll continue to use the predominant pattern, which in this case is a giant obj-y +=. But mixed stuff is terribly annoying.
| |