From: Helge Deller <deller@gmx.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] fbdev: omapfb: Replace custom memparse() implementation
Date: Wed, 18 Oct 2023 08:13:53 +0200 [thread overview]
Message-ID: <ccdcd70e-ab34-423a-81ca-6075eef3f01a@gmx.de> (raw)
In-Reply-To: <20231018034725.1124006-1-andriy.shevchenko@linux.intel.com>
On 10/18/23 05:47, Andy Shevchenko wrote:
> Our library has memparse() for parsing numbers with respective suffixes
> suitable for memory sizes. Use it instead of custom implementation.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/video/fbdev/omap/omapfb_main.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
both patches applied.
Thanks!
Helge
prev parent reply other threads:[~2023-10-18 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 3:47 [PATCH v1 1/1] fbdev: omapfb: Replace custom memparse() implementation Andy Shevchenko
2023-10-18 6:13 ` Helge Deller [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=ccdcd70e-ab34-423a-81ca-6075eef3f01a@gmx.de \
--to=deller@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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