From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
Date: Wed, 18 Dec 2013 22:03:36 +0530 [thread overview]
Message-ID: <20131218163336.GO16227@intel.com> (raw)
In-Reply-To: <CAPcyv4hiGg6J0sAEy6N=HRsLg_B9PGOc=khaTNR80==pDfNQzQ@mail.gmail.com>
On Wed, Dec 18, 2013 at 08:55:23AM -0800, Dan Williams wrote:
> >> > Vinod, if your fixes branch is ready I'll take it along with the rest
> >> > of the regression fixes to Linus.
> > Sorry I wasnt well last week, so I just managed to send the PULL on friday
> > morning. Wasnt sure if Linus will cut rc on friday or later, so sent it!
>
> Ok, glad you are feeling better.
Thanks
>
> >>
> >> Ok, I see you sent dma-slave/fixes up, I'll follow up with the rest:
> > Okay, did you manage to send it? If not I may have few (i think at least 1 more)
> >
>
> Patchwork id(s)? I want to send it it today.
3266451, I have acked it!
--
~Vinod
--
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr()
Date: Wed, 18 Dec 2013 22:03:36 +0530 [thread overview]
Message-ID: <20131218163336.GO16227@intel.com> (raw)
In-Reply-To: <CAPcyv4hiGg6J0sAEy6N=HRsLg_B9PGOc=khaTNR80==pDfNQzQ@mail.gmail.com>
On Wed, Dec 18, 2013 at 08:55:23AM -0800, Dan Williams wrote:
> >> > Vinod, if your fixes branch is ready I'll take it along with the rest
> >> > of the regression fixes to Linus.
> > Sorry I wasnt well last week, so I just managed to send the PULL on friday
> > morning. Wasnt sure if Linus will cut rc on friday or later, so sent it!
>
> Ok, glad you are feeling better.
Thanks
>
> >>
> >> Ok, I see you sent dma-slave/fixes up, I'll follow up with the rest:
> > Okay, did you manage to send it? If not I may have few (i think at least 1 more)
> >
>
> Patchwork id(s)? I want to send it it today.
3266451, I have acked it!
--
~Vinod
--
next prev parent reply other threads:[~2013-12-18 16:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 19:39 [PATCH] dma: mv_xor: remove mv_desc_get_dest_addr() Jason Cooper
2013-11-25 19:39 ` Jason Cooper
2013-11-25 19:46 ` Jason Cooper
2013-11-25 19:46 ` Jason Cooper
2013-11-27 19:45 ` Olof Johansson
2013-11-27 19:45 ` Olof Johansson
2013-11-27 23:58 ` Jason Cooper
2013-11-27 23:58 ` Jason Cooper
2013-11-28 5:57 ` Vinod Koul
2013-11-28 5:57 ` Vinod Koul
2013-12-09 23:50 ` Russell King - ARM Linux
2013-12-09 23:50 ` Russell King - ARM Linux
2013-12-10 10:13 ` Vinod Koul
2013-12-10 10:13 ` Vinod Koul
2013-12-10 11:14 ` Russell King - ARM Linux
2013-12-10 11:14 ` Russell King - ARM Linux
2013-12-11 9:10 ` Dan Williams
2013-12-11 9:10 ` Dan Williams
2013-12-13 7:00 ` Dan Williams
2013-12-13 7:00 ` Dan Williams
2013-12-18 15:40 ` Vinod Koul
2013-12-18 15:40 ` Vinod Koul
2013-12-18 16:55 ` Dan Williams
2013-12-18 16:55 ` Dan Williams
2013-12-18 16:33 ` Vinod Koul [this message]
2013-12-18 16:33 ` Vinod Koul
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=20131218163336.GO16227@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.