On Friday 11 October 2013 12:23 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 11 October 2013 12:00 PM, Nishanth Menon wrote:
>> On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I
>> wrote:
>>>
regulator-boot-on indicates that PMIC enables it by default as part of
OTP or s
Hi,
On Friday 11 October 2013 12:00 PM, Nishanth Menon wrote:
> On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I wrote:
>>
>>> regulator-boot-on indicates that PMIC enables it by default as part of
>>> OTP or some internal behavior -> Looking at the measurements done on
>>> uEVM and OTP in
From: Lan Tianyu
Make acpi_dev_resource_address_space() to accept struct
acpi_resource_address64 as param and rename it to *_full.
This is for some cases that acpi address info is also needed
after convert from acpi resouce to generic resource.
Add acpi_dev_resource_addres_space() again as a wr
From: Lan Tianyu
Using ACPI resource functions to convert ACPI resource to generic resource
Signed-off-by: Lan Tianyu
---
This patch just passes through compilation test due to no ia64 machine on hand.
arch/ia64/pci/pci.c | 38 +-
1 file changed, 21 inserti
From: Lan Tianyu
This patchset is to add memory prefecth flag setting and address
translation support in the ACPI resource function. Convert x86/iad64
PCI root bridge's ACPI resource to generic resource via ACPI resource
functions.
PATCH 3 is to add new function acpi_dev_resource_address_space_f
On Fri, Oct 11, 2013 at 07:46:55AM +0200, Ingo Molnar wrote:
>
> * Fengguang Wu wrote:
>
> > > Indeed. Something like the updated version below?
> > >
> > > [ I kept the asm_volatile_goto() naming to make sure the implicit
> > > volatile
> > > is visible. ]
> >
> > Ingo, I applied this pat
On Thu, Oct 10, 2013 at 11:30 PM, Benjamin Herrenschmidt
wrote:
> On Thu, 2013-10-10 at 22:26 +0200, Geert Uytterhoeven wrote:
>> > This is not CPUs. CPUs are threads really. Even if they were cores,
>> that
>> > still wouldn't cut it. I'm looking at chips here and not all of them
>> > actually pr
After H/W error happens under FFM enabled mode, lots of information
are shown but some important parts like DIMM location missed. This
patch is used to show these extra fileds.
Original-author: Tony Luck
Signed-off-by: Chen, Gong
---
drivers/acpi/apei/cper.c | 12
1 file changed, 1
To satisfy the necessary of following patches and make related definition
more clear, update some definitions about CPER. No functional changes.
Signed-off-by: Chen, Gong
---
drivers/acpi/apei/apei-internal.h | 12 -
drivers/acpi/apei/cper.c | 46
This error log driver (a.k.a eMCA driver) is implemented based on
http://www.intel.com/content/www/us/en/architecture-and-technology/enhanced-mca-logging-xeon-paper.html.
After errors are captured, more valuable information can be
got with this new enhanced error log driver.
Signed-off-by: Chen, G
Commit aaf9d93 only catches condition check before print,
but the similar check is needed during printing CPER error
sections.
Signed-off-by: Chen, Gong
---
drivers/acpi/apei/cper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/apei/cper.c b/drivers/acpi/apei/c
Keep up only the most important fields for memory error
reporting. The detail information will be moved to perf/trace
interface.
Suggested-by: Tony Luck
Signed-off-by: Chen, Gong
---
drivers/acpi/apei/cper.c | 42 ++
1 file changed, 14 insertions(+), 28 d
In latest UEFI spec(by now it is 2.4) memory error definition
for CPER (UEFI 2.4 Appendix N Common Platform Error Record)
adds some new fields. These fields help people to locate
memory error on actual DIMM location.
Original-author: Tony Luck
Signed-off-by: Chen, Gong
---
drivers/acpi/apei/cpe
Use trace interface to elaborate all H/W error related
information.
Signed-off-by: Chen, Gong
---
drivers/acpi/Kconfig| 7 ++-
drivers/acpi/Makefile | 4 ++
drivers/acpi/acpi_extlog.c | 28 +++-
drivers/acpi/apei/cper.c| 13 --
drivers/acpi/debug_extlog.h |
This patch adds a new interface to decode memory device (type 17)
to help error reporting on DIMMs.
Original-author: Tony Luck
Signed-off-by: Chen, Gong
---
arch/ia64/kernel/setup.c| 1 +
arch/x86/kernel/setup.c | 1 +
drivers/firmware/dmi_scan.c | 60 +
[PATCH 1/8] ACPI, APEI, CPER: Fix status check during error printing
[PATCH 2/8] ACPI, CPER: Update cper info
[PATCH 3/8] ACPI, x86: Extended error log driver for x86 platform
[PATCH 4/8] DMI: Parse memory device (type 17) in SMBIOS
[PATCH 5/8] ACPI, APEI, CPER: Add UEFI 2.4 support for memory erro
When inserting a wrong value to /sys/devices/system/memory/memoryX/state file,
following messages are shown. And device_hotplug_lock is never released.
[ BUG: lock held when returning to user space! ]
3.12.0-rc4-debug+ #3 Tainted: GW
---
On 2013/10/11 14:16, Gavin Shan wrote:
> On Fri, Oct 11, 2013 at 04:49:56PM +1100, Benjamin Herrenschmidt wrote:
>> On Fri, 2013-09-06 at 14:30 -0600, Bjorn Helgaas wrote:
>>> On Thu, Sep 05, 2013 at 03:55:27PM +0800, Yijing Wang wrote:
Use pci_is_pcie() to simplify code.
Acked-by: K
On Fri, Oct 11, 2013 at 1:13 AM, Kishon Vijay Abraham I wrote:
>
>> regulator-boot-on indicates that PMIC enables it by default as part of
>> OTP or some internal behavior -> Looking at the measurements done on
>> uEVM and OTP information -> regulator-boot-on should be kept here.
>
> No. Actually
This introduces an implementation of squashfs_readpage_block()
that directly decompresses into the page cache.
This uses the previously added page handler abstraction to push
down the necessary kmap_atomic/kunmap_atomic operations on the
page cache buffers into the decompressors. This enables
dir
Restructure squashfs_readpage() splitting it into separate
functions for datablocks, fragments and sparse blocks.
Move the memcpying (from squashfs cache entry) implementation of
squashfs_readpage_block into file_cache.c
This allows different implementations to be supported
Signed-off-by: Philli
Hi Linus,
Please pull a gdb related fix. This release, we've had more pull requests than
usual. Next time around I'll try to hold on to them for a bit before sending
over.
Thx,
-Vineet
--->
The following changes since commit d0e639c9e06d44e713170031fe05fb60ebe680af:
Linux 3.12-rc4 (2
This patch-set introduces an implementation of
squashfs_readpage() that directly decompresses into the
page cache.
It first generalises the decompressors by adding a page handler
abstraction. This adds helpers to allow the decompressors
to access and process the output buffers in an implementatio
On 2013/10/11 13:49, Benjamin Herrenschmidt wrote:
> On Fri, 2013-09-06 at 14:30 -0600, Bjorn Helgaas wrote:
>> On Thu, Sep 05, 2013 at 03:55:27PM +0800, Yijing Wang wrote:
>>> Use pci_is_pcie() to simplify code.
>>>
>>> Acked-by: Kumar Gala
>>> Reviewed-by: Gavin Shan
>>> Signed-off-by: Yijing W
Generalise the decompressors by adding a page handler
abstraction. This adds helpers to allow the decompressors
to access and process the output buffers in an implementation
independant manner.
This allows different types of output buffer to be passed
to the decompressors, with the implementation
Set match_any_dev and sysfs_bind_only such that echoing a platform
device ID to the driver sysfs bind file will successfully match and bind
the device to the vfio-platform meta-driver in accordance to the
desired semantics for vfio drivers.
Signed-off-by: Kim Phillips
---
this patch depends on th
Platform drivers such as the vfio-platform "meta-" driver [1]
should be allowed to specify that they can bind to any device,
much like PCI drivers can with PCI_ANY_ID.
Currently, binding platform drivers to devices depends on:
- a string match in the device node's compatible entry (OF)
- a string
VFIO supports pass-through of devices to user space - for sake
of illustration, say a PCI e1000 device:
- the e1000 is first unbound from the PCI e1000 driver via sysfs
- the vfio-pci driver is told via new_id that it now handles e1000 devices
- the e1000 is explicitly bound to vfio-pci through sy
Force the vfio-pci driver to only be bound explicitly via sysfs to avoid
conflics with other drivers in the event of a hotplug.
Signed-off-by: Kim Phillips
---
drivers/vfio/pci/vfio_pci.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_p
On 10/10/13 at 01:34pm, Matt Fleming wrote:
> On Thu, 10 Oct, at 10:58:28AM, Borislav Petkov wrote:
> > On Thu, Oct 10, 2013 at 04:14:34PM +0800, Dave Young wrote:
> > > Even though I still have no idea why kernel text overlap with efi boot
> > > region, anyway map the un-overlapped part is necessa
Hello,
On 10/10/2013 06:04 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Oct 09, 2013 at 08:41:57AM +0200, Robert Baldyga wrote:
>> @@ -2616,14 +2630,19 @@ static int s3c_hsotg_ep_enable(struct usb_ep *ep,
>> s3c_hsotg_set_ep_maxpacket(hsotg, hs_ep->index, mps);
>>
>> /* default, set to n
* Matthew Garrett wrote:
> On Thu, Oct 10, 2013 at 07:45:21PM +0200, Ingo Molnar wrote:
>
> > Also, the main question would be, what is the typical value for
> > si->lfb_depth. 32 on almost all EFI systems? All around the map? Depends
> > on what graphics state the EFI bootloader passes us?
>
* H. Peter Anvin wrote:
> I'm trying to wrap my head around if there are use cases where disabling
> either CONFIG_X86_UP_APIC or CONFIG_X86_LOCAL_APIC would ever make sense
> anymore.
>
> I am guessing there are probably some small number of embedded systems
> which still don't have LAPICs,
On Thursday 10 October 2013 06:41 PM, Laxman Dewangan wrote:
> On Thursday 10 October 2013 06:07 PM, Kishon Vijay Abraham I wrote:
>> The Palmas device contains only a USB VBUS-ID detector, so added a
>> compatible type *ti,palmas-usb-vid*. Didn't remove the existing compatible
>> types for backwar
On Thursday 10 October 2013 07:49 PM, Nishanth Menon wrote:
> On 16:19-20131010, Kishon Vijay Abraham I wrote:
>> smps10 should be enabled only in the case of host mode. So stop
>> doing always_on, boot_on from smps10_out1. The driver will enable it in host
>> mode.
>&g
With 23f0d2093c789 (sched: Factor out code to should_we_balance()),
we no longer pass balance as argument to update_sd_lb_stats().
So remove it's description.
Signed-off-by: Kamalesh Babulal
---
kernel/sched/fair.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/s
* Linus Torvalds wrote:
> On Thu, Oct 10, 2013 at 12:04 PM, Steven Rostedt wrote:
> >
> > I'm wondering if we can have a for_each_cpu() that only disables
> > preemption in the loop.
>
> I think we'd generally want to have it be something the loop asks for.
>
> If the loop is just some kind
Signed-off-by: Andreas Larsson
---
drivers/usb/gadget/Kconfig | 14 ++
drivers/usb/gadget/Makefile |3 ++-
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
index 48cddf3..922a04d 100644
--- a/drivers/usb/gadg
On Friday 11 October 2013 12:51 AM, Arokux X wrote:
> Hi,
>
> recently I have been working on mainlining a simple bus glue driver
> for the USB EHCI for the Allwinner family of the ARM SoCs aka sunxi.
> The patches are almost ready and can be found at [1] and will be
> submitted once completely re
On Wed, Oct 9, 2013 at 5:38 PM, Lukasz Majewski wrote:
> Attached commits provide cpufreq regression fixes for Trats and Trats2
> Exynos4 boards.
> Since v3.12 Exynos4 uses common clock framework for clock manipulation.
> Those patches restore correct output for cpuinfo_cur_freq [1] sysfs
> attrib
* Namhyung Kim wrote:
> Hello,
>
> This is a new version of callchain improvement patchset. Basically
> it's almost same as v4 but rebased on current acme/perf/core and some
> functions are renamed as Frederic requested.
>
> Now I'm hunting down a bug in 'perf report -s sym' which was found
>
On Fri, 2013-10-11 at 16:49 +1100, Ryan Mallon wrote:
> It doesn't matter what the value of kptr_restrict happens to be, the
> code is still broken. So, with your patch, values 0 and 2 of
> kptr_restrict will print a seemingly correct value, but when
> kptr_restrict is 1 then it will print 'pK-err
On 10/10/13 09:30, Michal Simek wrote:
> s/op/pdev/ in xilinxfb_of_probe().
> No functional chagnes.
>
> Signed-off-by: Michal Simek
> ---
> Changes in v3: None
> Changes in v2: None
>
> drivers/video/xilinxfb.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
Thanks,
On Fri, 2013-09-06 at 14:30 -0600, Bjorn Helgaas wrote:
> On Thu, Sep 05, 2013 at 03:55:27PM +0800, Yijing Wang wrote:
> > Use pci_is_pcie() to simplify code.
> >
> > Acked-by: Kumar Gala
> > Reviewed-by: Gavin Shan
> > Signed-off-by: Yijing Wang
> > Cc: Gavin Shan
> > Cc: Benjamin Herrenschmi
No real reason to do this.
"K. Y. Srinivasan" wrote:
>The variable hv_lapic_frequency is only used when CONFIG_X86_LOCAL_APIC
>is defined. Make the necessary adjustment.
>
>Signed-off-by: K. Y. Srinivasan
>---
> arch/x86/kernel/cpu/mshyperv.c |2 +-
> 1 files changed, 1 insertions(+), 1 dele
* Kirill A. Shutemov wrote:
> I've missed that we preallocate few pmds on pgd_alloc() if X86_PAE
> enabled. Let's add missed constructor/destructor calls.
>
> I haven't noticed it during testing since prep_new_page() clears
> page->mapping and therefore page->ptl. It's effectively equal to
> sp
On 11/10/13 16:38, Joe Perches wrote:
> On Fri, 2013-10-11 at 16:31 +1100, Ryan Mallon wrote:
>> On 11/10/13 16:25, Joe Perches wrote:
>>> Printing kernel pointers via %pK has a minor defect when
>>> kptr_restrict is set to 2: the pointer may be emitted
>>> as "pK-error" instead of all 0's when in
* Fengguang Wu wrote:
> > Indeed. Something like the updated version below?
> >
> > [ I kept the asm_volatile_goto() naming to make sure the implicit volatile
> > is visible. ]
>
> Ingo, I applied this patch (as commit c015a7f0b746) on top of
> tip/sched/core
>
> 3354781a2184 "sch
On Fri, 2013-10-11 at 16:31 +1100, Ryan Mallon wrote:
> On 11/10/13 16:25, Joe Perches wrote:
> > Printing kernel pointers via %pK has a minor defect when
> > kptr_restrict is set to 2: the pointer may be emitted
> > as "pK-error" instead of all 0's when in an interrupt.
>
> NAK. This is not a de
On Thu, Oct 10, 2013 at 06:03:01PM -0300, Marcelo Tosatti wrote:
> On Thu, Oct 10, 2013 at 10:16:46PM +0300, Gleb Natapov wrote:
> > On Thu, Oct 10, 2013 at 01:42:22PM -0300, Marcelo Tosatti wrote:
> > > On Thu, Oct 10, 2013 at 03:08:45PM +0300, Gleb Natapov wrote:
> > > > On Wed, Oct 09, 2013 at 1
On 11/10/13 16:25, Joe Perches wrote:
> Printing kernel pointers via %pK has a minor defect when
> kptr_restrict is set to 2: the pointer may be emitted
> as "pK-error" instead of all 0's when in an interrupt.
NAK. This is not a defect, as I explained earlier. It is really a defect
that it _doesn
On Fri, 2013-10-11 at 16:19 +1100, Ryan Mallon wrote:
> Yeah, that is probably the best solution. I'll try to put together a
> patch series doing this. It will obviously be more involved though, so I
> think it is still worth merging the original patch in the interm.
I just submitted a patch neate
Hi Linus,
all over the map,
nouveau: disable MSI, needs more work, will try again next merge window,
radeon: audio + uvd regression fixes, dpm fixes, reset fixes
i915: dpms one might fix your haswell,
and one pain in the ass revert, so we have VGA arbitration that when
implemented 4-5 years ago
Remove a few coding style nits:
o Leading spaces for tabs
o case indentation depth
o else and brace locations
o logical continuation placement
Several checkpatch bleats still exist,
mostly not worth changing.
Signed-off-by: Joe Perches
---
lib/vsprintf.c | 83 +-
Printing kernel pointers via %pK has a minor defect when
kptr_restrict is set to 2: the pointer may be emitted
as "pK-error" instead of all 0's when in an interrupt.
Fix this defect, neaten the code, and correct the sysctl
documentation.
Add missing documentation for 2 other uses: %pNF and %pV.
On 11/10/13 15:42, George Spelvin wrote:
> ebied...@xmission.com (Eric W. Biederman) wrote:
>> Sigh. This is all wrong. The only correct thing to test is
>> file->f_cred. Aka the capabilities of the program that opened the
>> file.
>>
>> Which means that the interface to %pK in the case of kptr_
From: Frederic Weisbecker
This way we can later delimit a lifecycle for the comm and map a hist to
a precise comm:timeslice couple.
Comm and fork events that don't have PERF_SAMPLE_TIME samples can only
send 0 value as a timestamp and thus should overwrite any previous comm
on a given thread bec
Hi Mark, Jean-Christophe,
On 10/10/13 20:50, Mark Brown wrote:
> Today's linux-next merge of the omap_dss2 tree got conflicts in
> drivers/video/omap2/dss/hdmi4_core.[ch] caused by ef26958a (omapdss:
> HDMI: Rename hdmi driver files to nicer names) interacting with a range
> of commits from Ricard
From: Frederic Weisbecker
As the thread comm is going to be implemented by way of a more
complicated data structure than just a pointer to a string from the
thread struct, convert the readers of comm to use an accessor instead
of accessing it directly. The accessor will be later overriden to
supp
From: Frederic Weisbecker
This new comm infrastructure provides two features:
1) It keeps track of all comms lifecycle for a given thread. This
way we can associate a timeframe to any thread comm, as long as
PERF_SAMPLE_TIME samples are joined to comm and fork events.
As a result we should have
From: Namhyung Kim
It can take quite amount of time so add progress bar UI to inform user.
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-annotate.c | 2 +-
tools/perf/builtin-diff.c | 2 +-
tools/perf/builtin-report.c | 10 +-
tools/perf/builtin-to
From: Frederic Weisbecker
Now that comm strings are allocated only once and refcounted to be shared
among threads, these can now be safely compared by addresses. This
should remove most hists collapses on post processing.
Signed-off-by: Frederic Weisbecker
Cc: Jiri Olsa
Cc: David Ahern
Cc: In
From: Namhyung Kim
At insert time, a hist entry should reference comm at the time
otherwise it'll get the last comm anyway.
Signed-off-by: Namhyung Kim
Cc: Frederic Weisbecker
Link: http://lkml.kernel.org/n/tip-n6pykiiymtgmcjs834go2...@git.kernel.org
[ Fixed up const pointer issues ]
Signed-of
From: Namhyung Kim
Introduce ui_progress_setup() and ui_progress__advance() to separate
out from the session logic. It'll be used by other places in the
upcoming patch.
Cc: Jiri Olsa
Cc: Frederic Weisbecker
Signed-off-by: Namhyung Kim
---
tools/perf/ui/progress.c | 18 ++
t
From: Namhyung Kim
Current collapse stage has a scalability problem which can be
reproduced easily with parallel kernel build. This is because it
needs to traverse every children of callchain linearly during the
collapse/merge stage. Convert it to rbtree reduced the overhead
significantly.
On
Hello,
This is a new version of callchain improvement patchset. Basically
it's almost same as v4 but rebased on current acme/perf/core and some
functions are renamed as Frederic requested.
Now I'm hunting down a bug in 'perf report -s sym' which was found
during the test, but I think it's not re
> I think something like the below may address the issue - I've only build
> tested this so far.
>
> We have another case where DRM does the wrong thing here too - a similar
> thing goes on with connectors as well. I've not yet looked into this,
> but I'll take a look later today.
>
> Fengguang
The variable hv_lapic_frequency is only used when CONFIG_X86_LOCAL_APIC
is defined. Make the necessary adjustment.
Signed-off-by: K. Y. Srinivasan
---
arch/x86/kernel/cpu/mshyperv.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x
ebied...@xmission.com (Eric W. Biederman) wrote:
> Sigh. This is all wrong. The only correct thing to test is
> file->f_cred. Aka the capabilities of the program that opened the
> file.
>
> Which means that the interface to %pK in the case of kptr_restrict is
> broken as it has no way to be pas
On 10/10/13 21:58, Lars-Peter Clausen wrote:
> According to the datasheet the the panel as a dedicated dout pin. Maybe
> you did not connect it in your design, which means you won't be able to
> read any data from the panel at all.
I don't see a dedicated dout in the datasheet...
http://dl.wolfga
From: Wei Yongjun
Use free_bch() instead of kfree() to free init_bch()
allocated data.
Signed-off-by: Wei Yongjun
---
drivers/mtd/devices/docg3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/docg3.c b/drivers/mtd/devices/docg3.c
index 3e1b0a0..4f091c1
From: Wei Yongjun
Use vfree() instead of kfree() to free vmalloc()
allocated data.
Signed-off-by: Wei Yongjun
---
drivers/staging/crystalhd/crystalhd_lnx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/crystalhd/crystalhd_lnx.c
b/drivers/staging/crystalhd
On Thu, Oct 10, 2013 at 05:12:19PM +0200, Ingo Molnar wrote:
>
> * Jakub Jelinek wrote:
>
> > On Thu, Oct 10, 2013 at 07:04:18AM -0700, Richard Henderson wrote:
> > > On 10/10/2013 01:31 AM, Jakub Jelinek wrote:
> > > > Also, for the bitops patch, you probably want an asm_volatile_goto
> > > >
> Damn gmail screwed up my reply-all,
>
> anyhoo I get the feeling I'd rather do this like fbdev does and stop using
> an embedded kdev for this if I can. The lifetime of the minor and the sysfs
> objects aren't necessarily that tied together esp with hot unplug of
> USB devices.
>
> e.g. when a US
Sorry for the very late reply, finally got some time to look at other
peoples code.
On Tue, 3 Sep 2013 14:05:08 +0900
Namhyung Kim wrote:
> From: Namhyung Kim
>
> The set_graph_notrace filter is analogous to set_ftrace_notrace and
> can be used for eliminating uninteresting part of function g
the capacity calculation is obvious buggy.
Signed-off-by: Shaohua Li
---
drivers/block/null_blk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: master/drivers/block/null_blk.c
===
--- master.orig/drivers/block/nul
On Sun, Oct 06, 2013 at 08:14:10PM -0400, Mike Snitzer wrote:
> On Fri, Oct 04 2013 at 1:07pm -0400,
> Mike Snitzer wrote:
>
> > With your latest fix I was able to create a thin device and format with
> > XFS. Unfortunately, when I tried to run the thinp-test-suite the very
> > first BasicTest
If a tag is freed, the request might be used very soon. There is a short window
rq->q is null, so cache it.
Signed-off-by: Shaohua Li
---
block/blk-mq.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: master/block/blk-mq.c
=
On Thu, Oct 10, 2013 at 8:53 PM, Russell King - ARM Linux
wrote:
> On Thu, Oct 10, 2013 at 10:19:20AM +0100, Russell King - ARM Linux wrote:
>> On Thu, Oct 10, 2013 at 03:23:45AM +0100, Dave Airlie wrote:
>> >
>> > > I think David Arlie also needs a quiet talking to about how to use the
>> > > dev
1. Add new supporting declarations to option.c, to support Huawei new devices
with new bInterfaceSubClass value.
Signed-off-by: fangxiaozhi
--- linux-3.11.4-orig/drivers/usb/serial/option.c 2013-10-10 16:13:25.443072876
+0800
+++ linux-3.11.4/drivers/usb/serial/o
Ryan Mallon writes:
> On 11/10/13 13:20, Eric W. Biederman wrote:
>> Joe Perches writes:
>>
>>> Some setuid binaries will allow reading of files which have read
>>> permission by the real user id. This is problematic with files which
>>> use %pK because the file access permission is checked at
On 10/10/2013 03:07 PM, Matt Porter wrote:
On 10/10/2013 01:57 PM, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, October 10, 2013 10:46 AM
On Thu, Oct 10, 2013 at 12:54:40PM -0400, Matt Porter wrote:
On 10/10/2013 11:29 AM, Felipe Balbi wrote:
On Mon, Oct 07,
On 11/10/13 13:20, Eric W. Biederman wrote:
> Joe Perches writes:
>
>> Some setuid binaries will allow reading of files which have read
>> permission by the real user id. This is problematic with files which
>> use %pK because the file access permission is checked at open() time,
>> but the kptr_
On Mon, Oct 07, 2013 at 07:19:58PM -0300, Geyslan G. Bem wrote:
> Free memory allocated to edma_desc when failing to allocate slot.
>
> Signed-off-by: Geyslan G. Bem
Applied thanks
~Vinod
> ---
> drivers/dma/edma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/dma/edma.c b/d
On Thu, Sep 26, 2013 at 02:28:37AM +0400, Sergei Shtylyov wrote:
> Commit c1c63a14f4f2419d093acd7164eccdff315baa86 (DMA: shdma: switch to managed
> resource allocation) got rid of shdma_free_irq() but unfortunately got merged
> later than commit c4f6c41ba790bbbfcebb4c47a709ac8ff1fe1af9 (dma: add d
On Thu, Oct 10, 2013 at 08:23:13PM -0600, Jens Axboe wrote:
> On Thu, Oct 10 2013, Kent Overstreet wrote:
> > Linus, please apply - the last fix in the bugfix series I sent you had an
> > embarassing screwup...
> >
> > For 3.13, shall I start sending you pull requests directly?
>
> Sorry I droppe
From: Hyunhee Kim
Date: Wed, 9 Oct 2013 16:21:36 +0900
Subject: [PATCH] Input: add regulator haptic driver
The regulator haptic driver function can be used to control motor by on/off
regulator.
User can control the haptic driver by using force feedback framework.
Signed-off-by: Hyunhee Kim
Sign
Thanks, Seth
On Thu, Oct 10, 2013 at 10:26 AM, Seth Jennings
wrote:
> On Thu, Oct 10, 2013 at 09:29:07AM +0800, Bob Liu wrote:
>> On 10/09/2013 10:40 PM, Seth Jennings wrote:
>> >
>> > The reason we never noticed this for zswap is that zswap has no
>> > dynamically allocated per-type resources.
On Thu, Oct 10 2013, Kent Overstreet wrote:
> Linus, please apply - the last fix in the bugfix series I sent you had an
> embarassing screwup...
>
> For 3.13, shall I start sending you pull requests directly?
Sorry I dropped the ball on that one, it's the first time ever I've
missed a deadline. I
From: Hyunhee Kim
Date: Wed, 9 Oct 2013 16:21:36 +0900
Subject: [PATCH] Input: add regulator haptic driver
The regulator haptic driver function can be used to control motor by on/off
regulator.
User can control the haptic driver by using force feedback framework.
Signed-off-by: Hyunhee Kim
Sign
Hi Jin,
On 10/11/2013 07:54 AM, Jin Xu wrote:
>> Date: Thu, 10 Oct 2013 16:11:53 +0800
>> From: guz.f...@cn.fujitsu.com
>> To: jinuxst...@live.com
>> CC: yuan.mark.zh...@samsung.com; jaegeuk@samsung.com;
>> linux-f2fs-de...@lists.sourceforge.net; linux-kernel@vger.kernel.org;
>> linux-fsde..
Joe Perches writes:
> Some setuid binaries will allow reading of files which have read
> permission by the real user id. This is problematic with files which
> use %pK because the file access permission is checked at open() time,
> but the kptr_restrict setting is checked at read() time. If a set
On Thu, 2013-10-10 at 17:22 -0600, David Ahern wrote:
> Running 3.12-rc3 just hit BUG in autofs4_expire_wait
It doesn't look like this could be due to Al's change to the locking in
autos4_wait() and that the only change to autofs that I'm aware of.
Could you do a bisect please?
>
> [787422.0654
Signed-off-by: Jingchang Lu
---
arch/arm/boot/dts/vf610.dtsi | 49 +
include/dt-bindings/dma/vf610-edma.h | 103 +++
2 files changed, 152 insertions(+)
create mode 100644 include/dt-bindings/dma/vf610-edma.h
diff --git a/arch/arm/boot/dts
Signed-off-by: Jingchang Lu
---
arch/arm/mach-imx/clk-vf610.c | 5 +
include/dt-bindings/clock/vf610-clock.h | 6 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/clk-vf610.c b/arch/arm/mach-imx/clk-vf610.c
index b169a39..29f88a2 100644
--- a/a
On Thu, Oct 10, 2013 at 09:21:36PM +0200, Arokux X wrote:
> Hi,
>
> recently I have been working on mainlining a simple bus glue driver
> for the USB EHCI for the Allwinner family of the ARM SoCs aka sunxi.
> The patches are almost ready and can be found at [1] and will be
> submitted once complet
From: Lan Tianyu
SBS's proc directory isn't useded and so remove it. Prepare for removing
/proc/acpi directory.
Signed-off-by: Lan Tianyu
---
drivers/acpi/sbs.c | 325 +
1 file changed, 4 insertions(+), 321 deletions(-)
diff --git a/drivers/
From: Lan Tianyu
There is no user of cm_sbs.c and CONFIG_ACPI_PROCFS_POWER. So remove
them. Prepare for removing /proc/acpi
Signed-off-by: Lan Tianyu
---
drivers/acpi/Kconfig | 17
drivers/acpi/Makefile | 1 -
drivers/acpi/cm_sbs.c | 105 ---
From: Lan Tianyu
Alarm proc file provides the info and control of RTC-CMOS alarm and
RTC CMOS driver provides wakealarm sysfs attribute for the same
purpose. The alarm file isn't compiled into kernel when RTC CMOS
driver is selected. The driver is default to be selected for x86
platform. So alarm
From: Lan Tianyu
The battery's proc directory isn't useded and remove it.
Signed-off-by: Lan Tianyu
---
drivers/acpi/battery.c | 328 +
1 file changed, 1 insertion(+), 327 deletions(-)
diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
1 - 100 of 802 matches
Mail list logo
