From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Bernie Thompson <bernie@plugable.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/4] video-UDLFB: Adjustments for five function implementations
Date: Fri, 29 Dec 2017 18:02:03 +0000 [thread overview]
Message-ID: <1768474.zA76iyE2Y1@amdc3058> (raw)
In-Reply-To: <6fb11bb4-2c1d-a939-087b-de31c42328b9@users.sourceforge.net>
On Friday, November 24, 2017 09:48:14 PM SF Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Fri, 24 Nov 2017 21:45:54 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (4):
> Delete an error message for a failed memory allocation in two functions
This patch removes the information about the device for which the allocation
fails.
> Return an error code only as a constant in dlfb_realloc_framebuffer()
This patch depends on the earlier patch (which is not being merged) so please
re-base it if you want it to be applied.
> Improve a size determination in dlfb_alloc_urb_list()
Patch queued for 4.16, thanks.
> Delete an unnecessary return statement in two functions
Patch queued for 4.16, thanks.
> drivers/video/fbdev/udlfb.c | 23 +++++------------------
> 1 file changed, 5 insertions(+), 18 deletions(-)
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2017-12-29 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171124204825epcas1p41626d598b6e437dfb4c6b648e3730cc1@epcas1p4.samsung.com>
2017-11-24 20:48 ` [PATCH 0/4] video-UDLFB: Adjustments for five function implementations SF Markus Elfring
2017-11-24 20:49 ` [PATCH 1/4] video: udlfb: Delete an error message for a failed memory allocation in two functions SF Markus Elfring
2017-11-24 20:51 ` [PATCH 2/4] video: udlfb: Return an error code only as a constant in dlfb_realloc_framebuffer() SF Markus Elfring
2017-11-24 20:52 ` [PATCH 3/4] video: udlfb: Improve a size determination in dlfb_alloc_urb_list() SF Markus Elfring
2017-11-24 20:54 ` [PATCH 4/4] video: udlfb: Delete an unnecessary return statement in two functions SF Markus Elfring
2017-12-29 18:02 ` Bartlomiej Zolnierkiewicz [this message]
2017-12-29 18:10 ` [0/4] video-UDLFB: Adjustments for five function implementations SF Markus Elfring
2018-01-04 17:08 ` Bartlomiej Zolnierkiewicz
2018-01-04 17:44 ` SF Markus Elfring
2018-01-07 13:33 ` [PATCH v2 0/2] video-UDLFB: Adjustments for dlfb_realloc_framebuffer() SF Markus Elfring
2018-01-07 13:34 ` [PATCH v2 1/2] video: udlfb: Return an error code only as a constant in dlfb_realloc_framebuffer() SF Markus Elfring
2018-03-28 13:42 ` [PATCH v2 1/2] video: udlfb: Return an error code only as a constant in dlfb_realloc_framebuffer Bartlomiej Zolnierkiewicz
2018-01-07 13:38 ` [PATCH v2 2/2] video: udlfb: Delete an error message for a failed memory allocation in dlfb_realloc_ SF Markus Elfring
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=1768474.zA76iyE2Y1@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=bernie@plugable.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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).