* Boqun Feng wrote:
>
>
> On Sun, May 6, 2018, at 8:11 PM, Ingo Molnar wrote:
> >
> > * Boqun Feng wrote:
> >
> > > > The only change I made beyond a trivial build fix is that I also added
> > > > the release
> > > > atomics variants
* Boqun Feng wrote:
>
>
> On Sun, May 6, 2018, at 8:11 PM, Ingo Molnar wrote:
> >
> > * Boqun Feng wrote:
> >
> > > > The only change I made beyond a trivial build fix is that I also added
> > > > the release
> > > > atomics variants explicitly:
> > > >
> > > > +#define
On Sun, May 6, 2018, at 8:11 PM, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > The only change I made beyond a trivial build fix is that I also added
> > > the release
> > > atomics variants explicitly:
> > >
> > > +#define atomic_cmpxchg_release(v, o, n) \
> > >
On Sun, May 6, 2018, at 8:11 PM, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > The only change I made beyond a trivial build fix is that I also added
> > > the release
> > > atomics variants explicitly:
> > >
> > > +#define atomic_cmpxchg_release(v, o, n) \
> > > +
* Boqun Feng wrote:
> > The only change I made beyond a trivial build fix is that I also added the
> > release
> > atomics variants explicitly:
> >
> > +#define atomic_cmpxchg_release(v, o, n) \
> > + cmpxchg_release(&((v)->counter), (o), (n))
> > +#define
* Boqun Feng wrote:
> > The only change I made beyond a trivial build fix is that I also added the
> > release
> > atomics variants explicitly:
> >
> > +#define atomic_cmpxchg_release(v, o, n) \
> > + cmpxchg_release(&((v)->counter), (o), (n))
> > +#define atomic64_cmpxchg_release(v, o, n)
On Sat, May 05, 2018 at 03:27:51PM +0200, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > May I suggest the patch below? No change in functionality, but it
> > > documents the
> > > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > >
On Sat, May 05, 2018 at 03:27:51PM +0200, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > May I suggest the patch below? No change in functionality, but it
> > > documents the
> > > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > > cmpxchg()
> > > version.
* Boqun Feng wrote:
> > May I suggest the patch below? No change in functionality, but it documents
> > the
> > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > cmpxchg()
> > version. (Which the generic code does now in a rather roundabout
* Boqun Feng wrote:
> > May I suggest the patch below? No change in functionality, but it documents
> > the
> > lack of the cmpxchg_release() APIs and maps them explicitly to the full
> > cmpxchg()
> > version. (Which the generic code does now in a rather roundabout way.)
> >
>
> Hmm..
10 matches
Mail list logo