Attachment 229257 Details for Bug 259636 – diff file, same changes as in the PR referenced above

[patch] diff file, same changes as in the PR referenced above

jb_spelling_fix.diff (text/plain), 6.17 KB, created by John Bentley on 2021-11-04 00:34:08 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: John Bentley

Created: 2021-11-04 00:34:08 UTC

Size: 6.17 KB

patch

obsolete

>diff --git a/contrib/llvm-project/clang/include/clang/Basic/Diagnostic.h b/contrib/llvm-project/clang/include/clang/Basic/Diagnostic.h
>index 3499c551cfdf..b1c903c0e499 100644
>--- a/contrib/llvm-project/clang/include/clang/Basic/Diagnostic.h
>+++ b/contrib/llvm-project/clang/include/clang/Basic/Diagnostic.h
>@@ -752,7 +752,7 @@ class DiagnosticsEngine : public RefCountedBase<DiagnosticsEngine> {
>   /// WARNINGs and EXTENSIONs can be mapped arbitrarily.
>   ///
>   /// \param Loc The source location that this change of diagnostic state should
>-  /// take affect. It can be null if we are setting the latest state.
>+  /// take effect. It can be null if we are setting the latest state.
>   void setSeverity(diag::kind Diag, diag::Severity Map, SourceLocation Loc);
> 
>   /// Change an entire diagnostic group (e.g. "unknown-pragmas") to
>@@ -765,7 +765,7 @@ class DiagnosticsEngine : public RefCountedBase<DiagnosticsEngine> {
>   /// state of the -Wfoo group and vice versa.
>   ///
>   /// \param Loc The source location that this change of diagnostic state should
>-  /// take affect. It can be null if we are setting the state from command-line.
>+  /// take effect. It can be null if we are setting the state from command-line.
>   bool setSeverityForGroup(diag::Flavor Flavor, StringRef Group,
>                            diag::Severity Map,
>                            SourceLocation Loc = SourceLocation());
>diff --git a/contrib/sendmail/contrib/buildvirtuser b/contrib/sendmail/contrib/buildvirtuser
>index 173f95b0cc8e..7ea3b381031c 100755
>--- a/contrib/sendmail/contrib/buildvirtuser
>+++ b/contrib/sendmail/contrib/buildvirtuser
>@@ -66,7 +66,7 @@ files with:
> 
> If a new domain is added (i.e., by adding a new file to
> /etc/mail/virtusers/), the sendmail daemon must be restarted for the change
>-to take affect.
>+to take effect.
> 
> =head1 EXAMPLES
> 
>diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4
>index f285d5276376..f07279566ee4 100644
>--- a/share/man/man4/bpf.4
>+++ b/share/man/man4/bpf.4
>@@ -698,7 +698,7 @@ will start receiving
> when packets arrive.
> Note that you must do an
> .Dv FIOSETOWN
>-in order for this to take affect,
>+in order for this to take effect,
> as the system will not default this for you.
> The signal may be changed via
> .Dv BIOCSRSIG .
>diff --git a/share/man/man4/bxe.4 b/share/man/man4/bxe.4
>index 4838b825b756..98d3040ef454 100644
>--- a/share/man/man4/bxe.4
>+++ b/share/man/man4/bxe.4
>@@ -88,7 +88,7 @@ There a number of configuration parameters that can be set to tweak the
> driver's behavior.
> These parameters can be set via the
> .Xr loader.conf 5
>-file to take affect during the next system boot.
>+file to take effect during the next system boot.
> The following parameters affect
> ALL instances of the driver.
> .Bl -tag -width indent
>diff --git a/sys/dev/e1000/e1000_phy.c b/sys/dev/e1000/e1000_phy.c
>index 872a5267bfdb..5395d560db66 100644
>--- a/sys/dev/e1000/e1000_phy.c
>+++ b/sys/dev/e1000/e1000_phy.c
>@@ -2020,7 +2020,7 @@ s32 e1000_phy_force_speed_duplex_ife(struct e1000_hw *hw)
>  *  disable auto-negotiation, configure duplex, configure speed, configure
>  *  the collision distance, write configuration to CTRL register.  The
>  *  caller must write to the PHY_CONTROL register for these settings to
>- *  take affect.
>+ *  take effect.
>  **/
> void e1000_phy_force_speed_duplex_setup(struct e1000_hw *hw, u16 *phy_ctrl)
> {
>diff --git a/sys/dev/igc/igc_phy.c b/sys/dev/igc/igc_phy.c
>index a1d71ab15829..f8574925e9f8 100644
>--- a/sys/dev/igc/igc_phy.c
>+++ b/sys/dev/igc/igc_phy.c
>@@ -592,7 +592,7 @@ s32 igc_setup_copper_link_generic(struct igc_hw *hw)
>  *  disable auto-negotiation, configure duplex, configure speed, configure
>  *  the collision distance, write configuration to CTRL register.  The
>  *  caller must write to the PHY_CONTROL register for these settings to
>- *  take affect.
>+ *  take effect.
>  **/
> void igc_phy_force_speed_duplex_setup(struct igc_hw *hw, u16 *phy_ctrl)
> {
>diff --git a/sys/dev/isci/scil/scif_sas_controller.c b/sys/dev/isci/scil/scif_sas_controller.c
>index b3987984afa2..a3dd5513bdc8 100644
>--- a/sys/dev/isci/scil/scif_sas_controller.c
>+++ b/sys/dev/isci/scil/scif_sas_controller.c
>@@ -561,7 +561,7 @@ SCI_STATUS scif_user_parameters_set(
> 
>    // In the future more could be done to prevent setting parameters at the
>    // wrong time, but for now we'll simply set the values even if it is too
>-   // late for them to take affect.
>+   // late for them to take effect.
>    return SCI_SUCCESS;
> }
> 
>diff --git a/sys/dev/mlx4/mlx4_core/mlx4_cmd.c b/sys/dev/mlx4/mlx4_core/mlx4_cmd.c
>index 39a4064e3ff4..bd9541bef7c8 100644
>--- a/sys/dev/mlx4/mlx4_core/mlx4_cmd.c
>+++ b/sys/dev/mlx4/mlx4_core/mlx4_cmd.c
>@@ -3110,7 +3110,7 @@ int mlx4_set_vf_rate(struct mlx4_dev *dev, int port, int vf, int min_tx_rate,
> 			mlx4_info(dev, "VF in VGT mode (needed VST)\n");
> 
> 		mlx4_info(dev,
>-			  "rate %d take affect when VF moves to valid state\n",
>+			  "rate %d take effect when VF moves to valid state\n",
> 			  max_tx_rate);
> 		return 0;
> 	}
>@@ -3286,4 +3286,3 @@ int mlx4_vf_set_enable_smi_admin(struct mlx4_dev *dev, int slave, int port,
> 	return 0;
> }
> EXPORT_SYMBOL_GPL(mlx4_vf_set_enable_smi_admin);
>-
>diff --git a/usr.sbin/bsdconfig/security/include/messages.subr b/usr.sbin/bsdconfig/security/include/messages.subr
>index f6df66751881..1ab2333c1fb8 100644
>--- a/usr.sbin/bsdconfig/security/include/messages.subr
>+++ b/usr.sbin/bsdconfig/security/include/messages.subr
>@@ -33,7 +33,7 @@ msg_exit="Exit"
> msg_exit_this_menu="Exit this menu"
> msg_highly_secure="Highly Secure"
> msg_highly_secure_mode="Highly secure mode"
>-msg_menu_text="This menu allows you to configure aspects of the operating system security\npolicy.  Please read the system documentation carefully before modifying\nthese settings, as they may cause service disruption if used improperly.\n\nMost settings will take affect only following a system reboot."
>+msg_menu_text="This menu allows you to configure aspects of the operating system security\npolicy.  Please read the system documentation carefully before modifying\nthese settings, as they may cause service disruption if used improperly.\n\nMost settings will take effect only following a system reboot."
> msg_network_secure="Network Secure"
> msg_network_secure_mode="Network secure mode"
> msg_nfs_port="NFS port"

Actions: View | Diff

Attachments on bug 259636: 229257 | 229275