On Tue, Jul 21, 2015 at 06:50:45PM -0700, Sukadev Bhattiprolu wrote:
> We are trying to use the following interface:
>
> start_txn(pmu, PERF_PMU_TXN_READ);
>
> perf_event_read(leader);
> list_for_each(sibling, >sibling_list, group_entry)
> perf_event_read(sibling)
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
> Hi Stefan,
>
> On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner wrote:
> > Hi Dmitry,
> >
> > As the original author of the driver I have some remarks to your review
> >
> > On 2015-07-18 01:42, Dmitry Torokhov wrote:
> > >> +
Thinkpad X240 laptop has a working acpi_video backlight control but
using the default native backlight control, brightness keys does not work.
This patch force acpi_video use for this laptop by adding an exception in
video_detect_dmi_table.
Signed-off-by: Mathieu OTHACEHE
---
On Tue, 2015-07-21 at 22:18 -0700, Jörn Engel wrote:
> On Wed, Jul 22, 2015 at 06:36:30AM +0200, Mike Galbraith wrote:
> > On Tue, 2015-07-21 at 15:07 -0700, Spencer Baugh wrote:
> >
> > > We have observed cases where the soft lockup detector triggered, but no
> > > kernel bug existed. Instead
From: Pan Xinhui
It's more reasonable to unlock memtype_lock right after
rbt_memtype_check_insert. memtype_lock protects all data stored in
rb-tree from multiple access. It's not cool to call kfree, pr_info, etc
with this lock held. So move spin_unlock a little ahead.
If *new* succeed to be
On 07/22/2015 12:43 PM, Bob Liu wrote:
>
> On 07/21/2015 05:25 PM, Roger Pau Monné wrote:
>> El 21/07/15 a les 5.30, Bob Liu ha escrit:
>>> This BUG_ON() in blkif_free() is incorrect, because indirect page can be
>>> added
>>> to list info->indirect_pages in blkif_completion() no matter
>>>
From: Konstantin Khlebnikov
Date: Tue, 21 Jul 2015 19:46:29 +0300
> @@ -23,7 +23,8 @@ static inline struct cgroup_cls_state *css_cls_state(struct
> cgroup_subsys_state
>
> struct cgroup_cls_state *task_cls_state(struct task_struct *p)
> {
> - return css_cls_state(task_css(p,
From: Chris J Arges
Date: Tue, 21 Jul 2015 12:36:33 -0500
> Some architectures like POWER can have a NUMA node_possible_map that
> contains sparse entries. This causes memory corruption with openvswitch
> since it allocates flow_cache with a multiple of num_possible_nodes() and
> assumes the
Hi Dmitry,
On 07/20/2015 11:54 AM, Dmitry Torokhov wrote:
> On Sun, Jul 19, 2015 at 11:09:30PM -0700, Tony Lindgren wrote:
>> * Vignesh R [150719 21:53]:
>>> @@ -445,6 +443,8 @@ static struct pixcir_ts_platform_data
>>> *pixcir_parse_dt(struct device *dev)
>>> dev_dbg(dev, "%s: x %d, y %d,
Hi all,
Changes since 20150721:
The nfsd tree lost its build failure.
The wireless-drivers-next tree gained a build failure so I used the
version from next-20150721.
The kvms390 tree gained a conflict against the s390 tree.
The gpio tree lost its build failure.
Non-merge commits (relative
On Tue, 2015-07-21 at 10:55 +0200, Mike Galbraith wrote:
> On Sun, 2015-07-19 at 10:02 +0200, Mike Galbraith wrote:
>
> > Why do we do nothing about these allegedly unbound work items?
>
> My box seems to think the answer is: no reason other than nobody having
> asked the source to please not do
From: Nicolas Schichan
Date: Tue, 21 Jul 2015 14:14:11 +0200
> These patches are fixing bugs in the ARM JIT and should probably find
> their way to a stable kernel. All 60 test_bpf tests in Linux 4.1 release
> are now passing OK (was 54 out of 60 before).
Series applied, thanks.
--
To
On Wed, Jul 22, 2015 at 06:36:30AM +0200, Mike Galbraith wrote:
> On Tue, 2015-07-21 at 15:07 -0700, Spencer Baugh wrote:
>
> > We have observed cases where the soft lockup detector triggered, but no
> > kernel bug existed. Instead we had a buggy realtime thread that
> > monopolized a cpu. So
On Wed, Jul 22, 2015 at 04:03:07AM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jul 21, 2015 at 07:17:41PM -0500, Michael Welling wrote:
> > On Tue, Jul 21, 2015 at 11:34:41AM +0200, Pavel Machek wrote:
> >
> > This code has my head spinning.
> >
> > I found that the errors do not occur
On Wed, 2015-07-22 at 00:46 -0400, David Long wrote:
> On 06/29/15 23:29, Michael Ellerman wrote:
> > On Wed, 2015-06-17 at 14:30 -0400, David Long wrote:
> >> On 06/16/15 09:17, Rob Herring wrote:
> >>> On Mon, Jun 15, 2015 at 11:42 AM, David Long wrote:
>
> #define
> +static void nest_change_cpu_context(int old_cpu, int new_cpu)
> +{
> + int i;
> +
> + for (i = 0; per_nest_pmu_arr[i] != NULL; i++)
> + perf_pmu_migrate_context(_nest_pmu_arr[i]->pmu,
> + old_cpu, new_cpu);
From patch 4, I see
On Mon, 20 Jul 2015 15:29:37 +0200 Christoph Hellwig wrote:
> Currently we have two different ways to signal an I/O error on a BIO:
>
> (1) by clearing the BIO_UPTODATE flag
> (2) by returning a Linux errno value to the bi_end_io callback
>
> The first one has the drawback of only
> +static void p8_nest_read_counter(struct perf_event *event)
> +{
> + uint64_t *addr;
> + u64 data = 0;
You've got a u64 and a uint64_t, and then...
> +
> + addr = (u64 *)event->hw.event_base;
... you cast to event_base to a u64 pointer, which you assign to a
uint64_t pointer.
> +
On 2015년 07월 22일 11:02, Joonyoung Shim wrote:
> On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> Today's linux-next (next-20150721) encounters boot failures on Exynos
>> Octa (Exynos5422) based boards. T
On Tue, Jul 21, 2015 at 10:08:28AM +0300, Andy Shevchenko wrote:
> On Tue, Jul 21, 2015 at 7:50 AM, Vinod Koul wrote:
> > On Mon, Jul 20, 2015 at 11:46:28AM +0300, Andy Shevchenko wrote:
> >> >> +static void idma64_chan_init(struct idma64 *idma64, struct idma64_chan
> >> >> *idma64c)
> >> >> +{
On Tue, Jul 21, 2015 at 10:14:11AM +0200, Michal Suchanek wrote:
> > Or alternatively we could publish the limitations of the channel using
> > capabilities so SPI knows I have a dmaengine channel and it can transfer
> > max N
> > length transfers so would be able to break rather than guessing it
On 06/29/15 23:29, Michael Ellerman wrote:
On Wed, 2015-06-17 at 14:30 -0400, David Long wrote:
On 06/16/15 09:17, Rob Herring wrote:
On Mon, Jun 15, 2015 at 11:42 AM, David Long wrote:
#define REG_OFFSET_NAME(r) \
{.name = #r, .offset = offsetof(struct pt_regs, ARM_##r)}
On Thu, 2015-07-16 at 16:43 +0530, Madhavan Srinivasan wrote:
> Add code to create event/format attributes and attribute groups for
> each nest pmu.
>
> Cc: Michael Ellerman
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Anton Blanchard
> Cc: Sukadev Bhattiprolu
> Cc: Anshuman
Previous patches introduce llvm__compile_bpf() to compile source file to
eBPF object. This patch adds testcase to test it. It also tests libbpf
by opening generated object after applying next patch which introduces
HAVE_LIBBPF_SUPPORT option.
Since llvm__compile_bpf() prints long messages which
On Tue, Jul 21, 2015 at 09:39:23PM -0700, Andy Lutomirski wrote:
> So your shiny perf profile shows cumulative time in whatever called
> them. Sure, this is arguably silly if we're stuck with frame
> pointers.
You can count 20ish cycles tops for any one of them.
At least that was from the last
On 07/21/2015 05:25 PM, Roger Pau Monné wrote:
> El 21/07/15 a les 5.30, Bob Liu ha escrit:
>> This BUG_ON() in blkif_free() is incorrect, because indirect page can be
>> added
>> to list info->indirect_pages in blkif_completion() no matter
>> feature_persistent
>> is true or false.
>>
>>
On 07/21/15 at 12:22pm, Yinghai Lu wrote:
> On Tue, Jul 21, 2015 at 1:58 AM, Baoquan He wrote:
>
> > Maybe system which don't need low memory is rare, only for testing?
>
> No, it is not rare.
>
> All recent intel based systems with iommu support does not need low.
>
> And those systems get
Hi Arnaldo,
I noticed that you have rebase your perf/ebpf branch to 4.2-rc3. I have also
done it in my tree. Please see:
https://github.com/WangNan0/linux.git ebpf
Also, please recollect patch "perf tests: Add LLVM test for eBPF on-the-fly
compiling", which adds verbose control. I'll also
On Tue, Jul 21, 2015 at 9:25 PM, Borislav Petkov wrote:
> On Tue, Jul 21, 2015 at 05:13:12PM -0700, Andy Lutomirski wrote:
>> Enough for oopses, perhaps, but maybe not enough for perf.
>>
>> It sounds like you want CFI unwinding :)
>
> What would you want to unwind in those __sw_hweight*
On Tue, 2015-07-21 at 15:07 -0700, Spencer Baugh wrote:
> We have observed cases where the soft lockup detector triggered, but no
> kernel bug existed. Instead we had a buggy realtime thread that
> monopolized a cpu. So let's kill the responsible party and not panic
> the entire system.
If you
On Tue, Jul 21, 2015 at 05:13:12PM -0700, Andy Lutomirski wrote:
> Enough for oopses, perhaps, but maybe not enough for perf.
>
> It sounds like you want CFI unwinding :)
What would you want to unwind in those __sw_hweight* almost-trivial,
tail functions?
--
Regards/Gruss,
Boris.
ECO tip
On Tue, Jul 21, 2015 at 02:50:25PM -0400, Jason Baron wrote:
> hmmm...so this is a case where need to the default the branch
> to the out-of-line branch at boot. That is, we can't just enable
> the out-of-line branch at boot time, b/c it might be too late at
> that point? IE native_sched_clock()
On Tue, Jul 21, 2015 at 7:53 PM, Brian Gerst wrote:
> On Tue, Jul 21, 2015 at 10:12 PM, Andy Lutomirski wrote:
>> On Tue, Jul 21, 2015 at 7:01 PM, Brian Gerst wrote:
>>> On Tue, Jul 21, 2015 at 3:59 PM, Andy Lutomirski wrote:
modify_ldt has questionable locking and does not synchronize
On Wed, 22 Jul 2015, Michael Schmitz wrote:
> Hi Finn,
>
> I'm afraid I cannot test anything on Atari hardware at present - my
> Falcon ate it's IDE disk partition table with all the fun that entails.
That doesn't sound good.
> Haven't even begun to try and recover that yet.
>
> If you
On Thu, Jul 09, 2015 at 10:11:05PM +0200, Laurent Navet wrote:
> derivatio -> derivation.
>
> Signed-off-by: Laurent Navet
Thanks, applied.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
> static struct perchip_nest_info p8_nest_perchip_info[P8_NEST_MAX_CHIPS];
> +static struct nest_pmu *per_nest_pmu_arr[P8_NEST_MAX_PMUS];
> +
> +static int nest_event_info(struct property *pp, char *name,
> + struct nest_ima_events *p8_events, int string, u32 val)
'int
On Thu, Jul 09, 2015 at 10:07:14PM +0200, Laurent Navet wrote:
> Return value of ext4_derive_key_aes() is stored but not used.
> Add test to exit cleanly if ext4_derive_key_aes() fail.
> Also fix coverity CID 1309760.
>
> Signed-off-by: Laurent Navet
Thanks, applied.
On Tue, Jul 21, 2015 at 4:58 PM, Luis R. Rodriguez wrote:
> On Sun, Jul 19, 2015 at 08:18:23PM -0400, Dan Williams wrote:
>> diff --git a/include/linux/io.h b/include/linux/io.h
>> index 080a4fbf2ba4..2983b6e63970 100644
>> --- a/include/linux/io.h
>> +++ b/include/linux/io.h
>> @@ -192,4 +192,15
During hwsim_init_netlink(), we should call genl_unregister_family()
if failed on netlink_register_notifier() since the genetlink is
already registered.
Signed-off-by: Su Kang Yin
---
drivers/net/wireless/mac80211_hwsim.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
This patch updates the tracing_thresh information
in ftrace documentation file(ftrace.txt).
Signed-off-by: Umesh Tiwari
---
Documentation/trace/ftrace.txt |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/trace/ftrace.txt
On Tue, Jun 16, 2015 at 06:53:13PM -0400, Tejun Heo wrote:
> For ordered and writeback data modes, all data IOs go through
> ext4_io_submit. This patch adds cgroup writeback support by invoking
> wbc_init_bio() from io_submit_init_bio() and wbc_account_io() in
> io_submit_add_bh(). Journal data
On Tue, Jun 16, 2015 at 06:53:12PM -0400, Tejun Heo wrote:
> ext4_io_submit_init() takes the pointer to writeback_control to test
> its sync_mode and determine between WRITE and WRITE_SYNC and records
> the result in ->io_op. This patch makes it record the pointer
> directly and moves the test to
Hi Finn,
I'm afraid I cannot test anything on Atari hardware at present - my
Falcon ate it's IDE disk partition table with all the fun that entails.
Haven't even begun to try and recover that yet.
If you send a patch I could build a kernel and send that to Christian
for testing (if he's got
Hi,
> +static struct perchip_nest_info p8_nest_perchip_info[P8_NEST_MAX_CHIPS];
> +
> +static int nest_ima_dt_parser(void)
> +{
> + const __be32 *gcid;
> + const __be64 *chip_ima_reg;
> + const __be64 *chip_ima_size;
> + struct device_node *dev;
> + struct perchip_nest_info
On 07/21/2015 08:26 PM, Eddie Huang wrote:
From: Greta Zhang
Without .shutdown(), watchdog might reset the system during power off.
For example, if watchdog's timeout is set to 30s, then it is reset to
zero by mtk_wdt_ping(). During power off, no app will ping watchdog,
but watchdog is still
From: Mathieu Poirier
This patch adds a driver that models itself as an stm_source and
who's sole purpose is to export an interface to the rest of the
kernel. Once the stm and stm_source have been linked via sysfs,
everything that is passed to the interface will endup in the STM
trace engine.
When the trace event happens, the traces would be committed to ring buffer.
This patch will add an output of the traces to an STM at this moment,
of course the precondition is TRACE_EVENT_STM be configured.
Signed-off-by: Chunyan Zhang
---
kernel/trace/trace_events.c | 2 ++
This patch introduced a new function to print the trace events logs
to STM buffer when the trace event happens.
Signed-off-by: Chunyan Zhang
---
kernel/trace/Makefile | 1 +
kernel/trace/trace_output_stm.c | 22 ++
2 files changed, 23 insertions(+)
create mode
IP blocks allowing a variety of trace sources to log debugging
information to a pre-defined area have been introduced on a couple of
architecture [1][2]. These system trace blocks (also known as STM)
typically follow the MIPI STPv2 protocol [3] and provide a system wide
logging facility to any
On 07/21/2015 08:26 PM, Eddie Huang wrote:
From: Greta Zhang
add wdt driver suspend/resume support
Signed-off-by: Greta Zhang
Signed-off-by: Roger Lu
Signed-off-by: Eddie Huang
---
drivers/watchdog/mtk_wdt.c | 38 ++
1 file changed, 38 insertions(+)
From: Greta Zhang
add wdt driver suspend/resume support
Signed-off-by: Greta Zhang
Signed-off-by: Roger Lu
Signed-off-by: Eddie Huang
---
drivers/watchdog/mtk_wdt.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/drivers/watchdog/mtk_wdt.c
From: Greta Zhang
Without .shutdown(), watchdog might reset the system during power off.
For example, if watchdog's timeout is set to 30s, then it is reset to
zero by mtk_wdt_ping(). During power off, no app will ping watchdog,
but watchdog is still running and may trigger reset.
Signed-off-by:
This series add Mediatek watchdog suspend, resume and shutdown support.
These patches are based on v4.2-rc1
Greta Zhang (2):
watchdog: add wdt suspend/resume support
watchdog: add wdt shutdown callback to disable wdt if enabled
drivers/watchdog/mtk_wdt.c | 47
On Tue, Jul 21, 2015 at 06:14:06PM -0400, Donald Parsons wrote:
> On Tue, 2015-07-21 at 14:10 -0700, Greg Kroah-Hartman wrote:
> > > Andrew Morton (1):
> > > arch/x86/kvm/mmu.c: work around gcc-4.4.4 bug
> > >
> > > which must be it. Added Andrew to cc as he hopefully knows the
> > answer
I'm announcing the release of the 4.1.3 kernel.
All users of the 4.1 kernel series must upgrade.
The updated 4.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.1.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
index 0f7afb2bb442..aef8cc5a677b 100644
--- a/Documentation/DMA-API-HOWTO.txt
+++ b/Documentation/DMA-API-HOWTO.txt
@@ -25,13 +25,18 @@ physical addresses. These are the addresses in
/proc/iomem. The physical
diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
index 0f7afb2bb442..aef8cc5a677b 100644
--- a/Documentation/DMA-API-HOWTO.txt
+++ b/Documentation/DMA-API-HOWTO.txt
@@ -25,13 +25,18 @@ physical addresses. These are the addresses in
/proc/iomem. The physical
--
Note, this is the last 4.0-stable release, it is now end-of-life.
Please move to 4.1-stable at this point in time.
--
I'm announcing the release of the 4.0.9 kernel.
All users of the 4.0 kernel series must
From: Minfei Huang
Now, ftrace only calculate the dyn_ftrace number in the adding
breakpoint loop, not in adding update and finish update loop.
Calculate the correct dyn_ftrace, once ftrace reports the failure message
to the userspace.
Signed-off-by: Minfei Huang
---
arch/x86/kernel/ftrace.c
On Tue, Jul 21, 2015 at 10:12 PM, Andy Lutomirski wrote:
> On Tue, Jul 21, 2015 at 7:01 PM, Brian Gerst wrote:
>> On Tue, Jul 21, 2015 at 3:59 PM, Andy Lutomirski wrote:
>>> modify_ldt has questionable locking and does not synchronize
>>> threads. Improve it: redesign the locking and
On Tue, Jul 21, 2015 at 09:40:29PM -0400, Mike Snitzer wrote:
> On Tue, Jul 21 2015 at 9:00pm -0400,
> Dave Chinner wrote:
>
> > On Wed, Jul 22, 2015 at 10:09:23AM +1000, Dave Chinner wrote:
> > > On Tue, Jul 21, 2015 at 01:47:53PM -0400, Mike Snitzer wrote:
> > > > On Tue, Jul 21 2015 at
On Wednesday, July 22, 2015 03:56:21 AM Rafael J. Wysocki wrote:
> On Wednesday, July 22, 2015 01:15:01 AM Rafael J. Wysocki wrote:
> > Hi VIresh,
> >
> > On Mon, Jul 20, 2015 at 11:47 AM, Viresh Kumar
> > wrote:
> > > Consider a dual core (0/1) system with two CPUs:
> > > - sharing
On 07/22/15 at 10:19am, Dave Young wrote:
> ---
>
> Update per comments from Vivek:
> - Moved below functions which are used by kexec_load only to kexec.c
> copy_user_segment_list() and kimage_alloc_init()
> - add slab.h to kexec.c because kimage_alloc_init will call kfree
> - drop unused
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
arch/s390/kernel/entry.S
between commit:
2a1a14484b97 ("s390/kernel: lazy restore fpu registers")
3af40983a937 ("s390/kvm: fix interrupt race with HANDLE_SIE_INTERCEPT")
0be8cda612d8 ("s390/kvm: integrate
2015-07-21 23:46 GMT+09:00 Uwe Kleine-König :
> From: Uwe Kleine-König
>
> The gpiod functions include variants for managed gpiod resources. Use it
> to simplify the remove function.
>
> As the driver handles a device node without a specification of dvs gpios
> just fine, additionally use the
On Wed, Jul 15, 2015 at 08:04:41AM +0800, Yuyang Du wrote:
> The cfs_rq's load_avg is composed of runnable_load_avg and blocked_load_avg.
> Before this series, sometimes the runnable_load_avg is used, and sometimes
> the load_avg is used. Completely replacing all uses of runnable_load_avg
> with
Now there's two kexec load syscall, one is kexec_load another is
kexec_file_load, kexec_file_load has been splited as kernel/kexec_file.c.
In this patch I split kexec_load syscall code to kernel/kexec.c.
And add a new kconfig option KEXEC_CORE, so we can disable kexec_load
and use kexec_file_load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.18.19 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
On 07/21/15 at 09:03am, Vivek Goyal wrote:
> On Mon, Jul 20, 2015 at 04:37:15PM +0800, dyo...@redhat.com wrote:
> > Now there's two kexec load syscall, one is kexec_load another is
> > kexec_file_load, kexec_file_load has been splited as kernel/kexec_file.c.
> > In this patch I split kexec_load
On Tue, Jul 21, 2015 at 7:04 PM, Boris Ostrovsky
wrote:
>
>
> On 07/21/2015 08:49 PM, Andrew Cooper wrote:
>>
>> On 22/07/2015 01:28, Andy Lutomirski wrote:
>>>
>>> On Tue, Jul 21, 2015 at 5:21 PM, Andrew Cooper
>>> wrote:
On 22/07/2015 01:07, Andy Lutomirski wrote:
>
> On Tue,
On Tue, Jul 21, 2015 at 7:01 PM, Brian Gerst wrote:
> On Tue, Jul 21, 2015 at 3:59 PM, Andy Lutomirski wrote:
>> modify_ldt has questionable locking and does not synchronize
>> threads. Improve it: redesign the locking and synchronize all
>> threads' LDTs using an IPI on all modifications.
>
>
On 07/13/2015 07:35 PM, Eric Anholt wrote:
> This interrupt controller is the new root interrupt controller with
> the timer, PMU events, and IPIs, and the bcm2835's interrupt
> controller is chained off of it to handle the peripherals.
> diff --git a/drivers/irqchip/irq-bcm2836.c
On 07/13/2015 07:35 PM, Eric Anholt wrote:
> The BCM2836 (Raspberry Pi 2) uses two levels of interrupt handling
> with the CPU-local interrupts being the root, so we need to register
> ours as chained off of the CPU's local interrupt.
Sorry for the slow review; laziness after vacation!
> diff
On 07/21/2015 08:49 PM, Andrew Cooper wrote:
On 22/07/2015 01:28, Andy Lutomirski wrote:
On Tue, Jul 21, 2015 at 5:21 PM, Andrew Cooper
wrote:
On 22/07/2015 01:07, Andy Lutomirski wrote:
On Tue, Jul 21, 2015 at 4:38 PM, Andrew Cooper
wrote:
On 21/07/2015 22:53, Boris Ostrovsky wrote:
On
The Kconfig for this option is currently:
config SERIAL_SGI_L1_CONSOLE
bool "SGI Altix L1 serial console support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the orphaned module code, so that when reading the
driver there is no doubt it is builtin-only.
The Kconfig for this driver is currently:
config SERIAL_SUNHV
bool "Sun4v Hypervisor Console support"
...meaning that it currently is not being built as a module by
anyone. Lets remove the modular and unused code here, so that
when reading the driver there is no doubt it is
Hi,
On Tue, Jul 21, 2015 at 07:17:41PM -0500, Michael Welling wrote:
> On Tue, Jul 21, 2015 at 11:34:41AM +0200, Pavel Machek wrote:
>
> This code has my head spinning.
>
> I found that the errors do not occur when the driver is built into the kernel.
>
> I also found that with the patch below
The Kconfig for this option is currently:
config SERIAL_LANTIQ
bool "Lantiq serial driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modularity, so that when reading the
driver there is no doubt it is builtin-only.
Since
The Kconfig for this driver is currently:
config SERIAL_SUNCORE
bool
...meaning that it currently is not being built as a module by
anyone. Lets remove the modular and unused code here, so that
when reading the driver there is no doubt it is builtin-only.
Since module_init translates
In the previous merge window, we made changes to allow better
delineation between modular and non-modular code in commit
0fd972a7d91d6e15393c449492a04d94c0b89351 ("module: relocate module_init
from init.h to module.h"). This allows us to now ensure module code
looks modular and non-modular code
On 07/21/2015 10:19 PM, Krzysztof Kozlowski wrote:
> Hi,
>
> Today's linux-next (next-20150721) encounters boot failures on Exynos
> Octa (Exynos5422) based boards. The boards hangs. I bisected it to:
>
> d80167b85024982c5f18d0481a5c248100360118 is the first b
On Tue, Jul 21, 2015 at 3:59 PM, Andy Lutomirski wrote:
> modify_ldt has questionable locking and does not synchronize
> threads. Improve it: redesign the locking and synchronize all
> threads' LDTs using an IPI on all modifications.
What does this fix? I can see sending an IPI if the LDT is
On 7/21/2015 5:06 PM, Kees Cook wrote:
> On Tue, Jul 21, 2015 at 5:03 PM, Casey Schaufler
> wrote:
>> On 7/21/2015 3:41 PM, Kees Cook wrote:
>>> On Tue, Jul 21, 2015 at 1:56 PM, Casey Schaufler
>>> wrote:
On 7/21/2015 1:09 PM, Josh Boyer wrote:
> On Tue, Jul 21, 2015 at 3:48 PM, Casey
2015-07-22 5:04 GMT+08:00 Jan Kiszka :
> On 2015-07-16 17:58, Houcheng Lin wrote:
>> Add data window feature to show current kernel status
>> on separate consoles, including: 1) registers, 2) back
>> trace and 3) watch data windows.
>>
>> The data window would help kernel developer to understand
On 7/21/2015 1:35 PM, Seth Forshee wrote:
> On Thu, Jul 16, 2015 at 05:59:22PM -0700, Andy Lutomirski wrote:
>> On Thu, Jul 16, 2015 at 5:45 PM, Casey Schaufler
>> wrote:
>>> On 7/16/2015 4:29 PM, Andy Lutomirski wrote:
I really don't see the benefit of making up extra rules that apply to
Peter Zijlstra [pet...@infradead.org] wrote:
| On Tue, Jul 14, 2015 at 08:01:54PM -0700, Sukadev Bhattiprolu wrote:
| > +/*
| > + * Use the transaction interface to read the group of events in @leader.
| > + * PMUs like the 24x7 counters in Power, can use this to queue the events
| > + * in the
On 07/14/2015 05:48 AM, Noralf Trønnes wrote:
> Den 14.07.2015 06:50, skrev Stephen Warren:
>> On 07/11/2015 09:26 AM, Noralf Trønnes wrote:
>>> Den 11.07.2015 06:09, skrev Stephen Warren:
(Sorry for the slow reply; I was on vacation)
On 06/18/2015 07:32 AM, Noralf Trønnes wrote:
From: Rafael J. Wysocki
The second sif argument of __cpufreq_remove_dev_prepare() is
never used by it, so drop it.
The second sif argument of __cpufreq_remove_dev_finish() is only
used for one check that is not necessary if the policy is freed
by cpufreq_remove_dev() itself, so make
On Wed, 2015-07-15 at 03:30 -0700, Jeff Kirsher wrote:
> On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote:
> > e1000e_disable_aspm_locked() is only used in __e1000_resume() which is
> > inside CONFIG_PM. So when CONFIG_PM=n we get a "defined but not used"
> > warning for
On Tue, Jul 21 2015 at 9:00pm -0400,
Dave Chinner wrote:
> On Wed, Jul 22, 2015 at 10:09:23AM +1000, Dave Chinner wrote:
> > On Tue, Jul 21, 2015 at 01:47:53PM -0400, Mike Snitzer wrote:
> > > On Tue, Jul 21 2015 at 11:34am -0400, Eric Sandeen
> > > wrote:
> > > > On 7/20/15 5:36 PM, Dave
On Tue, Jul 21, 2015 at 1:57 AM, Sagi Grimberg wrote:
> How were you able to get a chained SG list in the target code?
Local hack. So this bug can't be hit in current mainline code, but
patch improves the code and removes a hidden booby-trap, so I think it
makes sense to apply.
--
To
On Thu, Jun 25, 2015 at 02:20:42AM +0200, Javier Martinez Canillas wrote:
> The Chrome platform support depends on X86 || ARM because there are
> only Chromebooks using those architectures. But only some drivers
> depend on a given architecture, and the ones that do already have
> a dependency on
On Thu, Jun 25, 2015 at 10:44:28AM +0200, Javier Martinez Canillas wrote:
> Hello Lee,
>
> On 06/25/2015 10:38 AM, Lee Jones wrote:
> > On Thu, 25 Jun 2015, Javier Martinez Canillas wrote:
> >
> >> A dependency on X86 || ARM for MFD_CROS_EC was added to fix the warning:
> >>
> >> (MFD_CROS_EC)
On Tue, Jul 21, 2015 at 6:13 PM, Paul Gortmaker
wrote:
> [Re: [PATCH 2/3] mfd: Remove MFD_CROS_EC depends on X86 || ARM] On 25/06/2015
> (Thu 10:44) Javier Martinez Canillas wrote:
>
>> Hello Lee,
>>
>> On 06/25/2015 10:38 AM, Lee Jones wrote:
>> > On Thu, 25 Jun 2015, Javier Martinez Canillas
Allow Broadcom iProc PCIe core driver to be compiled for ARM64
Signed-off-by: Ray Jui
Reviewed-by: Vikram Prakash
Reviewed-by: Scott Branden
---
drivers/pci/host/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig
This patch adds support to Broadcom's iProc family of arm64 based SoCs
in the arm64 Kconfig and defconfig files
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm64/Kconfig |5 +
arch/arm64/configs/defconfig |2 ++
2 files changed, 7 insertions(+)
diff --git
Add Broadcom NS2 device tree binding document. Also add initial device
tree dtsi for Broadcom North Star 2 (NS2) SoC and board support for NS2
SVK board
Signed-off-by: Jon Mason
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
Documentation/devicetree/bindings/arm/bcm/ns2.txt |9 ++
On Wednesday, July 22, 2015 01:15:01 AM Rafael J. Wysocki wrote:
> Hi VIresh,
>
> On Mon, Jul 20, 2015 at 11:47 AM, Viresh Kumar
> wrote:
> > Consider a dual core (0/1) system with two CPUs:
> > - sharing clock/voltage rails and hence cpufreq-policy
> > - CPU1 is offline while the cpufreq
This patch enables arm64 support to the iProc PCIe driver
Note struct pci_sys_data is arm32 specific and will eventually be
removed. This change is done in such a way that when struct pci_sys_data
is removed from arm32, one only needs to also remove it from
pcie-iproc.h, no other change in the
This patch series adds Broadcom North Star 2 (NS2) SoC support. NS2 is an ARMv8
based SoC and under the Broadcom iProc family.
Sorry for tying this with the Broadcom iProc PCIe driver fixes for ARM64. I
have to tie them together because iProc PCIe support is enabled by default
when ARCH_BCM_IPROC
1 - 100 of 2004 matches
Mail list logo
