From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] intel_th: Remove an unused exit point from intel_th_remove()
Date: Thu, 6 May 2021 11:42:48 +0200 [thread overview]
Message-ID: <20210506094248.vkec2fcwzuudagqh@pengutronix.de> (raw)
In-Reply-To: <87zgx8jk0x.fsf@ashishki-desk.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Hello Alexander,
On Thu, May 06, 2021 at 12:20:30PM +0300, Alexander Shishkin wrote:
> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> writes:
>
> > As described in the added comment device_for_each_child never returns
> > a non-zero value. So remove the corresponding error check.
> >
> > This simplifies the quest to make struct bus_type::remove() return void.
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>
> Picked up, thanks! Out of curiosity: does the mentioned quest have a
> message-id or a git branch?
I just pushed my wip patch to
https://git.pengutronix.de/git/ukl/linux bus-make-remove-void
to satisfy your curiosity. If you prefer a clickable version:
https://git.pengutronix.de/cgit/ukl/linux/log/?h=bus-make-remove-void
There are already a few patches for that quest in mainline[1]. Other
than that nothing special.
Best regards
Uwe
[1] git log --oneline --author=Kleine-König --grep=void v5.10..
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-05-06 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 20:37 [PATCH] intel_th: Remove an unused exit point from intel_th_remove() Uwe Kleine-König
2021-05-06 9:20 ` Alexander Shishkin
2021-05-06 9:42 ` Uwe Kleine-König [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=20210506094248.vkec2fcwzuudagqh@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=alexander.shishkin@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).