On Wed, 2013-01-23 at 04:16 +, Ben Hutchings wrote:
> On Mon, 2013-01-21 at 21:12 +, Matt Fleming wrote:
> [...]
> > From 92e73f936e40a8c6562e47425d434a4e62d2b8e2 Mon Sep 17 00:00:00 2001
> > From: Matt Fleming
> > Date: Wed, 14 Nov 2012 09:42:35 +
> > Subject: [PATCH] efi: Make
During the development of this driver an in-house register
documentation was used. The last weeks some integration tests
were done and this problem was found. It turned out that
the released register documentation is wrong.
The fix is very simple: shift all masks by one.
Signed-off-by: Christian
During the development of this driver an in-house register
documentation was used. The last weeks some integration tests
were done and this problem was found. It turned out that
the released register documentation is wrong.
The fix is very simple: shift all masks by one.
Signed-off-by: Christian
(Cc net...@vger.kernel.org)
On Mon, Jan 21, 2013 at 07:57:28AM -0500, Tom St Denis wrote:
> Hey all,
>
> Here's an updated patch which addresses a couple of build issues and coding
> style complaints.
>
> I still can't get it to run via testmgr I get
>
> [ 162.407807] alg: No test for
From: Xufeng Zhang
While sctp handling a duplicate COOKIE-ECHO and the action is
'Association restart', sctp_sf_do_dupcook_a() will processing
the unexpected COOKIE-ECHO for peer restart, but it does not set
the association state to SCTP_STATE_ESTABLISHED, so the association
could stuck in
On Tuesday 22 January 2013 03:52 PM, James Bottomley wrote:
> On Tue, 2013-01-22 at 11:15 +0100, Marek Szyprowski wrote:
>> Hello,
>>
>> On 1/15/2013 5:56 PM, James Bottomley wrote:
>>> On Tue, 2013-01-15 at 15:07 +0100, Marek Szyprowski wrote:
Hello,
On 1/15/2013 10:13 AM, Geert
Fix compilation error, by adding the correct header file
for Tegra clocks.
Signed-off-by: Venu Byravarasu
---
drivers/tty/serial/serial-tegra.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/tty/serial/serial-tegra.c
b/drivers/tty/serial/serial-tegra.c
index
On Wed, Jan 23, 2013 at 09:23:57AM +0800, pclinux wrote:
> Sure. I will do it.
> Does it mean that the other commits only can be submitted to 3.9-rc?
>
Submit them now. They stay in Samuel's tree and are tested in
linux-next until 3.8 is released. Then Samuel submits them during
the 3.9 merge
update kernel headers to add pv event macros.
Signed-off-by: Wen Congyang
Signed-off-by: Hu Tao
---
linux-headers/asm-x86/kvm_para.h | 1 +
linux-headers/linux/kvm_para.h | 6 ++
2 files changed, 7 insertions(+)
diff --git a/linux-headers/asm-x86/kvm_para.h
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
The guest will be in this state when it is panicked.
If guest is panicked during live migration, the runstate
RUN_STATE_GUEST_PANICKED will be transferred to dest machine.
Signed-off-by: Wen Congyang
Signed-off-by: Hu Tao
---
migration.c | 1 +
qapi-schema.json | 6 +-
qmp.c
Signed-off-by: Wen Congyang
Signed-off-by: Hu Tao
---
hw/pc_piix.c| 9 -
qemu-options.hx | 3 ++-
vl.c| 4
3 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index fed6ccf..507c98b 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang
---
include/monitor/monitor.h | 1 +
monitor.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/include/monitor/monitor.h b/include/monitor/monitor.h
index 87fb49c..4006905 100644
---
This series implements a new interface, kvm pv event, to notify host when
some events happen in guest. Right now there is one supported event: guest
panic.
Also, the cpu runstate is preserved during save/load vm and migration. Thus,
if vm is panicked during migration, we can still know it by
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_EVENT_PORT when it is panciked. This patch introduces a new
qom device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value. The possible actions are:
1. emit
Signed-off-by: Hu Tao
---
docs/pv-event.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644 docs/pv-event.txt
diff --git a/docs/pv-event.txt b/docs/pv-event.txt
new file mode 100644
index 000..ac9e7fa
--- /dev/null
+++ b/docs/pv-event.txt
@@ -0,0 +1,17 @@
+KVM
From: Wen Congyang
The guest should run after resetting it, but it does not run if its
old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
We don't set runstate to RUN_STATE_PAUSED when resetting the guest,
so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or
RUN_STATE_PAUSED
This patch enables preservation of cpu runstate during save/load vm.
So when a vm is restored from snapshot, the cpu runstate is restored,
too.
See following example:
# save two vms: one is running, the other is paused
(qemu) info status
VM status: running
(qemu) savevm running
(qemu) stop
On 01/23/2013 02:28 PM, Mike Galbraith wrote:
> On Wed, 2013-01-23 at 13:09 +0800, Michael Wang wrote:
>> On 01/23/2013 12:31 PM, Mike Galbraith wrote:
>
>>> Another thing that wants fixing: root can set flags for _existing_
>>> domains any way he likes,
>>
>> Can he? on running time changing
On Tue, Jan 22, 2013 at 05:19:10PM -0600, Suthikulpanit, Suravee wrote:
> From: Suravee Suthikulpanit
> @@ -1171,6 +1195,8 @@ static int iommu_init_pci(struct amd_iommu *iommu)
> for (i = 0; i < 0x83; i++)
> iommu->stored_l2[i] = iommu_read_l2(iommu, i);
>
On 01/23/2013 02:33 PM, Stephen Rothwell wrote:
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm defconfig)
produced this warning:
mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not
used [-Wunused-function]
Introduced by commit "page_alloc:
Hi all,
Changes since 20130122:
The powerpc tree still had a build failure.
The wireless-next tree gained conflicts against the net and linus' trees.
The sound-asoc tree gained a build failure so I used the version from
next-20130122.
The trivial tree gained conflicts against the mips and pm
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm defconfig)
produced this warning:
mm/page_alloc.c:4477:23: warning: 'sanitize_zone_movable_limit' defined but not
used [-Wunused-function]
Introduced by commit "page_alloc: introduce zone_movable_limit[] to keep
movable
On Tue, Jan 22, 2013 at 02:17:38, Peter Korsgaard wrote:
> > "Philip" == Philip Avinash writes:
>
> Philip> From: "Philip, Avinash"
> Philip> Add ELM data node to AM33XX device tree file.
>
> Philip> Signed-off-by: Philip Avinash
> Philip> ---
> Philip> arch/arm/boot/dts/am33xx.dtsi
On Tue, Jan 22, 2013 at 02:31:53, Peter Korsgaard wrote:
> > "Philip" == Philip Avinash writes:
>
> Philip> From: "Philip, Avinash"
> Philip> Add GPMC data node to AM33XX device tree file.
>
> Philip> Signed-off-by: Philip Avinash
> Philip> ---
> Philip>
On Wed, 2013-01-23 at 13:09 +0800, Michael Wang wrote:
> On 01/23/2013 12:31 PM, Mike Galbraith wrote:
> > Another thing that wants fixing: root can set flags for _existing_
> > domains any way he likes,
>
> Can he? on running time changing the domain flags? I do remember I used to
> send out
On Tue, Jan 22, 2013 at 09:27:17AM +, Lee Jones wrote:
> On Mon, 21 Jan 2013, Anton Vorontsov wrote:
>
> > On Mon, Jan 21, 2013 at 12:03:59PM +, Lee Jones wrote:
> > > When compile testing the new AB8500 Battery Management changes
> > > due for inclusion into upstream, there were a few
[PATCH 6/6][v4]: perf: Document the ABI of perf sysfs entries
This patchset addes two new sets of files to sysfs for POWER architecture.
- perf event config format in /sys/devices/cpu/format/event
- generic and POWER-specific perf events in /sys/devices/cpu/events/
The format
[PATCH 5/6][v4]: perf: Create a sysfs entry for Power event format
Create a sysfs entry, '/sys/bus/event_source/devices/cpu/format/event'
which describes the format of a POWER cpu.
The format of the event is the same for all POWER cpus at least in
(Power6, Power7), so bulk of this change is
[PATCH 4/6][v4]: perf/POWER7: Make some POWER7 events available in sysfs
Make some POWER7-specific perf events available in sysfs.
$ /bin/ls -1 /sys/bus/event_source/devices/cpu/events/
branch-instructions
branch-misses
cache-misses
cache-references
[PATCH 3/6][v4]: perf/POWER7: Make generic event translations available in sysfs
Make the generic perf events in POWER7 available via sysfs.
$ ls /sys/bus/event_source/devices/cpu/events
branch-instructions
branch-misses
cache-misses
cache-references
[PATCH 2/6][v4]: perf: Make EVENT_ATTR global
Rename EVENT_ATTR() to PMU_EVENT_ATTR() and make it global so it is
available to all architectures.
Further to allow architectures flexibility, have PMU_EVENT_ATTR() pass
in the variable name as a parameter.
Changelog[v2]
- [Jiri Osla] No
[PATCH 1/6][v4]: perf/Power7: Use macros to identify perf events
Define and use macros to identify perf events codes This would make it
easier and more readable when these event codes need to be used in more
than one place.
Signed-off-by: Sukadev Bhattiprolu
Acked-by: Jiri Olsa
---
[PATCH 0/6][v4]: perf: Make POWER7 events available in sysfs
Make the generic and some POWER7-specific perf events available in sysfs.
These changes mainly extend similar functionality implemented in x86 to
work on POWER architecture as well.
Thanks to input from Stephane Eranian, Robert
On 01/22/2013 10:27 PM, Arend van Spriel wrote:
On 01/22/2013 02:46 PM, Thiago Farina wrote:
Hi folks,
Is there a way to list the drivers installed/used in my desktop and
map them (the path) to their source code in the linux kernel tree?
This might work for you (if using bash):
for m in
Hi Thomas,
I have a question regarding the bus setup when I use the patch
https://patchwork.kernel.org/patch/1870231. It configures buses as
defined in "pinctrl-0 = ...".
But in the function dw_mci_exynos_setup_bus(), it tries again to
configure gpios and probing is failed because there is no
From: fangxiaozhi
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
2. Add to support new switch command for new Huawei USB dongles.
Signed-off-by: fangxiaozhi
From: fangxiaozhi
1. Define a new macro for USB storage match rules:
matching with Vendor ID and interface descriptors.
Signed-off-by: fangxiaozhi
diff -uprN linux-3.8-rc4_orig/drivers/usb/storage/usb.c
s':
> (.text+0x162492): undefined reference to `i2c_smbus_write_byte_data'
> drivers/built-in.o: In function `lp55xx_write':
> (.text+0x1624c5): undefined reference to `i2c_smbus_write_byte_data'
>
> Caused by commit 597eb710be87 ("leds-lp55xx: add new common driver for
> lp5
Stephen Warren wrote @ Tue, 22 Jan 2013 17:57:39 +0100:
> Hiroshi, is this series the only dependency you need for your
> Tegra114
Basically yes.
> series? So, I could merge your Tegra114 series once this series is applied?
But now "CCF" seems to be in. Then, the HACK(*1) needs to be replaced
On Tue, Jan 22, 2013 at 11:59 PM, Steve French wrote:
> merged into cifs-2.6.git
and added cc: stable
--
Thanks,
Steve
--
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
merged into cifs-2.6.git
On Tue, Jan 22, 2013 at 7:36 PM, Jeff Layton wrote:
> On Tue, 22 Jan 2013 19:20:58 -0500
> Cong Ding wrote:
>
>> When it goes to error through line 144, the memory allocated to *devname is
>> not freed, and the caller doesn't free it either in line 250. So we free the
kobject_add() will setup the kobject parent correctly.
This patch removes the redundant code.
Tested on Lenovo T420.
Signed-off-by: Wei Yang
Reviewed-by: Ram Pai
Reviewed-by: Gavin Shan
---
drivers/base/core.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git
To solve undefined symbol errors for LED class and I2C, lp55xx-common driver
should support a module build as well.
make x86_64 allmodconfig failed like this:
drivers/built-in.o: In function `lp55xx_unregister_leds':
(.text+0x161dab): undefined reference to `led_classdev_unregister'
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
drivers/clk/Makefile between commit bd3bffb544b1 ("clk: x86: add support
for Lynxpoint LPSS clocks") from the pm tree and commit 82f6b0926514
("clk: tegra: add Tegra specific clocks") from the tegra tree.
I fixed it up (see
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
arch/arm/mach-tegra/platsmp.c between commit 520f7bd73354 ("irqchip: Move
ARM gic.h to include/linux/irqchip/arm-gic.h") from the arm-soc tree and
commit 4c6e1ff5b5fe ("ARM: tegra: move tegra_cpu_car.h to
linux/clk/tegra.h")
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
arch/arm/mach-tegra/common.c between commit 0529e315bbda ("ARM: use
common irqchip_init for GIC init") from the arm-soc tree and commit
567f70da22d2 ("ARM: tegra: migrate to new clock code") from the tegra
tree.
I fixed it up
On Tue, Jan 22, 2013 at 01:08:04PM +0200, Pantelis Antoniou wrote:
> Hi
>
> On Jan 22, 2013, at 5:50 AM, David Gibson wrote:
>
> > On Fri, Jan 04, 2013 at 09:31:10PM +0200, Pantelis Antoniou wrote:
> >> Introduce DT overlay support.
> >> Using this functionality it is possible to dynamically
On Tuesday 22 January 2013 10:32 PM, Koen Kooi wrote:
Op 22 jan. 2013, om 17:16 heeft kishon het volgende geschreven:
Hi,
On Tuesday 22 January 2013 09:15 PM, kishon wrote:
On Tuesday 22 January 2013 09:11 PM, Koen Kooi wrote:
Op 22 jan. 2013, om 10:58 heeft Kishon Vijay Abraham I
het
On Wednesday 23 January 2013 03:22 AM, Tony Lindgren wrote:
* John Stultz [130122 11:02]:
Correct, with HRT, we actually trigger the HZ-frequency timer tick
from an hrtimer (which expires based on the system time driven by
the clocksource). Thus even if there is a theoretical error between
On 01/23/2013 12:31 PM, Mike Galbraith wrote:
> On Wed, 2013-01-23 at 10:44 +0800, Michael Wang wrote:
>> On 01/22/2013 10:41 PM, Mike Galbraith wrote:
>>> On Tue, 2013-01-22 at 16:56 +0800, Michael Wang wrote:
>>>
What about this patch? May be the wrong map is the killer on balance
On Tue, Jan 22, 2013 at 10:18 PM, Linus Walleij
wrote:
>> - If poll timer is activated, We use consistent DMA mappings to avoid from
>> the frequent cache operation of the timer function. sg->coherency is used
>> to check if buffer is coherent.
>
> Hm. We can begin like this but maybe we
On 28 December 2012 16:57, Naveen Krishna Chatradhi
wrote:
> Adds support for High Speed I2C driver found in Exynos5 and later
> SoCs from Samsung. This driver currently supports Auto mode.
>
> Driver only supports Device Tree method of passing platform data.
> Note: Added debugfs support for
On Tue, 2013-01-22 at 20:55 -0800, Greg Kroah-Hartman wrote:
> On Tue, Jan 22, 2013 at 11:44:09PM -0500, Steven Rostedt wrote:
> > On Tue, 2013-01-22 at 23:31 -0500, Steven Rostedt wrote:
> >
> > > >
> > > > But again, I'd really not want to do this in debugfs, how about your own
> > > >
On Wed, 2013-01-23 at 11:01 +0800, Michael Wang wrote:
> On 01/22/2013 07:34 PM, Mike Galbraith wrote:
> I suppose it's A, so my logical is:
> >> 1. find idle cpu in prev domain.
> >> 2. if failed and affine, find idle cpu in current domain.
> >
> > Hm. If cpu and prev_cpu are cache affine,
On Wed, Jan 23, 2013 at 03:58:52PM +1100, Stephen Rothwell wrote:
> Hi Linus,
>
> Today's linux-next merge of the pinctrl tree got a conflict in
> drivers/pinctrl/pinctrl-nomadik.c between commit 9e0c1fb29a7c ("pinctrl:
> Convert to devm_ioremap_resource()") from the driver-core tree and commit
>
This patch add an ADC IP found on EXYNOS5 series socs from Samsung.
Also adds the Documentation for device tree bindings.
Signed-off-by: Naveen Krishna Chatradhi
---
Changes since v1:
1. Fixed comments from Lars
2. Added support for ADC on EXYNOS5410
Changes since v2:
1. Changed the instance
Hi Linus,
Today's linux-next merge of the pinctrl tree got a conflict in
drivers/pinctrl/pinctrl-nomadik.c between commit 9e0c1fb29a7c ("pinctrl:
Convert to devm_ioremap_resource()") from the driver-core tree and commit
50f690d85e4e ("pinctrl/nomadik: simplify GPIO probe") from the pinctrl
tree.
On Tue, Jan 22, 2013 at 11:44:09PM -0500, Steven Rostedt wrote:
> On Tue, 2013-01-22 at 23:31 -0500, Steven Rostedt wrote:
>
> > >
> > > But again, I'd really not want to do this in debugfs, how about your own
> > > filesystem?
> >
> > I will note that this never modifies the debugfs code. But
On Tue, 2013-01-22 at 20:41 -0800, Greg Kroah-Hartman wrote:
> Yes, you would need to require distros to mount it in the proper place,
> which is a pain, but not impossible. It's up to you, as I thought you
> needed to modify debugfs, I didn't like it, but if you can do it in your
> own code, I
On Wed, Jan 23, 2013 at 03:45:25PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in
> drivers/staging/et131x/et131x.c between commit f9a8f83b04e0 ("net: phy:
> remove flags argument from phy_{attach, connect, connect_direct}") from
> the
On Tue, 2013-01-22 at 23:44 -0500, Steven Rostedt wrote:
> + ret = event_trace_add_tracer(tr->dir, tr);
> + if (ret)
> + goto out_free_tr;
> +
> + init_tracer_debugfs(tr, tr->dir);
> +
> + mutex_unlock(_types_lock);
> +
> + list_add(>list, _trace_arrays);
I just
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/et131x/et131x.c between commit f9a8f83b04e0 ("net: phy:
remove flags argument from phy_{attach, connect, connect_direct}") from
the net-next tree and commit 26ef1021c1c7 ("staging: et131x: Modify block
On Tue, 2013-01-22 at 23:31 -0500, Steven Rostedt wrote:
> >
> > But again, I'd really not want to do this in debugfs, how about your own
> > filesystem?
>
> I will note that this never modifies the debugfs code. But it does
> circumvent it. That is, all this code lives in kernel/trace/trace.c.
On Tue, Jan 22, 2013 at 01:06:09PM +0200, Pantelis Antoniou wrote:
> Hi
>
> On Jan 22, 2013, at 6:05 AM, David Gibson wrote:
>
> > On Mon, Jan 21, 2013 at 12:59:15PM +0200, Pantelis Antoniou wrote:
> >> Hi David
> >>
> >> On Jan 21, 2013, at 6:48 AM, David Gibson wrote:
> >>
> >>> On Fri, Jan
On Wed, Jan 23, 2013 at 03:15:52PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core tree got a conflict in
> drivers/gpio/gpio-mvebu.c between commit 11c0ceec073c ("gpio: mvebu:
> Don't free chip label memory") from Linus' tree and commit 641d03422a59
>
Hi experts,
Seems there is an bug related to function n_tty_set_roomin source file
drivers/tty/n_tty.c. This function is used to set receive_room based on
the read_cntby both the consumer and the producer of the tty's read buffer.
But this function is not serialized, so I am afraid there is
a
On Tue, Jan 22, 2013 at 11:31:35PM -0500, Steven Rostedt wrote:
> On Tue, 2013-01-22 at 20:08 -0800, Greg Kroah-Hartman wrote:
>
> > > Is doing something as silly as the following fine, or is there a better
> > > way?
> >
> > Yes, why not create your own fs for ftrace? :)
>
> But but but...
>
On Wed, 2013-01-23 at 10:44 +0800, Michael Wang wrote:
> On 01/22/2013 10:41 PM, Mike Galbraith wrote:
> > On Tue, 2013-01-22 at 16:56 +0800, Michael Wang wrote:
> >
> >> What about this patch? May be the wrong map is the killer on balance
> >> path, should we check it? ;-)
> >
> > [
On Tue, 2013-01-22 at 20:08 -0800, Greg Kroah-Hartman wrote:
> > Is doing something as silly as the following fine, or is there a better
> > way?
>
> Yes, why not create your own fs for ftrace? :)
But but but...
debugfs is s convenient!
Do you think it would be worth doing that though? I
Hi Ezequiel,
On Tue, Jan 22, 2013 at 06:46:58AM -0300, Ezequiel Garcia wrote:
> From: Ezequiel Garcia
>
> The purpose of trace_analyze.py tool is to perform static
> and dynamic memory analysis using a kmem ftrace
> log file and a built kernel tree.
>
> This script and related work has been
On Tue, 22 Jan 2013 20:44:41 -0500 (EST) Mikulas Patocka
wrote:
>
>
> On Wed, 16 Jan 2013, Guangliang Zhao wrote:
>
> > On Wed, Jan 09, 2013 at 12:43:21AM -0500, Mikulas Patocka wrote:
> > > Hi
> > Hi,
> >
> > I think it is very good that your patches could be used for other
> >
Hi Andrey,
On Tue, Jan 22, 2013 at 11:15 AM, Andrey Vagin wrote:
> This patch set adds ability to choose a signal queue and
> to read signals without dequeuing them.
>
> Three new flags are added:
> SFD_SHARED_QUEUE -- reads will be from process-wide shared signal queue
>
On Mon, 2013-01-21 at 21:12 +, Matt Fleming wrote:
[...]
> From 92e73f936e40a8c6562e47425d434a4e62d2b8e2 Mon Sep 17 00:00:00 2001
> From: Matt Fleming
> Date: Wed, 14 Nov 2012 09:42:35 +
> Subject: [PATCH] efi: Make 'efi_enabled' a function to query EFI facilities
>
> Originally
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in
drivers/gpio/gpio-mvebu.c between commit 11c0ceec073c ("gpio: mvebu:
Don't free chip label memory") from Linus' tree and commit 641d03422a59
("gpio: Convert to devm_ioremap_resource()") from the driver-core tree.
I fixed
From: Freddy Xin
Date: Wed, 23 Jan 2013 10:32:17 +0800
> Fixed coding style errors.
There are still many style issues remaining, you have a lot more
work to do, for example:
> + return fn(dev, cmd, USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_DEVICE,
> +value, index, data, size);
On Tue, 2013-01-22 at 23:26 +0100, Geert Uytterhoeven wrote:
> On Tue, Jan 22, 2013 at 6:47 AM, Stepan Moskovchenko
> wrote:
> > Add the %pa format specifier for printing a phys_addr_t
> > type, since the physical address size on some platforms
> > can vary based on build options, regardless of
undefined reference to `i2c_smbus_write_byte_data'
Caused by commit 597eb710be87 ("leds-lp55xx: add new common driver for
lp5521/5523").
I have used the leds tree from next-20130122 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpwXoIzEojxK.pgp
Description: PGP signature
On Tue, Jan 22, 2013 at 10:01:54PM -0500, Steven Rostedt wrote:
> Let me explain the situation.
>
> I'm adding the ability to create multiple ftrace instances (buffers). I
> have a directory: /debug/tracing/instances that will hold sub
> directories that have the control files for these buffers.
On 1/21/2013 6:32 PM, Julia Lawall wrote:
> From: Julia Lawall
>
> Delete successive tests to the same location. The current value of ln has
> been tested already, and is clearly not NULL, given the enclosing if
> condition. Furthermore, the result of csio_lnode_alloc is currently
> ignored.
>
On Wed, 2013-01-09 at 17:03 -0800, Sukadev Bhattiprolu wrote:
> [PATCH 1/6][v3] perf/Power7: Use macros to identify perf events
>
> Define and use macros to identify perf events codes. This would make it
> easier and more readable when these event codes need to be used in more
> than one place.
>
On Tue, 2013-01-22 at 22:01 -0500, Steven Rostedt wrote:
> As you can see, I haven't implemented the rmdir yet.
I decided to implement this too :-)
static int instance_rmdir(struct inode *inode, struct dentry *dentry)
{
struct dentry *parent;
int ret;
/* Paranoid: Make
On Wed, Jan 23, 2013 at 03:24:22AM +, Fangxiaozhi (Franko) wrote:
> Dear Greg:
>
> > -Original Message-
> > From: Greg KH [mailto:g...@kroah.com]
> > Sent: Tuesday, January 22, 2013 11:04 PM
> > To: Fangxiaozhi (Franko)
> > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
Dear Greg:
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Tuesday, January 22, 2013 11:04 PM
> To: Fangxiaozhi (Franko)
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Xueguiying
> (Zihan);
> Linlei (Lei Lin); Yili (Neil); Wangyuhua (Roger, Credit);
From: xueminsu
Date: Tue, 22 Jan 2013 22:39:39 +0800
Subject: [PATCH] drm_crtc: check if fb_create return NULL
Some buggy driver may still return NULL in fb_create,
which leads to kernel panic.
Signed-off-by: xueminsu
---
drivers/gpu/drm/drm_crtc.c |7 +++
1 files changed, 7
Dear Minchan,
> So what's the effect for user?
Sorry I have no idea.
The kernel seems to work well without this patch; or in fact not so
well, PAE crashing with spurious OOM. In my fruitless efforts of
avoiding OOM by sensible choices of sysctl tunables, I noticed that
maybe the treatment of
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
drivers/devfreq/exynos4_bus.c between commit 8fa938acb318 ("PM / devfreq:
exynos4_bus: honor RCU lock usage") from the pm tree and commit
8a168ca7074b ("treewide: Fix typo in various drivers") from the trivial
tree.
I fixed
On 01/22/2013 06:35 PM, Jason Gunthorpe wrote:
On Tue, Jan 22, 2013 at 05:54:21PM -0800, John Stultz wrote:
complicated part. Additionally, there may be cases where the
timekeeping clocksource is one clocksource and the suspend
clocksource is another. So I think to properly integrate this sort
Hi Jiri,
On Wed, 23 Jan 2013 14:03:48 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the trivial tree got a conflict in
> arch/mips/cavium-octeon/executive/cvmx-helper-util.c between commit
> baf783ede9dc ("MIPS: Whitespace cleanup") from the mips tree and commit
> d82603c6da75
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in
arch/mips/cavium-octeon/executive/cvmx-helper-util.c between commit
baf783ede9dc ("MIPS: Whitespace cleanup") from the mips tree and commit
d82603c6da75 ("treewide: Replace incomming with incoming in all comments
and
Let me explain the situation.
I'm adding the ability to create multiple ftrace instances (buffers). I
have a directory: /debug/tracing/instances that will hold sub
directories that have the control files for these buffers. Basically,
each directory in the instances directory will be a duplicate
On 01/22/2013 07:34 PM, Mike Galbraith wrote:
> On Tue, 2013-01-22 at 16:56 +0800, Michael Wang wrote:
>> On 01/22/2013 04:03 PM, Mike Galbraith wrote:
>> [snip]
>>> ...
>
> That was with your change backed out, and the q/d below applied.
So that change will help to solve the
On Tue, Jan 22, 2013 at 09:46:24AM +, Lee Jones wrote:
> To locate a consumer that currently holds a regulattor, a new sysfs
> entry is created. The consumer are published in
> /sys/class/regulator/regulator.<#>/use.
We call our reference counts use count but this was in fact the original
Hi experts,
Seems there is an bug related to function n_tty_set_roomin source file
drivers/tty/n_tty.c. This function is used to set receive_room based on
the read_cntby both the consumer and the producer of the tty's read buffer.
But this function is not serialized, so I am afraid there is
a
On 01/22/2013 10:41 PM, Mike Galbraith wrote:
> On Tue, 2013-01-22 at 16:56 +0800, Michael Wang wrote:
>
>> What about this patch? May be the wrong map is the killer on balance
>> path, should we check it? ;-)
>
> [1.232249] Brought up 40 CPUs
> [1.236003] smpboot: Total of 40
On Mon, Jan 14, 2013 at 4:30 PM, Colin Cross wrote:
> On Mon, Jan 14, 2013 at 4:25 PM, Andrew Morton
> wrote:
>> On Mon, 14 Jan 2013 16:19:23 -0800
>> Colin Cross wrote:
>>
>>> >> +static void watchdog_check_hardlockup_other_cpu(void)
>>> >> +{
>>> >> + unsigned int next_cpu;
>>> >> +
>>>
On 2013/1/23 8:27, Tejun Heo wrote:
> (cc'ing Andrew as scheduler folks are difficult to get response from
> these days and I can't think of anyone else to bother :)
>
> Hello, Li.
>
> The cgroup part looks good to me but it would be great if the
> descriptions are more detailed, especially,
On Tue, Jan 22, 2013 at 05:54:21PM -0800, John Stultz wrote:
> >>complicated part. Additionally, there may be cases where the
> >>timekeeping clocksource is one clocksource and the suspend
> >>clocksource is another. So I think to properly integrate this sort
> >Does the difference matter? The
From: Freddy Xin
This is a resubmission.
Fixed coding style errors.
The _nopm version usb functions were added to access register in suspend and
resume functions.
Serveral variables allocted dynamically were removed and replaced by stack
variables.
ax88179_get_eeprom were modified from
From: xueminsu
Date: Tue, 22 Jan 2013 22:39:39 +0800
Subject: [PATCH] drm_crtc: check if fb_create return NULL
Some buggy driver may still return NULL in fb_create,
which leads to kernel panic.
Signed-off-by: xueminsu
---
drivers/gpu/drm/drm_crtc.c |6 ++
1 files changed, 6
1 - 100 of 1450 matches
Mail list logo
