Hi Jonathan,
Sorry, I didn't notice that you are the DOCUMENTATION Maintainers now. I just
checked the MAINTAINERS file.
will cc to you for all the documentation patch.
And thanks for mentioning this :-)
a new patch(v2) just was sent, please help me to check that, Thanks! :-)
On 03/26/2015
* Benjamin Herrenschmidt wrote:
> On Wed, 2015-03-25 at 19:36 +0100, Ingo Molnar wrote:
> > * Ingo Molnar wrote:
> >
> > > > +#define __HAVE_ARCH_REMAP
> > > > +static inline void arch_remap(struct mm_struct *mm,
> > > > + unsigned long old_start, unsigned long
>
Hi Holger,
[Cc'ed John Stultz]
On 03/25/2015 10:51 AM, Holger Dengler wrote:
From: Benedikt Spranger
The Eberspaecher Flexcard PMC II offers a Flexray network synchronized
counter with a selectable resolution of 1us, 100ns or 10ns. Add basic
support for the timestamp counter with 1us
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Wednesday, March 25, 2015 11:02 AM
>> To: KY Srinivasan
>> Cc: Haiyang Zhang; de...@linuxdriverproject.org; linux-
>> ker...@vger.kernel.org; Dexuan Cui
>> Subject: [PATCH 0/1]
* Borislav Petkov wrote:
> On Wed, Mar 25, 2015 at 05:05:50PM -0700, Linus Torvalds wrote:
> > so 'as' is clearly just stupid. It already takes the size of the
> > constant into account and generates different instructions. Why not
> > for the common 32-bit case too?
>
> I think the
On Thu, Mar 26, 2015 at 10:02:15AM +0100, Ingo Molnar wrote:
> This is_e820_ram() factoring out becomes really messy in patch #3.
>
> So you left out a bunch of places making comparisons with E820_RAM,
> notably e820_reserve_resources_late() and memblock_x86_fill() - and of
> course those have
Add irq disable and enable in bfin_serial_rx_dma_timeout in case of
system hang.
This reverts part of commit 9642dbe73c8a ("serial: bfin-uart: avoid
dead lock in rx irq handler in smp kernel").
Signed-off-by: Hao Liang
---
drivers/tty/serial/bfin_uart.c |2 ++
1 file changed, 2
* Linus Torvalds wrote:
> On Wed, Mar 25, 2015 at 10:18 AM, Denys Vlasenko wrote:
> > The $AUDIT_ARCH_X86_64 parameter to syscall_trace_enter_phase1/2
> > is a 32-bit constant, loading it with 32-bit MOV produces 5-byte insn
> > instead of 10-byte one.
>
> Side note: has anybody talked to the
Hi all,
Changes since 20150325:
New trees: arm64-acpi, uml
The mips tree gained a conflict against the imx-mxs tree.
The powerpc-mpe tree gained a build failure for which I added a merge
fix patch.
The vfs tree still had its build failure for which I applied a patch.
The xen-tip tree gained
Am 28.02.2015 um 11:23 schrieb Brian Norris:
> The comparison from the previous line seems to have been erroneously
> (partially) copied-and-pasted onto the next. The second line should be
> checking req.bytes, not req.lnum.
>
> Coverity CID #139400
>
> Signed-off-by: Brian Norris
> ---
>
On Thu, Mar 19, 2015 at 9:44 AM, Alexey Brodkin
wrote:
> So IMHO we need to update "gpio-dwapb" driver in the following manner:
>
> [1] In dwapb_configure_irqs() in accordance to "snps,nr-gpios" in the
> first bank set a value in GPIO_INTEN. This way we turn N pins in that
> port/bank in
On Wed, Mar 25, 2015 at 05:05:50PM -0700, Linus Torvalds wrote:
> so 'as' is clearly just stupid. It already takes the size of the
> constant into account and generates different instructions. Why not
> for the common 32-bit case too?
I think the destination register mandates which insn to use:
From: Richard Weinberger
Fixes:
drivers/clocksource/sh_tmu.c: In function ‘sh_tmu_map_memory’:
drivers/clocksource/sh_tmu.c:506:2: error: implicit declaration of function
‘ioremap_nocache’ [-Werror=implicit-function-declaration]
tmu->mapbase = ioremap_nocache(res->start, resource_size(res));
From: Richard Weinberger
Fixes:
drivers/clocksource/sh_mtu2.c: In function ‘sh_mtu2_map_memory’:
drivers/clocksource/sh_mtu2.c:391:2: error: implicit declaration of function
‘ioremap_nocache’ [-Werror=implicit-function-declaration]
mtu->mapbase = ioremap_nocache(res->start,
From: Maxime Ripard
The sched_clock we use on some system is this timer, and since we
started using cpufreq, the cpu clock (that is one of the timer's clock
indirect parent) now changes, along with the actual sched_clock rate.
We can safely remove the sched_clock on those systems, since we have
From: Richard Weinberger
Fixes:
drivers/clocksource/sh_cmt.c: In function ‘sh_cmt_map_memory’:
drivers/clocksource/sh_cmt.c:920:2: error: implicit declaration of function
‘ioremap_nocache’ [-Werror=implicit-function-declaration]
cmt->mapbase = ioremap_nocache(mem->start, resource_size(mem));
On Wed, Mar 25, 2015 at 05:16:28PM -0700, Andy Lutomirski wrote:
> Quick ping: does anyone want to review this?
Yes, sorry, I'm still way behind on my patch queue review, want to get
to this this week.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Tue, Mar 10, 2015 at 10:44:00AM -0400, Jérémie Galarneau wrote:
> On Tue, Mar 10, 2015 at 10:11 AM, Jiri Olsa wrote:
> > On Tue, Mar 10, 2015 at 11:01:34AM -0300, Arnaldo Carvalho de Melo wrote:
> >> Em Tue, Mar 10, 2015 at 01:00:35PM +0100, Jiri Olsa escreveu:
> >> > On Mon, Mar 09, 2015 at
25.03.2015 11:59, Tomeu Vizoso пишет:
As there isn't a way for the firmware on the Nyan chromebooks to hand
over the display to the kernel, and the kernel isn't redoing the whole
configuration at present.
With this patch, the SOR is brought to a known state and we get correct
display on every
On 25/03/15 22:03, Greg Kroah-Hartman wrote:
> On Wed, Mar 25, 2015 at 03:39:50PM +, James Hogan wrote:
>> Add MIPS Common Device Memory Map (CDMM) support in the form of a bus in
>> the standard Linux device model. Each device attached via CDMM is
>> discoverable via an 8-bit type identifier
* Jiri Kosina wrote:
> On Wed, 25 Mar 2015, Josh Poimboeuf wrote:
>
> > In discussions around my live kernel patching consistency model RFC [1],
> > Peter and Ingo correctly pointed out that stack traces aren't reliable.
> > And as Ingo said, there's no "strong force" which ensures we can
Hi Lad and Hans,
2015-03-08 22:40 GMT+08:00 Lad Prabhakar :
> From: "Lad, Prabhakar"
>
> This patch series, enhances blackfin capture driver with
> vb2 helpers.
>
> Changes for v4:
> 1: Improved commit message for path 4/17 and 5/17.
> 2: Added Ack's from Scott to patches 1-15
> 3: Two new
在 2015/3/25 15:50, Xinwei Kong 写道:
From: kongxinwei
This patch adds the support for hisilicon thermal sensor, within
hisilicon SoC. there will register sensors for thermal framework
and use device tree to bind cooling device.
Signed-off-by: Leo Yan
Signed-off-by: kongxinwei
---
On 03/25/2015 06:49 PM, Stephane Viau wrote:
Add the GDSC instances that exist as part of apq8084 MMCC block.
Signed-off-by: Stephane Viau
---
drivers/clk/qcom/Kconfig | 1 +
drivers/clk/qcom/mmcc-apq8084.c | 56 ++-
Am 06.03.2015 um 03:04 schrieb Brian Norris:
> On Thu, Mar 05, 2015 at 11:33:14AM +0100, Richard Weinberger wrote:
>> Brian,
>>
>> Am 28.02.2015 um 11:23 schrieb Brian Norris:
>>> Except for the last one, these were inspired by Coverity Scan results.
>>>
>>> These fixes have barely been tested,
On 25/03/15 18:43, Ioan Nicu wrote:
> Probe deferral is not an error case. It happens only when
> the necessary dependencies are not there yet.
>
> The driver core is already printing a message when a driver
> requests probe deferral, so this can be traced in the logs
> without these error
This is a trivial port from kGraft. Module relocations are not
supported.
Signed-off-by: Jiri Slaby
---
[v2] return ENOSYS
[v3] proper return value from klp_check_compiler_support
arch/s390/Kconfig | 3 +++
arch/s390/include/asm/livepatch.h | 43
On Thu, Mar 26, 2015 at 09:42:47AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > And is it possible to use offset within BAR and/or memory BARs?
> > If yes I'd strongly prefer this.
>
> What is the point? Do you want place virtio regions and vga framebuffer
> in the same pci bar? Why? virtio is
From: Fu Wei
This is a Chinese translated version of
Documentation/arm64/legacy_instructions.txt
It is based on the modifications of Documentation/arm64/legacy_instructions.txt
in submission:
"587064b6", "bd35a4ad", "2d888f48", "c852f320".
Signed-off-by: Fu Wei
---
* Christoph Hellwig wrote:
> This will allow to deal with persistent memory which needs to be
> treated like ram in many, but not all cases.
>
> Based on an earlier patch from Dave Jiang .
>
> Signed-off-by: Christoph Hellwig
> Tested-by: Ross Zwisler
> ---
> arch/x86/kernel/e820.c | 15
On Sun, Feb 1, 2015 at 12:10 PM, wrote:
> From: David Oberhollenzer
>
> Emulate random power cuts by switching device to ro after a number of
> writes to allow simple power cut testing with nand-sim.
>
> Maximum and minimum number of successful writes before power cut and
> what kind of writes
On Wed, Mar 25, 2015 at 03:53:09PM +0100, Gerd Hoffmann wrote:
> > > Signed-off-by: Dave Airlie
> > > Signed-off-by: Gerd Hoffmann
> >
> > Standard request from my side for new drm drivers (especially if they're
> > this simple): Can you please update the drivers to latest drm internal
> >
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/arm64/Kconfig between commit dbdacfa963f7 ("ARM64 / ACPI: Select
ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on ARM64") from the
arm64-acpi tree and commit cbc0632906e6 ("mm: split ET_DYN ASLR from
mmap ASLR")
Hi Kishon
On 03/26/2015 12:11 AM, Kishon Vijay Abraham I wrote:
+Maxime, Srinivas, patrice
On Monday 09 March 2015 06:55 PM, Axel Lin wrote:
2015-03-09 19:44 GMT+08:00 Kishon Vijay Abraham I :
Hi,
On Thursday 05 March 2015 07:27 AM, Axel Lin wrote:
The defines in phy-miphy365x.h are all
On Tue, Mar 24, 2015 at 01:08:46PM +0100, Gerd Hoffmann wrote:
> virtio-input is basically evdev-events-over-virtio, so this driver isn't
> much more than reading configuration from config space and forwarding
> incoming events to the linux input layer.
>
> Signed-off-by: Gerd Hoffmann
Looks
My platform is suffering with the external fragmentation problem.
If I run a heavy load test for a few days in 1GB memory system, I cannot
allocate even order=3 pages because-of the external fragmentation.
I found that my driver is main reason.
It repeats to allocate 16MB pages with
Some board designers, when running out of clock output pads, decide to
(mis)use PWM output pads to provide a clock to external components.
This driver supports this practice by providing an adapter between the
PWM and clock bindings in the device tree. As the PWM bindings specify
the period in the
Hi,
> And is it possible to use offset within BAR and/or memory BARs?
> If yes I'd strongly prefer this.
What is the point? Do you want place virtio regions and vga framebuffer
in the same pci bar? Why? virtio is mmio and traps into qemu on
access, whereas the vga framebuffer is
On 03/26/2015 at 07:32 AM, Xi Ruoyao wrote:
On 03/26/2015 at 03:40 AM, Josh Boyer wrote:
drm-Fixup-racy-refcounting-in-plane_force_disable.patch
drm-i915-Don-t-try-to-reference-the-fb-in-get_initia.patch
and this patch:
I hide the patch since it has been managled by Thunderbird.
(BTW, who
Huh. Weird. Please, could you just move it forward instead so we don't
have to have the prototype declaration?
regars,
dan carpenter
--
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
On Mon, Feb 09, 2015 at 03:39:23PM -0800, David Daney wrote:
> From: David Daney
>
Better if it is added in commit message:
how to determine kernel version for a given commit id.
> Signed-off-by: David Daney
> ---
> Documentation/stable_kernel_rules.txt | 10 ++
> 1 file changed, 10
Hi Ivan,
On 03/26/2015 01:01 PM, Ivan T. Ivanov wrote:
Hi Sricharan,
On Thu, 2015-03-26 at 11:14 +0530, Sricharan R wrote:
+ if (msg->flags & I2C_M_RD)
+ qup->rx_tag_len = (qup->blocks << 1);
here again.
hmm, why not shift ?
Because it makes reading code harder
On Wed, 25 Mar 2015, Johan Hovold wrote:
> Since commit 6e3f62f0793e ("mfd: core: Fix platform-device id
> generation") we honour PLATFORM_DEVID_AUTO and PLATFORM_DEVID_NONE when
> registering mfd-devices.
>
> Unfortunately, some mfd-drivers rely on the old behaviour of generating
>
From: Ross Zwisler
PMEM is a new driver that presents a reserved range of memory as a
block device. This is useful for developing with NV-DIMMs, and
can be used with volatile memory as a development platform.
Signed-off-by: Ross Zwisler
[hch: convert to use a platform_device for discovery,
Various recent BIOSes support NVDIMMs or ADR using a non-standard
e820 memory type, and Intel supplied reference Linux code using this
type to various vendors.
Wire this e820 table type up to export platform devices for the pmem
driver so that we can use it in Linux, and also provide a memmap=
This will allow to deal with persistent memory which needs to be
treated like ram in many, but not all cases.
Based on an earlier patch from Dave Jiang .
Signed-off-by: Christoph Hellwig
Tested-by: Ross Zwisler
---
arch/x86/kernel/e820.c | 15 ++-
1 file changed, 10 insertions(+),
Here is another version of the same trivial pmem driver, because two
obviously aren't enough. The first patch is the same pmem driver
that Ross posted a short time ago, just modified to use platform_devices
to find the persistant memory region instead of hardconding it in the
Kconfig. This
On Wed, 25 Mar 2015, Johan Hovold wrote:
> Fix broken probe of da9052 regulators, which since commit b3f6c73db732
> ("mfd: da9052-core: Fix platform-device id collision") use a
> non-deterministic platform-device id to retrieve static regulator
> information. Fortunately, adequate error handling
Hi Christian,
After merging the access_once tree, today's linux-next build (arm
multi_v7_defconfig) produced lots of this warning:
In file included from include/linux/linkage.h:4:0,
from include/linux/preempt.h:9,
from include/linux/spinlock.h:50,
On 25/03/15 21:43, Pavel Machek wrote:
> Hi!
>
>> Here are some patches to address an issue with SDHCI
>> in Intel Baytrail. Intel Baytrail has been observed
>> sometimes to hang if host controllers are using DMA
>> while deep C-states are used. Workaround that by
>
> I wonder if there is more
Unlike normal kexec case, we don't have a chance to reset EL2 context in
a generic way because bad exceptions may directly invoke crash_kexec().
(See die().)
Kvm is not useful on crash dump kernel anyway, and so we let it
un-initialized across rebooting.
Signed-off-by: AKASHI Takahiro
---
Signed-off-by: AKASHI Takahiro
---
arch/arm64/configs/defconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 3f1c593..f5af17f 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -45,6 +45,7 @@
Please read the following commits for arm64-specific constraints:
arm64: kdump: reserve memory for crash dump kernel
arm64: kdump: do not go into EL2 before starting a crash dump kernel
Signed-off-by: AKASHI Takahiro
---
Documentation/kdump/kdump.txt | 31
On Wed, 25 Mar 2015, Andy Shevchenko wrote:
> dmi_get_system_info() may return NULL either when CONFIG_DMI is not set or
> when
> board has an old firmware. The patch prevents a crash and changes the default
> frequency to be in align with older board.
>
> Signed-off-by: Andy Shevchenko
> ---
kdump calls machine_crash_shutdown() to shut down non-boot cpus and
save per-cpu general-purpose registers before restarting the crash dump
kernel. See kernel_kexec().
ipi_cpu_stop() is used and a bit modified to support this behavior.
Signed-off-by: AKASHI Takahiro
---
On system kernel, the memory region used by crash dump kernel must be
specified by "crashkernel=X@Y" boot parameter. reserve_crashkernel()
will allocate the region in "System RAM" and reserve it for later use.
On crash dump kernel, memory region information in system kernel is
described in a
This patch set enables kdump (crash dump kernel) support on arm64 on top of
Geoff's kexec patchset.
In this version, there are some arm64-specific usage/constraints:
1) "mem=" boot parameter must be specified on crash dump kernel
2) Kvm will not be enabled on crash dump kernel even if configured
Cpu must be put back into its initial state, at least, in the
following cases in order to shutdown the system and/or re-initialize cpus
later on:
1) kexec/kdump
2) cpu hotplug (offline)
3) removing kvm as a module
To address those issues in later patches, this patch adds a tear-down
function,
Signed-off-by: AKASHI Takahiro
---
arch/arm/include/asm/kvm_asm.h |1 +
arch/arm/include/asm/kvm_host.h | 12
arch/arm/include/asm/kvm_mmu.h |5 +
arch/arm/kvm/init.S |6 ++
4 files changed, 24 insertions(+)
diff --git
This patch doesn't enable kvm to be built as a module, but is
a prerequisite when kvm is transformed to be module-capable.
Signed-off-by: AKASHI Takahiro
---
arch/arm/kvm/arm.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index
On Fri, 20 Feb 2015, Chen-Yu Tsai wrote:
> From: Carlo Caione
>
> Signed-off-by: Carlo Caione
> Signed-off-by: Chen-Yu Tsai
> Acked-by: Lee Jones
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
> diff --git
This patch doesn't enable cpu hotplug under kvm, but is a prerequiste
when the feature is implemented.
Once kvm_arch_hardware_enable/disable() is properly implemented,
arm64-specific cpu notifier hook, hyp_init_cpu_notify(), will be
able to be removed and replaced by generic kvm_cpu_hotplug().
The current kvm implementation keeps EL2 vector table installed even
when the system is shut down. This prevents kexec from putting the system
with kvm back into EL2 when starting a new kernel.
This patch resolves this issue by calling a cpu tear-down function via
reboot notifier,
On Fri, 20 Feb 2015, Chen-Yu Tsai wrote:
> From: Carlo Caione
>
> Bindings documentation for the AXP20x driver. In this file also
> sub-nodes are documented.
>
> Signed-off-by: Carlo Caione
> [w...@csie.org: clarify interrupt source for the axp PMIC]
> [w...@csie.org: explain dcdc-workmode in
This patch set addresses KVM issue described in Geoff's kexec patch set[1].
(The subject was changed from "arm64: kexec: fix kvm issue in kexec.")
See "Changes" below.
The basic approach here is to define a kvm tear-down function and add
a reboot hook to gracefully shutdown the 1st kernel. This
On Thu, Mar 26, 2015 at 08:12:39AM +0100, Gerd Hoffmann wrote:
> On Mi, 2015-03-25 at 18:09 +0100, Michael S. Tsirkin wrote:
> > On Wed, Mar 25, 2015 at 04:37:16PM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > BTW can we teach virtio-gpu to look for framebuffer using
> > > > virtio pci
Hi Amos Kong,
Great thanks for your review!
my feedback is inline below
On 03/26/2015 02:26 PM, Amos Kong wrote:
> On Wed, Mar 25, 2015 at 12:09:03PM +0800, w...@redhat.com wrote:
>> From: Fu Wei
>>
>> This is a Chinese translated version of
>> Documentation/arm64/legacy_instructions.txt
>>
>>
Hello Stefan,
On Thu, Mar 26, 2015 at 08:24:05AM +0100, Stefan Agner wrote:
> While adding the MSCM interrupt router, all interrupts have been moved
> to vfxxx.dtsi again. However, some properties got lost. Readd the
> missing interrupt properties.
>
> Offending commit:
> 97e6466ab9 ("ARM: dts:
On (03/26/15 16:39), Minchan Kim wrote:
> Hello Sergey,
>
> Sorry for slow response.
> I am overwhelmed with too much to do. :(
>
Hello,
sure, no problem.
> > > diff -puN
> > > mm/zsmalloc.c~zsmalloc-remove-extra-cond_resched-in-__zs_compact
> > > mm/zsmalloc.c
> > > ---
On Wed, Mar 25, 2015 at 02:21:53PM -0600, Ross Zwisler wrote:
> What needed to be fixed with the partition support? I used to have real
> numbers for first_minor and passed into alloc_disk(), but simplified it based
> on code found in this commit in the nvme driver:
>
> 469071a37afc NVMe:
On 26 March 2015 at 08:38, Ulf Hansson wrote:
> On 26 March 2015 at 02:18, NeilBrown wrote:
>> On Thu, 26 Mar 2015 08:43:37 +1100 NeilBrown wrote:
>>
>>> enable and disable are only used to get and put
>>> runtime pm references. .set_ios already does this
>>> itself, and other drivers just do
On Wed, Mar 25, 2015 at 02:26:52PM -0600, Ross Zwisler wrote:
> Cool - yep, feel free to update this if you want in the next version of
> your series, Christoph.
Ok, I've fixed this up.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Mar 25, 2015 at 02:25:33PM -0600, Ross Zwisler wrote:
> > + case E820_PROTECTED_KERN:
> > + printk(KERN_CONT "protected (type %u)\n", type);
>
> I don't think we want a newline in this string.
Fixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Wed, Mar 25, 2015 at 07:47:26PM +, Elliott, Robert (Server Storage)
wrote:
> If this goes into the kernel, I think someone should request that the
> ACPI specification mark the value 12 as permanently tainted. Otherwise
> they could assign it to some new meaning that conflicts with all
>
> +static int
> +jit_open(struct jit_buf_desc *jd, const char *name)
> +{
> + struct jitheader header;
> + struct jr_prefix *prefix;
> + ssize_t bs, bsz = 0;
> + void *n, *buf = NULL;
> + int ret, retval = -1;
> +
> + jd->in = fopen(name, "r");
> + if (!jd->in)
> +
On Wed, Mar 25, 2015 at 07:15:42PM -0700, Dan Williams wrote:
> Random thought, type-12 memory happens to correspond to "legacy"
> NVDIMM systems with smaller capacities. Perhaps "new NVDIMM" should
> not be is_e820_ram() by default?
Let's look into that once we can see the spec..
> > Based on
When a CPU is kicked to do nohz idle balancing, it wakes up to do load balancing
on itself, followed by load balancing on behalf of idle CPUs. But it may end
up with load after the load balancing attempt on itself. This aborts nohz
idle balancing. As a result several idle CPUs are left without
On Thu, Mar 26, 2015 at 4:29 AM, Dave Airlie wrote:
> I've pushed a drm-fixes-staging branch that backport's Daniel's
> drm-next fix from 9 hours ago,
>
> However it isn't tested yet, so if you want to give it a whirl grab it.
>
> Hopefully when Daniel comes on line he can provide assurance that
On 03/26/2015 06:00 AM, Elliott, Robert (Server Storage) wrote:
>
>
>> -Original Message-
>> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
>> ow...@vger.kernel.org] On Behalf Of Andy Lutomirski
>> Sent: Wednesday, March 18, 2015 1:07 PM
>> To: Boaz Harrosh
>> Cc: Matthew
Hello Sergey,
Sorry for slow response.
I am overwhelmed with too much to do. :(
On Thu, Mar 26, 2015 at 09:27:17AM +0900, Sergey Senozhatsky wrote:
> On (03/25/15 13:25), a...@linux-foundation.org wrote:
> > The patch titled
> > Subject: zsmalloc: remove extra cond_resched() in __zs_compact
On 26 March 2015 at 02:18, NeilBrown wrote:
> On Thu, 26 Mar 2015 08:43:37 +1100 NeilBrown wrote:
>
>> enable and disable are only used to get and put
>> runtime pm references. .set_ios already does this
>> itself, and other drivers just do it in set_ios
>> and .request without using
Hi Sricharan,
On Thu, 2015-03-26 at 11:14 +0530, Sricharan R wrote:
>
> > > + if (msg->flags & I2C_M_RD)
> > > + qup->rx_tag_len = (qup->blocks << 1);
> >
> > here again.
> >
> hmm, why not shift ?
Because it makes reading code harder and because compiler
is smart enough
Quick ping: does anyone want to review this?
--Andy
On Tue, Feb 10, 2015 at 3:44 PM, Andy Lutomirski wrote:
> This isn't adequately tested, and I don't have a demonstration (yet).
> It's here for review for whether it's a good idea in the first place
> and for weather the fully_dynamic
>>> Is there an git tree with this so I can just try it out?
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
>> pci/enumeration-yw6 has similar code (it exports the single
>
> I presume now it is bjorn/pci/enumeration-yw8 ? Going to test this out
> this week.
Hi Konrad, I
On Wed, Mar 25, 2015 at 07:37:40PM -0700, David Rientjes wrote:
> That would be true only for
>
> ptr = mempool_alloc(gfp, pool);
> mempool_free(ptr, pool);
>
> and nothing in between, and that's pretty pointless. Typically, callers
> allocate memory, modify it, and then free it.
While adding the MSCM interrupt router, all interrupts have been moved
to vfxxx.dtsi again. However, some properties got lost. Readd the
missing interrupt properties.
Offending commit:
97e6466ab9 ("ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)"
---
arch/arm/boot/dts/vfxxx.dtsi
2015-03-25 1:39 GMT+01:00 Beomho Seo :
>
> Then, Can I request merge this patch ?
Yes, but it is not up to me :).
--
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
On Thu, 2015-03-26 at 11:32 +1100, Stephen Rothwell wrote:
> Hi Artem,
>
> I noticed merge commit 3527a86b7ae1 ("Merge tag 'v4.0-rc5' into
> linux-next"). Just a note that if you had merged the commit that the
> tag points to, you would have just had a fast forward instead of a
> "real" merge.
On Mi, 2015-03-25 at 18:09 +0100, Michael S. Tsirkin wrote:
> On Wed, Mar 25, 2015 at 04:37:16PM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > BTW can we teach virtio-gpu to look for framebuffer using
> > > virtio pci caps?
> >
> > The virtio-gpu driver doesn't matter much here, it doesn't use
Hi,
Am 26.03.2015 um 06:56 schrieb Pavel Machek :
> Hi!
>
> Main reason is, that I would need to go
> through the UART to “communicate" with the w2sg0004.
You can always "communicate” through the UART. Even without DT. As long as
the connected chip is powered up by any
> > diff --git a/drivers/phy/phy-twl4030-usb.c
b/drivers/phy/phy-twl4030-usb.c
> > index 8e87f54671f3..1a244f34b748 100644
> > --- a/drivers/phy/phy-twl4030-usb.c
> > +++ b/drivers/phy/phy-twl4030-usb.c
> > @@ -144,6 +144,16 @@
> > #define PMBR1 0x0D
> > #define
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in
drivers/xen/Kconfig between commit 94ccae47e02d ("XEN / ACPI: Make XEN
ACPI depend on X86") from the arm64-acpi tree and commit 628c28eefd6f
("xen: unify foreign GFN map/unmap for auto-xlated physmap guests")
from the xen-tip
On Thu, 2015-03-26 at 06:23 +0100, Mike Galbraith wrote:
> I plan on taking a poke at getting "don't raise timer unconditionally"
> working again when I get myself unburied, and see if I can come up with
> a somewhat less icky way to work around take rtmutex in irq naughtiness.
Hm.. like maybe
On Wed, Mar 25, 2015 at 12:09:03PM +0800, w...@redhat.com wrote:
> From: Fu Wei
>
> This is a Chinese translated version of
> Documentation/arm64/legacy_instructions.txt
>
> It is based on the modifications of
> Documentation/arm64/legacy_instructions.txt in submission:
> "587064b6",
On 2015/3/26 13:19, Daniel Axtens wrote:
> Hi Yijing,
>
> Pulled.
>
> I'm now getting build errors:
>
> /scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c: In function
> 'pcibios_scan_phb':
> /scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c:1638:14: error:
> 'bus'
The perf kmem command records and analyze kernel memory allocation
only for SLAB objects. This patch implement a simple page allocator
analyzer using kmem:mm_page_alloc and kmem:mm_page_free events.
It adds two new options of --slab and --page. The --slab option is
for analyzing SLAB allocator
It perf kmem support caller statistics for page. Unlike slab case,
the tracepoints in page allocator don't provide callsite info. So
it records with callchain and extracts callsite info.
Note that the callchain contains several memory allocation functions
which has no meaning for users. So
The struct page is opaque for userspace tools, so it'd be better to save
pfn in order to identify page frames.
The textual output of $debugfs/tracing/trace file remains unchanged and
only raw (binary) data format is changed - but thanks to libtraceevent,
userspace tools which deal with the raw
Hi Ivan,
On 03/25/2015 06:40 PM, Ivan T. Ivanov wrote:
Hi Sricharan,
On Fri, 2015-03-13 at 23:19 +0530, Sricharan R wrote:
#define QUP_I2C_MASTER_GEN 0x408
+#define QUP_I2C_MASTER_CONFIG 0x408
Unused.
Ok, will remove it
#define QUP_READ_LIMIT 256
+#define
Currently perf kmem shows total (page) allocation stat by default, but
sometimes one might want to see live (total alloc-only) requests/pages
only. The new --live option does this by subtracting freed allocation
from the stat.
Signed-off-by: Namhyung Kim
---
701 - 800 of 1610 matches
Mail list logo
