lkml.org 
[lkml]   [2013]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [RFC] next cycle fun: ->release() API change
From
On Sat, May 11, 2013 at 2:06 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Less boilerplate? We used to pass inode to fput() as well, but
> switched to passing file alone...

.. and that was painful.

The advantage has to be balanced against the pain it causes. I'm not
seeing the advantage here as being worth it. If this kind of thing not
only causes way more churn, _and_ it causes us to pick a new (worse)
name just because it also forces a non-compatible ABI, I'm really
doubtful.

I mean, if we had *other* reasons for the churn, and the name needed
to change anyway, then maybe, but..

Linus


\
 
 \ /
  Last update: 2013-05-11 23:41    [W:0.087 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site