linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: "Rusty Russell" <rusty@rustcorp.com.au>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
	"Nicholas Krause" <xerofoify@gmail.com>,
	"Duan Jiong" <duanj.fnst@cn.fujitsu.com>,
	"Sachin Kamat" <sachin.kamat@linaro.org>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] err.h: remove deprecated PTR_RET for good
Date: Sun, 22 Mar 2020 22:42:56 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2003222240500.19500@cbobk.fhfr.pm> (raw)
In-Reply-To: <20200322165702.6712-1-lukas.bulwahn@gmail.com>

On Sun, 22 Mar 2020, Lukas Bulwahn wrote:

> Initially, commit fa9ee9c4b988 ("include/linux/err.h: add a function to
> cast error-pointers to a return value") from Uwe Kleine-König introduced
> PTR_RET in 03/2011. Then, in 07/2013, commit 6e8b8726ad50 ("PTR_RET is
> now PTR_ERR_OR_ZERO") from Rusty Russell renamed PTR_RET to
> PTR_ERR_OR_ZERO, and left PTR_RET as deprecated-marked alias.
> 
> After six years since the renaming and various repeated cleanups in the
> meantime, it is time to finally remove the deprecated PTR_RET for good.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Rusty, if you are still around, Acked-by is appreciated.
> Uwe, Acked-by is appreciated.
> Kudos to Gustavo, Nicholas, Duan & Sachin for previous cleanups.
> 
> applies cleanly on current master and on next-20200320
> Jiri, please pick this trival patch for the next merge window. Thanks.

I am queuing it right away; it's been marked deprecated back in 2013, and 
it doesn't have any in-tree users anyway.

Thanks,

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2020-03-22 21:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 16:57 [PATCH] err.h: remove deprecated PTR_RET for good Lukas Bulwahn
2020-03-22 21:42 ` Jiri Kosina [this message]
2020-03-22 22:04   ` Uwe Kleine-König

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=nycvar.YFH.7.76.2003222240500.19500@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=duanj.fnst@cn.fujitsu.com \
    --cc=gustavo@embeddedor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sachin.kamat@linaro.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=xerofoify@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;
as well as URLs for NNTP newsgroup(s).