From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org
Subject: Re: [PATCH v3] sparc: use generic dma_noncoherent_ops
Date: Wed, 22 Aug 2018 08:03:26 +0200 [thread overview]
Message-ID: <20180822060326.GA18493@lst.de> (raw)
In-Reply-To: <20180821.225737.2130615341518333532.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Tue, Aug 21, 2018 at 10:57:37PM -0700, David Miller wrote:
> From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> Date: Wed, 22 Aug 2018 07:36:13 +0200
>
> > I fear you have already pushed out your tree, but otherwise it would
> > be better do merge it through the dma-mapping tree.
>
> I did and asked Linus to pull as well. Sorry :-/
Oh, if you pushed that for 4.19 that is actually perfect to prepare
for my 4.20 changes. Never mind the interruption!
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org
Subject: Re: [PATCH v3] sparc: use generic dma_noncoherent_ops
Date: Wed, 22 Aug 2018 06:03:26 +0000 [thread overview]
Message-ID: <20180822060326.GA18493@lst.de> (raw)
In-Reply-To: <20180821.225737.2130615341518333532.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Tue, Aug 21, 2018 at 10:57:37PM -0700, David Miller wrote:
> From: Christoph Hellwig <hch@lst.de>
> Date: Wed, 22 Aug 2018 07:36:13 +0200
>
> > I fear you have already pushed out your tree, but otherwise it would
> > be better do merge it through the dma-mapping tree.
>
> I did and asked Linus to pull as well. Sorry :-/
Oh, if you pushed that for 4.19 that is actually perfect to prepare
for my 4.20 changes. Never mind the interruption!
next prev parent reply other threads:[~2018-08-22 6:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 8:02 [PATCH v3] sparc: use generic dma_noncoherent_ops Christoph Hellwig
2018-07-31 8:02 ` Christoph Hellwig
[not found] ` <20180731080204.22753-1-hch-jcswGhMUV9g@public.gmane.org>
2018-08-03 7:48 ` Christoph Hellwig
2018-08-03 7:48 ` Christoph Hellwig
[not found] ` <20180803074840.GA2763-jcswGhMUV9g@public.gmane.org>
2018-08-21 19:38 ` David Miller
2018-08-21 19:38 ` David Miller
[not found] ` <20180821.123800.1007897552850427796.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-08-22 5:36 ` Christoph Hellwig
2018-08-22 5:36 ` Christoph Hellwig
[not found] ` <20180822053613.GA17836-jcswGhMUV9g@public.gmane.org>
2018-08-22 5:57 ` David Miller
2018-08-22 5:57 ` David Miller
[not found] ` <20180821.225737.2130615341518333532.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2018-08-22 6:03 ` Christoph Hellwig [this message]
2018-08-22 6:03 ` 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=20180822060326.GA18493@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org \
--cc=sparclinux-u79uwXL29TY76Z2rM5mHXA@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.