From: Lee Jones <lee.jones@linaro.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-omap@vger.kernel.org,
SF Markus Elfring <elfring@users.sourceforge.net>,
Tony Lindgren <tony@atomide.com>, Roger Quadros <rogerq@ti.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] mfd: omap-usb-tll: Allocate driver data at once
Date: Tue, 23 Jan 2018 12:55:58 +0000 [thread overview]
Message-ID: <20180123125558.pcvztj2spuimatdk@dell> (raw)
In-Reply-To: <20180115202505.GA2628@lenoch>
On Mon, 15 Jan 2018, Ladislav Michl wrote:
> Allocating memory to store clk array together with driver
> data simplifies error unwinding and allows deleting memory
> allocation failure message as there is now only single point
> of failure already covered by allocation failure report.
>
> Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> [Markus Elfring: simplified error unwinding, error message removal]
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> Link: https://lkml.org/lkml/2018/1/15/411
> ---
> Changes:
> - v2: reindent 'rev' debug message
> credit Markus Elfring
>
> drivers/mfd/omap-usb-tll.c | 60 +++++++++++++++++++---------------------------
> 1 file changed, 25 insertions(+), 35 deletions(-)
Applied, thanks.
--
Lee Jones
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-23 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 20:25 [PATCH v2] mfd: omap-usb-tll: Allocate driver data at once Ladislav Michl
2018-01-17 15:22 ` Roger Quadros
2018-01-23 12:55 ` Lee Jones [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=20180123125558.pcvztj2spuimatdk@dell \
--to=lee.jones@linaro.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=ladis@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.com \
/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