public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Joel Granados <j.granados@samsung.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [resend, PATCH v1 0/3] parport: Switch to some modern APIs
Date: Mon, 16 Oct 2023 16:31:32 +0300	[thread overview]
Message-ID: <20231016133135.1203643-1-andriy.shevchenko@linux.intel.com> (raw)

This is a set of ad-hoc refactorings and cleanups to the parport driver.

In v1,resent:
- resent with Greg KH in Cc list

Initial contribution have been seen here 6 weeks ago:
https://lore.kernel.org/r/20230901134250.1172990-1-andriy.shevchenko@linux.intel.com

Andy Shevchenko (3):
  parport: Use kasprintf() instead of fixed buffer formatting
  parport: Use list_for_each() helper
  parport: Drop unneeded NULL or 0 assignments

 drivers/parport/procfs.c | 53 +++++++---------------------------------
 drivers/parport/share.c  | 25 ++++++++-----------
 include/linux/parport.h  |  2 --
 3 files changed, 19 insertions(+), 61 deletions(-)

-- 
2.40.0.1.gaa8946217a0b


             reply	other threads:[~2023-10-16 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 13:31 Andy Shevchenko [this message]
2023-10-16 13:31 ` [resend, PATCH v1 1/3] parport: Use kasprintf() instead of fixed buffer formatting Andy Shevchenko
2023-10-16 13:31 ` [resend, PATCH v1 2/3] parport: Use list_for_each() helper Andy Shevchenko
2023-10-16 13:31 ` [resend, PATCH v1 3/3] parport: Drop unneeded NULL or 0 assignments Andy Shevchenko
2023-10-16 19:38 ` [resend, PATCH v1 0/3] parport: Switch to some modern APIs Luis Chamberlain

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=20231016133135.1203643-1-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=j.granados@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=sudipm.mukherjee@gmail.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