linux-kernel - Re: [PATCH 08/20] m68knommu: change to new flag variables

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CA34F0B.6010605@suse.cz>
Date:	Wed, 29 Sep 2010 16:36:59 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	matt mooney <mfm@...eddisk.com>
Cc:	Greg Ungerer <gerg@...pgear.com>, Greg Ungerer <gerg@...inux.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Howells <dhowells@...hat.com>,
	Tim Abbott <tabbott@...lice.com>, linux-kernel@...r.kernel.org,
	kernel-janitors@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH 08/20] m68knommu: change to new flag variables

On 28.9.2010 09:16, matt mooney wrote:
> My original intent was through the maintainer trees; however, I am starting to
> realize that it probably would have been best to all go into the kbuild tree as
> one patch series. That being said, some people have picked them up and others
> have just acked, so really whatever is easiest for you. All unapplied will
> eventually go through the kbuild tree.

Please try push as much through maintainer trees as possible, to avoid
unnecessary merge conflicts. Of course, if you end up with some patches
that nobody is picking up, I'll apply them to the kbuild tree.

Thanks,
Michal
--
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/