From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 5/8] dmaengine: rcar-dmac: Add Renesas R-Car Gen2 DMA Controller (DMAC) driver
Date: Tue, 05 Aug 2014 11:48:47 +0000 [thread overview]
Message-ID: <CAMuHMdXh0c5LXRYZWfFxd6B7BGNQW4VJGSoSdcbavCE+uVYQXw@mail.gmail.com> (raw)
In-Reply-To: <1405727425-6237-6-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Mon, Aug 4, 2014 at 5:02 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>> > + GFP_KERNEL);
>> > + if (!rchan->irqname)
>> > + return -ENOMEM;
>> > + sprintf(rchan->irqname, "%s:%u", dev_name(dmac->dev), index);
>>
>> We really need devm_kasprintf() (coding it up)...
>>
>> > +static int rcar_dmac_probe(struct platform_device *pdev)
>> > +{
>> >
>> > + dmac->irqname = devm_kmalloc(dmac->dev,
>> > strlen(dev_name(dmac->dev)) + 7, +
>> > GFP_KERNEL);
>> > + if (!dmac->irqname)
>> > + return -ENOMEM;
>> > + sprintf(dmac->irqname, "%s:error", dev_name(&pdev->dev));
>>
>> We really need devm_kasprintf()...
>
> I'll update the driver to use it once it will be upstream :-)
Apparently someone already implemented it during my holidays, and it's
now upstream, causing rebase conflicts in my local tree...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2014-08-05 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 23:50 [PATCH v2 5/8] dmaengine: rcar-dmac: Add Renesas R-Car Gen2 DMA Controller (DMAC) driver Laurent Pinchart
2014-08-04 11:30 ` Geert Uytterhoeven
2014-08-04 15:02 ` Laurent Pinchart
2014-08-05 11:48 ` Geert Uytterhoeven [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=CAMuHMdXh0c5LXRYZWfFxd6B7BGNQW4VJGSoSdcbavCE+uVYQXw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.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).