On Tue, 3 Nov 2015, Petr Mladek wrote:
> Also I would omit the suffix at all when it is the first occurrence. It
> will cause that unique symbols will not be numbered.
That'd mean that the names (including suffixes) are not stable, because a
particular name that has originally been unique can
On Tue, Nov 3, 2015 at 10:28 AM, atull wrote:
> On Fri, 30 Oct 2015, Rob Herring wrote:
>
>> On Thu, Oct 29, 2015 at 11:02 AM, atull wrote:
>> > On Wed, 28 Oct 2015, Rob Herring wrote:
>> >
>> >> On Tue, Oct 27, 2015 at 5:09 PM, wrote:
>> >> > From: Alan Tull
>> >> >
>> >> > New bindings
On Tue, Nov 03, 2015 at 01:41:53PM -0600, Aravind Gopalakrishnan wrote:
> cpu_llc_id references should be wrapped under #ifdef CONFIG_SMP.
>
> Did that and kernel build worked with the attached config.
>
> Will send a V2 with the fix.
Why aren't you doing all that figuring out what the llc_id
This is a pretty big change that I haven't tested any, which worries
me a lot. The general idea here is that "struct elf_prstatus" can be
visible to userspace (from )
"
Generic ptrace interface that exports the architecture specific
regsets using the corresponding NT_* types (which are
On Tue, 3 Nov 2015, Grygorii Strashko wrote:
> On 11/02/2015 09:38 PM, Thomas Gleixner wrote:
> >
> > Why aren't you simply marking these demultiplex handlers with IRQ_NO_THREAD?
> >
> In general, it's possible. But, in this case, worst scenario will look like:
> dra7xx_pcie_msi_irq_handler()
>
This used to be hidden behind CONFIG_MMAP_ALLOW_UNINITIALIZED, so
userspace wouldn't actually ever see it be non-zero. While I had
originally hoped to avoid hiding it, it looks like this conflicts with
MAP_HUGE_SHIFT so I think it's safer to just keep this 0.
Architectures that want to define
I'm not sure what this is, but it doesn't feel like something that
should be exposed to userspace here. I'm assuming this file was
exposed for the structure in it, which doesn't depend on
MAX_SHARED_LIBS.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
This doesn't make any sense to expose to userspace, so it's been moved
to the one user. This was introduced by commit 95f19f658ce1 ("epoll:
drop EPOLLWAKEUP if PM_SLEEP is disabled").
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
fs/eventpoll.c
Nothing else in the kernel defines this, and this header is visible to
userspace. Rather than hiding it in an #ifdef, I think it's sane to
just make this visible to userspace.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert Ou
---
include/uapi/linux/fb.h | 3
This has a "#ifdef CONFIG_*" that used to be exposed to userspace.
The names in here are so generic that I don't think it's a good idea
to expose them to userspace (or even the rest of the kernel). Since
there's only one kernel user, it's been moved to that file.
Signed-off-by: Palmer Dabbelt
I don't think this was ever intended to be exposed to userspace, but
it did require an "#ifdef CONFIG_*". Since the name is kind of
generic and was only used in one place, I've moved the definition to
the one user.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew Waterman
Reviewed-by: Albert
I think this change actually doesn't do anything: __NR_fork was still
being defined either way, and on my machine fork() in comes
from libc.
This just moves to the standard mechanism for defining syscalls that
aren't implemented instead, which has the side-effect of no longer
having an #ifdef
While I don't think this was ever meant to be exposed to userspace, if
anyone is using it then this will at least provide a correct (if
unlikely) definition.
MAX_RAW_MINORS used to be used in the kernel, where it's been replaced
with CONFIG_MAX_RAW_MINORS.
Note that there's a checkpatch.pl
This used to be behind an #ifdef COMPAT_COMPAT, so most of userspace
wouldn't have seen the definition before. Unfortunately this header
file became visible to userspace, so the definition has instead been
moved to net/atm/svc.c (the only user).
Signed-off-by: Palmer Dabbelt
Reviewed-by: Andrew
It looks like there aren't actually users of this macro anywhere:
* The kernel doesn't use it on x86 because we don't suppor ELF FDPIC.
* The only Google results point to LMKL patches, both the one that
wrote this (from 2010) and my patch to hide it behind __KERNEL__.
* I grep'd through
I recently got bit by a CONFIG_ in userspace bug. This has apparently
happened before, but the check got disabled for triggering too much.
In order to reduce false positives, I added some hueristics to avoid
detecting comments.
Since these tests all pass, I've now re-enabled them.
When working on the RISC-V port I noticed that F_SETLK64 was being
defined on our 64-bit platform, despite our port being so new that
we've only ever had the 64-bit file ops. Since there's not compat
layer for these, this causes fcntl to bail out.
It turns out that one of the ways in with
I think this is good to go. There are two acks, but I wasn't sure if I was
supposed to collect them in the patches or not. Arnd Bergman acked #1 and #7.
Changes since v3 (<1442271047-4908-1-git-send-email-pal...@dabbelt.com>)
* #4 is very different: rather than defining a canonical value for
On 11/3/2015 1:27 PM, kbuild test robot wrote:
Hi Aravind,
[auto build test ERROR on bp/for-next]
[also ERROR on: v4.3 next-20151103]
url:
https://github.com/0day-ci/linux/commits/Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
base
Hello, Tetsuo.
On Tue, Nov 03, 2015 at 11:32:06AM +0900, Tetsuo Handa wrote:
> Tejun Heo wrote:
> > If
> > the possibility of sysrq getting stuck behind concurrency management
> > is an issue, queueing them on an unbound or highpri
On Mon, Nov 2, 2015 at 5:57 PM, Paul E. McKenney
wrote:
>>
>> Alpha isn't special. And smp_read_barrier_depends() hasn't magically
>> become something new.
>
> The existing control dependencies (READ_ONCE_CTRL() and friends) only
> guarantee ordering against later stores, and not against later
On Tue, Nov 3, 2015 at 6:56 AM, Arnd Bergmann wrote:
> The input_configured callback was recently changed to return
> an 'int', but the newly added driver uses the old API:
>
> drivers/hid/hid-gfrm.c:151:22: warning: initialization from incompatible
> pointer type [-Wincompatible-pointer-types]
On Sun, Nov 01, 2015 at 11:30:10PM -0500, Dan Williams wrote:
> This masking prevents access to the end of the device via dax_do_io(),
> and is unnecessary as arch_add_memory() would have rejected an unaligned
> allocation.
>
> Cc:
> Cc: Ross Zwisler
> Signed-off-by: Dan Williams
> ---
>
On Tue, Nov 03, 2015 at 11:09:51AM -0800, Alexandra Yates wrote:
> @@ -161,6 +162,13 @@ static const struct ata_port_info ahci_port_info[] = {
> .port_ops = _ops,
> },
> /* by chipsets */
> + [board_ahci_lbg] = {
> + .flags =
Hi Aravind,
[auto build test ERROR on bp/for-next]
[also ERROR on: v4.3 next-20151103]
url:
https://github.com/0day-ci/linux/commits/Aravind-Gopalakrishnan/x86-intel_cacheinfo-Fix-LLC-topology-for-AMD-Fam17h-systems/20151104-031725
base: https://github.com/0day-ci/linux
Aravind
Adding Intel codename Lewisburg platform device IDs for PCH.
Signed-off-by: Alexandra Yates
---
drivers/mfd/lpc_ich.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/mfd/lpc_ich.c b/drivers/mfd/lpc_ich.c
index c5a9a08..d9904ac6 100644
--- a/drivers/mfd/lpc_ich.c
+++
On Wed, 21 Oct 2015, Thomas Gleixner wrote:
> On Tue, 20 Oct 2015, John Stultz wrote:
>> Being able to have various hardware sharing a time base is quite
>> useful, and methods for correlating timestamps together are useful.
>> But I don't yet really understand why its important that we can
>>
On Tue, Nov 3, 2015 at 10:10 AM, Daniel Cashman wrote:
> From: dcashman
>
> arm: arch_mmap_rnd() uses a hard-code value of 8 to generate the
> random offset for the mmap base address. This value represents a
> compromise between increased ASLR effectiveness and avoiding
> address-space
On Tue, Nov 3, 2015 at 10:10 AM, Daniel Cashman wrote:
> From: dcashman
>
> ASLR currently only uses 8 bits to generate the random offset for the
> mmap base address on 32 bit architectures. This value was chosen to
> prevent a poorly chosen value from dividing the address space in such
> a way
On AMD Fam17h systems, the last level cache is not resident in
Northbridge. Therefore, we cannot assign cpu_llc_id to same
value as Node ID (as we have been doing currently)
We should rather look at the ApicID bits of the core to provide
us the last level cache ID info. Doing that here.
On Sun, Nov 01, 2015 at 11:30:04PM -0500, Dan Williams wrote:
> Before the dynamically allocated struct pages from devm_memremap_pages()
> can be put to use outside the driver, we need a mechanism to track
> whether they are still in use at teardown. Towards that goal reorder
> the initialization
On 10/22/2015 05:42 PM, Dave Hansen wrote:
> On 10/22/2015 02:39 PM, Sasha Levin wrote:
>> > Trinity seems to be able to hit the newly added warnings pretty easily:
> Kirill reported the same thing. Is it fixed with this applied?
>
>> >
>> Resource are defined as index and as match_table_t.
>>
>> enum rdma_resource_type {
>> RDMA_VERB_RESOURCE_UCTX,
>> RDMA_VERB_RESOURCE_AH,
>> RDMA_VERB_RESOURCE_PD,
>> RDMA_VERB_RESOURCE_CQ,
>> RDMA_VERB_RESOURCE_MR,
>> RDMA_VERB_RESOURCE_MW,
>>
On 11/02/2015 09:38 PM, Thomas Gleixner wrote:
> On Mon, 2 Nov 2015, Grygorii Strashko wrote:
>> Now in kernel below code pattern is used by many drivers:
>> static irqreturn_t driver_xx_hw_irq_handler(int irq, void *arg)
>> {
>>
>>
>>
>> for () {
>>
>>
On 11/03/2015 03:46 PM, Sebastian Andrzej Siewior wrote:
> On 11/02/2015 08:30 PM, Grygorii Strashko wrote:
>> On -RT above code will generate warnings, because driver_xx_hw_irq_handler()
>> will be forced threaded (by default) and, as result, generic_handle_irq()
>> will be called with IRQs
Ross Zwisler writes:
> On Sun, Nov 01, 2015 at 11:29:58PM -0500, Dan Williams wrote:
>> The DAX implementation needs to protect new calls to ->direct_access()
>> and usage of its return value against unbind of the underlying block
>> device. Use blk_queue_enter()/blk_queue_exit() to either
Adding Intel codename Lewisburg platform device IDs for SATA.
Signed-off-by: Alexandra Yates
---
drivers/ata/ahci.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index a466602..8c7a04a 100644
--- a/drivers/ata/ahci.c
+++
Hi Viresh,
On 30 October 2015 at 22:36, Viresh Kumar wrote:
> Hi Ashwin,
>
> On 30-10-15, 16:46, Ashwin Chaugule wrote:
>> On 29 October 2015 at 08:27, Viresh Kumar wrote:
>> > This could be made lightweight by keeping per-cpu deferred timers with a
>> > single work item, which is scheduled by
On Sun, Nov 01, 2015 at 11:29:58PM -0500, Dan Williams wrote:
> The DAX implementation needs to protect new calls to ->direct_access()
> and usage of its return value against unbind of the underlying block
> device. Use blk_queue_enter()/blk_queue_exit() to either prevent
> blk_cleanup_queue()
Hi,
On Tue, Nov 3, 2015 at 3:30 AM, Will Deacon wrote:
> On Tue, Nov 03, 2015 at 04:10:08PM +0800, Caesar Wang wrote:
>> As the following log:
>> where we experience a CPU hard lockup. The assembly code (disassembled by
>> gdb)
>>
>> 0xc06c6e90 <__tcp_select_window+148>:beq
>>
On Tue, Nov 03, 2015 at 03:55:29PM +0100, Geert Uytterhoeven wrote:
> On Tue, Nov 3, 2015 at 3:38 PM, Catalin Marinas
> wrote:
> > On Tue, Nov 03, 2015 at 12:05:05PM +, Catalin Marinas wrote:
> >> On Tue, Nov 03, 2015 at 12:07:06PM +0100, Geert Uytterhoeven wrote:
> >> > On Wed, Oct 28, 2015
Jarkko,
On Tue, Nov 03, 2015 at 01:09:00PM +0200, Jarkko Nikula wrote:
> Commit d80d134182ba ("i2c: designware: Move common probe code into
> i2c_dw_probe()") caused the I2C adapter lookup code here to fail for PCI
> enumerated i2c-designware because commit changed the adapter name but
> didn't
TP_ARGS is not used anywhere in trace.h nor trace_entries.h
Firstly, I left just #undef TP_ARGS and had no errors - remove it.
Signed-off-by: Dmitry Safonov <0x7f454...@gmail.com>
---
kernel/trace/trace.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/trace/trace.h
On 11/03/2015 01:15 PM, Andrey Ryabinin wrote:
> 2015-11-03 20:20 GMT+03:00 Sasha Levin :
>> Anyone knows why wasn't this merged a year ago? I didn't see any review
>> comments, and it
>> ended up finding real bugs.
>>
>
> Probably because I didn't ping so it just lost.
> I'll send v3 after the
On Tue, Nov 3, 2015 at 8:04 AM, markus at trippelsdorf dot de
wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=19197
>
> Markus Trippelsdorf changed:
>
>What|Removed |Added
>
On Tue, 3 Nov 2015 21:25:44 +0300
Dmitry Safonov <0x7f454...@gmail.com> wrote:
> Ping?
Thanks, this was lost in my INBOX. I'll take a look at it.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Em Tue, Nov 03, 2015 at 08:41:48AM +0100, Jiri Olsa escreveu:
> On Mon, Nov 02, 2015 at 07:53:53PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Nov 02, 2015 at 12:10:25PM +0100, Jiri Olsa escreveu:
> > > If machine's thread gets excited (EXIT event is received),
> > > we set thread->dead =
From: SF Markus Elfring
Date: Tue, 3 Nov 2015 18:30:58 +0100
> From: Markus Elfring
> Date: Tue, 3 Nov 2015 18:18:37 +0100
>
> The irlmp_unregister_service() function tests whether its argument is NULL
> and then returns immediately. Thus the test around the call is not needed.
>
> This issue
On 11/03/15 15:04, Paolo Bonzini wrote:
>
>
> On 03/11/2015 15:02, Laszlo Ersek wrote:
>> On 11/03/15 14:46, Paolo Bonzini wrote:
>>>
>>>
>>> On 03/11/2015 14:40, Laszlo Ersek wrote:
On 11/03/15 14:29, Paolo Bonzini wrote:
> The SDM says that exiting system management mode from 64-bit
Hi Stefano,
[auto build test ERROR on arm64/for-next/core]
[cannot apply to: xen-tip/linux-next]
[also ERROR on: v4.3 next-20151103]
url:
https://github.com/0day-ci/linux/commits/Stefano-Stabellini/xen-arm-arm64-CONFIG_PARAVIRT-and-stolen-ticks-accounting/20151104-002433
base: https
Ping?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Em Thu, Oct 15, 2015 at 07:58:38PM +0800, Wangnan (F) escreveu:
> >>+void test__llvm_prepare(void)
> >>+{
> >>+ p_test_llvm__bpf_result = mmap(NULL, SHARED_BUF_INIT_SIZE,
> >>+ PROT_READ | PROT_WRITE,
> >>+ MAP_SHARED |
On Tue, Nov 03, 2015 at 06:59:58PM +0100, Oleg Nesterov wrote:
> > - raw_spin_unlock_wait(>pi_lock);
> > - smp_mb();
> > + smp_cond_acquire(!raw_spin_is_locked(>pi_lock));
>
> Unfortunately this doesn't look exactly right...
>
> spin_unlock_wait() is not equal to
On 11/01/2015 01:50 PM, Eric W. Biederman wrote:
> Daniel Cashman writes:
>
>> On 10/28/2015 08:41 PM, Eric W. Biederman wrote:
>>> Dan Cashman writes:
>>>
>> This all would be much cleaner if the arm architecture code were just to
>> register the sysctl itself.
>>
>> As it sits
This patch introduces a module that registers and implements a low-level
reset function for the AMD XGBE device.
it performs the following actions:
- reset the PHY
- disable auto-negotiation
- disable & clear auto-negotiation IRQ
- soft-reset the MAC
Those tiny pieces of code are inherited from
On Mon, Nov 2, 2015 at 4:39 PM, Dirk Steinmetz
wrote:
> In order to hardlink to a sgid-executable, it is sufficient to be the
> file's owner. When hardlinking within an unprivileged user namespace, the
> users of that namespace could thus use hardlinks to pin setgid binaries
> owned by themselves
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.18.24 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be
2015-11-03 20:20 GMT+03:00 Sasha Levin :
> Anyone knows why wasn't this merged a year ago? I didn't see any review
> comments, and it
> ended up finding real bugs.
>
Probably because I didn't ping so it just lost.
I'll send v3 after the merge window.
--
To unsubscribe from this list: send the
Let's retrieve the compatibility string on probe and store it
in the vfio_platform_device struct
Signed-off-by: Eric Auger
---
v2 -> v3:
- populate compat after vdev check
---
drivers/vfio/platform/vfio_platform_common.c | 15 ---
drivers/vfio/platform/vfio_platform_private.h |
To prepare for vfio platform reset rework let's build
vfio_platform_common.c and vfio_platform_irq.c in a separate
module from vfio-platform and vfio-amba. This makes possible
to have separate module inits and works around a race between
platform driver init and vfio reset module init: that way we
Jarkko,
On Tue, Nov 03, 2015 at 09:28:55AM +0200, Jarkko Nikula wrote:
> Hi
>
> On 03.11.2015 06:02, Jeremiah Mahler wrote:
> >Jarkko, all,
> >
> >Commit d80d134182ba5 introduced a bug which causes a cyapa based touch
> >pad on an Acer C720 Chromebook to become inoperative. This is present
>
This patch adds the reset function registration/unregistration.
This is handled through the module_vfio_reset_handler macro. This
latter also defines a MODULE_ALIAS which simplifies the load from
vfio-platform.
Signed-off-by: Eric Auger
Reviewed-by: Arnd Bergmann
---
v3 -> v4:
- I restored
This series fixes the current implementation by getting rid of the
usage of __symbol_get which caused a compilation issue with
CONFIG_MODULES disabled. On top of this, the usage of MODULE_ALIAS makes
possible to add a new reset module without being obliged to update the
framework. The new
The module_vfio_reset_handler macro
- define a module alias
- implement module init/exit function which respectively registers
and unregisters the reset function.
Signed-off-by: Eric Auger
Reviewed-by: Arnd Bergmann
---
v4 -> v5:
- add Arnd's R-b
v3 -> v4:
- pass reset to
In the current code the vfio_platform_region is copied on the stack.
As a consequence the ioaddr address is not iounmapped in the vfio
platform driver (vfio_platform_regions_cleanup). The patch uses the
pointer to the region instead.
Signed-off-by: Eric Auger
---
It might be helpful for the end-user to check the device reset
function was found by the vfio platform reset framework.
Lets store a pointer to the struct device in vfio_platform_device
and trace when the reset function is called or not found.
Signed-off-by: Eric Auger
---
v3: creation
---
In preparation for subsequent changes in reset function lookup,
lets introduce a dynamic list of reset combos (compat string,
reset module, reset function). The list can be populated/voided with
vfio_platform_register/unregister_reset. Those are not yet used in
this patch.
Signed-off-by: Eric
Remove the static lookup table and use the dynamic list of registered
reset functions instead. Also load the reset module through its alias.
The reset struct module pointer is stored in vfio_platform_device.
We also remove the useless struct device pointer parameter in
vfio_platform_get_reset.
From: dcashman
arm: arch_mmap_rnd() uses a hard-code value of 8 to generate the
random offset for the mmap base address. This value represents a
compromise between increased ASLR effectiveness and avoiding
address-space fragmentation. Replace it with a Kconfig option, which
is sensibly bounded,
From: dcashman
ASLR currently only uses 8 bits to generate the random offset for the
mmap base address on 32 bit architectures. This value was chosen to
prevent a poorly chosen value from dividing the address space in such
a way as to prevent large allocations. This may not be an issue on all
The following changes since commit 7379047d5585187d1288486d4627873170d0005a:
Linux 4.3-rc6 (2015-10-18 16:08:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git
tags/please-pull-pstore
for you to fetch changes up to
From: Yaowei Bai
Make rb_event_is_commit() return bool to improve readability
due to this particular function only using either one or zero as its
return value.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-7-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
From: Yaowei Bai
This patch makes report_latency return bool due to this
particular function only using either one or zero as its
return value.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-3-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
Signed-off-by:
From: Yaowei Bai
Make ftrace_event_is_function() return bool to improve readability
due to this particular function only using either one or zero as its
return value.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-9-git-send-email-bywxiao...@163.com
Signed-off-by:
From: Yaowei Bai
This patch makes report_latency return bool to improve readability,
indicating whether this new latency should be reported/recorded.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-2-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
From: Li Bin
Although, the default value of rel_type_nop is zero, and the value
of R_386_NONE/R_X86_64_NONE is zero too, but it should be assigned
a meaningful value explicitly, otherwise it looks confused.
Assign R_386_NONE to rel_type_nop for 386, assign R_X86_64_NONE
to rel_type_nop for
From: Yaowei Bai
Make is_legal_op() return bool to improve readability due to this particular
function only using either one or zero as its return value.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-8-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
From: Chunyan Zhang
The commit 889204278ccf ("tracing: Update trace-event-sample with
TRACE_SYSTEM_VAR documentation") changed TRACE_SYSTEM to 'sample-trace',
but didn't make the according change of its name in the comments.
Link:
From: Chunyan Zhang
There's no need to record the time tracepoints take when tracing is off.
This is because:
1) We cannot see these records since ring_buffer record is off at that
moment.
2) If tracing is off and benchmark tracepoint is enabled, the time
tracepoint takes is fewer than the same
From: Yaowei Bai
Makes rb_per_cpu_empty() return bool to improve readability.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-6-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
Signed-off-by: Steven Rostedt
---
kernel/trace/ring_buffer.c | 4 ++--
1 file
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: c6650b2e57725abaa2e36e620d06fa576d26c21c
Chunyan Zhang (2):
tracing: Only benchmark the time tracepoints take if tracing is on
Sample: Trace_event: Correct the comments
Jiaxing Wang (1):
From: Yaowei Bai
Make rb_is_reader_page() return bool to improve readability due to this
particular function only using either true or false as its return value.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-4-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
From: "Steven Rostedt (Red Hat)"
For the case where pids are already in set_event_pid, and one is added or
removed then each CPU should be checked to make sure that the new or old pid
is on or not on a CPU.
For example:
# echo 123 >> set_event_pid
or
# echo '!123' >> set_event_pid
Link:
From: Jiaxing Wang
Update instancd_rmdir to use tracefs_remove_recursive instead of
debugfs_remove_recursive.This was left in the transition from debugfs
to tracefs.
Link:
http://lkml.kernel.org/r/1445169490-18315-2-git-send-email-hello@gmail.com
Cc: sta...@vger.kernel.org # 4.1+
Fixes:
From: Yaowei Bai
Make ring_buffer_empty() and ring_buffer_empty_cpu() return bool.
No functional change.
Link:
http://lkml.kernel.org/r/1443537816-5788-5-git-send-email-bywxiao...@163.com
Signed-off-by: Yaowei Bai
Signed-off-by: Steven Rostedt
---
include/linux/ring_buffer.h | 4 ++--
Hi David
> -Original Message-
> From: David Daney [mailto:dda...@caviumnetworks.com]
> Sent: 03 November 2015 17:39
> To: Hanjun Guo
> Cc: Lorenzo Pieralisi; Sinan Kaya; Tomasz Nowicki; bhelg...@google.com;
> a...@arndb.de; will.dea...@arm.com; catalin.mari...@arm.com;
>
Hi Jungseok,
On 03/11/15 13:49, Jungseok Lee wrote:
> Additionally, I've been thinking of do_softirq_own_stack() which is your
> another comment [3]. Recently, I've realized there is possibility that
> I misunderstood your intention. Did you mean that irq_handler hook is not
> enough? Should
On Mon, Nov 02, 2015 at 09:31:11PM -0800, Dan Williams wrote:
> On Mon, Nov 2, 2015 at 8:48 PM, Dave Chinner wrote:
> > On Mon, Nov 02, 2015 at 07:27:26PM -0800, Dan Williams wrote:
> >> On Mon, Nov 2, 2015 at 4:51 PM, Dave Chinner wrote:
> >> > On Sun, Nov 01, 2015 at 11:29:53PM -0500, Dan
On 11/03/2015 10:31 AM, Mark Brown wrote:
On Tue, Nov 03, 2015 at 09:57:46AM -0600, Andrew F. Davis wrote:
On 10/31/2015 09:37 PM, Mark Brown wrote:
On Fri, Oct 30, 2015 at 05:41:43PM -0500, Andrew F. Davis wrote:
+ struct regulator_desc desc;
+ unsigned int decay_reg;
+
On Wed, 4 Nov 2015, kbuild test robot wrote:
> Hi Stefano,
>
> [auto build test ERROR on arm64/for-next/core]
> [cannot apply to: xen-tip/linux-next]
> [also ERROR on: v4.3 next-20151103]
>
> url:
> https://github.com/0day-ci/linux/commits/Stefano-Stabellini/xen-a
On Mon, 2 Nov 2015 20:33:39 -0500
Jeff Layton wrote:
> On Mon, 2 Nov 2015 14:56:33 -0500
> Jeff Layton wrote:
>
> > On Mon, 2 Nov 2015 09:48:41 -1000
> > Chris Worley wrote:
> >
> > > On Sat, Oct 31, 2015 at 11:54 AM, Jeff Layton
> > > wrote:
> > > > On Sat, 31 Oct 2015 17:31:07 -0400
> >
On 11/03/2015 12:45 PM, Dmitry Vyukov wrote:
> On Tue, Nov 3, 2015 at 6:35 PM, Dmitry Vyukov wrote:
>> > I guess just nobody reviewed this. I would like to see this merged as well.
Hm, at v2 it was working pretty well and the feeling I got was that there are
no further review comments (rather
On Sat, Oct 10, 2015 at 7:59 AM, Dirk Steinmetz
wrote:
> Attempting to hardlink to an unsafe file (e.g. a setuid binary) from
> within an unprivileged user namespace fails, even if CAP_FOWNER is held
> within the namespace. This may cause various failures, such as a gentoo
> installation within a
Hello Caesar,
On Thu, Oct 29, 2015 at 03:14:15PM +0800, Caesar Wang wrote:
> The RK3368 SoCs support to 2 channel TS-ADC, the temperature criteria
> of each channel can be configurable.
>
> The system has two Temperature Sensors, channel 0 is for CPU,
> and channel 1 is for GPU.
Please improve
+Andrey
On Tue, Nov 3, 2015 at 6:35 PM, Dmitry Vyukov wrote:
> I guess just nobody reviewed this. I would like to see this merged as well.
>
>
>
> On Tue, Nov 3, 2015 at 6:20 PM, Sasha Levin wrote:
>> Anyone knows why wasn't this merged a year ago? I didn't see any review
>> comments, and it
On 11/3/2015 11:55 AM, Arnd Bergmann wrote:
On Tuesday 03 November 2015 11:33:18 Sinan Kaya wrote:
On 11/3/2015 10:59 AM, Arnd Bergmann wrote:
On Tuesday 03 November 2015 10:10:21 Sinan Kaya wrote:
I don't see anywhere in the SBSA spec addendum that the PCI
configuration space section
It's probably a good idea to keep the patches bisectable, so I made this
a separate patch which applies on top of the first one.
(Note that it completely removes all the code from the first patch, so
there's no need for a v2 of the first patch which would have had
Miroslav's suggested style
>It's slightly winding code, but if you look at the callers of
>efivar_init() you'll see that none of them set both 'atomic' and
>'duplicates', so dup_variable_bug() will never be called while holding
>a spinlock.
>Or am I missing something?
I was assuming that there could be a possibility when
On 11/03/2015 07:19 AM, Hanjun Guo wrote:
On 11/03/2015 10:15 PM, Lorenzo Pieralisi wrote:
On Wed, Oct 28, 2015 at 02:46:37PM -0400, Sinan Kaya wrote:
[...]
-int raw_pci_write(unsigned int domain, unsigned int bus,
-unsigned int devfn, int reg, int len, u32 val)
+struct pci_ops
I guess just nobody reviewed this. I would like to see this merged as well.
On Tue, Nov 3, 2015 at 6:20 PM, Sasha Levin wrote:
> Anyone knows why wasn't this merged a year ago? I didn't see any review
> comments, and it
> ended up finding real bugs.
>
> On 11/14/2014 07:50 AM, Andrey Ryabinin
301 - 400 of 1812 matches
Mail list logo
