The global kprobes_all_disarmed flag says that all Kprobes are disarmed
even when they are marked as enabled. Therefore the flag should get
checked by kprobe_disarmed().
Signed-off-by: Petr Mladek
---
kernel/kprobes.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --gi
On CPM2, the SPI parameter RAM is dynamically allocated in the dualport RAM
whereas in CPM1, it is statically allocated to a default address with
capability to relocate it somewhere else via the use of CPM micropatch.
The address of the parameter RAM is given by the boot loader and expected
to be m
On Thu, Feb 26, 2015 at 9:54 AM, Peter Hurley wrote:
> On 02/26/2015 09:58 AM, Rob Herring wrote:
>> On Thu, Feb 26, 2015 at 8:48 AM, Peter Hurley
>> wrote:
>>> Hi Rob,
>>>
>>> On 02/24/2015 03:20 PM, Rob Herring wrote:
On Tue, Feb 24, 2015 at 1:53 PM, Peter Hurley
wrote:
[...]
>>>
This series of patchsets contains the Broadcom keypad controller driver
and device tree binding documentation.
Changes from v1:
- updated dt documentation to remove to matrix-keymap.txt
- removed bcm_kp_remove as it is not necessary
- removed key-interrupt-trigger-type dt binding
- added bcm_kp_re
- Original Message -
> From: "Peter Zijlstra"
> To: "Andi Kleen"
> Cc: "Andi Kleen" , x...@kernel.org,
> linux-kernel@vger.kernel.org, "mathieu desnoyers"
> , o...@redhat.com,
> paul...@linux.vnet.ibm.com, ru...@rustcorp.com.au,
> mi...@kernel.org
> Sent: Thursday, February 26, 2015 6:4
Hi Olof,
On 25 February 2015 at 17:59, Olof Johansson wrote:
> On Tue, Feb 17, 2015 at 07:26:50PM -0700, Simon Glass wrote:
>> Hi,
>>
>> On 16 February 2015 at 01:19, Javier Martinez Canillas
>> wrote:
>> > Hello Olof,
>> >
>> > On 02/02/2015 12:26 PM, Javier Martinez Canillas wrote:
>> >> Hello
(Removing stable from CC...)
Ping on this?
On Mon, Feb 02, 2015 at 02:58:36PM +0100, Quentin Casasnovas wrote:
> It is possible for the *_read*() functions to fail, in which case it'll
> leave its third argument untouched. Most of the code do not check the
> return value of *_read*() functions,
On Thu, Feb 26, 2015 at 07:16:28AM -0800, Andy Lutomirski wrote:
> I'm declaring a temporary moratorium on new development here until
> the already-queued stuff is in -tip, looks okay, and we're in an
> appropriate part of the cycle. The series is already huge.
>
> IOW I'm not applying this or the
Hello Kukjin,
On 02/26/2015 04:55 PM, Kukjin Kim wrote:
> Javier Martinez Canillas wrote:
>>
>> After this series all the peripherals in the Peach boards are working
>> at least at a basic level, more work is needed to make the ASoC audio
>> driver more robust or the WiFi chip to support highspee
Improper arithmetics when calculting the address of the extended ref could
lead to an out of bounds memory read and kernel panic.
Signed-off-by: Quentin Casasnovas
---
fs/btrfs/tree-log.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git fs/btrfs/tree-log.c fs/btrfs/tree-log.c
in
On Wed, 25 Feb 2015 22:26:44 -0500
Steven Rostedt wrote:
> +static int find_next_push_cpu(struct rq *rq)
> +{
> + struct rq *next_rq;
> + int cpu;
> +
> + while (1) {
> + cpu = rto_next_cpu(rq);
> + if (cpu >= nr_cpu_ids)
> + break;
> +
Javier Martinez Canillas wrote:
>
> Hello Kukjin,
>
Hi,
> This series adds support for the remaining peripherals that were not
> supported in the Exynos5420 Peach Pit and Exynos5800 Peach Pi boards.
>
> Javier Martinez Canillas (2):
> ARM: dts: Mux XMMCnDATA[0] pad correctly for Exynos5420 bo
On Thu, Feb 26, 2015 at 07:30:54AM -0800, Andy Lutomirski wrote:
> How can the error code be propagated? Would that echo command fail in
> case of error?
Yeah, either that or we can put the error code in the sysfs file which
userspace can cat.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim yo
We also make sure that user won't be able to reconfigure the window while it is
mmap'ed.
Signed-off-by: Dmitry Kalinkin
Cc: Igor Alekseev
---
drivers/staging/vme/devices/vme_user.c | 85 ++
drivers/vme/vme.c | 26 +++
include/linux/vm
The Exynos5420 SoC has 3 sets of 8 pads used as data lines for the 3
MMC/SD/SDIO slots. These needs to be muxed as SD_n_DATA instead of a
GPIO or external interrupt to allow the MMC controller to communicate
with the attached cards or SDIO devices.
Which data lines needs to be muxed as SD_n_DATA d
Hello Kukjin,
This series adds support for the remaining peripherals that were not
supported in the Exynos5420 Peach Pit and Exynos5800 Peach Pi boards.
Javier Martinez Canillas (2):
ARM: dts: Mux XMMCnDATA[0] pad correctly for Exynos5420 boards.
ARM: dts: Add WiFi module support for Peach bo
Dear all,
mmap() on VME bridge devices is a feature present in many existing Linux and
UNIX drivers. The proposed solution follows the approach so that mmap()
offsets are coherent with read() and write() offsets, which seems to be the
only manner compatible with the current vme_user API. It also
From: Tushar Behera
On Peach Pit and Pi boards, the Exynos SoC XCLKOUT pin provides
master clock (mclk) to the codec. So make it a clock consumer.
Signed-off-by: Tushar Behera
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 2 ++
arch/arm/boot/dts/exyn
Peach Pit and Pi boards have a WiFi module that is always powered
but needs toggling an enable pin and ungating a 32kHz reference
clock as part of their power sequencing.
Add a dev node for the SDIO slot and a MMC power sequence provider.
Signed-off-by: Javier Martinez Canillas
---
arch/arm/boo
From: Martyn Welch
The tsi148 driver is registering the slave images as supporting the "USER"
access modes and CR/CSR access mode rather than the master images as it
should.
Remove the incorrect case entries for these modes from the
tsi148_slave_set() function, stop registering slave_images as s
This implements more granular locking in vme_user_ioctl() by using separate
locks for each devfs device.
This also provides a synchronization between vme_user_read(), vme_user_write()
and vme_user_ioctl().
Signed-off-by: Dmitry Kalinkin
Cc: Igor Alekseev
---
drivers/staging/vme/devices/vme_use
Improper pointer arithmetics when calculating the address of the extended
header could lead to an out of bounds memory read and kernel panic.
Signed-off-by: Quentin Casasnovas
---
arch/x86/kernel/cpu/microcode/intel_early.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
On 02/26/2015 09:58 AM, Rob Herring wrote:
> On Thu, Feb 26, 2015 at 8:48 AM, Peter Hurley
> wrote:
>> Hi Rob,
>>
>> On 02/24/2015 03:20 PM, Rob Herring wrote:
>>> On Tue, Feb 24, 2015 at 1:53 PM, Peter Hurley
>>> wrote:
>>
>> [...]
>>
>> Direct earlycon
>>
>> This feature enables a
Currently an enabled break state is not disabled on final close nor on
re-open and has to be disabled manually.
Fix this by disabling break on port shutdown.
Reported-by: Jari Ruusu
Tested-by: Jari Ruusu
Signed-off-by: Johan Hovold
---
drivers/usb/serial/pl2303.c | 18 +-
1 fi
On Thu, 26 Feb 2015 16:44:16 +0100
"Rafael J. Wysocki" wrote:
> On Thursday, February 26, 2015 09:03:47 AM Boris Brezillon wrote:
> > Hi Rafael,
> >
> > On Wed, 25 Feb 2015 22:59:36 +0100
> > "Rafael J. Wysocki" wrote:
> >
> > > On Tuesday, February 24, 2015 10:55:59 AM Boris Brezillon wrote:
On Thursday 26 February 2015 17:18:41 Chanwoo Choi wrote:
> I add following aliases and serial_1/serial_3 dt node in board dtsi:
> I tested that change the alias of serial_x node.
>
> aliases {
> serial0 = &serial_1;
> serial1 = &serial_3;
>
ENTRY(lg_irq_enable)
/*
* The reverse of irq_disable, this sets lguest_data.irq_enabled to
* X86_EFLAGS_IF (ie. "Interrupts enabled").
*/
movl $X86_EFLAGS_IF, lguest_data+LGUEST_DATA_irq_enabled
/*
* But now we need to check if the Host wa
On Wed, Feb 25, 2015 at 02:25:19PM -0600, Christoph Lameter wrote:
> On Wed, 25 Feb 2015, Serge Hallyn wrote:
>
> > Yeah we could make this
>
> Well doing that breaks su.
Don't what exactly? You're saying that doing
pI' = pI
pA' = pA (pA is ambient)
pP' = (X & fP) | (pI & (fI | pA))
pE' = pP'
The omap_serial.txt binding documentation lacks a number of properties
that are used in DTS files for platforms incorporating this peripheral.
Fix this by documenting the missing required and optional fields and
add an example.
Signed-off-by: Matt Porter
---
.../devicetree/bindings/serial/omap_s
On 2/26/2015 6:35 AM, Kirill A. Shutemov wrote:
We would want to use number of page table level to define mm_struct.
Let's expose it as CONFIG_PGTABLE_LEVELS.
Signed-off-by: Kirill A. Shutemov
Cc: Chris Metcalf
Tested-by: Guenter Roeck
---
arch/tile/Kconfig | 5 +
1 file changed, 5 insert
On Tue, Feb 24, 2015 at 7:23 PM, Brian Gerst wrote:
> On Tue, Feb 24, 2015 at 3:08 PM, Denys Vlasenko
> wrote:
>> On Tue, Feb 24, 2015 at 9:02 PM, Andy Lutomirski wrote:
This currently fails in 32-bit kernels (at least in qemu):
/ # ./es_test
Allocated GDT index 7
[FAIL]
On Wed, Feb 25, 2015 at 3:47 AM, Borislav Petkov wrote:
> On Tue, Feb 24, 2015 at 12:49:09PM +, Kweh, Hock Leong wrote:
>> So the process steps basically look like this:
>> 1.) cat capsule_ticket===> acquire a number and lock mutex then
>>
Hi Maxime,
On Tue, Feb 24, 2015 at 05:55:08PM +0100, Maxime Ripard wrote:
> Hi Markus,
>
> On Mon, Feb 23, 2015 at 10:49:36PM +0100, Markus Pargmann wrote:
> > Hi,
> >
> > On Thu, Nov 13, 2014 at 03:06:54PM +0100, Maxime Ripard wrote:
> > > Hi,
> > >
> > > The current ft5x06 reports to the user
From: Ahmed S. Darwish
Use can-dev's unregister_candev() instead of directly calling
networking unregister_netdev(). While both are functionally
equivalent, unregister_candev() might do extra stuff in the
future than just calling networking layer unregistration code.
Signed-off-by: Ahmed S. Darw
On Thu, Feb 26, 2015 at 7:21 AM, Andy Lutomirski wrote:
> On Thu, Feb 26, 2015 at 3:42 AM, Ingo Molnar wrote:
>>
>> * Andy Lutomirski wrote:
>>
>>> >> I added that in and applied this patch.
>>> >
>>> > So this is not just slightly buggy, it's fundamentally
>>> > wrong as well as it removes the
From: Ahmed S. Darwish
A number of tx queue wake-up events went missing due to the
outlined scenario below. Start state is a pool of 16 tx URBs,
active tx_urbs count = 15, with the netdev tx queue open.
start_xmit() tx_acknowledge()
On 02/26/2015 06:05 AM, Zefan Li wrote:
>> +static void cpuset_seq_print_isolcpus(struct seq_file *sf, struct cpuset
>> *cs)
>> +{
>> +cpumask_var_t my_isolated_cpus;
>> +
>> +if (!alloc_cpumask_var(&my_isolated_cpus, GFP_KERNEL))
>> +return;
>> +
>
> Make it return -ENOMEM ?
On Thursday, February 26, 2015 09:03:47 AM Boris Brezillon wrote:
> Hi Rafael,
>
> On Wed, 25 Feb 2015 22:59:36 +0100
> "Rafael J. Wysocki" wrote:
>
> > On Tuesday, February 24, 2015 10:55:59 AM Boris Brezillon wrote:
> > > Hello,
> > >
> > > I put the
> > > IRQF_NO_SUSPEND_SAFE/IRQF_TIMER_SIB
From: Ahmed S. Darwish
Upon a URB submission failure, the driver calls usb_free_urb()
but then manually frees the URB buffer by itself. Meanwhile
usb_free_urb() has alredy freed out that transfer buffer since
we're the only code path holding a reference to this URB.
Remove two of such invalid m
From: Ahmed S. Darwish
The driver currently limits the number of outstanding, not yet
ACKed, transfers to 16 URBs. Meanwhile, the Kvaser firmware
provides its actual max supported number of outstanding
transmissions in its reply to the CMD_GET_SOFTWARE_INFO message.
One example is the UsbCan-II
On Thu, Feb 26, 2015 at 5:12 AM, tip-bot for Wang Nan wrote:
> Commit-ID: b4d8327024637cb2a1f7910dcb5d0ad7a096f473
> Gitweb: http://git.kernel.org/tip/b4d8327024637cb2a1f7910dcb5d0ad7a096f473
> Author: Wang Nan
> AuthorDate: Thu, 26 Feb 2015 13:49:39 +0800
> Committer: Ingo Molnar
> Co
From: Ahmed S. Darwish
The Kvaser firmware can only read and write messages that are
not crossing the USB endpoint's wMaxPacketSize boundary. While
receiving commands from the CAN device, if the next command in
the same URB buffer crossed that max packet size boundary, the
firmware puts a zero-le
On Thu, Feb 26, 2015 at 3:42 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> >> I added that in and applied this patch.
>> >
>> > So this is not just slightly buggy, it's fundamentally
>> > wrong as well as it removes the possibility of an RSP
>> > value optimization from the 64-bit path
On Wed, Feb 25, 2015 at 11:06 PM, Wang Nan wrote:
> The reason why mapping idt_table to fixmap area should also be applied
> to debug_idt_table and trace_idt_table. This patch does same thing for
> all IDTs.
>
> Signed-off-by: Wang Nan
> ---
>
> I believe trace_idt_table and debug_idt_table shoul
Em Mon, Feb 09, 2015 at 05:39:44AM +, kan.li...@intel.com escreveu:
> From: Kan Liang
> Currently, the perf diff only works with same binaries. That's because
> it compares the symbol start address. It doesn't work if the perf.data
> comes from different binaries. This patch matches the symbol
On Thu, Feb 26, 2015 at 6:13 AM, Denys Vlasenko
wrote:
> On Thu, Feb 26, 2015 at 12:04 AM, Borislav Petkov wrote:
>> On Wed, Feb 25, 2015 at 01:00:16AM +0100, Denys Vlasenko wrote:
>>> After TEST insn, JE actually performs "jump if zero",
>>> let's use JZ mnemonic instead.
>>>
>>> No code changes
On Thu, Feb 26, 2015 at 09:45:00AM -0500, J. Bruce Fields wrote:
> On Thu, Feb 26, 2015 at 11:00:46AM +, One Thousand Gnomes wrote:
> > On Tue, 17 Feb 2015 11:13:39 -0800
> > Linus Torvalds wrote:
> >
> > > On Tue, Feb 17, 2015 at 11:08 AM, J. Bruce Fields
> > > wrote:
> > > >
> > > > I agr
On Thu, Feb 26, 2015 at 6:08 AM, Denys Vlasenko wrote:
> If syscall_trace_enter_phase1 returns 0,
> code restores %rax from pt_regs->ax, but should restore it from
> pt_regs->orig_ax.
>
> The bug crept in because LOAD_ARGS macro was very sublty different
> from RESTORE_ARGS, it had only two callsi
Em Thu, Feb 26, 2015 at 03:55:01PM +0900, Masami Hiramatsu escreveu:
> Show usage if no action is specified or unexpected parameter
> is given. In other words, be more user friendly.
Thanks for doing that!
Doesn't apply due to previous patches being delayer at the moment.
- Arnaldo
> Signed-of
On Feb 26, 2015 1:55 AM, "Denys Vlasenko" wrote:
>
> On Wed, Feb 25, 2015 at 10:59 PM, Andy Lutomirski wrote:
> > On Wed, Feb 25, 2015 at 1:28 PM, Denys Vlasenko wrote:
> >> On 02/25/2015 09:10 PM, Andy Lutomirski wrote:
> >> This part?
> >>
> >> .macro FORK_LIKE func
> >> ENTRY(stub_\f
On Wed, Feb 25, 2015 at 10:15 PM, Wang Nan wrote:
> X86_TRAP_NMI, X86_TRAP_DF and X86_TRAP_MC use their own stack. Those
> stacks are invalid until cpu_init() installs TSS.
>
> This patch moves setting of the 3 gates after cpu_init().
>
> Signed-off-by: Wang Nan
> ---
>
> If I understand correctl
Hello.
On 02/26/2015 05:45 PM, Robert ABEL wrote:
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were replaced with interval of values that produce the same
number of clock ticks.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.
Em Thu, Feb 26, 2015 at 03:54:54PM +0900, Masami Hiramatsu escreveu:
> Use pr_debug instead of the combination of verbose and pr_info.
>
> "if (verbose) pr_info(...)" is same as "pr_debug(...)", replace it.
This one doesn't apply because 2/4 got delayed.
- Arnaldo
--
To unsubscribe from this lis
Em Thu, Feb 26, 2015 at 03:54:47PM +0900, Masami Hiramatsu escreveu:
> @@ -285,6 +308,7 @@ int cmd_buildid_cache(int argc, const char **argv,
> bool force = false;
> char const *add_name_list_str = NULL,
> *remove_name_list_str = NULL,
> +*purge_name_lis
On Thu, Feb 26, 2015 at 8:48 AM, Peter Hurley wrote:
> Hi Rob,
>
> On 02/24/2015 03:20 PM, Rob Herring wrote:
>> On Tue, Feb 24, 2015 at 1:53 PM, Peter Hurley
>> wrote:
>
> [...]
>
> Direct earlycon
>
> This feature enables arches and proms to start an earlycon directly,
> rather
On 02/26/2015 02:51 PM, Vlastimil Babka wrote:
> From: Jerome Marchand
>
> Currently looking at /proc//status or statm, there is no way to
> distinguish shmem pages from pages mapped to a regular file (shmem
> pages are mapped to /dev/zero), even though their implication in
> actual memory use is
On 26/02/15 13:21, Maxime Ripard wrote:
On Thu, Feb 26, 2015 at 09:16:27AM +, Srinivas Kandagatla wrote:
I think we are making simple eeprom framework too smart which will
break in future.
IMHO, Anything on top of eeprom interface that interprets the data should
not go into the eeprom fra
Hi Rob,
On 02/24/2015 03:20 PM, Rob Herring wrote:
> On Tue, Feb 24, 2015 at 1:53 PM, Peter Hurley
> wrote:
[...]
Direct earlycon
This feature enables arches and proms to start an earlycon directly,
rather than requiring an "earlycon=" command line parameter.
Devicetre
GPMC debug output is aligned to 10 characters for field names.
However, some fields have bigger names, screwing up the alignment.
Consequently, alignment was changed to longest field name (17 chars) for now.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 +-
1 file changed, 1 inse
This patch adds support for spawning buses as children of the GPMC.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 5cabac8..74a8c52 1006
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were replaced with interval of values that produce the same
number of clock ticks.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 35 ++-
1 file change
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
These are the changes I proposed in three separate patchsets
#([1], [2], [3]) rebased to 3.19 as well as new changes for little bugs
I noticed while preparing this patchset.
1. DEBUG was undefined in source code --> remove offending lines
2. add capability to have busses as children of the GPMC an
Em Thu, Feb 26, 2015 at 05:25:04PM +0900, Masami Hiramatsu escreveu:
> Fix get_real_path to free allocated memory when comp_dir
> is used for complementing path and getting an error.
While reviewing this patch I noticed this is needed, ack?
- Arnaldo
diff --git a/tools/perf/util/probe-event.c
On 25/02/2015 20:41, Radim Krčmář wrote:
> 2015-02-25 17:00+0100, Borislav Petkov:
>> Hi,
>>
>> commit in $Subject breaks my kvm guest on AMD host, causing it to do the
>> following below. Mouse doesn't work anymore in the guest, network is
>> gone too.
>>
>> Reverting it fixes the issue.
>
> Th
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
OMAP2+ GPMC driver undefines DEBUG, which makes it unnecessarily
hard to turn DEBUG on. Remove the offending lines.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 24696f5
> Sorry if I was unclear. My question was not _whether_ to fix this
> for earlycon, but rather _how_.
>
> IOW, is the ':' character accepted as a path terminator for
> 1. all nodes, so fix this in fdt_path_offset();
> 2. only chosen nodes;
> 3. unique to stdout-path, so fix this in early_init_dt_s
GPMC_CONFIG1_i parameters CLKACTIVATIONTIME and WAITMONITORINGTIME
have reserved values.
Raise an error if calculated timings try to program reserved values.
GPMC_CONFIG1_i ATTACHEDDEVICEPAGELENGTH and DEVICESIZE were already checked
when parsing the DT.
Explicitly comment invalid values on gpmc_
On Thu, Feb 26, 2015 at 11:00:46AM +, One Thousand Gnomes wrote:
> On Tue, 17 Feb 2015 11:13:39 -0800
> Linus Torvalds wrote:
>
> > On Tue, Feb 17, 2015 at 11:08 AM, J. Bruce Fields
> > wrote:
> > >
> > > I agree that it's weird, but I think it's what we're stuck with.
> >
> > And if by "w
On Thu, 2015-02-26 at 12:30 +0100, Ingo Molnar wrote:
> * Toshi Kani wrote:
>
> > On Wed, 2015-02-25 at 08:22 +0100, Ingo Molnar wrote:
> > > * Toshi Kani wrote:
> > >
> > > > +int set_pages_array_wt(struct page **pages, int addrinarray)
> > > > +{
> > > > + return _set_pages_array(pages,
Hi Guenter,
> On 02/26/2015 05:59 AM, Lukasz Majewski wrote:
> > The PWM FAN device can now be used as a thermal cooling device.
> > Necessary infrastructure has been added in this commit.
> >
> > Signed-off-by: Lukasz Majewski
> > Acked-by: Eduardo Valentin
> > ---
> > Changes for v2:
> > - Rep
Em Thu, Feb 26, 2015 at 01:57:42PM +0900, Masami Hiramatsu escreveu:
> (2015/02/25 22:25), Arnaldo Carvalho de Melo wrote:
> > Em Wed, Feb 25, 2015 at 11:53:16AM +0900, Masami Hiramatsu escreveu:
> >> (2015/02/25 3:49), Arnaldo Carvalho de Melo wrote:
> >> Hmm, strange. Could you tell me the versio
On 02/26/2015 02:51 PM, Vlastimil Babka wrote:
> Currently, /proc/pid/smaps will always show "Swap: 0 kB" for shmem-backed
> mappings, even if the mapped portion does contain pages that were swapped out.
> This is because unlike private anonymous mappings, shmem does not change pte
> to swap entry,
On 27.01.15 15:35, Stuart Yoder wrote:
> Hi Arnd/Alex,
>
> German has posted an example driver for the fsl-mc bus in his RFC
> "[RFC PATCH 1/1] drivers/bus: fsl-mc object allocator driver".
>
> In addition I have made available the skeleton for a driver for
> one of the objects/devices (crypto)
On 24.02.15 23:50, J. German Rivera wrote:
> The fsl-mc object allocator driver manages "allocatable" fsl-mc
> objects such as DPBPs, DPMCPs and DPCONs. It provides services to
> other fsl-mc drivers to allocate/deallocate these types of objects.
Oh sorry, what I forgot to mention in the other m
On 24.02.15 23:50, J. German Rivera wrote:
> The fsl-mc object allocator driver manages "allocatable" fsl-mc
> objects such as DPBPs, DPMCPs and DPCONs. It provides services to
I'd recommend to explain what these abbreviations mean. It's
ridiculously hard to remember what they are about. So plea
On 26/02/15 12:31, Rameshwar Sahu wrote:
> Hi Vinod,
>
>
> On Tue, Feb 24, 2015 at 6:23 PM, Rameshwar Prasad Sahu wrote:
>> This patch implements the APM X-Gene SoC DMA engine driver. The APM X-Gene
>> SoC DMA engine consists of 4 DMA channels for performing DMA operations.
>> These DMA operatio
2015-02-26, 14:54:33 +0100, Denys Vlasenko wrote:
> On Thu, Feb 26, 2015 at 1:11 PM, Denys Vlasenko
> wrote:
> > On Thu, Feb 26, 2015 at 10:55 AM, Denys Vlasenko
> > wrote:
> >> On Wed, Feb 25, 2015 at 10:59 PM, Andy Lutomirski
> >> wrote:
> >> In addition to my previous tests, I ran my home ma
On 25 February 2015 at 22:53, Shawn Guo wrote:
> On Wed, Feb 25, 2015 at 04:32:32PM -0700, Mathieu Poirier wrote:
>> diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm
>> b/Documentation/ABI/testing/sysfs-bus-coresight-devices-stm
>> new file mode 100644
>> index .
> On Feb 26, 2015, at 9:32 PM, Nicolas Ferre wrote:
>
> Le 08/02/2015 19:23, Boris Brezillon a écrit :
>> The gpiochip_lock_as_irq call can fail and return an error, while the
>> irq_startup is not expected to fail (returns an unsigned int which is not
>> checked by irq core code).
>>
>> irq_re
Hello.
On 02/26/2015 12:56 AM, Ameen Ali wrote:
Whenever there is a division it is usually worthwhile to
add some belt'n'braces code to ensure that cnt != 0, otherwise
a machine signal can occur.
Signed-off-by : Ameen Ali
---
drivers/net/ethernet/qlogic/qlcnic/qlcnic_dcb.c | 2 +-
1 file
On 02/21/2015 05:16 PM, Pavol Cupka wrote:
> Hi list,
>
> I am encountering a bug on my desktop PC. Running gentoo-sources
> (patches for gentoo) 3.19.0, gcc 4.8.4, glibc 2.19
Although there don't seem to be many gentoo patches on top, you should try
reproducing this with vanilla 3.19 kernel firs
On Thu, Feb 26, 2015 at 12:04 AM, Borislav Petkov wrote:
> On Wed, Feb 25, 2015 at 01:00:16AM +0100, Denys Vlasenko wrote:
>> After TEST insn, JE actually performs "jump if zero",
>> let's use JZ mnemonic instead.
>>
>> No code changes, but less confusion.
>>
>> Signed-off-by: Denys Vlasenko
>> C
On Thu, Feb 26, 2015 at 12:43:09PM +0100, Peter Zijlstra wrote:
> +static struct module *__tree_find(struct rb_root *r, unsigned long addr)
> +{
> + struct rb_node *n = r->rb_node;
> +
> + while (n) {
> + struct module *m = mod_entry(n);
> + int idx = mod_node_idx(m
* Xander Huff | 2015-01-28 15:06:59 [-0600]:
>>Fixed by wrapping the test definitions in #ifndef CONFIG_PREEMPT_RT_FULL
>>conditionals.
>>
>FYI: To be clearer, this should apply to all stable RT releases 3.4 and later.
Applied
Sebastian
--
To unsubscribe from this list: send the line "unsubscrib
Introduce /dev/zram-control interface which lets user-space to add a new zram
device (ZRAM_CTL_ADD ioctl) or remove the existing one (ZRAM_CTL_REMOVE ioctl).
This patch adds only two ioctl operations: add device and remove device. There
is no support for `automatic' device_id generation in this pa
On 02/26/2015 05:59 AM, Lukasz Majewski wrote:
The PWM FAN device can now be used as a thermal cooling device. Necessary
infrastructure has been added in this commit.
Signed-off-by: Lukasz Majewski
Acked-by: Eduardo Valentin
---
Changes for v2:
- Replace pwm_fan_cooling_states with pwm_fan_coo
Hi Andrew,
On 02/26/2015 08:46 AM, Andrew Lunn wrote:
> On Thu, Feb 26, 2015 at 06:55:22AM -0500, Peter Hurley wrote:
>> On 11/27/2014 12:56 PM, Leif Lindholm wrote:
>>> Support specifying console options (like with console=ttyXN,)
>>> by appending them to the stdout-path property after a separati
Device reset currently consists of two steps:
a) holding ->bd_mutex we ensure that there are no device users
(bdev->bd_openers)
b) and internal part (executed under bdev->bd_mutex and partially
under zram->init_lock) that resets the device - frees allocated
memory and returns the device back to it
If no particular device_id was requested (passed -1 to zram_add()) during new
zram
device creation, generate one automatically and return it back. So,
schematically,
device creation can be done as:
dev_id = ioctl ZRAM_CTL_ADD -1
# dev_id == 1 or error code
init device zra
Hello,
this patchset introduces dynamic (on demand) zram device add-remove
functionality via /dev/zram-control interface. Two ioctl commands are
defined as of now (accessible in user-space via new zram.h header file):
-- ZRAM_CTL_ADD
add new device (generates device_id automatically or use
Explanation of several properties, which allow PWM fan working as a cooling
device, have been embraced in this commit.
Signed-off-by: Lukasz Majewski
Acked-by: Eduardo Valentin
---
Changes for v2:
- Rename cooling-pwm-values to cooling-levels
- Remove default-pulse-width property and stick to de
On 24.02.15 23:21, J. German Rivera wrote:
> A DPRC (Data Path Resource Container) is an isolation device
> that contains a set of DPAA networking devices to be
> assigned to an isolation domain (e.g., a virtual machine).
>
> Signed-off-by: J. German Rivera
> Signed-off-by: Stuart Yoder
> ---
This patch makes some preparations for dynamic device ADD/REMOVE functionality
via /dev/zram-control interface.
Remove `zram_devices' array and switch to id-to-pointer translation (idr).
idr doesn't bloat zram struct with additional members, f.e. list_head, yet
still provides ability to match the
If syscall_trace_enter_phase1 returns 0,
code restores %rax from pt_regs->ax, but should restore it from
pt_regs->orig_ax.
The bug crept in because LOAD_ARGS macro was very sublty different
from RESTORE_ARGS, it had only two callsites and only this one
was using that difference.
Signed-off-by: De
Limiting the number of zram devices to 32 (default max_num_devices value)
is confusing, let's drop it. A user with 2TB or 4TB of RAM, for example,
can request as many devices as he can handle.
Signed-off-by: Sergey Senozhatsky
---
drivers/block/zram/zram_drv.c | 6 --
drivers/block/zram/zram
From: Kamil Debski
Add pwm-fan node to the Odroid-U3 board file to enable PWM control of the
cooling fan. In addition, add the "pwm" label to the pwm@139D node
in the exynos4412.dtsi.
Signed-off-by: Kamil Debski
Signed-off-by: Lukasz Majewski
---
Changes since v1:
- added pwm label to the
On Thu, 26 Feb 2015 14:56:30 +0100
Sebastian Andrzej Siewior wrote:
> I am not sure if we want keep doing that. The only reason why we grab
> the lock in the first place was to check if there is a timer pending
> and we run on the isolated CPU. It should not matter for the other CPUs,
> right?
>
401 - 500 of 793 matches
Mail list logo
