From: Jon Mason <jon.mason@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-raid <linux-raid@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: dmaengine 3.13 v2
Date: Sun, 17 Nov 2013 15:17:55 -0700 [thread overview]
Message-ID: <20131117221755.GC498@jonmason-lab> (raw)
In-Reply-To: <CAPcyv4iMY84dbZLtZceAKnhbkDP-+Vszss8BYriB9pva6nxCfg@mail.gmail.com>
On Sat, Nov 16, 2013 at 10:37:38AM -0800, Dan Williams wrote:
> On Nov 15, 2013 11:48 PM, "Vinod Koul" <[1]vinod.koul@intel.com> wrote:
>
> > While the dmaengine-v2 has:
> >
> > commit 82a1402eaee5dab1f3ab2d5aa4c316451374c5af
> > Author: Ezequiel Garcia <[2]ezequiel.garcia@free-electrons.com>
> > Date: Wed Oct 30 12:01:43 2013 -0300
> >
> > Which also explains the diff I got with test. I have pushed my merge
> to
> > dan_merge2 for your ref. You next branch also doesnt show this commit
> and these
> > are missing below. I guess we need this for the fix. Looks like you
> tagged
> > without these patches. I can go ahead and merge commit
> > bad6f9dba84e7ddc448f306ce4b289dcaa95b9f9 directly if you want.
>
> No, use the tag directly. We're still sorting those ntb patches out
> internally and I accidentally included them in the test branch.
The NTB patches should go through my tree anyway.
Thanks,
Jon
>
> Thanks!
>
> Sent from my phone so excuse HTML
>
> References
>
> 1. mailto:vinod.koul@intel.com
> 2. mailto:ezequiel.garcia@free-electrons.com
prev parent reply other threads:[~2013-11-17 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 18:33 dmaengine 3.13 v2 Dan Williams
2013-11-16 6:52 ` Vinod Koul
[not found] ` <CAPcyv4iMY84dbZLtZceAKnhbkDP-+Vszss8BYriB9pva6nxCfg@mail.gmail.com>
2013-11-17 16:28 ` Vinod Koul
2013-11-20 1:10 ` Dan Williams
2013-11-17 22:17 ` Jon Mason [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=20131117221755.GC498@jonmason-lab \
--to=jon.mason@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=b.zolnierkie@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-raid@vger.kernel.org \
--cc=vinod.koul@intel.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).