From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Richard Kuo <rkuo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: linux-hexagon-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/3] hexagon: remove the sync_single_for_cpu DMA operation
Date: Tue, 7 Aug 2018 09:01:36 +0200 [thread overview]
Message-ID: <20180807070136.GA32634@lst.de> (raw)
In-Reply-To: <20180731152229.GA956-jcswGhMUV9g@public.gmane.org>
On Tue, Jul 31, 2018 at 05:22:29PM +0200, Christoph Hellwig wrote:
> On Wed, Jul 25, 2018 at 06:39:27AM +0200, Christoph Hellwig wrote:
> > On Tue, Jul 24, 2018 at 10:29:48PM -0500, Richard Kuo wrote:
> > > Patch series looks good. Definitely appreciate the cleanup.
> > >
> > > I can take it through my tree, or if not:
> > >
> > > Acked-by: Richard Kuo <rkuo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
> >
> > Please take it through your tree, thanks!
>
> I haven't seen it in linux-next yet, do you still plan to take it?
>
> Otherwise I'll merge it in the dma-mapping tree.
Given that I haven't seen this in linux-next nor haven't heard back
from you I assume you are on your well deserved summer vacation.
If I don't hear back until tomorrow night I'll merge it through the
dma-mapping tree, so that I have it in linux-next before heading out
to my summer vacation.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-hexagon@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] hexagon: remove the sync_single_for_cpu DMA operation
Date: Tue, 7 Aug 2018 09:01:36 +0200 [thread overview]
Message-ID: <20180807070136.GA32634@lst.de> (raw)
In-Reply-To: <20180731152229.GA956@lst.de>
On Tue, Jul 31, 2018 at 05:22:29PM +0200, Christoph Hellwig wrote:
> On Wed, Jul 25, 2018 at 06:39:27AM +0200, Christoph Hellwig wrote:
> > On Tue, Jul 24, 2018 at 10:29:48PM -0500, Richard Kuo wrote:
> > > Patch series looks good. Definitely appreciate the cleanup.
> > >
> > > I can take it through my tree, or if not:
> > >
> > > Acked-by: Richard Kuo <rkuo@codeaurora.org>
> >
> > Please take it through your tree, thanks!
>
> I haven't seen it in linux-next yet, do you still plan to take it?
>
> Otherwise I'll merge it in the dma-mapping tree.
Given that I haven't seen this in linux-next nor haven't heard back
from you I assume you are on your well deserved summer vacation.
If I don't hear back until tomorrow night I'll merge it through the
dma-mapping tree, so that I have it in linux-next before heading out
to my summer vacation.
next prev parent reply other threads:[~2018-08-07 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 12:56 use the generic dma-noncoherent code for hexagon Christoph Hellwig
2018-07-19 12:56 ` [PATCH 1/3] hexagon: remove the sync_single_for_cpu DMA operation Christoph Hellwig
[not found] ` <20180719125635.824-2-hch-jcswGhMUV9g@public.gmane.org>
2018-07-25 3:29 ` Richard Kuo
2018-07-25 3:29 ` Richard Kuo
[not found] ` <20180725032948.GG12771-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-07-25 4:39 ` Christoph Hellwig
2018-07-25 4:39 ` Christoph Hellwig
2018-07-31 15:22 ` Christoph Hellwig
[not found] ` <20180731152229.GA956-jcswGhMUV9g@public.gmane.org>
2018-08-07 7:01 ` Christoph Hellwig [this message]
2018-08-07 7:01 ` Christoph Hellwig
[not found] ` <20180807070136.GA32634-jcswGhMUV9g@public.gmane.org>
2018-08-08 0:19 ` Richard Kuo
2018-08-08 0:19 ` Richard Kuo
2018-08-08 6:19 ` Christoph Hellwig
2018-08-27 8:41 ` Christoph Hellwig
2018-07-19 12:56 ` [PATCH 2/3] hexagon: implement the sync_sg_for_device " Christoph Hellwig
2018-07-19 12:56 ` [PATCH 3/3] hexagon: use generic dma_noncoherent_ops Christoph Hellwig
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=20180807070136.GA32634@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-hexagon-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rkuo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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.