On 05/26/2017 09:20 PM, David Daney wrote:
On 05/26/2017 12:09 PM, Daniel Borkmann wrote:
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
On 05/26/2017 09:20 PM, David Daney wrote:
On 05/26/2017 12:09 PM, Daniel Borkmann wrote:
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
On May 22, 2017 10:49:06 PM PDT, Ingo Molnar wrote:
>
>* H. Peter Anvin wrote:
>
>> On 05/22/17 04:12, Ingo Molnar wrote:
>> \>>
>> >> This construct might be useful for other arches, which is why I
>called
>> >> it "FP" instead of "BP". But then I ruined that
On May 22, 2017 10:49:06 PM PDT, Ingo Molnar wrote:
>
>* H. Peter Anvin wrote:
>
>> On 05/22/17 04:12, Ingo Molnar wrote:
>> \>>
>> >> This construct might be useful for other arches, which is why I
>called
>> >> it "FP" instead of "BP". But then I ruined that with the last 3
>:-)
>> >
>> >
On 05/26/2017 12:09 PM, Daniel Borkmann wrote:
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
64-bit kernels. As of the writing of this
On 05/26/2017 12:09 PM, Daniel Borkmann wrote:
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
64-bit kernels. As of the writing of this
On Fri 26 May 06:01 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote:
> On 5/26/2017 11:33 AM, Bjorn Andersson wrote:
> > On Tue 16 May 11:01 PDT 2017, Avaneesh Kumar Dwivedi wrote:
[..]
> > > diff --git a/include/linux/qcom_scm.h b/include/linux/qcom_scm.h
[..]
> > > +#define QCOM_SCM_VMID_HLOS
On Fri 26 May 06:01 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote:
> On 5/26/2017 11:33 AM, Bjorn Andersson wrote:
> > On Tue 16 May 11:01 PDT 2017, Avaneesh Kumar Dwivedi wrote:
[..]
> > > diff --git a/include/linux/qcom_scm.h b/include/linux/qcom_scm.h
[..]
> > > +#define QCOM_SCM_VMID_HLOS
lis...@veco.ru
>
Subject: Gegenseitiger Partnervorschlag
Date: Fri, 26 May 2017 18:15:45 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.
lis...@veco.ru
>
Subject: Gegenseitiger Partnervorschlag
Date: Fri, 26 May 2017 18:15:45 +0200
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.
Hi Roshni,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.12-rc2 next-20170526]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Roshni-Shah/misc
Hi Roshni,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.12-rc2 next-20170526]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Roshni-Shah/misc
On Fri 26 May 06:19 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote:
>
>
> On 5/26/2017 7:46 AM, Bjorn Andersson wrote:
> > On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> > > @@ -471,6 +517,11 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc,
> > > const struct firmware
On Fri 26 May 06:19 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote:
>
>
> On 5/26/2017 7:46 AM, Bjorn Andersson wrote:
> > On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote:
> > > @@ -471,6 +517,11 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc,
> > > const struct firmware
Some 64-bit atomic operations use 'long long' as operand/return type
(e.g. asm-generic/atomic64.h, arch/x86/include/asm/atomic64_32.h);
while others use 'long' (e.g. arch/x86/include/asm/atomic64_64.h).
This makes it impossible to write portable code.
For example, there is no format specifier that
Some 64-bit atomic operations use 'long long' as operand/return type
(e.g. asm-generic/atomic64.h, arch/x86/include/asm/atomic64_32.h);
while others use 'long' (e.g. arch/x86/include/asm/atomic64_64.h).
This makes it impossible to write portable code.
For example, there is no format specifier that
The new header allows to wrap per-arch atomic operations
and add common functionality to all of them.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
The new header allows to wrap per-arch atomic operations
and add common functionality to all of them.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Ingo Molnar
Cc: kasan-...@googlegroups.com
Cc: linux...@kvack.org
KASAN uses compiler instrumentation to intercept all memory accesses.
But it does not see memory accesses done in assembly code.
One notable user of assembly code is atomic operations. Frequently,
for example, an atomic reference decrement is the last access to an
object and a good candidate for a
KASAN uses compiler instrumentation to intercept all memory accesses.
But it does not see memory accesses done in assembly code.
One notable user of assembly code is atomic operations. Frequently,
for example, an atomic reference decrement is the last access to an
object and a good candidate for a
The comments are factored out from the code changes to make them
easier to read. Add them separately to explain some non-obvious
aspects.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
The comments are factored out from the code changes to make them
easier to read. Add them separately to explain some non-obvious
aspects.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Ingo Molnar
Cc:
Add arch_ prefix to all atomic operations and include
. This will allow
to add KASAN instrumentation to all atomic ops.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc:
Add arch_ prefix to all atomic operations and include
. This will allow
to add KASAN instrumentation to all atomic ops.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: Andrew Morton
Cc: Andrey Ryabinin
Cc: Ingo Molnar
Cc: kasan-...@googlegroups.com
Cc:
CPP turns perfectly readable code into an unreadable,
unmaintainable mess. Ingo suggested to write them out as-is.
Do this.
Signed-off-by: Dmitry Vyukov
Suggested-by: Ingo Molnar
Cc: Mark Rutland
Cc: Andrey Ryabinin
CPP turns perfectly readable code into an unreadable,
unmaintainable mess. Ingo suggested to write them out as-is.
Do this.
Signed-off-by: Dmitry Vyukov
Suggested-by: Ingo Molnar
Cc: Mark Rutland
Cc: Andrey Ryabinin
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Cc: Peter Zijlstra
Cc: Andrew
Use strlcpy with sized buffer instead of strncpy to
avoid non NUL-terminated source strings problems.
Signed-off-by: Karim Eshapa
---
drivers/edac/edac_mc_sysfs.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/edac/edac_mc_sysfs.c
Use strlcpy with sized buffer instead of strncpy to
avoid non NUL-terminated source strings problems.
Signed-off-by: Karim Eshapa
---
drivers/edac/edac_mc_sysfs.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/edac/edac_mc_sysfs.c
KASAN uses compiler instrumentation to intercept all memory accesses.
But it does not see memory accesses done in assembly code.
One notable user of assembly code is atomic operations. Frequently,
for example, an atomic reference decrement is the last access to an
object and a good candidate for a
Currently kasan_check_read/write() accept 'const void*', make them
accept 'const volatile void*'. This is required for instrumentation
of atomic operations and there is just no reason to not allow that.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc:
KASAN uses compiler instrumentation to intercept all memory accesses.
But it does not see memory accesses done in assembly code.
One notable user of assembly code is atomic operations. Frequently,
for example, an atomic reference decrement is the last access to an
object and a good candidate for a
Currently kasan_check_read/write() accept 'const void*', make them
accept 'const volatile void*'. This is required for instrumentation
of atomic operations and there is just no reason to not allow that.
Signed-off-by: Dmitry Vyukov
Cc: Mark Rutland
Cc: Andrey Ryabinin
Cc: Thomas Gleixner
Cc:
On Fri, May 26, 2017 at 11:43 AM, Mickaël Salaün wrote:
> Hi,
>
> This patch series make the seccomp/test_harness.h more generally available [1]
> and update the kselftest documentation in the Sphinx format. It also improve
> the Makefile of seccomp tests to take into account
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
64-bit kernels. As of the writing of this commit log test-bpf is showing:
test_bpf:
On Thu, May 25, 2017 at 10:24:46PM -0500, Christoph Lameter wrote:
> On Thu, 25 May 2017, Marcelo Tosatti wrote:
>
> > Argument? We're showing you the data that this is causing a latency
> > problem for us.
>
> Sorry I am not sure where the data shows a latency problem. There are
> interrupts
On Fri, May 26, 2017 at 11:43 AM, Mickaël Salaün wrote:
> Hi,
>
> This patch series make the seccomp/test_harness.h more generally available [1]
> and update the kselftest documentation in the Sphinx format. It also improve
> the Makefile of seccomp tests to take into account any
On 05/26/2017 05:39 PM, David Daney wrote:
On 05/26/2017 08:14 AM, Daniel Borkmann wrote:
On 05/26/2017 02:38 AM, David Daney wrote:
Since the eBPF machine has 64-bit registers, we only support this in
64-bit kernels. As of the writing of this commit log test-bpf is showing:
test_bpf:
On Thu, May 25, 2017 at 10:24:46PM -0500, Christoph Lameter wrote:
> On Thu, 25 May 2017, Marcelo Tosatti wrote:
>
> > Argument? We're showing you the data that this is causing a latency
> > problem for us.
>
> Sorry I am not sure where the data shows a latency problem. There are
> interrupts
On Fri, May 26, 2017 at 11:44 AM, Mickaël Salaün wrote:
> Add ReST metadata to kselftest_harness.h to be able to include the
> comments in the Sphinx documentation.
>
> Changes since v4:
> * exclude the TEST_API() changes (requested by Kees Cook)
>
> Changes since v3:
> *
On Fri, May 26, 2017 at 11:44 AM, Mickaël Salaün wrote:
> Add ReST metadata to kselftest_harness.h to be able to include the
> comments in the Sphinx documentation.
>
> Changes since v4:
> * exclude the TEST_API() changes (requested by Kees Cook)
>
> Changes since v3:
> * document macros as
On Fri, May 26, 2017 at 11:44 AM, Mickaël Salaün wrote:
> Remove the TEST_API() wrapper to expose the underlying macro arguments
> to the documentation tools.
>
> Use "git diff --patience" to get a more readable patch.
>
> Changes since v4:
> * standalone patch to ease the
On Fri, May 26, 2017 at 11:44 AM, Mickaël Salaün wrote:
> Remove the TEST_API() wrapper to expose the underlying macro arguments
> to the documentation tools.
>
> Use "git diff --patience" to get a more readable patch.
>
> Changes since v4:
> * standalone patch to ease the review (requested by
Hi Linus,
I have a few miscellaneous bug fixes & cleanups for you for 4.12-rc3.
--Darrick
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
Hi Linus,
I have a few miscellaneous bug fixes & cleanups for you for 4.12-rc3.
--Darrick
The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
are available in the git repository at:
On Fri, May 26, 2017 at 10:37 AM, Mark Rutland wrote:
> If a key's refcount is dropped to zero between key_lookup() peeking at
> the refcount and subsequently attempting to increment it, refcount_inc()
> will see a zero refcount. Here, refcount_inc() will WARN_ONCE(), and
>
On Fri, May 26, 2017 at 10:37 AM, Mark Rutland wrote:
> If a key's refcount is dropped to zero between key_lookup() peeking at
> the refcount and subsequently attempting to increment it, refcount_inc()
> will see a zero refcount. Here, refcount_inc() will WARN_ONCE(), and
> will *not* increment
Use strlcpy with sized buffer instead of strncpy to
avoid non NUL-terminated source strings problems.
Signed-off-by: Karim Eshapa
---
drivers/edac/edac_mc_sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/edac_mc_sysfs.c
Use strlcpy with sized buffer instead of strncpy to
avoid non NUL-terminated source strings problems.
Signed-off-by: Karim Eshapa
---
drivers/edac/edac_mc_sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/edac_mc_sysfs.c b/drivers/edac/edac_mc_sysfs.c
On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> Just reply with success to the other end for now. Delay the allocation
> of the actual socket to bind and/or connect.
>
> Signed-off-by: Stefano Stabellini
> CC: boris.ostrov...@oracle.com
> CC: jgr...@suse.com
> ---
>
On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> Just reply with success to the other end for now. Delay the allocation
> of the actual socket to bind and/or connect.
>
> Signed-off-by: Stefano Stabellini
> CC: boris.ostrov...@oracle.com
> CC: jgr...@suse.com
> ---
>
From: Peter Dawson
Date: Fri, 26 May 2017 06:35:18 +1000
> This fix addresses two problems in the way the DSCP field is formulated
> on the encapsulating header of IPv6 tunnels.
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195661
>
> 1) The IPv6 tunneling code
From: Peter Dawson
Date: Fri, 26 May 2017 06:35:18 +1000
> This fix addresses two problems in the way the DSCP field is formulated
> on the encapsulating header of IPv6 tunnels.
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195661
>
> 1) The IPv6 tunneling code was manipulating the
Kaby Lake seems to work just like Skylake.
Signed-off-by: Jason Baron
Reported-and-tested-by: Doug Thompson
Cc: Borislav Petkov
Cc: Mauro Carvalho Chehab
Cc: Tony Luck
---
Kaby Lake seems to work just like Skylake.
Signed-off-by: Jason Baron
Reported-and-tested-by: Doug Thompson
Cc: Borislav Petkov
Cc: Mauro Carvalho Chehab
Cc: Tony Luck
---
drivers/edac/ie31200_edac.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git
From: Jane Chu
Date: Thu, 25 May 2017 13:51:20 -0600
> SPARC M6-32 platform has (2^5) NUMA nodes, so need to bump up the
> CONFIG_NODES_SHIFT to 5.
>
> Orabug: 25577754
>
> Signed-off-by: Jane Chu
>
> Reviewed-by: Bob Picco
>
From: Jane Chu
Date: Thu, 25 May 2017 13:51:20 -0600
> SPARC M6-32 platform has (2^5) NUMA nodes, so need to bump up the
> CONFIG_NODES_SHIFT to 5.
>
> Orabug: 25577754
>
> Signed-off-by: Jane Chu
>
> Reviewed-by: Bob Picco
> Reviewed-by: Atish Patra
This looks fine, applied, thanks.
Include and convert kselftest to the Sphinx format.
Changes since v2:
* lighten the modifications (suggested by Kees Cook)
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Jonathan Corbet
Cc: Shuah Khan
---
Include and convert kselftest to the Sphinx format.
Changes since v2:
* lighten the modifications (suggested by Kees Cook)
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Jonathan Corbet
Cc: Shuah Khan
---
Documentation/dev-tools/index.rst | 1 +
Move kselftest.txt to dev-tools/kselftest.rst .
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Jonathan Corbet
Cc: Shuah Khan
---
Documentation/00-INDEX | 2 --
Move kselftest.txt to dev-tools/kselftest.rst .
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Jonathan Corbet
Cc: Shuah Khan
---
Documentation/00-INDEX | 2 --
Documentation/{kselftest.txt => dev-tools/kselftest.rst} | 0
2 files changed, 2
Hi,
This patch series make the seccomp/test_harness.h more generally available [1]
and update the kselftest documentation in the Sphinx format. It also improve
the Makefile of seccomp tests to take into account any kselftest_harness.h
update.
[1]
Hi,
This patch series make the seccomp/test_harness.h more generally available [1]
and update the kselftest documentation in the Sphinx format. It also improve
the Makefile of seccomp tests to take into account any kselftest_harness.h
update.
[1]
Remove the TEST_API() wrapper to expose the underlying macro arguments
to the documentation tools.
Use "git diff --patience" to get a more readable patch.
Changes since v4:
* standalone patch to ease the review (requested by Kees Cook)
Signed-off-by: Mickaël Salaün
Cc: Andy
Keep the content consistent with the new name.
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Andy Lutomirski
Cc: Shuah Khan
Cc: Will Drewry
---
Remove the TEST_API() wrapper to expose the underlying macro arguments
to the documentation tools.
Use "git diff --patience" to get a more readable patch.
Changes since v4:
* standalone patch to ease the review (requested by Kees Cook)
Signed-off-by: Mickaël Salaün
Cc: Andy Lutomirski
Cc:
Keep the content consistent with the new name.
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Andy Lutomirski
Cc: Shuah Khan
Cc: Will Drewry
---
tools/testing/selftests/kselftest_harness.h | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
Add ReST metadata to kselftest_harness.h to be able to include the
comments in the Sphinx documentation.
Changes since v4:
* exclude the TEST_API() changes (requested by Kees Cook)
Changes since v3:
* document macros as actual functions (suggested by Jonathan Corbet)
* remove the TEST_API()
Add ReST metadata to kselftest_harness.h to be able to include the
comments in the Sphinx documentation.
Changes since v4:
* exclude the TEST_API() changes (requested by Kees Cook)
Changes since v3:
* document macros as actual functions (suggested by Jonathan Corbet)
* remove the TEST_API()
Rebuild the seccomp tests when kselftest_harness.h is updated.
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Andy Lutomirski
Cc: Shuah Khan
Cc: Will Drewry
---
The seccomp/test_harness.h file contains useful helpers to build tests.
Moving it to the selftest directory should benefit to other test
components.
Keep seccomp maintainers for this file.
Changes since v1:
* rename to kselftest_harness.h (suggested by Shuah Khan)
* keep maintainers
The seccomp/test_harness.h file contains useful helpers to build tests.
Moving it to the selftest directory should benefit to other test
components.
Keep seccomp maintainers for this file.
Changes since v1:
* rename to kselftest_harness.h (suggested by Shuah Khan)
* keep maintainers
Rebuild the seccomp tests when kselftest_harness.h is updated.
Signed-off-by: Mickaël Salaün
Acked-by: Kees Cook
Cc: Andy Lutomirski
Cc: Shuah Khan
Cc: Will Drewry
---
tools/testing/selftests/seccomp/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Fri, May 26, 2017 at 02:32:42PM +0300, Alexander Amelkin wrote:
> NOTE:
> Please don't use the plain text here as a patch because it most probably is
> corrupted by my webmail client.
> Attached is a copy of the following text guaranteed to have correct
> tabs/spaces.
Why is this here
On Fri, May 26, 2017 at 02:32:42PM +0300, Alexander Amelkin wrote:
> NOTE:
> Please don't use the plain text here as a patch because it most probably is
> corrupted by my webmail client.
> Attached is a copy of the following text guaranteed to have correct
> tabs/spaces.
Why is this here
On Fri, May 26, 2017 at 02:22:47PM +0300, Alexander Amelkin wrote:
> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
>
> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
>
> are available in the git repository at:
>
>
On Fri, May 26, 2017 at 02:22:47PM +0300, Alexander Amelkin wrote:
> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
>
> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
>
> are available in the git repository at:
>
>
On Fri, May 26, 2017 at 03:04:26PM +0200, Jan Kiszka wrote:
> Greg,
>
> On 2017-05-13 09:28, Jan Kiszka wrote:
> > This is the safe default for GPIOs with unknown external wiring.
> >
> > Signed-off-by: Jan Kiszka
> > ---
> > drivers/tty/serial/8250/8250_exar.c | 4 ++--
On Fri, May 26, 2017 at 03:04:26PM +0200, Jan Kiszka wrote:
> Greg,
>
> On 2017-05-13 09:28, Jan Kiszka wrote:
> > This is the safe default for GPIOs with unknown external wiring.
> >
> > Signed-off-by: Jan Kiszka
> > ---
> > drivers/tty/serial/8250/8250_exar.c | 4 ++--
> > 1 file changed, 2
On Fri, May 26, 2017 at 11:10:32AM +0100, Juri Lelli wrote:
> Hi,
>
> On 25/05/17 15:18, Greg KH wrote:
> > On Thu, Apr 20, 2017 at 03:43:16PM +0100, Juri Lelli wrote:
> > > Now that some functions that deal with arch topology information live
> > > under drivers, there is a clash of naming that
On Fri, May 26, 2017 at 11:10:32AM +0100, Juri Lelli wrote:
> Hi,
>
> On 25/05/17 15:18, Greg KH wrote:
> > On Thu, Apr 20, 2017 at 03:43:16PM +0100, Juri Lelli wrote:
> > > Now that some functions that deal with arch topology information live
> > > under drivers, there is a clash of naming that
On Fri, May 26, 2017 at 10:45:59AM -0700, Badhri Jagan Sridharan wrote:
> User space applications in some cases have the need to enforce a
> specific port type(DFP/UFP/DRP). This change allows userspace to
> attempt setting the desired port type. Low level drivers can
> however reject the request
On Fri, May 26, 2017 at 10:45:59AM -0700, Badhri Jagan Sridharan wrote:
> User space applications in some cases have the need to enforce a
> specific port type(DFP/UFP/DRP). This change allows userspace to
> attempt setting the desired port type. Low level drivers can
> however reject the request
On 05/26/2017 01:07 AM, Matt Redfearn wrote:
[...]
-{ insn_lwx, 0, 0 },
-{ insn_ldx, 0, 0 },
-{ insn_invalid, 0, 0 }
+static struct insn insn_table_MM[insn_invalid] = {
^ You could make this const too, like you have the one in uasm-mips.c.
Good catch. I meant to do that.
I
On 05/26/2017 01:07 AM, Matt Redfearn wrote:
[...]
-{ insn_lwx, 0, 0 },
-{ insn_ldx, 0, 0 },
-{ insn_invalid, 0, 0 }
+static struct insn insn_table_MM[insn_invalid] = {
^ You could make this const too, like you have the one in uasm-mips.c.
Good catch. I meant to do that.
I
From: Lin Zhang
Date: Thu, 25 May 2017 14:07:18 +0800
> There is a race condition in llc_ui_bind if two or more processes/threads
> try to bind a same socket.
>
> If more processes/threads bind a same socket success that will lead to
> two problems, one is this action
From: Lin Zhang
Date: Thu, 25 May 2017 14:07:18 +0800
> There is a race condition in llc_ui_bind if two or more processes/threads
> try to bind a same socket.
>
> If more processes/threads bind a same socket success that will lead to
> two problems, one is this action is not what we expected,
Dear Talented,
I am Talent Scout For Sony Pictures Animation, Present Sony Pictures Animation
Movies a Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope
Dear Talented,
I am Talent Scout For Sony Pictures Animation, Present Sony Pictures Animation
Movies a Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope
> static void __pvcalls_back_accept(struct work_struct *work)
> {
> + struct sockpass_mapping *mappass = container_of(
> + work, struct sockpass_mapping, register_work);
> + struct sock_mapping *map;
> + struct pvcalls_ioworker *iow;
> + struct pvcalls_back_priv
> static void __pvcalls_back_accept(struct work_struct *work)
> {
> + struct sockpass_mapping *mappass = container_of(
> + work, struct sockpass_mapping, register_work);
> + struct sock_mapping *map;
> + struct pvcalls_ioworker *iow;
> + struct pvcalls_back_priv
This patch adds Device Tree support to the Analog Devices
digital potentiometers (SPI bus) AD525x driver.
Signed-off-by: Roshni Shah
---
.../devicetree/bindings/misc/ad525x_dpot-spi.txt | 44 ++
drivers/misc/ad525x_dpot-spi.c | 161
This patch adds Device Tree support to the Analog Devices
digital potentiometers (SPI bus) AD525x driver.
Signed-off-by: Roshni Shah
---
.../devicetree/bindings/misc/ad525x_dpot-spi.txt | 44 ++
drivers/misc/ad525x_dpot-spi.c | 161 -
2 files
On Vi, 2017-05-26 at 14:55 +0200, Frederic Weisbecker wrote:
> On Wed, May 24, 2017 at 03:39:24PM +0300, Octavian Purdila wrote:
> >
> > Currently, when detecting expired timers in
> > tick_nohz_stop_sched_tick
> > we just schedule a new hrtimer and let its handler to schedule
> > TIMER_SOFITRQ.
On Vi, 2017-05-26 at 14:55 +0200, Frederic Weisbecker wrote:
> On Wed, May 24, 2017 at 03:39:24PM +0300, Octavian Purdila wrote:
> >
> > Currently, when detecting expired timers in
> > tick_nohz_stop_sched_tick
> > we just schedule a new hrtimer and let its handler to schedule
> > TIMER_SOFITRQ.
On Fri, May 26, 2017 at 10:45:59AM -0700, Badhri Jagan Sridharan wrote:
> User space applications in some cases have the need to enforce a
> specific port type(DFP/UFP/DRP). This change allows userspace to
> attempt setting the desired port type. Low level drivers can
> however reject the request
On Fri, May 26, 2017 at 10:45:59AM -0700, Badhri Jagan Sridharan wrote:
> User space applications in some cases have the need to enforce a
> specific port type(DFP/UFP/DRP). This change allows userspace to
> attempt setting the desired port type. Low level drivers can
> however reject the request
User space applications in some cases have the need to enforce a
specific port type(DFP/UFP/DRP). This change allows userspace to
attempt setting the desired port type. Low level drivers can
however reject the request if the specific port type is not supported.
Signed-off-by: Badhri Jagan
User space applications in some cases have the need to enforce a
specific port type(DFP/UFP/DRP). This change allows userspace to
attempt setting the desired port type. Low level drivers can
however reject the request if the specific port type is not supported.
Signed-off-by: Badhri Jagan
On Fri, May 26, 2017 at 02:45:21PM +0200, Miroslav Benes wrote:
> If TRIM_UNUSED_KSYMS is enabled, all unneeded exported symbols are made
> unexported. Two-pass build of the kernel is done to find out which
> symbols are needed based on a configuration. This effectively
> complicates things for
On Fri, May 26, 2017 at 02:45:21PM +0200, Miroslav Benes wrote:
> If TRIM_UNUSED_KSYMS is enabled, all unneeded exported symbols are made
> unexported. Two-pass build of the kernel is done to find out which
> symbols are needed based on a configuration. This effectively
> complicates things for
401 - 500 of 1416 matches
Mail list logo