linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Lars Poeschel <poeschel@lemonage.de>,
	Miguel Ojeda <ojeda@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] auxdisplay for v5.17-rc7
Date: Thu, 3 Mar 2022 13:16:07 +0100	[thread overview]
Message-ID: <20220303121607.GA11312@kernel.org> (raw)

Hi Linus,

Please pull these fixes for auxdisplay (they have been in today's
-next run, only).

Cheers,
Miguel

The following changes since commit 7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3:

  Linux 5.17-rc6 (2022-02-27 14:36:33 -0800)

are available in the Git repository at:

  https://github.com/ojeda/linux.git tags/auxdisplay-for-linus-v5.17-rc7

for you to fetch changes up to 9ed331f8a0fb674f4f06edf05a1687bf755af27b:

  auxdisplay: lcd2s: Use proper API to free the instance of charlcd object (2022-03-03 00:30:31 +0100)

----------------------------------------------------------------
A few `lcd2s` fixes for `auxdisplay` from Andy Shevchenko.

----------------------------------------------------------------
Andy Shevchenko (3):
      auxdisplay: lcd2s: Fix lcd2s_redefine_char() feature
      auxdisplay: lcd2s: Fix memory leak in ->remove()
      auxdisplay: lcd2s: Use proper API to free the instance of charlcd object

 drivers/auxdisplay/lcd2s.c | 24 ++++++++++--------------
 1 file changed, 10 insertions(+), 14 deletions(-)

             reply	other threads:[~2022-03-03 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 12:16 Miguel Ojeda [this message]
2022-03-03 19:18 ` [GIT PULL] auxdisplay for v5.17-rc7 pr-tracker-bot

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=20220303121607.GA11312@kernel.org \
    --to=ojeda@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=poeschel@lemonage.de \
    --cc=torvalds@linux-foundation.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).