[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190116065304.GA26290@kroah.com>
Date: Wed, 16 Jan 2019 07:53:04 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Christian Brauner <christian@...uner.io>
Cc: Wei Yongjun <weiyongjun1@...wei.com>, devel@...verdev.osuosl.org,
tkjos@...roid.com, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org, arve@...roid.com,
joel@...lfernandes.org, maco@...roid.com
Subject: Re: [PATCH -next] binderfs: fix error return code in
binderfs_fill_super()
On Wed, Jan 16, 2019 at 07:28:26AM +0100, Christian Brauner wrote:
> On Wed, Jan 16, 2019 at 07:25:46AM +0100, Christian Brauner wrote:
> > On Wed, Jan 16, 2019 at 03:01:04AM +0000, Wei Yongjun wrote:
> > > Fix to return a negative error code -ENOMEM from the new_inode() and
> > > d_make_root() error handling cases instead of 0, as done elsewhere in
> > > this function.
> > >
> > > Fixes: 3ad20fe393b3 ("binder: implement binderfs")
>
> This Fixes tag is technically wrong since this codepath was introduced
> by a commit that is still sitting in Greg's char-misc-linus branch. Not
> sure how to handle that though. Might just leave it.
Use the git commit id of the patch in that branch, it is not going to
change as I do not rebase that branch.
thanks,
greg k-h
Powered by blists - more mailing lists