linux-kernel - Re: [PATCH 2/3] SCRIPTS: s/should/must/ for all ERRORs

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]

Date:	Wed, 10 Feb 2010 21:22:00 -0800
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Richard Hartmann <richih.mailinglist@...il.com>
Cc:	linux-crypto@...r.kernel.org, Andy Whitcroft <apw@...onical.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Walker <dwalker@...o99.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] SCRIPTS: s/should/must/ for all ERRORs

On Wed, 10 Feb 2010 18:59:11 +0100 Richard Hartmann wrote:

> PS: As I am new to the whole concept of touching the large scary kernel
> let me use this opportunity to ask if I should expect answers on the
> other patch emails or if they are just merged zsh-style: Silently and
> you will notice what went through when you pull a few days later.

OK, since nobody else has tried to answer this, I'll give it a shot.

It happens many different ways in linux-kernel land, mostly depending on
who is doing the merging, and it's really up to the subsystem or driver
maintainer.

If Andrew Morton merges a patch into his mmotm patchset, you'll get an email
confirmation of it, but this just means that it's in the mmotm patches for
testing, not necessarily for merging into the mainline kernel tree.

If you send a networking patch and David S. Miller merges it, you will get
both an acknowledgement of that and you can see the patch's status at
http://patchwork.ozlabs.org/project/netdev/list/

Same for multimedia driver patches, but view their status at
http://patchwork.kernel.org/project/linux-media/list/

I don't recall if Andy Whitcroft acks checkpatch patches or not, but
you should note that checkpatch is not his highest priority job
(but I'm not trying to speak for him).

If you send patches for the staging or USB or stable pr serial/tty trees,
GregKH will usually ack them when they are merged.

If you send patches for ATA drivers, Jeff Garzik will usually ack them when
they are merged.

If you send patches for the SCSI drivers/subsystem, good luck, the SCSI
mailing list is the best place to find out their status.

If you send patches for parts of Documentation/ that are obviously not
cared for by someone else, I'll try to get to them, but that's not my
highest priority either.  I will ack them if/when I merge them.

I guess if it's not clear to you or anyone else, most Linux maintainers
also have other jobs that they usually need to do...

HTH.  If you have specific questions, ask away, or maybe Andy can tell us
about checkpatch patches.

---
~Randy
--
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/