linux-kernel - Re: linux-next: status of the logfs tree?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20141218113108.150d2edd@canb.auug.org.au>
Date:	Thu, 18 Dec 2014 11:31:08 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Prasad Joshi <prasadjoshi.linux@...il.com>,
	Jörn Engel <joern@...fs.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: status of the logfs tree?

Hi,

On Mon, 13 Oct 2014 11:33:04 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 9 Oct 2014 10:54:18 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > The top commit in the logfs tree was committed in November 2012.  Is
> > there any intention to ask Linus to merge this tree?  Or should I just
> > drop it completely?
> > 
> > It is a pain because it takes considerable time for git to actually
> > merge it.
> > 
> > $ git log --oneline origin/master..logfs/master  
> > 339466142b3f Fix the call to BUG() caused by no free segment found
> > ab2ec19f42dc logfs: fix possible memory leak in logfs_mtd_can_write_buf()
> > $ git diff --stat origin/master...logfs/master 
> >  fs/logfs/dev_mtd.c | 2 +-
> >  fs/logfs/super.c   | 6 +++---
> >  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> Ping?

Ping?

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped