From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
Cc: sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
"David S . Miller"
<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Subject: Re: [PATCH] sparc: use generic dma_noncoherent_ops
Date: Mon, 30 Jul 2018 10:02:47 +0200 [thread overview]
Message-ID: <20180730080247.GA10682@lst.de> (raw)
In-Reply-To: <20180727210548.GA1476-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
On Fri, Jul 27, 2018 at 11:05:48PM +0200, Sam Ravnborg wrote:
> Hi Christoph.
>
> Some observations below - nitpick and bikeshedding only.
>
> The parameter of phys_addr_t is sometimes renamed
> to use the same name as in the original prototype (good),
> and sometimes uses the old name (bad).
> This makes it inconsistent as the local name changes in the
> different functions, but they represents the same.
I'll change it.
> You can add my:
> Acked-by: Sam Ravnborg <sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
I will resend it with your nitpicks addressed and your ack added.
> > +void *arch_dma_alloc(struct device *dev, size_t len, dma_addr_t *pba, gfp_t gfp,
> > + unsigned long attrs)
>
> This function was renamed in ee664a9252d24 and is now renamed again.
> The printk statements should be updated to use arch_dma_alloc.
I've switched the printk statements to use __func__ instead, not that
I plan for another rename any time soon.
I've also update the comments referring to this function to use the
right name.
next prev parent reply other threads:[~2018-07-30 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 16:44 generic noncoherent dma ops for sparc32, 2nd resend Christoph Hellwig
[not found] ` <20180727164409.14873-1-hch-jcswGhMUV9g@public.gmane.org>
2018-07-27 16:44 ` [PATCH] sparc: use generic dma_noncoherent_ops Christoph Hellwig
[not found] ` <20180727164409.14873-2-hch-jcswGhMUV9g@public.gmane.org>
2018-07-27 21:05 ` Sam Ravnborg
[not found] ` <20180727210548.GA1476-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org>
2018-07-30 8:02 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-30 16:17 Christoph Hellwig
[not found] ` <20180730161723.9445-1-hch-jcswGhMUV9g@public.gmane.org>
2018-07-30 19:41 ` Sam Ravnborg
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=20180730080247.GA10682@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 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).