rust: auxiliary: fix "initialialized" typo
Subsystems (2)
PATCH 1/1 rust: auxiliary: fix "initialialized" typo
From: Jaime Fan <[email protected]>
Fixes a spelling mistake in a comment: "initialialized" → "initialized". This improves clarity in the documentation and avoids confusion for readers.
--- rust/kernel/auxiliary.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
rust/kernel/auxiliary.rs +2 -2
@@ -317,12 +317,12 @@ pub fn new(parent: &device::Device, name: &CStr, id: u32, modname: &CStr) -> Res// SAFETY: // - `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, which has -// been initialialized, +// been initialized, // - `modname.as_char_ptr()` is a NULL terminated string. let ret =unsafe { bindings::__auxiliary_device_add (adev, modname.as_char_ptr ()) };if ret !=0 {// SAFETY: `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, -// which has been initialialized. +// which has been initialized. unsafe { bindings::auxiliary_device_uninit (adev) };return Err (Error ::from_errno (ret));
Signature · 1 line
2.50.1
Greg KH
maintainerQuoted 34 lines · JaimeF
From: Jaime Fan <[email protected]>
Fixes a spelling mistake in a comment: "initialialized" → "initialized". This improves clarity in the documentation and avoids confusion for readers.
Suggested-by onur-ozkan <[email protected]>Signed-off-by Jaime Fan <[email protected]>--- rust/kernel/auxiliary.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)rust/kernel/auxiliary.rs +2
-2@@ -317,12 +317,12 @@ pub fn new(parent: &device::Device, name: &CStr, id: u32, modname: &CStr) -> Res// SAFETY: // - `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, which has -// been initialialized, +// been initialized, // - `modname.as_char_ptr()` is a NULL terminated string. let ret =unsafe { bindings::__auxiliary_device_add (adev, modname.as_char_ptr ()) };if ret !=0 {// SAFETY: `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, -// which has been initialialized. +// which has been initialized. unsafe { bindings::auxiliary_device_uninit (adev) };return Err (Error ::from_errno (ret));Signature · 1 line
2.50.1
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot
A message that is not in the archive (sent off-list or not yet received): CAL-mriLdm9NiNBvAqV3BEKVELJ1B1FsZtZL=NOsM_2RipoU0FA@mail.gmail.com
Greg KH
maintainerQuoted 1 line · Jaime Fine
Fixed!
Please slow down and relax. Take a day at the very least between patch submissions to fully read the responses and then do a new version. There is no rush here.
thanks,
greg k-h
Quoted 6 lines · Greg KH
Quoted 1 line · Jaime Fine
Fixed!
Please slow down and relax. Take a day at the very least between patch submissions to fully read the responses and then do a new version. There is no rush here.
+1
And perhaps check out the b4 tool[*] which can help with tracking changes to a patch set and help with patch submissions.
[*] https://git.kernel.org/pub/scm/utils/b4/b4.git
See the prep option.
Ira
Greg KH
maintainerQuoted 35 lines · JaimeF
From: Jaime Fan <[email protected]>
Fixes a spelling mistake in a comment: "initialialized" → "initialized". This improves clarity in the documentation and avoids confusion for readers.
Suggested-by onur-ozkan <[email protected]>Signed-off-by Jaime Fan <[email protected]>--- rust/kernel/auxiliary.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)rust/kernel/auxiliary.rs +2
-2@@ -317,12 +317,12 @@ pub fn new(parent: &device::Device, name: &CStr, id: u32, modname: &CStr) -> Res// SAFETY: // - `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, which has -// been initialialized, +// been initialized, // - `modname.as_char_ptr()` is a NULL terminated string. let ret =unsafe { bindings::__auxiliary_device_add (adev, modname.as_char_ptr ()) };if ret !=0 {// SAFETY: `adev` is guaranteed to be a valid pointer to a `struct auxiliary_device`, -// which has been initialialized. +// which has been initialized. unsafe { bindings::auxiliary_device_uninit (adev) };return Err (Error ::from_errno (ret));Signature · 1 line
2.50.1
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/process/submitting-patches.rst for what needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot