Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1472356
| From | Catalin Marinas <catalin.marinas@arm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/2] jump_labels: Allow array initialisers |
| Date | 2016-08-30 11:30 +0200 |
| Message-ID | <sbNwK-2W9-13@gated-at.bofh.it> (permalink) |
| References | <sa6Dv-3XY-27@gated-at.bofh.it> <sa6Dw-3XY-35@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Aug 25, 2016 at 06:26:31PM +0100, Catalin Marinas wrote: > diff --git a/Documentation/static-keys.txt b/Documentation/static-keys.txt > index 477927becacb..fd490f8b1cfa 100644 > --- a/Documentation/static-keys.txt > +++ b/Documentation/static-keys.txt > @@ -15,6 +15,8 @@ The updated API replacements are: > > DEFINE_STATIC_KEY_TRUE(key); > DEFINE_STATIC_KEY_FALSE(key); > +DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count); > +DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count); > static_branch_likely() > static_branch_unlikely() > > @@ -140,6 +142,12 @@ static_branch_inc(), will change the branch back to true. Likewise, if the > key is initialized false, a 'static_branch_inc()', will change the branch to > true. And then a 'static_branch_dec()', will again make the branch false. > > +Where an array of keys is required, it can be defined as: > + > + DEFINE_STATIC_KEY_ARRAY_TRUE(keys, count); > + > +or: > + DEFINE_STATIC_KEY_ARRAY_FALSE(keys, count); Nitpick to myself: for consistency, we need an empty line between "or:" and "DEFINE_STATIC_KEY_ARRAY_FALSE" (I fixed it locally). -- Catalin
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 1/2] jump_labels: Allow array initialisers Catalin Marinas <catalin.marinas@arm.com> - 2016-08-25 19:30 +0200 Re: [PATCH 1/2] jump_labels: Allow array initialisers Catalin Marinas <catalin.marinas@arm.com> - 2016-08-30 11:30 +0200
csiph-web