Fix paramter -> parameter, and recomended ->
recommended in sysctl.sh's help messages.
Also correct grammar: "number amount of times
is recommended" etc -> "the recommended number of
times".
Signed-off-by: Bharadwaj Raju
---
tools/testing/selftests/sysctl/sysctl.sh | 6 +++---
1 file changed, 3
Le Sat, Feb 15, 2025 at 02:38:04AM -0800, Paul E. McKenney a écrit :
> On Fri, Feb 14, 2025 at 01:10:52PM +0100, Frederic Weisbecker wrote:
> > Le Fri, Feb 14, 2025 at 01:01:56AM -0800, Paul E. McKenney a écrit :
> > > On Fri, Feb 14, 2025 at 12:25:59AM +0100, Frederic Weisbecker wrote:
> > > > A C
On Sun, Feb 09, 2025 at 04:47:44PM +0200, Andy Shevchenko wrote:
> On Sat, Feb 08, 2025 at 04:13:24PM -0500, Aren Moynihan wrote:
> > Using dev_err_probe instead of dev_err and return makes the errors
>
> Use dev_err_probe()
> dev_err()
>
> > easier to understand by including the error name, and
Hi Tamir,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 7b7a883c7f4de1ee5040bd1c32aabaafde54d209]
url:
https://github.com/intel-lab-lkp/linux/commits/Tamir-Duberstein/scanf-implicate-test-line-in-failure-messages/20250215-002302
base
…
> and it will cause that socket can not be unusable after resume.
…
I find such a wording confusing.
Can the change description become clearer?
Regards,
Markus
On Sat, Feb 15, 2025 at 4:03 AM David Gow wrote:
>
> On Fri, 14 Feb 2025 at 22:41, Tamir Duberstein wrote:
> >
> > On Fri, Feb 14, 2025 at 2:42 AM David Gow wrote:
> > >
> > > From: José Expósito
> > >
> > > In some cases, we need to call test-only code from outside the test
> > > case, for exa
On Sat, Feb 15, 2025 at 4:03 AM David Gow wrote:
>
> On Fri, 14 Feb 2025 at 22:41, Tamir Duberstein wrote:
> >
> > Very excited to see this progress.
> >
> > On Fri, Feb 14, 2025 at 2:41 AM David Gow wrote:
> > >
> > > From: José Expósito
> > >
> > > Add a couple of Rust const functions and mac
On Tue, Feb 4, 2025 at 6:26 AM Sami Tolvanen wrote:
>
> Using dwarf_getscopes_die to resolve fully-qualified names turns out to
> be rather slow, and also results in duplicate scopes being processed,
> which doesn't help. Simply adding an extra pass to resolve names for all
> DIEs before processin
Tue, 11 Feb 2025, Julian Anastasov wrote:
>>
>>
>> Hello,
>>
>>On Mon, 10 Feb 2025, mengkanglai wrote:
>>
>>> Hello:
>>> I found a problem with ftp ipvs.
>>> I create 3 virtual machine in one host. One is the FTP client, the other is
>>> the ipvs transition host, and the other is the FTP serv
On Fri, Feb 14, 2025 at 01:10:52PM +0100, Frederic Weisbecker wrote:
> Le Fri, Feb 14, 2025 at 01:01:56AM -0800, Paul E. McKenney a écrit :
> > On Fri, Feb 14, 2025 at 12:25:59AM +0100, Frederic Weisbecker wrote:
> > > A CPU coming online checks for an ongoing grace period and reports
> > > a quies
On Sat, 15 Feb 2025 at 04:49, Miguel Ojeda
wrote:
>
> On Fri, Feb 14, 2025 at 8:41 AM David Gow wrote:
> >
> > After much delay, v6 of the KUnit/Rust integration patchset is here.
> > This change incorporates most of Miguels suggestions from v5 (save for
> > some of the copyright headers I wasn't
From: José Expósito
In some cases, we need to call test-only code from outside the test
case, for example, to mock a function or a module.
In order to check whether we are in a test or not, we need to test if
`CONFIG_KUNIT` is set.
Unfortunately, we cannot rely only on this condition because:
-
From: José Expósito
Add a new procedural macro (`#[kunit_tests(kunit_test_suit_name)]`) to
run KUnit tests using a user-space like syntax.
The macro, that should be used on modules, transforms every `#[test]`
in a `kunit_case!` and adds a `kunit_unsafe_test_suite!` registering
all of them.
The
From: José Expósito
Add a couple of Rust const functions and macros to allow to develop
KUnit tests without relying on generated C code:
- The `kunit_unsafe_test_suite!` Rust macro is similar to the
`kunit_test_suite` C macro. It requires a NULL-terminated array of
test cases (see below).
Hi all,
This is v7 of the Rust/KUnit integration patch. I think all of the
suggestions have at least been responded to (even if there are a few I'm
leaving as either future projects or matters of taste). Hopefully this
is good-to-go for 6.15, so we can start using it concurrently with
making any a
On Fri, 14 Feb 2025 at 22:41, Tamir Duberstein wrote:
>
> On Fri, Feb 14, 2025 at 2:42 AM David Gow wrote:
> >
> > From: José Expósito
> >
> > In some cases, we need to call test-only code from outside the test
> > case, for example, to mock a function or a module.
> >
> > In order to check whet
On Fri, 14 Feb 2025 at 22:41, Tamir Duberstein wrote:
>
> Very excited to see this progress.
>
> On Fri, Feb 14, 2025 at 2:41 AM David Gow wrote:
> >
> > From: José Expósito
> >
> > Add a couple of Rust const functions and macros to allow to develop
> > KUnit tests without relying on generated C
Fix misspellings flagged by codespell.
Signed-off-by: Ujwal Kundur
---
tools/testing/selftests/mm/uffd-common.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/mm/uffd-common.c
b/tools/testing/selftests/mm/uffd-common.c
index 717539eddf98..2544099
18 matches
Mail list logo
