On Fri, Oct 11, 2013 at 09:37:45AM +0200, Boris BREZILLON wrote:
> This patch moves at91_pmc.h header from machine specific directory
> (arch/arm/mach-at91/include/mach/at91_pmc.h) to clk include directory
> (include/linux/clk/at91_pmc.h).
> We need this to avoid reference to machine specific
On 10/10/2013 03:55 PM, Mark Brown wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131010 tag is also provided for convenience.
There were a few new conflicts which have been
On Fri, Oct 11, 2013 at 02:32:45AM -0400, Chen, Gong wrote:
> 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
* Linus Walleij [131011 09:05]:
> On Fri, Oct 11, 2013 at 5:43 PM, Tony Lindgren wrote:
> > * Linus Walleij [131011 03:40]:
> >> On Fri, Oct 11, 2013 at 10:56 AM, Roger Quadros wrote:
> >>
> >> > The register handling is fine. But how do we deal with resource handling?
> >> > e.g. the block
On Fri, Oct 11, 2013 at 09:26:27AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney wrote:
>
> > > So, I think this code lives within kernel/params.c. Might be fixable?
> >
> > But of course! I was just trying to be lazy. ;-)
> >
> > I could imagine adding a filename field to struct
Hi,
On Friday, October 11, 2013 11:10:38 AM Eduardo Valentin wrote:
> Hi Naveen,
>
> On 09-10-2013 10:03, Bartlomiej Zolnierkiewicz wrote:
> >
> > Hi,
> >
> > All patches (#1-#3) look good to me, FWIW you can add:
> >
> > Reviewed-by: Bartlomiej Zolnierkiewicz
> >
> > Please note that
On Fri, Oct 11, 2013 at 5:43 PM, Tony Lindgren wrote:
> * Linus Walleij [131011 03:40]:
>> On Fri, Oct 11, 2013 at 10:56 AM, Roger Quadros wrote:
>>
>> > The register handling is fine. But how do we deal with resource handling?
>> > e.g. the block that has the deep-core registers might need to
On Fri, Oct 11, 2013 at 03:36:25PM +0900, Yasuaki Ishimatsu wrote:
> 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
On Fri, Oct 11, 2013 at 4:59 PM, Prabhakar Lad
wrote:
> On 10/11/13, Linus Walleij wrote:
>> On Fri, Oct 4, 2013 at 6:03 PM, Prabhakar Lad
>> wrote:
>>> +- ti,davinci-gpio-irq-base: Base from where GPIO interrupt numbering
>>> starts.
>>
>> What is this?
>>
>> If I have ever ACKed this I have
Karel,
On Fri, Oct 11, 2013 at 2:51 AM, Karel Zak wrote:
> On Thu, Oct 10, 2013 at 04:28:22PM -0700, Doug Anderson wrote:
>> + *
>> + * Consider a bad value here to be a warning to support dd-ing
>> + * an image from a smaller disk to a bigger disk.
>>*/
>> if (ret
In vfio_iommu_type1.c there is a bug in vfio_dma_do_map, when checking
that pages are not already mapped. Since the check is being done in a
for loop nested within the main loop, breaking out of it does not create
the intended behavior. If the underlying IOMMU driver returns a non-NULL
value, this
On Fri, Oct 11, 2013 at 02:32:44AM -0400, Chen, Gong wrote:
> 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,
On Fri, Oct 11, 2013 at 11:44:50AM -0400, Vivek Goyal wrote:
> Just Curious. How is it useful. IOW, what's your use case of booting a new
> kernel and then jumping back.
I'm kexecing into a kernel with a modified /dev/mem, modifying the
original kernel and then jumping back into it.
--
In (27a7c64 partitions/efi: account for pmbr size in lba) we started
treating bad sizes in lba field of the partition that has the 0xEE
(GPT protective) as errors. However, we may run into these "bad
sizes" in the real world if someone uses dd to copy an image from a
smaller disk to a bigger
* Balaji T K [131011 08:51]:
> On Friday 11 October 2013 09:06 PM, Tony Lindgren wrote:
> >>>What the pin control driver should do is control the pins. Whether the
> >>>registers
> >>>are spread out in the entire IO-memory does not matter. We did have one
> >>>system
> >>>which placed the
On Fri, Oct 11, 2013 at 11:06:30AM +0200, Borislav Petkov wrote:
> > - printk("%s""APEI generic hardware error status\n", pfx);
> > + printk("%s""Generic Hardware Error Status\n", pfx);
>
> Btw, what's the story with printk not using KERN_x levels in this file?
> Why are we falling back to
Davidlohr,
On Thu, Oct 10, 2013 at 5:31 PM, Davidlohr Bueso wrote:
> On Thu, 2013-10-10 at 16:28 -0700, Doug Anderson wrote:
>> In (27a7c64 partitions/efi: account for pmbr size in lba) we started
>> treating bad sizes in lba field of the partition that has the 0xEE
>> (GPT protective) as
On Fri, Oct 11, 2013 at 04:37:27PM +0100, Matthew Garrett wrote:
> On Fri, Oct 11, 2013 at 08:52:06AM -0400, Vivek Goyal wrote:
> > On Fri, Oct 11, 2013 at 01:04:55PM +0200, Daniel Kiper wrote:
> >
> > [..]
> > > > In theory you can swap between to kernels with the preserve_context
> > > > case.
On Fri, Oct 11, 2013 at 4:53 PM, Jonas Jensen wrote:
> I agree it is a bit strange GPIO control is divided in two
> separate registers. Unfortunately I can't offer an explanation
> because the documentation is not publicly available.
>
> The register responsible for doing
On Friday 11 October 2013 09:06 PM, Tony Lindgren wrote:
What the pin control driver should do is control the pins. Whether the registers
are spread out in the entire IO-memory does not matter. We did have one system
which placed the IO-muxing together with each peripheral (!) and I did
still
* Linus Walleij [131011 03:40]:
> On Fri, Oct 11, 2013 at 10:56 AM, Roger Quadros wrote:
>
> > The register handling is fine. But how do we deal with resource handling?
> > e.g. the block that has the deep-core registers might need to be clocked or
> > powered
> > before the registers can be
On Fri, Oct 11, 2013 at 02:32:43AM -0400, Chen, Gong wrote:
> 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.
>
>
On Fri, Oct 11, 2013 at 02:32:42AM -0400, Chen, Gong wrote:
> 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
Reviewed-by: Borislav Petkov
Just a question below:
> ---
>
The kernel has a few events with a format similar to this excerpt:
field:unsigned int len; offset:12; size:4; signed:0;
field:__data_loc unsigned char[] data_array; offset:16; size:4;
signed:0;
print fmt: "%s", __print_hex(__get_dynamic_array(data_array), REC->len)
On Fri, 11 Oct 2013, Matias Bjorling wrote:
The doorbell code is repeated various places. Refactor it into its own function
for clarity.
Signed-off-by: Matias Bjorling
Looks good to me.
Reviewed-by: Keith Busch
---
drivers/block/nvme-core.c | 29 +
1 file
On Fri, Oct 11, 2013 at 08:52:06AM -0400, Vivek Goyal wrote:
> On Fri, Oct 11, 2013 at 01:04:55PM +0200, Daniel Kiper wrote:
>
> [..]
> > > In theory you can swap between to kernels with the preserve_context
> > > case. Technically I like the ability but I don't know that it has ever
> > >
* Roger Quadros [131011 02:04]:
> On 10/11/2013 11:00 AM, Linus Walleij wrote:
> > On Thu, Oct 10, 2013 at 6:20 PM, Tony Lindgren wrote:
> >> * Linus Walleij [131010 09:19]:
> >>> On Thu, Oct 10, 2013 at 6:00 PM, Tony Lindgren wrote:
> * Roger Quadros [131010 06:32]:
> >
> > I
On Fri, Oct 11, 2013 at 10:58:18AM +0800, ethan.zhao wrote:
> From: "ethan.zhao"
>
> While loading ixgbevf driver,every vf detected will be output as the
> same name 'eth4':
>
> ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver -
> version 2.8.7
> Copyright (c)
> > At LSF this year, there was a discussion about the "wishlist" for
> > userland file servers. One of the things brought up was the goofy and
> > problematic behavior of POSIX locks when a file is closed. Boaz
> > started a thread on it here:
> >
> >
On Fri, Oct 11, 2013 at 02:54:13PM +, Luck, Tony wrote:
> It's such a simple goal - I can't believe it took this long to get
> here :-)
Right, I'd guess some standard's body needed to be persuaded :-)
> > Btw, what's "Memriser1"?
>
> Each memory controller on this machine routes to a
The patch description doesn't match what the patch does. We do not normally
have the asm file include the linux file, which is what the patch seems to do.
Matt Fleming wrote:
>From: Matt Fleming
>
>Every file that includes asm/efi.h also includes linux/efi.h. Just
>include linux/efi.h
On Fri, Oct 11, 2013 at 02:32:41AM -0400, Chen, Gong wrote:
> 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
>
On 10/11/13 9:11 AM, David Ahern wrote:
It would be nice to fix the callchain arg handler to not attempt to
process the next argument if it is not fp or dwarf.
Specifically, something like this which maintains syntax and default fp
option:
diff --git a/tools/perf/builtin-record.c
This adds a driver for hardware random number generator present
on Qualcomm MSM SoC's.
Signed-off-by: Stanimir Varbanov
---
drivers/char/hw_random/Kconfig | 12 +++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/msm-rng.c | 195 +++
3
Hello,
On Thu 10-10-13 23:23:11, Péter András Felvégi wrote:
> recently I made the mistake trying to mount an unformatted ssd
> partition. The mount command 'hang', was unable to kill it. Top showed
> the process is in the uninterruptible D state. However, iotop showed
> slight activity, about
This adds Qualcomm PRNG driver device tree binding documentation
to use as an example in dts trees.
Signed-off-by: Stanimir Varbanov
---
Documentation/devicetree/bindings/rng/qcom,prng.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
Here is the second version of RNG driver for MSM SoC's.
During the time since first version I've made some tests using
rng tools this is the result:
# cat /dev/hw_random | rngtest -c 10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying
* Roger Quadros [131011 07:07]:
> On 10/11/2013 11:49 AM, Roger Quadros wrote:
> > On 10/10/2013 07:00 PM, Tony Lindgren wrote:
> >>
> >> Well the irq_set_wake() should only be needed for suspend and resume. For
> >> runtime PM
> >> the wake-events should be always enabled by default as pointed
"Linuxppc-dev"
wrote on 2013/10/11 14:56:40:
>
> Activating CONFIG_PIN_TLB allows access to the 24 first Mbytes of memory
at
> bootup instead of 8. It is needed for "big" kernels for instance when
activating
> CONFIG_LOCKDEP_SUPPORT. This needs to be taken into account in init_32
too,
>
On 10/11/13 1:34 AM, Jiri Olsa wrote:
'-g' takes optional parameter, so having it in front of
non option string is causing the error, you could use:
./perf record -g -- ~/hackbench 10
maybe we could display just only help string of the option
we failed to process in this case
That's a syntax
Hi Naveen,
On 09-10-2013 10:03, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> All patches (#1-#3) look good to me, FWIW you can add:
>
> Reviewed-by: Bartlomiej Zolnierkiewicz
>
> Please note that (at least) patch #3 conflicts with Lukasz's EXYNOS4412
> fixup patchset:
>
>
Hi,
On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
> Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
> power_on and power_off the following APIs are used phy_init(), phy_exit(),
> phy_power_on() and phy_power_off().
>
> However using the old USB phy library wont be
On Fri, Oct 11, 2013 at 7:01 AM, Steven Rostedt wrote:
> On Fri, 11 Oct 2013 13:13:47 +0200
> "Rafael J. Wysocki" wrote:
>>
>> From: Rafael J. Wysocki
>> Subject: ACPI / hotplug / PCI: Accept coexistence with native PCIe hotplug
>>
>> Allow ACPIPHP (ACPI-based PCI hotplug) to handle event
On 09/16/2013 10:37 AM, Roger Quadros wrote:
> On 09/16/2013 06:01 AM, Kishon Vijay Abraham I wrote:
>> On Thursday 12 September 2013 04:49 PM, Roger Quadros wrote:
>>> Hi Kishon,
>>>
>>> On 09/02/2013 06:43 PM, Kishon Vijay Abraham I wrote:
Adapted omap-usb3 PHY driver to Generic PHY
On Thu, Oct 10, 2013 at 06:50:27PM +0100, Oussama Ghorbel wrote:
> The ip6_tnl.hlen (gre and ipv6 headers length) is independent from the
> outgoing interface, so it would be better to initialize it even when no
> route is found, otherwise its value will be zero.
> While I'm not sure if this could
Hi Linus ,
On 10/11/13, Linus Walleij wrote:
> On Fri, Oct 4, 2013 at 6:03 PM, Prabhakar Lad
> wrote:
>
>> This patch adds OF parser support for davinci gpio
>> driver and also appropriate documentation in gpio-davinci.txt
>> located at Documentation/devicetree/bindings/gpio/.
>>
>>
>> [56005.785981] {3}physical_address: 0x000851fe
>> [56005.786027] {3}DIMM location: Memriser1 CHANNEL A DIMM 0
>
> Very good guys, I've been waiting for years for this to be possible,
> good job! :-)
It's such a simple goal - I can't believe it took this long to get here :-)
> Btw,
Add GPIO driver for MOXA ART SoCs.
Signed-off-by: Jonas Jensen
---
Notes:
Thanks for the replies,
I agree it is a bit strange GPIO control is divided in two
separate registers. Unfortunately I can't offer an explanation
because the documentation is not publicly available.
New API regmap_multi_reg_write() is defined that allows a set of reg,val
pairs to be written to a I2C client device as one block transfer from the
point of view of a single I2C master system.
A simple demonstration implementation is included that just splits the
block write request into a
Hi,
On 10/10/2013 01:49 PM, Kishon Vijay Abraham I wrote:
> From: George Cherian
>
> Added dr_mode property in dwc3 and set its default mode to device.
If there is a specific reason why this is not set to "otg", we need
to explain it here.
AFAIK the port is meant to be used as OTG port.
>
>
Hello,
running X86-64 on Intel motherboard DL87-RH with Opensuse-12.3 results in
lots of messages like
kernel: [ 459.263752] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
kernel: [ 459.263753] EDD information not available.
...
until I rename edd.ko. This happens still with "kernel of
On Fri, 11 Oct 2013 15:30:22 +0200
Sebastian Andrzej Siewior wrote:
> On 10/11/2013 02:37 PM, Steven Rostedt wrote:
> > On Fri, 11 Oct 2013 12:18:00 +0200
> > Sebastian Andrzej Siewior wrote:
> >
> >> * Mario Kleiner | 2013-09-26 18:16:47 [+0200]:
> >>
> >>> Good! I will do that. Thanks for
From: Matt Fleming
Every file that includes asm/efi.h also includes linux/efi.h. Just
include linux/efi.h directly and avoid the duplication.
Cc: H. Peter Anvin
Cc: Thomas Gleixner
Suggested-by: Ingo Molnar
Signed-off-by: Matt Fleming
---
arch/x86/boot/compressed/eboot.c | 1 -
From: Matt Fleming
It's incredibly difficult to diagnose early EFI boot issues without
special hardware because earlyprintk=vga doesn't work on EFI systems.
Add support for writing to the EFI framebuffer, via earlyprintk=efi,
which will actually give users a chance of providing debug output.
From: Matt Fleming
These two patches cleanup the #include duplication and add
support for earlyprintk=efi, which is the only way users can debug early
boot crashes without special hardware.
Matt Fleming (2):
x86/efi: Include linux/efi.h in asm/efi.h
x86/efi: Add EFI framebuffer earlyprintk
усиляет обмен веществ http://tiny.pl/qxwzs
On 10/10/2013 10:11 PM, Shaohua Li wrote:
>
> If a tag is freed, the request might be used very soon. There is a short
> window
> rq->q is null, so cache it.
Thanks, good catch! Applied.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On 10/11/2013 01:18 AM, Shaohua Li wrote:
> Using percpu-ida to manage blk-mq tags. the percpu-ida has similar algorithm
> like the blk-mq-tag. The difference is when a cpu can't allocate tags
> blk-mq-tag uses ipi to purge remote cpu cache and percpu-ida directly purges
> remote cpu cache. In
On 10/11/2013 10:23 AM, Naveen Krishna Chatradhi wrote:
> This patch does the following
> 1. use wait_for_completion_timeout instead of
>wait_for_completion_interruptible_timeout
> 2. Reset software if a timeout happens.
> 3. Also reduce the timeout to 100milli secs
It is always good to have
On 10/10/2013 10:14 PM, Shaohua Li wrote:
> the capacity calculation is obvious buggy.
Thanks, applied.
--
Jens Axboe
--
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 Fri, Oct 4, 2013 at 7:59 PM, Alexandre Courbot wrote:
> Patch be1a4b brought some improvements to the GPIO error handling code,
> but also changed the return value of gpiod_request() when called on a
> not yet initialized GPIO descriptor: it now returns -EINVAL instead of
> -EPROBE_DEFER, and
On Fri, Oct 4, 2013 at 7:59 PM, Alexandre Courbot wrote:
> The current implementation of desc_to_gpio() relies on the chip pointer
> to be set to a valid value in order to compute the GPIO number. This
> was done in the hope that we can get rid of the gpio_desc global array,
> but this is not
On 10/11/2013 06:19 AM, Christoph Hellwig wrote:
> On Thu, Oct 10, 2013 at 09:32:41PM +0200, Alexander Gordeev wrote:
>> I wonder, if blk-mq- prefix should remain?.. This s code seems pretty much
>> generic to me.
>
> Seems like nowdays you should just use the percpu-ida allocator directly,
>
On Fri, Oct 4, 2013 at 10:01 PM, David Cohen
wrote:
> After file was renamed from gpio-langwell to gpio-intel-mid, this patch
> updates the variables, functions and structs to be based on intel-mid
> instead of langwell.
>
> There is no function change.
>
> Signed-off-by: David Cohen
Some call
kmemleak reports a leak after every mount-umount cycle:
unreferenced object 0x88006b339150 (size 8):
comm "mount.nfs", pid 752, jiffies 4294802777 (age 1515.620s)
hex dump (first 8 bytes):
00 00 00 00 00 00 00 00
backtrace:
[]
On Fri, Oct 4, 2013 at 10:01 PM, David Cohen
wrote:
> gpio-langwell is a deprecated name. Despite the driver was made
> initially for Langwell, it supports now other Intel Mid SoC's.
>
> This patch does no change beside the file renaming with Kconfig/Makefile
> update.
>
> Signed-off-by: David
On Fri, Oct 4, 2013 at 10:01 PM, David Cohen
wrote:
> This patch implements a better way to handle multiple SoC's and adds
> Intel Merrifield support to gpio-langwell.
>
> It was based on previous work from Ning Li
>
> Signed-off-by: David Cohen
> Signed-off-by: Fei Yang
> Signed-off-by: Ning
On 10/11/2013 10:57 AM, Fengguang Wu wrote:
> On Fri, Oct 11, 2013 at 10:42:19AM +0200, Toralf Förster wrote:
>> yeah, now the picture becomes more clear
>> ...
>> net.core.warnings = 0
>> [ ok ]
>> ick: pause : -717
>>
On Fri, Oct 4, 2013 at 6:03 PM, Prabhakar Lad
wrote:
> This patch adds OF parser support for davinci gpio
> driver and also appropriate documentation in gpio-davinci.txt
> located at Documentation/devicetree/bindings/gpio/.
>
> Signed-off-by: KV Sujith
> Signed-off-by: Philip Avinash
>
On Thu, 10 Oct 2013 18:00:48 -0700
Linus Torvalds wrote:
> File a bug on Claws, and if the developers brush it off as your own
> problem, just stop using the PoS.
They acknowledge the bug - it was already known to them, actually. With
luck we'll see a fix soon.
jon
--
To unsubscribe from this
On Thu, 10 Oct 2013, Kirill A. Shutemov wrote:
> Christoph Lameter wrote:
> > On Thu, 10 Oct 2013, Kirill A. Shutemov wrote:
> >
> > > +static inline bool ptlock_alloc(struct page *page)
> > > +{
> > > + if (sizeof(spinlock_t) > sizeof(page->ptl))
> > > + return __ptlock_alloc(page);
> >
On Fri, Oct 11, 2013 at 02:46:10PM +0300, Ivan T. Ivanov wrote:
From: "Ivan T. Ivanov"
Allows MSM EHCI controller to be specified via device tree.
Signed-off-by: Ivan T. Ivanov
---
.../devicetree/bindings/usb/msm-hsusb.txt | 17 +
drivers/usb/host/ehci-msm.c
On Fri, Oct 11, 2013 at 02:46:09PM +0300, Ivan T. Ivanov wrote:
From: "Ivan T. Ivanov"
Use struct usb_hcd::phy to hold USB PHY instance.
Signed-off-by: Ivan T. Ivanov
---
drivers/usb/host/ehci-msm.c |5 +++--
Acked-by: David Brown
--
sent by an employee of the Qualcomm Innovation
On Fri, 2013-10-11 at 22:47 +0900, Masami Hiramatsu wrote:
> (2013/10/11 9:48), Tom Zanussi wrote:
> > /**
> > + * tracing_alloc_snapshot - allocate snapshot buffer.
> > + *
> > + * This only allocates the snapshot buffer if it isn't already
> > + * allocated - it doesn't also take a snapshot.
>
On Mon, Sep 30, 2013 at 7:29 PM, Darren Hart wrote:
> I'm currently working with a graphics driver that makes use of 2 GPIO
> pins for EDID communication (clock and data). In order to coexist
> peacefully with the driver for the GPIO chip, it must use gpiolib to
> request the lines, set
On Thu, 10 Oct, at 07:28:44PM, Ingo Molnar wrote:
> Btw., could we perhaps remap the whole framebuffer at init time, or is it
> too large? If early_ioremap() fails for whatever reason then that will
> emit a WARN_ON(), which will recurse in a fairly nasty way ...
The framebuffer memory will be
On 10/11/2013 11:49 AM, Roger Quadros wrote:
> On 10/10/2013 07:00 PM, Tony Lindgren wrote:
>> * Roger Quadros [131010 06:32]:
>>>
>>> I tried testing this with the USB EHCI driver, but I'm not getting wake up
>>> interrupts
>>> while the system is still running and only the EHCI controller is
> The problem is that the scheduler doesn't see that the current task has
> preemption disabled. It only looks at the priorities of the current
> task, and if it can preempt it, it will. It sets the NEED_RESCHED to the
> current task and waits for the preemption to schedule it out.
Ah, got it.
On 10/11/2013 03:30 PM, Sebastian Andrzej Siewior wrote:
On 10/11/2013 02:37 PM, Steven Rostedt wrote:
On Fri, 11 Oct 2013 12:18:00 +0200
Sebastian Andrzej Siewior wrote:
* Mario Kleiner | 2013-09-26 18:16:47 [+0200]:
Good! I will do that. Thanks for clarifying the irq and constraints
on
On 10/10/2013 11:31 AM, Felipe Balbi wrote:
Hi,
On Mon, Oct 07, 2013 at 06:12:30AM -0400, Matt Porter wrote:
Broadcom BCM281xx parts have a PHY control block that
operates in conjunction with the DWC2 USB OTG. This driver
exposes an API that allows control of power/reset for a
connected USB
(2013/10/11 9:48), Tom Zanussi wrote:
> /**
> + * tracing_alloc_snapshot - allocate snapshot buffer.
> + *
> + * This only allocates the snapshot buffer if it isn't already
> + * allocated - it doesn't also take a snapshot.
> + *
> + * This is meant to be used in cases where the snapshot buffer
Matt,
The kernel I referring is the boot kernel aka the 1st kernel,
the boot loader is grub2 from Fedora 19.
[sorry for top reply because of using webmail]
- Original Message -
From: "Matt Fleming"
To: "Dave Young"
Cc: "Borislav Petkov" , "X86 ML" , "LKML"
, "Borislav Petkov" ,
Em Wed, Oct 09, 2013 at 03:01:13PM +0300, Adrian Hunter escreveu:
> Add a function to find a symbol using an ip that
> might be on a different map.
>
> Signed-off-by: Adrian Hunter
Can you take a look at the following patch? Since we have an
addr_map_symbol struct and the method looks more
Hi,
On Fri, Oct 11, 2013 at 08:23:35AM +0200, Robert Baldyga wrote:
> 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,
> >>
Hi,
On Thu, Oct 10, 2013 at 11:21:30PM -0400, Matt Porter wrote:
> 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
Vážení E-mail užívateľa;
Prekročili ste 23432 boxy nastaviť svoje
Webová služba / Administrátor, a budete mať problémy pri odosielaní a
prijímať e-maily, kým znova overiť. Musíte aktualizovať kliknutím na
odkaz nižšie a vyplňte údaje pre overenie vášho účtu
Prosím,kliknite: na odkaz nižšie
On Fri, 11 Oct 2013 08:25:17 -0400
Jeff Layton wrote:
> At LSF this year, there was a discussion about the "wishlist" for
> userland file servers. One of the things brought up was the goofy and
> problematic behavior of POSIX locks when a file is closed. Boaz started
> a thread on it here:
>
>
On Fri, Oct 11, 2013 at 05:42:17PM -0400, Youquan Song wrote:
> Currently, the DMA channel calculates its data transferred only at network
> device driver. When other devices like UART or SPI etc, transfers data by DMA
> mode, but it always shows 0 at /sys/class/dma/dma0chan*/bytes_transferred.
On Fri, Oct 11, 2013 at 05:42:18PM -0400, Youquan Song wrote:
> When using UART transfers data by DMA mode, but it always shows 0 at
> /sys/class/dma/dma0chan*/bytes_transferred.
>
> Call the new function to calculate how many the data has been transferred
> after doing it by DMA mode.
How
On Fri, 2013-10-11 at 22:00 +0900, Masami Hiramatsu wrote:
> (2013/10/11 9:48), Tom Zanussi wrote:
> > If CONFIG_STACKTRACE is turned off, trace_dump_stack() isn't defined,
> > resulting in an 'undefined reference' error - define a stub to remedy
> > that.
> >
> > Signed-off-by: Tom Zanussi
>
>
On 10/11/2013 02:37 PM, Steven Rostedt wrote:
> On Fri, 11 Oct 2013 12:18:00 +0200
> Sebastian Andrzej Siewior wrote:
>
>> * Mario Kleiner | 2013-09-26 18:16:47 [+0200]:
>>
>>> Good! I will do that. Thanks for clarifying the irq and constraints
>>> on raw locks in the other thread.
>>
>> Are
On Fri, 2013-10-11 at 21:50 +0900, Masami Hiramatsu wrote:
> (2013/10/11 9:48), Tom Zanussi wrote:
> > The names of the functions are tracing_snapshot_*, not
> > trace_snapshot_* - fix up the kerneldoc to avoid confusion.
> >
> > Signed-off-by: Tom Zanussi
>
> It seems that this is not related
On 10/11/13 3:55 AM, Ian Kent wrote:
On Fri, 2013-10-11 at 10:06 +0800, Ian Kent wrote:
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 tpacpi_acpi_handle_locate function makes use of acpi_get_devices to
locate handle for ACPI video by HID, the problem is, ACPI video node
doesn't really have HID defined(i.e. no _HID control method is defined
for video device), so.. that function would fail. This can be solved by
enhancing the
According to Matthew Garrett, "Windows 8 leaves backlight control up
to individual graphics drivers rather than making ACPI calls itself.
There's plenty of evidence to suggest that the Intel driver for
Windows [8] doesn't use the ACPI interface, including the fact that
it's broken on a bunch of
The backlight control and event delivery functionality provided by ACPI
video module is mixed together and registered all during video device
enumeration time. As a result, the two functionality are also removed
together on module unload time or by the acpi_video_unregister function.
The two
v5:
1 Introduce video.use_native_backlight module parameter and set its
value to false by default as suggested by Rafael. For Win8 systems
which have broken ACPI video backlight control, the parameter can be
set to 1 in kernel cmdline to skip registering ACPI video's backlight
interface.
Introduce a new API for modules to query if a specific type of backlight
device has been registered. This is useful for some backlight device
provider module(e.g. ACPI video) to know if a native control
interface(e.g. the interface created by i915) is available and then do
things accordingly(e.g.
The return value of arm_smmu_iova_to_phys is directly passed to the
user of the IOMMU API via iommu_iova_to_phys; however the ARM SMMU
driver returns -EINVAL on error, which is not consistent with the
rest of the drivers implementing the IOMMU API. VFIO also relies on
the call returning NULL when
IOMMU groups are expected by certain users of the IOMMU API,
e.g. VFIO. Add new devices found by the SMMU driver to an IOMMU
group to satisfy those users.
Signed-off-by: Antonios Motakis
---
drivers/iommu/arm-smmu.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff
601 - 700 of 2146 matches
Mail list logo
