From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795015829; b=C1FVJh6d3byW4fAloiZGNmJTPOvEcwB99ujNcH+wmw5qT8jxVLMs575BHR0Y7nvI9TUz vGF/kvIWEz5AkcqKzJvduvspY0+7Xq21fJY8uftJBKzZhP5e0TRxToO3Be+zcEKLRD3uK JDGzc6TTtRHsPrzVzgDK2t9dB5BIGZ19JYlUCzNIFqTbsYQ0UlUZK92gcPAuf0aO4cOyy uoeYScEVulRmr3b7m/6wr+/DHKhHr9CtfdRCV84z48vdyiF/kQxQNskbVGL17LY8z3IBQ VU5uqKHlcKfoGpiLNfOZakzufidVmti7QyFHO4l+tSuZZlLKB7YOzPTxEWMkbD6NjhQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795015829; h=DMARC-Filter:DKIM-Signature:Received:X-MC-Unique: X-Mimecast-MFC-AGG-ID:Received:Received:Message-ID:Date:MIME-Version: User-Agent:Subject:To:Cc:References:Content-Language:From:In-Reply-To: Content-Type:Content-Transfer-Encoding:X-Scanned-By; bh=SJS70BAWykYwtLt0R9l5sSECIeSKnz9myNvBTFJeYzc=; b=uouzizHOaRjSKHCNIEdxZBaWOTH5ci3PI0jKg+eiRz5/P3uowKxvQDy+KYxwEgXlYuXy vIvuDDR4MrH2+6AA8LeLTlSg5lJmVIa0Je4Cvze4HHmnNx2DAVtjWhDXJijy9lJB+M5Cv eESSySmIy57RTVFtlaxwY1QpwSB8hfjtMeHefORmnteAIxXDnGn0ZZjgwXQ3NTH0wTnUc ok6lu/7j4McpJu5UwY8quhuoZl1B+rjoehC1tpUVhIb5vKx2fLcKj0HqMNmp5PIWyd9Ze 1Y/jqr/FdW5EeZe/S899gTJjOcUdmxkLD8Y0OFPqN7gA4jppr1d1a3q95NO4oRJhvZw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=STNzfWvn; arc=none smtp.remote-ip=170.10.129.124 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 876B0606A32F for ; Wed, 18 Nov 2026 15:30:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 876B0606A32F Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=STNzfWvn DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1795015827; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SJS70BAWykYwtLt0R9l5sSECIeSKnz9myNvBTFJeYzc=; b=STNzfWvnjuDBwaRjb26BuMhbhcl4et9q0pM1fyk7g8mPeLwgsQD4NKl4JH1PAH3E1ISjSZ kqOEcgk3xcrbIWj6U0RC7t26LQ1/VYa//CMzBMfS+dWTl0f+h0GBdHIDKjNhejilAv58Ky W72tJ9zhDSnbksNMwdfIctss1+8+n9c= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-657-rGcLiJ-dP9KHVHSGNVzrkg-1; Wed, 18 Nov 2026 10:30:22 -0500 X-MC-Unique: rGcLiJ-dP9KHVHSGNVzrkg-1 X-Mimecast-MFC-AGG-ID: rGcLiJ-dP9KHVHSGNVzrkg_1795015819 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id AA4231800556; Wed, 18 Nov 2026 15:30:18 +0000 (UTC) Received: from [100.91.101.41] (headnet04.pony-001.prod.iad2.dc.redhat.com [10.2.32.116]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 3B9C91800543; Wed, 18 Nov 2026 15:30:12 +0000 (UTC) Message-ID: Date: Wed, 18 Nov 2026 16:30:10 +0100 X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net-next v2 0/9] dpll: do not serialize driver callbacks under global dpll_lock To: Jakub Kicinski Cc: netdev@vger.kernel.org, Vadim Fedorenko , Arkadiusz Kubalewski , Jiri Pirko , Jonathan Corbet , Shuah Khan , Randy Dunlap , Min Li , Tony Nguyen , Przemek Kitszel , Andrew Lunn , "David S. Miller" , Eric Dumazet , Paolo Abeni , Richard Cochran , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, Grzegorz Nitka , Karol Kolacinski , Saeed Mahameed , Tariq Toukan , Petr Oros References: <20261111164021.273409-1-ivecera@redhat.com> <20261116181715.6f7d7f09@kernel.org> Content-Language: en-US From: Ivan Vecera In-Reply-To: <20261116181715.6f7d7f09@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 On 11/17/26 03:17, Jakub Kicinski wrote: > On Mon, 16 Nov 2026 09:24:39 +0100 Ivan Vecera wrote: >> v2 no longer applies to net-next since net was merged in. It conflicts >> with 7a3837929d04 ("dpll: notify about a reference sync pair only if it >> was added") in dpll_pin_ref_sync_pair_add(). Patches 3 and 4 fail on >> the same lines and the rest applies cleanly. After patch 4 the >> resolution is: > > What makes you think we'd rebase your patches for you? Sorry, that came out wrong. I wanted to flag the conflict with the fix from net, not to hand the rebase to you. I will send v3 rebased on net-next once the questions in your other reply are settled. Thanks, Ivan