kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: arnd@arndb.de, gregkh@linuxfoundation.org,
	mihai.carabas@oracle.com, andriy.shevchenko@linux.intel.com,
	pizhenwei@bytedance.com, pbonzini@redhat.com,
	bobo.shaobowang@huawei.com, linqiheng@huawei.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH v2 0/5] misc/pvpanic: Fix some errro handling path and simplify code
Date: Sat, 22 May 2021 08:52:35 +0200	[thread overview]
Message-ID: <cover.1621665058.git.christophe.jaillet@wanadoo.fr> (raw)

This serie was previously sent in 2 parts, one for -pci.c and one for
-mmio.c.
Execpt the patch 5/5 which is new, the 4 first patches are the same as the
ones previously posted. Only the description has been slighly updated.

Pacth 5/5 is a proposal to simplify code and turn 'pvpanic_probe()' into a
fully resource managed version.
This way callers don't need to do some clean-up on error in the
probe and on remove.


"Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>" was only
added on patch 1 and 3. I was unsure if his Reviewed-by was also related to
the s/GFP_ATOMIC/GFP_KERNEL/ of patch 2 et 4.

Christophe JAILLET (5):
  misc/pvpanic-pci: Fix error handling in 'pvpanic_pci_probe()'
  misc/pvpanic-pci: Use GFP_KERNEL instead of GFP_ATOMIC
  misc/pvpanic-mmio: Fix error handling in 'pvpanic_mmio_probe()'
  misc/pvpanic-mmio: Use GFP_KERNEL instead of GFP_ATOMIC
  misc/pvpanic: Make 'pvpanic_probe()' resource managed

 drivers/misc/pvpanic/pvpanic-mmio.c | 17 ++--------------
 drivers/misc/pvpanic/pvpanic-pci.c  | 22 ++++-----------------
 drivers/misc/pvpanic/pvpanic.c      | 30 ++++++++++++++---------------
 drivers/misc/pvpanic/pvpanic.h      |  3 +--
 4 files changed, 22 insertions(+), 50 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-05-22  6:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22  6:52 Christophe JAILLET [this message]
2021-05-22  6:54 ` [PATCH v2 1/5] misc/pvpanic-pci: Fix error handling in 'pvpanic_pci_probe()' Christophe JAILLET
2021-05-22  6:54 ` [PATCH v2 2/5] misc/pvpanic-pci: Use GFP_KERNEL instead of GFP_ATOMIC Christophe JAILLET
2021-05-22  6:55 ` [PATCH v2 3/5] misc/pvpanic-mmio: Fix error handling in 'pvpanic_mmio_probe()' Christophe JAILLET
2021-05-22  6:55 ` [PATCH v2 4/5] misc/pvpanic-mmio: Use GFP_KERNEL instead of GFP_ATOMIC Christophe JAILLET
2021-05-22  6:55 ` [PATCH v2 5/5] misc/pvpanic: Make 'pvpanic_probe()' resource managed Christophe JAILLET
2021-05-22 10:06   ` Andy Shevchenko
2021-05-22 10:09     ` Andy Shevchenko
2021-05-22 10:57       ` Christophe JAILLET
2021-05-22 11:06         ` Andy Shevchenko
2021-05-22 11:30           ` Christophe JAILLET
2021-05-22 10:03 ` [PATCH v2 0/5] misc/pvpanic: Fix some errro handling path and simplify code Andy Shevchenko

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=cover.1621665058.git.christophe.jaillet@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bobo.shaobowang@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linqiheng@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.carabas@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=pizhenwei@bytedance.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).