Joerg Schilling wrote: > Jens Axboe <axboe@suse.de> wrote: > >> It just looks like Joerg needs to do his homework, before spreading >> false information on lkml. Then again, all his "arguments" are the same >> as last time (and the time before, and before, and so on). > > Before spreading your false claims, please do your homework. I think we'd better call the whole discussion off. In personal conversation with Jörg, I fell prey to the illusion he might have grown up last week-end, and Lee's promising post was the idea to start the whole thing and see if both sides get closer together, but it seems Jörg is unwilling to stick to a civilized discussion. Sorry for starting this noise. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Jens Axboe <axboe@suse.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Lee Revell <rlrevell@joe-job.com>
- CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <axboe@suse.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <axboe@suse.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):
![]() |