On Sat, Jan 17, 2015 at 03:29:01PM -0800, Greg KH wrote:
> On Sat, Dec 13, 2014 at 03:58:46PM +0100, Loïc Pefferkorn wrote:
> > > >>> Don't hide "implementation of locks" in functions like this, it only
> > > >>> causes problems. This code ha
> >>> Don't hide "implementation of locks" in functions like this, it only
> >>> causes problems. This code has layers of layers of layers of
> >>> abstractions due to it wanting to be originally ported to other
> >>> operating systems and lots of different kernel versions of Linux itself.
> >>> U
On Tue, Dec 02, 2014 at 02:11:33PM -0700, Andreas Dilger wrote:
> On Nov 28, 2014, at 11:50 AM, Greg KH wrote:
> > On Thu, Nov 27, 2014 at 07:34:10PM +0100, Loïc Pefferkorn wrote:
> >> Hello Greg,
> >>
> >> After some investigation, I think that removing
On Fri, Nov 28, 2014 at 02:22:07PM -0800, Greg KH wrote:
>
> That's even worse than I imagined. Putting sparse markings on these
> function calls is just papering over nonsense. Please work on unwinding
> the mess so that you don't need callbacks for locks, that is an
> abstraction that isn't ne
Hello Greg,
After some investigation, I think that removing these wrappers is not going to
improve the code readability:
On Wed, Nov 26, 2014 at 12:54:43PM -0800, Greg KH wrote:
> On Wed, Nov 26, 2014 at 05:15:48PM +0100, Loic Pefferkorn wrote:
> > Add __acquires() and __releases() function anno
On Wed, Nov 26, 2014 at 12:54:43PM -0800, Greg KH wrote:
>
> Ugh, how horrid, please just delete these functions and push down the
> spin_lock/unlock calls down into the places these are called.
>
> Same for these.
>
> Same thing here.
Hello Greg,
Thanks for your comments, I will write a v2.
-
