From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Bastian Stender <bst@pengutronix.de>, Jyri Sarha <jsarha@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [0/2] video: ssd1307fb: Adjustments for ssd1307fb_probe()
Date: Fri, 29 Dec 2017 18:23:39 +0000 [thread overview]
Message-ID: <f5dd0d53-2014-a967-03c3-05ff8a1cc05d@users.sourceforge.net> (raw)
In-Reply-To: <2091464.qzRHS0Wsad@amdc3058>
>> Delete an error message for a failed memory allocation
>
> This patch removes the information about the device for which the allocation fails.
How do you think about to take another look if a Linux allocation failure report
could be sufficient in this use case?
>> Improve a size determination
>
> This patch depends on the earlier patch (which is not being merged)
Partly, yes.
> so please re-base it if you want it to be applied.
Would you dare to reduce any context lines for this update step so that
such a small adjustment will still work?
Regards,
Markus
next prev parent reply other threads:[~2017-12-29 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171125160425epcas5p43b2d94fbcc74745017c4c91ff08de685@epcas5p4.samsung.com>
2017-11-25 16:04 ` [PATCH 0/2] video: ssd1307fb: Adjustments for ssd1307fb_probe() SF Markus Elfring
2017-11-25 16:05 ` [PATCH 1/2] video: ssd1307fb: Delete an error message for a failed memory allocation in ssd1307fb_pr SF Markus Elfring
2017-11-25 16:06 ` [PATCH 2/2] video: ssd1307fb: Improve a size determination in ssd1307fb_probe() SF Markus Elfring
2017-12-29 18:10 ` [PATCH 0/2] video: ssd1307fb: Adjustments for ssd1307fb_probe() Bartlomiej Zolnierkiewicz
2017-12-29 18:23 ` SF Markus Elfring [this message]
2018-01-07 18:34 ` [PATCH v2] video: ssd1307fb: Improve a size determination in ssd1307fb_probe() SF Markus Elfring
2018-03-28 13:53 ` Bartlomiej Zolnierkiewicz
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=f5dd0d53-2014-a967-03c3-05ff8a1cc05d@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=bst@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).