From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] linux/pcifront: fix freeing of device
Date: Mon, 04 Oct 2010 13:23:39 +0100 [thread overview]
Message-ID: <C8CF85DB.24EA3%keir@xen.org> (raw)
In-Reply-To: <4CA9E33B020000780001A60F@vpn.id2.novell.com>
On 04/10/2010 13:22, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> On 04.10.10 at 13:46, Keir Fraser <keir@xen.org> wrote:
>> Are the two patches you sent out for 2.6.18? If so, you need to make it
>> clear. There are several Linux trees now and I'm ignoring Linux patches by
>> default.
>
> Yes, they are. If distinguishing by the recipient (xen-devel vs. Jeremy)
> isn't sufficient, I'll state this explicitly in the future.
Yes, put it in the subject line, thanks.
K.
> Jan
>
prev parent reply other threads:[~2010-10-04 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 11:09 [PATCH] linux/pcifront: fix freeing of device Jan Beulich
2010-10-04 11:46 ` Keir Fraser
2010-10-04 12:22 ` Jan Beulich
2010-10-04 12:23 ` Keir Fraser [this message]
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=C8CF85DB.24EA3%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).