[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140606234501.b950d5d0.akpm@linux-foundation.org>
Date: Fri, 6 Jun 2014 23:45:01 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: paulmck@...ux.vnet.ibm.com
Cc: David Laight <David.Laight@...lab.com>,
"'Ken Helias'" <kenhelias@...email.de>,
lkml <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"b.a.t.m.a.n@...ts.open-mesh.org" <b.a.t.m.a.n@...ts.open-mesh.org>,
"bridge@...ts.linux-foundation.org"
<bridge@...ts.linux-foundation.org>
Subject: Re: [PATCH] list: Fix order of arguments for hlist_add_after(_rcu)
On Fri, 6 Jun 2014 10:22:51 -0700 "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> On Fri, Jun 06, 2014 at 03:56:52PM +0000, David Laight wrote:
> > From: Behalf Of Ken Helias
> > > All other add functions for lists have the new item as first argument and the
> > > position where it is added as second argument. This was changed for no good
> > > reason in this function and makes using it unnecessary confusing.
> > >
> > > Also the naming of the arguments in hlist_add_after was confusing. It was
> > > changed to use the same names as hlist_add_after_rcu.
> > ...
> > > -static inline void hlist_add_after_rcu(struct hlist_node *prev,
> > > - struct hlist_node *n)
> > > +static inline void hlist_add_after_rcu(struct hlist_node *n,
> > > + struct hlist_node *prev)
> >
> > It is rather a shame that the change doesn't generate a compilation
> > error for old source files.
>
> I am also a bit concerned by this.
>
yup. hlist_add_behind()?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists