Message ID | 20231005210556.466856-2-ojeda@kernel.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:2016:b0:403:3b70:6f57 with SMTP id fe22csp566675vqb; Thu, 5 Oct 2023 14:06:55 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHubBpCAp9LTKyX0uIAlzbV4aZVM+wEMB+AvzpfQlin0hctwftshzuw1/RRckO+7nYYz4BV X-Received: by 2002:a05:6a20:5485:b0:143:f4dd:dfae with SMTP id i5-20020a056a20548500b00143f4dddfaemr7346695pzk.43.1696540015224; Thu, 05 Oct 2023 14:06:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696540015; cv=none; d=google.com; s=arc-20160816; b=XL7xm6tJXbI+0slu9Zx3lAf7gSx+IeHTw33EJHni84bpqfrU6Bw28w8aancD5yu4o8 KtXAqQ9NGSbYVLirHhaMLKR8TcOSNajZzNxKsyztPPW+egW1xp4+aSFCZPtMuM3XQspr Vkhp1tONyk1ykOJZflTakwxZkWZg10xsXomnT6itBty9nUNZsKc1Nij9GGjbDpJedXKj 3u8NwasiFdKbe/tcV9eBPo259VP6pdRMC4wwNCJpOwNJF34wk/bNWM0uTm2Qc90NqHoz FTUyp2YMTGZsHKvxqYMt7tzbHHCalAw+rzEy25+OFx1pTwNoU49LGu1XoVT6W6XQIeA4 IQeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=Hwe4StUr/jqoSZku6LGtzN4oPj947McjZU4ZwOxI0Go=; fh=au7aoxhxwiGjd3un8PPv3AApc8jH8uW5iTGRpBKg8nc=; b=FDGSxOsyH4SgbFS5GRLKsYw7FBO6l1Yz7SGIvys1gHbJ+faPIfnxPzBeQG5BvereyD bEDtegPI7R329tuwS+L1rKszkfmkYWNxBFXMFBATlRlUIxVNj7GCuW7fvu3TbQZEmuJE a+sY/j5nLsExvr7VHjEMQm6laSwzm4Z48QXRZL/Oqx1i23x51X3Ew9Qc2YX3xHEQoCnh PZZjGCPAogxVgkRBmAQg94VMSDLTjF3+QVMq4haO5pJdM95zIxQGvdxWTIM+HK+S60Z3 I2/FAPIRQfD4WSw44IlT53uVKf5TM54xMfPbS47zyH8ZtwBYKPpVvBFTaP9dIwARio7U 2apw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Ss+OX7Sh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from agentk.vger.email (agentk.vger.email. [23.128.96.32]) by mx.google.com with ESMTPS id b18-20020a656692000000b0056c297d163asi2173625pgw.523.2023.10.05.14.06.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Oct 2023 14:06:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Ss+OX7Sh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id DF8688301528; Thu, 5 Oct 2023 14:06:46 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231828AbjJEVGa (ORCPT <rfc822;ezelljr.billy@gmail.com> + 18 others); Thu, 5 Oct 2023 17:06:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42146 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229852AbjJEVG2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 5 Oct 2023 17:06:28 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51BD193 for <linux-kernel@vger.kernel.org>; Thu, 5 Oct 2023 14:06:26 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 291AAC433C9; Thu, 5 Oct 2023 21:06:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1696539986; bh=qOUKIAiTh0O8Uv4d8SH+C2EBhe15SUCFuHgeJkj8nGo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ss+OX7ShDShHRvKvbDoKbBv/UKoDuGOabQmFEhc/WAfNzMKrUpyNgS/LDvY+b09EU KW0Z4EiStk/ehgmYwEmMg+UEYP6ZkMdZoz7KQ1JUd7ppKyooRLt43dmOnm+sOLlAj4 sgvL1a8hNEa/+pK0cRwinEzC2pCb4UfEuWtSQX66f6Wnimv9yBijvpG8PH/EF4zIcY QwnfixNMVLViZVk3fOnu1ipkzndYZhNriCNI0hgjuTYJca2Wwvl/NHSS0TSLqweOIq IRHLDR/2v+2RZLm00kg81qulD/gZltGyNvUBbiS4dpAXKbILQtuEeMFLIN3rgMXlXz 69WgsBYgdspXw== From: Miguel Ojeda <ojeda@kernel.org> To: Miguel Ojeda <ojeda@kernel.org>, Wedson Almeida Filho <wedsonaf@gmail.com>, Alex Gaynor <alex.gaynor@gmail.com> Cc: Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>, =?utf-8?q?Bj=C3=B6rn_Roy_Baron?= <bjorn3_gh@protonmail.com>, Benno Lossin <benno.lossin@proton.me>, Andreas Hindborg <a.hindborg@samsung.com>, Alice Ryhl <aliceryhl@google.com>, rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org, patches@lists.linux.dev Subject: [PATCH 1/3] rust: task: remove redundant explicit link Date: Thu, 5 Oct 2023 23:05:53 +0200 Message-ID: <20231005210556.466856-2-ojeda@kernel.org> In-Reply-To: <20231005210556.466856-1-ojeda@kernel.org> References: <20231005210556.466856-1-ojeda@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Thu, 05 Oct 2023 14:06:46 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1778951143015941298 X-GMAIL-MSGID: 1778951143015941298 |
Series |
Rust 1.73.0 upgrade
|
|
Commit Message
Miguel Ojeda
Oct. 5, 2023, 9:05 p.m. UTC
Starting with Rust 1.73.0, `rustdoc` detects redundant explicit
links with its new lint `redundant_explicit_links` [1]:
error: redundant explicit link target
--> rust/kernel/task.rs:85:21
|
85 | /// [`current`](crate::current) macro because it is safe.
| --------- ^^^^^^^^^^^^^^ explicit target is redundant
| |
| because label contains path that resolves to same destination
|
= note: when a link's destination is not specified,
the label is used to resolve intra-doc links
= note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings`
help: remove explicit link target
|
85 | /// [`current`] macro because it is safe.
In order to avoid the warning in the compiler upgrade commit,
make it an intra-doc link as the tool suggests.
Link: https://github.com/rust-lang/rust/pull/113167 [1]
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
---
rust/kernel/task.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
On 10/5/23 18:05, Miguel Ojeda wrote: > Starting with Rust 1.73.0, `rustdoc` detects redundant explicit > links with its new lint `redundant_explicit_links` [1]: > > error: redundant explicit link target > --> rust/kernel/task.rs:85:21 > | > 85 | /// [`current`](crate::current) macro because it is safe. > | --------- ^^^^^^^^^^^^^^ explicit target is redundant > | | > | because label contains path that resolves to same destination > | > = note: when a link's destination is not specified, > the label is used to resolve intra-doc links > = note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings` > help: remove explicit link target > | > 85 | /// [`current`] macro because it is safe. > > In order to avoid the warning in the compiler upgrade commit, > make it an intra-doc link as the tool suggests. > > Link: https://github.com/rust-lang/rust/pull/113167 [1] > Signed-off-by: Miguel Ojeda <ojeda@kernel.org> > --- > [...] Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
On 5 Oct 2023, at 23:05, Miguel Ojeda wrote: > Starting with Rust 1.73.0, `rustdoc` detects redundant explicit > links with its new lint `redundant_explicit_links` [1]: > > error: redundant explicit link target > --> rust/kernel/task.rs:85:21 > | > 85 | /// [`current`](crate::current) macro because it is safe. > | --------- ^^^^^^^^^^^^^^ explicit target is redundant > | | > | because label contains path that resolves to same destination > | > = note: when a link's destination is not specified, > the label is used to resolve intra-doc links > = note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings` > help: remove explicit link target > | > 85 | /// [`current`] macro because it is safe. > > In order to avoid the warning in the compiler upgrade commit, > make it an intra-doc link as the tool suggests. > > Link: https://github.com/rust-lang/rust/pull/113167 [1] > Signed-off-by: Miguel Ojeda <ojeda@kernel.org> > --- Reviewed-by: Finn Behrens <me@kloenk.dev>
On Thu, Oct 5, 2023 at 11:06 PM Miguel Ojeda <ojeda@kernel.org> wrote: > Starting with Rust 1.73.0, `rustdoc` detects redundant explicit > links with its new lint `redundant_explicit_links` [1]: > > error: redundant explicit link target > --> rust/kernel/task.rs:85:21 > | > 85 | /// [`current`](crate::current) macro because it is safe. > | --------- ^^^^^^^^^^^^^^ explicit target is redundant > | | > | because label contains path that resolves to same destination > | > = note: when a link's destination is not specified, > the label is used to resolve intra-doc links > = note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings` > help: remove explicit link target > | > 85 | /// [`current`] macro because it is safe. > > In order to avoid the warning in the compiler upgrade commit, > make it an intra-doc link as the tool suggests. > > Link: https://github.com/rust-lang/rust/pull/113167 [1] > Signed-off-by: Miguel Ojeda <ojeda@kernel.org> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> Starting with Rust 1.73.0, `rustdoc` detects redundant explicit > links with its new lint `redundant_explicit_links` [1]: > > error: redundant explicit link target > --> rust/kernel/task.rs:85:21 > | > 85 | /// [`current`](crate::current) macro because it is safe. > | --------- ^^^^^^^^^^^^^^ explicit target is redundant > | | > | because label contains path that resolves to same destination > | > = note: when a link's destination is not specified, > the label is used to resolve intra-doc links > = note: `-D rustdoc::redundant-explicit-links` implied by `-D warnings` > help: remove explicit link target > | > 85 | /// [`current`] macro because it is safe. > > In order to avoid the warning in the compiler upgrade commit, > make it an intra-doc link as the tool suggests. > > Link: https://github.com/rust-lang/rust/pull/113167 [1] > Signed-off-by: Miguel Ojeda <ojeda@kernel.org> > --- Reviewed-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
diff --git a/rust/kernel/task.rs b/rust/kernel/task.rs index 7eda15e5f1b3..b2299bc7ac1f 100644 --- a/rust/kernel/task.rs +++ b/rust/kernel/task.rs @@ -82,7 +82,7 @@ impl Task { /// Returns a task reference for the currently executing task/thread. /// /// The recommended way to get the current task/thread is to use the - /// [`current`](crate::current) macro because it is safe. + /// [`current`] macro because it is safe. /// /// # Safety ///