On Mon, Oct 24, 2016 at 08:37:15AM +0200, Christoph Hellwig wrote:
> On Sat, Oct 15, 2016 at 01:33:29AM +0100, Al Viro wrote:
> > IMO that's a plain and simple "just before -rc1" fodder, to be sent
> > straight to Linus. No objections from me, anyway.
>
> It's "just after -rc2" now, but maybe
On Mon, Oct 24, 2016 at 08:37:15AM +0200, Christoph Hellwig wrote:
> On Sat, Oct 15, 2016 at 01:33:29AM +0100, Al Viro wrote:
> > IMO that's a plain and simple "just before -rc1" fodder, to be sent
> > straight to Linus. No objections from me, anyway.
>
> It's "just after -rc2" now, but maybe
On Sat, Oct 15, 2016 at 01:33:29AM +0100, Al Viro wrote:
> IMO that's a plain and simple "just before -rc1" fodder, to be sent
> straight to Linus. No objections from me, anyway.
It's "just after -rc2" now, but maybe it's still time for this
trivial removal?
On Sat, Oct 15, 2016 at 01:33:29AM +0100, Al Viro wrote:
> IMO that's a plain and simple "just before -rc1" fodder, to be sent
> straight to Linus. No objections from me, anyway.
It's "just after -rc2" now, but maybe it's still time for this
trivial removal?
On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up
On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up
On 2016-09-12 02:55, Artem Bityutskiy wrote:
On Sun, 2016-09-11 at 15:04 +0200, Christoph Hellwig wrote:
Logfs was introduced to the kernel in 2009, and hasn't seen any non
drive-by changes since 2012, while having lots of unsolved issues
including the complete lack of error handling, with more
On 2016-09-12 02:55, Artem Bityutskiy wrote:
On Sun, 2016-09-11 at 15:04 +0200, Christoph Hellwig wrote:
Logfs was introduced to the kernel in 2009, and hasn't seen any non
drive-by changes since 2012, while having lots of unsolved issues
including the complete lack of error handling, with more
On Sun, 2016-09-11 at 15:04 +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up without any
On Sun, 2016-09-11 at 15:04 +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up without any
On Mon, Sep 12, 2016 at 11:53:19AM +1000, Dave Chinner wrote:
> Wasn't the lib/btree.c implementation introduced with and only used
> by logfs? Should that go as well?
The qla2xxx SCSI target driver also uses the btree library.
On Mon, Sep 12, 2016 at 11:53:19AM +1000, Dave Chinner wrote:
> Wasn't the lib/btree.c implementation introduced with and only used
> by logfs? Should that go as well?
The qla2xxx SCSI target driver also uses the btree library.
On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up
On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up
14 matches
Mail list logo
