mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jarod Wilson <jwilson@redhat.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH update] firewire: debug AT, AR, and selfID-complete events
Date: Wed, 12 Mar 2008 17:01:17 +0100	[thread overview]
Message-ID: <47D7FE4D.5090107@s5r6.in-berlin.de> (raw)
In-Reply-To: <200803121034.39583.jwilson@redhat.com>

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/

  reply	other threads:[~2008-03-12 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-09 20:49 [PATCH] " Stefan Richter
2008-03-10  4:47 ` Jarod Wilson
2008-03-10 22:28   ` [PATCH update] " Stefan Richter
2008-03-11  1:16     ` [PATCH] firewire: fw-ohci: untangle a mixed unsigned/signed expression Stefan Richter
2008-03-12  9:15     ` [PATCH update] firewire: debug AT, AR, and selfID-complete events Stefan Richter
2008-03-12 14:34       ` Jarod Wilson
2008-03-12 16:01         ` Stefan Richter [this message]
2008-03-15  1:57           ` Jarod Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D7FE4D.5090107@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=jwilson@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome