linux-kernel - Re: GFS2 & DLM merge request

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: <20060922091134.8602588b.akpm@osdl.org>
Date:	Fri, 22 Sep 2006 09:11:34 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Steven Whitehouse <swhiteho@...hat.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Linus Torvalds <torvalds@...l.org>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	linux-kernel@...r.kernel.org
Subject: Re: GFS2 & DLM merge request

On Fri, 22 Sep 2006 17:02:24 +0100
Steven Whitehouse <swhiteho@...hat.com> wrote:

> > >  include/linux/fs.h                 |    3 
> > >  include/linux/iflags.h             |  102 
> > >  include/linux/kernel.h             |    1 
> > >  mm/filemap.c                       |    3 
> > >  mm/readahead.c                     |    1 
> > 
> > And while we're at it, please don't push core change as part of a subsystem
> > tree ever.  They should go into clearly marked and separately patches via
> > -mm.
> 
> Ok, I'm quite happy to do that. They are pretty minor changes, but the
> usual argument is that such changes are not acceptable until there is
> something in the kernel that makes use of them, and they have to happen
> one way around or the other,

There's no 100% comfortable solution to this.  Steven presumably needs
those changes present in his tree so he can test.

What I usually suggest is that the developer get the core changes reviewed
on-list at an early stage and then explicitly flag their presence in the
covering description when sending the please-pull email.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/