linux-kernel - Re: [PATCH update] firewire: debug AT, AR, and selfID-complete events

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, 12 Mar 2008 17:01:17 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Jarod Wilson <jwilson@...hat.com>
CC:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH update] firewire: debug AT, AR, and selfID-complete events

Jarod Wilson wrote:
> Want to do that as a later follow-up patch, or roll it into this one and post 
> another update?

I haven't committed to linux1394-2.6.git, hence I prefer to post an
update rather than incremental patch.

> (I'm fully prepared to sign off on either way after having 
> extensively used these patches the past several days...)

BTW, if I get sign-offs/ acks/ test feedback on a patch before another
patch update (but not before committing the final version to the
upstream submission branch), I add those sign-offs etc. like this

    S-o-b: Someone
    S-o-b: Me (modified whitespace or something else trivial)

or this

    Initial changelog

    S-o-b: Someone

    Changelog post scriptum

    S-o-b: Me

provided that the update only marginally changes the patch or can be
clearly distinguished from the formerly signed off parts.  Of course if
I get sign-offs etc. on the final version of the patch
-- 
Stefan Richter
-=====-==--- --== -==--
http://arcgraph.de/sr/
--
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/