From: Kevin Winchester <kjwinchester@gmail.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Possible locking issue in viotape.c
Date: Sat, 08 Dec 2007 15:19:12 -0400 [thread overview]
Message-ID: <475AEE30.4070806@gmail.com> (raw)
In-Reply-To: <1197138162.1568.172.camel@jnielson-xp.ddns.mvista.com>
Daniel Walker wrote:
>> Yes, you are right, I hadn't finished looking at all of the up() calls
>> when I came to my conclusion. I will try to convert a few that are not
>> on your list, but I would like to know how you are generating your
>> patches into those files with the diffstat and recipient list. Is that
>> a feature of some git command?
>
> Git may have a similar feature, but I'm using a tool call Quilt. It's
> used for managing a list of patches, and it can automatically add a
> diffstat to the patch header (part of the quilt refresh command). I also
> use it for emailing a list of patches.
>
Yes, I've used quilt for working with mm patches in the past, but I'm
not too familiar with the mail features. For example, how do you get
the recipient list and Signed-off-by in the patch file? Do you just
edit it by hand? Or is there some guide to quilt I should be reading?
I looked at the guide in /usr/share/doc/quilt/quilt.pdf, but it didn't
have anything about email. /usr/share/doc/quilt/README.MAIL has the
details of all of the mail options, but doesn't give a nice example of
what to do with the patch file and how to call 'quilt mail'.
--
Kevin Winchester
next prev parent reply other threads:[~2007-12-08 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071206021857.826386004@mvista.com>
2007-12-05 8:00 ` [PATCH 1/3] stopmachine semaphore to mutex Daniel Walker
2007-12-05 8:00 ` [PATCH 2/3] Amiga serial driver: port_write_mutex fixup Daniel Walker
2007-12-05 8:00 ` [PATCH 3/3] printer port driver: semaphore to mutex Daniel Walker
2007-12-06 10:23 ` Ingo Molnar
2007-12-06 16:34 ` Daniel Walker
2007-12-06 20:01 ` Remy Bohmer
2007-12-06 20:12 ` Daniel Walker
2007-12-06 20:40 ` Remy Bohmer
2007-12-06 20:05 ` Matthias Kaehlcke
2007-12-06 20:12 ` Remy Bohmer
2007-12-06 20:23 ` Daniel Walker
2007-12-07 7:40 ` Matthias Kaehlcke
2007-12-06 20:44 ` Ingo Molnar
2007-12-06 23:30 ` Kevin Winchester
2007-12-07 1:05 ` Daniel Walker
2007-12-07 1:29 ` Possible locking issue in viotape.c Kevin Winchester
2007-12-07 1:40 ` Daniel Walker
2007-12-08 18:17 ` Kevin Winchester
2007-12-08 18:22 ` Daniel Walker
2007-12-08 19:19 ` Kevin Winchester [this message]
2007-12-08 19:45 ` Daniel Walker
2007-12-06 10:22 ` [PATCH 1/3] stopmachine semaphore to mutex Ingo Molnar
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=475AEE30.4070806@gmail.com \
--to=kjwinchester@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/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