linux-kernel - Re: Should I really bother all maintainers with this?

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: <alpine.LNX.2.00.1004222357150.7579@pobox.suse.cz>
Date:	Thu, 22 Apr 2010 23:57:55 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Francis Galiegue <fgaliegue@...il.com>
Cc:	Mike Frysinger <vapier.adi@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Should I really bother all maintainers with this?

On Thu, 22 Apr 2010, Francis Galiegue wrote:

> >> This patch only fixes quite a common mistake in Documentation/, and if I
> >> scripts/get_maintainer.pl on the patch (which is recommended), I potentially
> >> mail thousands of people who probably have more useful/exciting stuff to do
> >> anyway. So, I submit it as is.
> >
> > this kind of stuff usually goes through the trivial tree.  look at
> > TRIVIAL PATCHES in the MAINTAINERS file.
> > -mike
> >
> 
> Point taken... But the patch doesn't apply as is over trivial/master or
> trivial/for-next, as two files don't seem to exist on either branch (trivial
> being the git repository mentioned in MAINTAINERS):
> Documentation/DMA-API-HOWTO.txt and Documentation/filesystems/ceph.txt.

That's not a problem, I pull Linus' tree into my tree when needed. Just 
resend the patch (based on Linus' tree) to trivial@...nel.org and I'll 
process it appropriately.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/