From: chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil>
To: Quentin Lambert <lambert.quentin@gmail.com>
Cc: linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] moving from pci to dma
Date: Mon, 12 Jan 2015 10:39:50 -0500 [thread overview]
Message-ID: <20150112103950.0631916b@thirdoffive.cmf.nrl.navy.mil> (raw)
In-Reply-To: <54B3E91E.9060100@gmail.com>
On Mon, 12 Jan 2015 16:32:46 +0100
Quentin Lambert <lambert.quentin@gmail.com> wrote:
>
> On 12/01/2015 16:27, chas williams - CONTRACTOR wrote:
> > There doesn't seem to be a patch for review?
> >
> I made a mistake and forgot to number the mails. I did send them though.
> Would you like me to send them again, with the proper subject format?
>
>
> Quentin Lambert
>
That would be nice. Thanks!
prev parent reply other threads:[~2015-01-12 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 10:02 [PATCH] moving from pci to dma Quentin Lambert
2015-01-12 15:27 ` chas williams - CONTRACTOR
2015-01-12 15:32 ` Quentin Lambert
2015-01-12 15:39 ` chas williams - CONTRACTOR [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=20150112103950.0631916b@thirdoffive.cmf.nrl.navy.mil \
--to=chas@cmf.nrl.navy.mil \
--cc=lambert.quentin@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).