From: Romain Gantois <romain.gantois@bootlin•com>
To: Wolfram Sang <wsa@the-dreams•de>,
Romain Gantois <romain.gantois@bootlin•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Mauro Carvalho Chehab <mchehab@kernel•org>,
Hans Verkuil <hverkuil@xs4all•nl>,
Jai Luthra <jai.luthra@ideasonboard•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Sakari Ailus <sakari.ailus@linux•intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard•com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the i2c tree
Date: Mon, 02 Jun 2025 17:57:08 +0200 [thread overview]
Message-ID: <5203152.31r3eYUQgx@fw-rgant> (raw)
In-Reply-To: <aDrwb1YvwFKQB8x1@shikoro>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
Hi Wolfram,
On Saturday, 31 May 2025 14:05:03 CEST Wolfram Sang wrote:
> > Below is the resolution I came up with.
>
> Linus solved it differently [1]. I think he is right, but those
> interested please double check.
>
> [1]
> https://lore.kernel.org/all/CAHk-=wiKW=BPcDvBAsVDemdWBR0uh09A_WMOCoceqj3w3d
> oGJg@mail•gmail.com/
Indeed Linus' resolution is correct, the mutex destroy line should be:
mutex_destroy(&it.rxport->aliased_addrs_lock);
Thanks,
--
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-06-02 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 0:49 linux-next: manual merge of the v4l-dvb tree with the i2c tree Stephen Rothwell
2025-04-28 1:22 ` Stephen Rothwell
2025-04-28 1:30 ` Stephen Rothwell
2025-04-29 11:46 ` Tomi Valkeinen
2025-05-29 2:49 ` Stephen Rothwell
2025-05-30 8:13 ` Romain Gantois
2025-05-30 11:24 ` Wolfram Sang
2025-06-02 16:17 ` Romain Gantois
2025-05-31 12:05 ` Wolfram Sang
2025-06-02 15:57 ` Romain Gantois [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 1:12 Stephen Rothwell
2013-05-01 3:27 ` Stephen Rothwell
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=5203152.31r3eYUQgx@fw-rgant \
--to=romain.gantois@bootlin$(echo .)com \
--cc=hverkuil@xs4all$(echo .)nl \
--cc=jai.luthra@ideasonboard$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=sakari.ailus@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tomi.valkeinen@ideasonboard$(echo .)com \
--cc=wsa@the-dreams$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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