Even if I am right the problem is really minor, the patch should
be ignored without the authoritative acks.
I am only sending it because I am curious, and I would like to ask
another question about audit.
search_binary_handler()->audit_bprm(bprm) looks a bit strange, and
I can't understand if
Hi Jan,
On Wed, 2013-08-07 at 17:20 +0200, Jan Kara wrote:
> On Thu 01-08-13 20:58:46, Davidlohr Bueso wrote:
> > On Thu, 2013-08-01 at 22:33 +0200, Jan Kara wrote:
> > > Hi,
> > >
> > > On Thu 01-08-13 13:14:19, Davidlohr Bueso wrote:
> > > > FYI I'm seeing loads of the following messages
On 7/29/2013 4:39 PM, Bjorn Andersson wrote:
On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh wrote:
Add a new device tree enabled pinctrl driver for
Qualcomm MSM SoC's. This driver provides an extensible
framework to interface all MSM's that use a TLMM pinmux,
with the pinctrl subsytem.
On 7 August 2013 23:13, Stephen Warren wrote:
> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>> cpufreq-cpu0 driver is dependent on OPP library and hence we need to enable
>> it
>> for Tegra as we are going to use cpufreq-cpu0.
>
> Shouldn't these be selected by something in
On Tue, Aug 06, 2013 at 08:45:12PM -0700, Roy Franz wrote:
> This patch adds EFI stub support for the ARM Linux kernel. The EFI stub
> operations similarly to the x86 stub: it is a shim between the EFI firmware
> and the normal zImage entry point, and sets up the environment that the
> zImage is
On 7 August 2013 23:12, Stephen Warren wrote:
> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>> cpufreq-cpu0 driver needs OPPs to be present in DT which can be probed by it
>> to
>> get frequency table. This patch adds OPPs and clock-latency to tegra cpu0
>> node
>> for multiple SoCs.
>>
>>
On Wed, Aug 7, 2013 at 10:40 AM, Dave Hansen wrote:
> On 08/07/2013 06:40 AM, Jan Kara wrote:
>> One question before I look at the patches: Why don't you use fallocate()
>> in your application? The functionality you require seems to be pretty
>> similar to it - writing to an already allocated
On 7 August 2013 23:23, Stephen Warren wrote:
> That link only describes why we shouldn't have a dedicated compatible
> value for cpufreq. I certainly agree with that. However, I think it's
> reasonable that whatever code binds to:
>
> compatible = "arm,cortex-a9";
>
> ... should
On Wed, 2013-08-07 at 13:36 -0400, Steven Rostedt wrote:
> plain text document attachment
> (0002-x86-jump-labels-Use-etiher-5-byte-or-2-byte-jumps.patch)
> From: Steven Rostedt
>
> Have the jump labels add a "jmp" in the assembly instead
> of a default nop. This will cause the assembler to put
On Wed, Aug 7, 2013 at 1:33 PM, Tom Cooksey wrote:
>
>> >> > Didn't you say that programmatically describing device placement
>> >> > constraints was an unbounded problem? I guess we would have to
>> >> > accept that it's not possible to describe all possible constraints
>> >> > and instead find
On Wed, 7 Aug 2013, Kent Overstreet wrote:
> +{
> + DEFINE_WAIT(wait);
> + struct percpu_ida_cpu *tags;
> + unsigned long flags;
> + unsigned this_cpu;
> + int tag;
> +
> + local_irq_save(flags);
> + this_cpu = smp_processor_id();
> + tags =
On 7 August 2013 23:18, Stephen Warren wrote:
> On 08/07/2013 11:45 AM, Viresh Kumar wrote:
>> On 7 August 2013 23:08, Stephen Warren wrote:
>>> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
This patch adds CPU0's clk driver for Tegra. It will be used by the generic
cpufreq-cpu0 driver
On Wed, 2013-08-07 at 13:36 -0400, Steven Rostedt wrote:
> As I said, I would post the patches that let the jmps used by jump labels
> be turn to 2 bytes where possible. These are a bit controversial due
> to the complexity of the update_jump_label code.
>
> These patches are based off of tip's
On 08/07/2013 11:49 AM, Viresh Kumar wrote:
> On 7 August 2013 23:16, Stephen Warren wrote:
>> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>>> cpufreq-cpu0 driver can be probed over DT only if a corresponding device
>>> node is
>>> created for the SoC which wants to use it. Lets create a
On 08/07/2013 10:46 AM, Steven Rostedt wrote:
> On Wed, 2013-08-07 at 19:37 +0200, Borislav Petkov wrote:
>> On Wed, Aug 07, 2013 at 01:33:06PM -0400, Steven Rostedt wrote:
>>> Right, and this code keeps the same logic as it was before. If it was
>>> disabled by CONFIG_EXPERT, it stays disabled,
On Tue, Aug 6, 2013 at 5:00 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> In theory, under a given ACPI namespace node there should be only
> one child device object with _ADR whose value matches a given bus
> address exactly. In practice, however, there are systems in which
>
On 7 August 2013 23:16, Stephen Warren wrote:
> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>> cpufreq-cpu0 driver can be probed over DT only if a corresponding device
>> node is
>> created for the SoC which wants to use it. Lets create a platform device for
>> cpufreq-cpu0 driver for Tegra.
>>
On 08/07/2013 11:45 AM, Viresh Kumar wrote:
> On 7 August 2013 23:08, Stephen Warren wrote:
>> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>>> This patch adds CPU0's clk driver for Tegra. It will be used by the generic
>>> cpufreq-cpu0 driver to get/set cpu clk.
>>>
>>> Most of the platform
On 08/07/13 17:19, Borislav Petkov wrote:
> On Tue, Aug 06, 2013 at 05:31:29PM +0200, Laszlo Ersek wrote:
>> Can you capture the OVMF debug output? Do you see
>>
>> ConvertPages: Incompatible memory types
>>
>> there?
>>
>> Can you set the following bits too in the debug mask?
>>
>> #define
get() implies taking a ref or sometimes an allocation, which this
function definitely does not do - rename it to something more sensible.
Signed-off-by: Kent Overstreet
Cc: Andrew Morton
Cc: Tejun Heo
---
drivers/block/drbd/drbd_main.c | 2 +-
drivers/block/drbd/drbd_nl.c | 2 +-
The deprecated idr interfaces don't have any in kernel users, so let's
delete them as prep work for the idr rewrite.
Signed-off-by: Kent Overstreet
Cc: Andrew Morton
Cc: Tejun Heo
---
include/linux/idr.h | 63 -
lib/idr.c | 36
The old idr code was really a second radix tree implementation - we
already have one in lib/radix-tree.c.
This patch reimplements idr on top of our existing radix trees, using
our shiny new ida implementation for allocating/freeing the ids. The old
idr code was noticably slower than
On 08/07/2013 08:46 AM, Viresh Kumar wrote:
> cpufreq-cpu0 driver can be probed over DT only if a corresponding device node
> is
> created for the SoC which wants to use it. Lets create a platform device for
> cpufreq-cpu0 driver for Tegra.
>
> Also it removes the Kconfig entry responsible to
On Wed, 2013-08-07 at 19:37 +0200, Borislav Petkov wrote:
> On Wed, Aug 07, 2013 at 01:33:06PM -0400, Steven Rostedt wrote:
> > Right, and this code keeps the same logic as it was before. If it was
> > disabled by CONFIG_EXPERT, it stays disabled, but at least you get to
> > see a warning that
On 7 August 2013 23:08, Stephen Warren wrote:
> On 08/07/2013 08:46 AM, Viresh Kumar wrote:
>> This patch adds CPU0's clk driver for Tegra. It will be used by the generic
>> cpufreq-cpu0 driver to get/set cpu clk.
>>
>> Most of the platform specific bits are picked from tegra-cpufreq.c.
>
> Hmmm.
On 08/07/2013 08:46 AM, Viresh Kumar wrote:
> cpufreq-cpu0 driver is dependent on OPP library and hence we need to enable it
> for Tegra as we are going to use cpufreq-cpu0.
Shouldn't these be selected by something in drivers/cpufreq/Kconfig?
--
To unsubscribe from this list: send the line
On 08/07/2013 08:46 AM, Viresh Kumar wrote:
> cpufreq-cpu0 driver needs OPPs to be present in DT which can be probed by it
> to
> get frequency table. This patch adds OPPs and clock-latency to tegra cpu0 node
> for multiple SoCs.
>
> Voltage levels aren't used until now for tegra and so a flat
From: Eric Dumazet
Date: Wed, 07 Aug 2013 09:40:09 -0700
> On Wed, 2013-08-07 at 18:22 +0200, Johannes Berg wrote:
>
>> Maybe. I haven't tested it, but I'm thinking that skb->data doesn't
>> point to the start of the data frame in this case, since we now call
>> eth_type_trans() which pulls the
From: Steven Rostedt
Add the infrastructure to allow architectures to modify the jump label
locations at compile time. This is mainly for x86, where the jmps may
be either 2 bytes or 5 bytes. Instead of wasting 5 bytes for all jump labels,
this code will let x86 put in a jmp instead of a 5 byte
As I said, I would post the patches that let the jmps used by jump labels
be turn to 2 bytes where possible. These are a bit controversial due
to the complexity of the update_jump_label code.
These patches are based off of tip's x86/jumplabel code.
But if someone cares to play with it, feel
From: Steven Rostedt
Have the jump labels add a "jmp" in the assembly instead
of a default nop. This will cause the assembler to put in
either a 2 byte or 5 byte jmp depending on where the target
lable is.
Then at compile time, the update_jump_label code will replace
the jmps with either 2 or 5
On Wed, Aug 07, 2013 at 08:34:39AM +0200, Krzysztof Kozlowski wrote:
Fix compilation error in gpiomux (CONFIG_MSM_GPIOMUX=y):
arch/arm/mach-msm/gpiomux.c:24:13: error: static declaration of
‘__msm_gpiomux_write’ follows non-static declaration
arch/arm/mach-msm/gpiomux.h:85:6: note:
On 08/07/2013 06:40 AM, Jan Kara wrote:
> One question before I look at the patches: Why don't you use fallocate()
> in your application? The functionality you require seems to be pretty
> similar to it - writing to an already allocated block is usually quick.
One problem I've seen is that it
On 08/07/2013 08:46 AM, Viresh Kumar wrote:
> This patch adds CPU0's clk driver for Tegra. It will be used by the generic
> cpufreq-cpu0 driver to get/set cpu clk.
>
> Most of the platform specific bits are picked from tegra-cpufreq.c.
Hmmm. I'm not sure if it makes sense to represent this as a
On Wed, Aug 07, 2013 at 01:33:06PM -0400, Steven Rostedt wrote:
> Right, and this code keeps the same logic as it was before. If it was
> disabled by CONFIG_EXPERT, it stays disabled, but at least you get to
> see a warning that your kernel may be corrupt now :-)
Don't we really want to panic
Percpu frontend for allocating ids. With percpu allocation (that works),
it's impossible to guarantee it will always be possible to allocate all
nr_tags - typically, some will be stuck on a remote percpu freelist
where the current job can't get to them.
We do guarantee that it will always be
This is a new, from scratch implementation of ida that should be
simpler, faster and more space efficient.
Two primary reasons for the rewrite:
* A future patch will reimplement idr on top of this ida implementation +
radix trees. Once that's done, the end result will be ~1k fewer lines
of
Andrew - this should be pretty much identical to the patch series I
mailed out during last merge window, except rebased onto 3.11-rc4 and
retested.
I think the series should be more or less ready to go, and it'd be
really nice to get at least the percpu bits in - think you can have a
look and
On Wed, 2013-08-07 at 19:20 +0200, Borislav Petkov wrote:
>
> > +static void bug_at(unsigned char *ip, int line)
> > +{
> > + /*
> > +* The location is not an op that we were expecting.
> > +* Something went wrong. Crash the box, as something could be
> > +* corrupting the kernel.
On Wed 07-08-13 16:47:30, Michal Hocko wrote:
> On Wed 07-08-13 15:57:34, Michal Hocko wrote:
> [...]
> > Hmm, OK so you think that the fd limit is sufficient already?
>
> Hmm, that would need to touch the code as well (the register callback
> would need to make sure only one event is registered
Oh - one more thing - and my apologies for not spotting this before:
dst = allocate_buf_for_compression(big_buf_sz);
No - you may not call kmalloc() in oops/panic context. Please pre-allocate
everything you need in some initialization code to make sure that we don't
fail in the
Hello Thomas,
Sorry for the noise, this mail was filtered by LKML and LAKML beacause
thunderbird
added HTML contents.
On 07/08/2013 18:08, Thomas Petazzoni wrote:
Dear Boris BREZILLON,
On Wed, 7 Aug 2013 12:14:26 +0200, Boris BREZILLON wrote:
This patch splits the sam9x5 peripheral
On 08/07, Grazvydas Ignotas wrote:
>
> It's not that wine needs all this, it's the Windows games that use
> debug registers to store random values to them for their copy
> protection stuff.
Thanks.
> My wine commits try to sidestep these
> kernel restrictions/sanity checking.
My point was, it
On Wed, 7 August 2013 03:21:47 -0600, Andreas Dilger wrote:
>
> I'm not saying that a tool to check this would be a bad thing, but
> if the compression support is a generic feature of the VFS, then it
> makes sense that the checker can also be generic and unrelated to
> the filesystem metadata
On Aug 7, 2013, at 8:19 AM, Borislav Petkov wrote:
> On Tue, Aug 06, 2013 at 05:31:29PM +0200, Laszlo Ersek wrote:
>> Can you capture the OVMF debug output? Do you see
>>
>> ConvertPages: Incompatible memory types
>>
>> there?
>>
>> Can you set the following bits too in the debug mask?
>>
On Wed, Aug 07, 2013 at 12:49:38PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt
>
> When modifying text sections for jump labels, a paranoid check is
> performed. If the check fails, the system "bugs". But why it failed
> is not shown.
>
> The BUG_ON()s in the jump label update code is
On Wed, Aug 7, 2013 at 6:09 AM, Matt Fleming wrote:
> On Tue, 06 Aug, at 08:45:08PM, Roy Franz wrote:
>> The x86/AMD64 EFI stubs must us a call wrapper to convert between
>> the Linux and EFI ABIs, so void pointers are sufficient. For ARM,
>> the ABIs are compatible, so we can directly invoke
Quoting Yadwinder Singh Brar (2013-07-07 04:44:21)
> This patch adds clock to list of mfd cells for s2mps11 and DT documentation
> for clock part.
>
> Signed-off-by: Yadwinder Singh Brar
Reviewed-by: Mike Turquette
> ---
> Documentation/devicetree/bindings/mfd/s2mps11.txt | 20
kvp_daemon does some operations which take an unpredicable amount of
time. In addition the kernel driver gives the kvp_daemon a 5 second
timeout to respond to message from the host. If an operation such as
getaddrinfo takes a long time and the timeout triggers then netlink
errors occour. As a
[trimmed my old email]
On Wed, Aug 07, 2013 at 10:37:17AM +0300, Pantelis Antoniou wrote:
> Hi Greg,
>
> On Aug 7, 2013, at 8:56 AM, Greg Kroah-Hartman wrote:
>
> > On Tue, Aug 06, 2013 at 01:27:35PM +0300, Pantelis Antoniou wrote:
> >> Hi Greg,
> >>
> >> On Aug 6, 2013, at 1:15 PM, Greg
On Wed, Aug 7, 2013 at 6:09 AM, Matt Fleming wrote:
> On Tue, 06 Aug, at 08:45:00PM, Roy Franz wrote:
>> Rename them to be more similar, as low_free() could be used to free
>> memory allocated by both high_alloc() and low_alloc().
>> high_alloc() -> efi_high_alloc()
>> low_alloc() ->
>From 5b6fbb6496ddc4e428f5dd0950b0617faed6596b Mon Sep 17 00:00:00 2001
From: Paul McQuade
Date: Wed, 7 Aug 2013 16:21:16 +0100
Subject: [PATCH] Staging:BCM:DDRInit.c:Replacing __FUNCTION__
__func__ replaces __Function__.
Signed-off-by: Paul McQuade
---
drivers/staging/bcm/DDRInit.c | 58
On Wed, Aug 7, 2013 at 6:08 AM, Matt Fleming wrote:
> On Tue, 06 Aug, at 08:44:59PM, Roy Franz wrote:
>> Signed-off-by: Roy Franz
>> ---
>> arch/x86/boot/compressed/eboot.c | 38 +++--
>> drivers/firmware/efi/efi-stub-helper.c | 96
>> +---
>> 2
On 08/07/2013 10:23 AM, Linus Walleij wrote:
> On Wed, Jul 17, 2013 at 7:31 AM, Sonic Zhang wrote:
>
> I'd like Stephen and Axel to have a look at this as well...
>
>> From: Sonic Zhang
>>
>> in pinmux_disable_setting after current device fails to request
>> the same pins.
>>
>> Signed-off-by:
> This breaks compatibility, both for an old kernel and a new dt and a new
> kernel with an old dt. Is anyone using these bindings?
They only affect Samsung SoCs and have only been upstream for half a
year, so I doubt it's heavily used.
> Why are we describing fewer registers now? Are they
On Tue, Aug 6, 2013 at 10:13 PM, Jingoo Han wrote:
> On Wednesday, July 31, 2013 5:14 PM, Jingoo Han wrote:
>> Exynos PCIe IP consists of Synopsys specific part and Exynos
>> specific part. Only core block is a Synopsys designware part;
>> other parts are Exynos specific.
>> Also, the Synopsys
On Wed, Aug 7, 2013 at 6:40 AM, Jan Kara wrote:
> On Mon 05-08-13 12:43:58, Andy Lutomirski wrote:
>> My application fallocates and mmaps (shared, writable) a lot (several
>> GB) of data at startup. Those mappings are mlocked, and they live on
>> ext4. The first write to any given page is slow
From: Steven Rostedt
When modifying text sections for jump labels, a paranoid check is
performed. If the check fails, the system "bugs". But why it failed
is not shown.
The BUG_ON()s in the jump label update code is replaced with bug_at(ip).
This is a function that will show what pointer
On 08/05/2013 11:41 AM, Jay Fenlason wrote:
On Mon, Aug 05, 2013 at 12:59:04PM +1000, Alexey Kardashevskiy wrote:
Hi!
Recently I started getting multiple errors like this:
cxgb3 0006:01:00.0: iommu_alloc failed, tbl c3067980 vaddr
c01fbdaaa882 npages 1
cxgb3 0006:01:00.0:
On Wed, Aug 07, 2013 at 01:05:11AM -0400, Dave Jones wrote:
> Still seeing these (though not as frequently)
>
>
> INFO: rcu_preempt self-detected stall on CPU { 2} (t=6500 jiffies g=4433279
> c=4433278 q=0)
> sending NMI to all CPUs:
> NMI backtrace for cpu 0
> CPU: 0 PID: 0 Comm: swapper/0
On 08/07/2013 09:30 AM, Sebastian Andrzej Siewior wrote:
On 08/07/2013 06:21 PM, John Stultz wrote:
On 08/07/2013 03:56 AM, Sebastian Andrzej Siewior wrote:
This patch adds a menu item to clocksource' Kconfig file. Without it the
changeable items look somehow lost in the main drivers' menu
So
On Wed, Aug 7, 2013 at 9:21 AM, Oleg Nesterov wrote:
> On 08/06, Andy Lutomirski wrote:
>>
>> I assume that what the man page means is that the return value is
>> whatever fsgid was prior to the call. On error, fsgid isn't changed, so
>> the return value is still "current".
>
> Probably... Still
On Wed, 2013-08-07 at 14:51 +0900, Greg Kroah-Hartman wrote:
> On Tue, Aug 06, 2013 at 10:31:25PM +0200, Paul Bolle wrote:
> > On Fri, 2013-08-02 at 08:31 +0800, Greg Kroah-Hartman wrote:
> > > On Wed, Jul 31, 2013 at 11:35:13PM +0200, Paul Bolle wrote:
> > > > 2) Please note that if the callback
On 13-08-07 12:29 PM, Boris BREZILLON wrote:
Add clocks to clock lookup table for uart DT entries.
Signed-off-by: Boris BREZILLON
Tested-by: Douglas Gilbert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, 2013-08-07 at 09:12 -0700, Srinivas Pandruvada wrote:
> RAPL(Running Average Power Limit) interface provides platform software
> with the ability to monitor, control, and get notifications on SOC
> power consumptions.
trivial notes:
> diff --git a/drivers/powercap/intel_rapl.c
From: Steven Rostedt
As specified by H. Peter Anvin, the best nops for x86 without knowing
the running computer is:
32bit:
0x3e, 0x8d, 0x74, 0x26, 0x00 also known as GENERIC_NOP5_ATOMIC
64bit:
0x0f, 0x1f, 0x44, 0x00, 0x00 also known as P6_NOP5_ATOMIC
Currently the default nop that is
On Wed, 2013-08-07 at 18:22 +0200, Johannes Berg wrote:
> Maybe. I haven't tested it, but I'm thinking that skb->data doesn't
> point to the start of the data frame in this case, since we now call
> eth_type_trans() which pulls the ethernet header. So if the device just
> transmits skb->len
On Wed, Aug 07, 2013 at 06:25:03PM +0800, Lai Jiangshan wrote:
> Signed-off-by: Lai Jiangshan
> ---
> kernel/rcutree.h|1 +
> kernel/rcutree_plugin.h |1 +
> kernel/rcutree_trace.c |1 +
> 3 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/rcutree.h
From: Steven Rostedt
On boot up, the jump label init function scans all the jump label locations
and converts them to the best nop for the machine. If the nop is already
the ideal nop, do not bother with changing it.
Cc: Jason Baron
Cc: H. Peter Anvin
Signed-off-by: Steven Rostedt
---
Peter,
These 4 patches were taken from the patchset that did the 2-5 byte
jumps, but had nothing to do with the 2-5 byte jumps itself. They
were clean ups and safety checks that were needed for the jump code.
Although the 2-5 byte jump code is controversial, these cleanups are
not.
The first
From: Steven Rostedt
As with all modifying of kernel text, we need to be very paranoid.
When converting the jump label locations to and from nops to jumps
a check has been added to make sure what we are replacing is what we
expect, otherwise we bug.
Cc: H. Peter Anvin
Cc: Jason Baron
On Wed, Aug 07, 2013 at 04:13:57PM +0930, Rusty Russell wrote:
> Christoph Jaeger writes:
> > In param_get_byte(), to which the macro STANDARD_PARAM_DEF(byte, ...)
> > expands,
> > "%c" is used to print an unsigned char. So it gets printed as a character
> > what
> > is not intended here. Use
On Fri, Aug 02, 2013 at 12:59:24AM -0700, Felipe F. Tonello wrote:
> +int jack_ctl_integer_info(struct snd_kcontrol *kcontrol,
> + struct snd_ctl_elem_info *uinfo)
> +{
> + uinfo->type = SNDRV_CTL_ELEM_TYPE_INTEGER;
> + uinfo->count = 0x1U;
> +
Quoting Viresh Kumar (2013-08-07 07:46:43)
> This patch adds CPU0's clk driver for Tegra. It will be used by the generic
> cpufreq-cpu0 driver to get/set cpu clk.
>
> Most of the platform specific bits are picked from tegra-cpufreq.c.
>
> Signed-off-by: Viresh Kumar
Hi Viresh,
It is nice to
On Wed, Aug 07, 2013 at 10:06:30AM -0600, Stephen Warren wrote:
> On 08/07/2013 03:35 AM, Wei Ni wrote:
> > On 08/07/2013 04:45 PM, Alexander Shiyan wrote:
> >>> On 08/07/2013 03:50 PM, Guenter Roeck wrote:
> On 08/07/2013 12:32 AM, Wei Ni wrote:
> > On 08/07/2013 03:27 PM, Alexander
On Tue, Aug 06, 2013 at 06:33:06PM -0700, Stepan Moskovchenko wrote:
> Update the reg property of the memory node in
> skeleton64.dtsi to reflect the fact that the root node uses
> address-cells=2 and size-cells=2.
>
> Change-Id: Ie9b61166143969e020ceebc51e9a384405d8c0f2
> Signed-off-by: Stepan
On Wed, Aug 07, 2013 at 11:29:52AM +0100, Laxman Dewangan wrote:
> Palmas series device like TPS65913, TPS80036 supports the backup battery
> for powering the RTC when no other energy source is available.
>
> The backup battery is optional, connected to the VBACKUP pin, and can be
>
On Wed, 2013-08-07 at 18:12 +0200, Johannes Berg wrote:
> On Wed, 2013-08-07 at 17:59 +0200, Phil Sutter wrote:
>
> > The idea behind this patch is that users setting the protocol to
> > something else probably do know better and so should be left alone.
>
> Regardless of that, I think that
On 13-08-07 11:50 AM, Roland Dreier wrote:
On Wed, Aug 7, 2013 at 7:38 AM, David Milburn wrote:
I was able to succesfully test this patch overnight, I had been experimenting
with the
sg driver setting the BIO_NULL_MAPPED flag in sg_rq_end_io_usercontext for a
orphan process
which prevented
On 8/7/13 8:44 AM, Miklos Szeredi wrote:
On Tue, Aug 6, 2013 at 10:06 PM, Anand Avati wrote:
On 8/6/13 7:30 AM, Miklos Szeredi wrote:
From: Anand Avati
Drop a subtree when we find that it has moved or been delated. This can
be
done as long as there are no submounts under this location.
On Wed, Jul 17, 2013 at 7:31 AM, Sonic Zhang wrote:
I'd like Stephen and Axel to have a look at this as well...
> From: Sonic Zhang
>
> in pinmux_disable_setting after current device fails to request
> the same pins.
>
> Signed-off-by: Sonic Zhang
I don't quite understand the patch. Can you
On Tue, Aug 06, 2013 at 07:00:17PM +0100, Julius Werner wrote:
> This patch simplifies the way the phy-samsung-usb code finds the correct
> power management register to enable PHY clock gating. Previously, the
> code would calculate the register address from a device tree supplied
> base address
On 08/07/2013 06:21 PM, John Stultz wrote:
> On 08/07/2013 03:56 AM, Sebastian Andrzej Siewior wrote:
>> This patch adds a menu item to clocksource' Kconfig file. Without it the
>> changeable items look somehow lost in the main drivers' menu
>
> So I'd like to push back on this a bit and ask why
Jan Kara wrote:
> On Sun 04-08-13 05:17:03, Kirill A. Shutemov wrote:
> > From: "Kirill A. Shutemov"
> >
> > The radix tree is variable-height, so an insert operation not only has
> > to build the branch to its corresponding item, it also has to build the
> > branch to existing items if the size
Add clocks to clock lookup table for uart DT entries.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9x5.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-at91/at91sam9x5.c b/arch/arm/mach-at91/at91sam9x5.c
index 2abee66..916e5a1 100644
---
On 08/06, Andy Lutomirski wrote:
>
> I assume that what the man page means is that the return value is
> whatever fsgid was prior to the call. On error, fsgid isn't changed, so
> the return value is still "current".
Probably... Still
On success, the previous value of fsuid is returned.
On Tue, Jul 23, 2013 at 1:34 PM, Heiko Stübner wrote:
> The correct header to include for clock handling is clk.h .
> clk-provider.h should not be used in simple clock consumers.
>
> Signed-off-by: Heiko Stuebner
Patch applied.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the
Hi Tony,
On Aug 7, 2013, at 7:15 PM, Tony Lindgren wrote:
> * Pantelis Antoniou [130806 02:44]:
>> On Aug 6, 2013, at 12:33 PM, Greg Kroah-Hartman wrote:
>>> On Tue, Aug 06, 2013 at 10:53:44AM +0300, Pantelis Antoniou wrote:
+
static int _omap_device_notifier_call(struct
On Wed, 2013-08-07 at 09:17 -0700, Eric Dumazet wrote:
> On Wed, 2013-08-07 at 18:12 +0200, Johannes Berg wrote:
> > On Wed, 2013-08-07 at 17:59 +0200, Phil Sutter wrote:
> >
> > > The idea behind this patch is that users setting the protocol to
> > > something else probably do know better and so
On 08/07/2013 03:56 AM, Sebastian Andrzej Siewior wrote:
This patch adds a menu item to clocksource' Kconfig file. Without it the
changeable items look somehow lost in the main drivers' menu
So I'd like to push back on this a bit and ask why we need user-visible
clocksource config options?
On Wed, Aug 7, 2013 at 5:07 AM, Cho KyongHo wrote:
...
>> I don't understand how this is possible. Can someone explain this
>> better in the IOMMU documentation please?
>
> System MMU is dedicated to a master H/W such as FIMD and FIMC.
Sory - Exynos 5250 documentation I have (confidential
Roland Dreier wrote:
On Wed, Aug 7, 2013 at 7:38 AM, David Milburn wrote:
I was able to succesfully test this patch overnight, I had been experimenting
with the
sg driver setting the BIO_NULL_MAPPED flag in sg_rq_end_io_usercontext for a
orphan process
which prevented the corruption, but
Added changes to Makefile and Kconfig to include in driver build.
Signed-off-by: Srinivas Pandruvada
---
drivers/Kconfig | 2 ++
drivers/Makefile | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/Kconfig b/drivers/Kconfig
index 9953a42..89ff2f8 100644
--- a/drivers/Kconfig
+++
Added power cap class driver, which provides an API for client drivers
to use and provide a consistant sysfs interface to user mode.
For details on API refer to PowerCappingFramework.txt under
Documentation/powercap.
Signed-off-by: Srinivas Pandruvada
Signed-off-by: Jacob Pan
Signed-off-by:
* Pantelis Antoniou [130806 02:44]:
> On Aug 6, 2013, at 12:33 PM, Greg Kroah-Hartman wrote:
> > On Tue, Aug 06, 2013 at 10:53:44AM +0300, Pantelis Antoniou wrote:
> >> +
> >> static int _omap_device_notifier_call(struct notifier_block *nb,
> >> unsigned long
This patch allows to set up the bits per word together with all other SPI
parameters in the SPI Node of the OF device tree
In the node, you then have to include the 'spi-bits' property.
Exemple:
fpga-loader@7 {
compatible = "cs,fpga-loader";
From: Jacob Pan
Having 64-bit MSR access methods on given CPU can avoid shifting and
simplify MSR content manipulation. We already have other combinations
of rdmsrl_xxx and wrmsrl_xxx but missing the _on_cpu version.
Signed-off-by: Jacob Pan
Signed-off-by: Srinivas Pandruvada
---
From: Jacob Pan
RAPL(Running Average Power Limit) interface provides platform software
with the ability to monitor, control, and get notifications on SOC
power consumptions. Since its first appearance on Sandy Bridge, more
features have being added to extend its usage. In RAPL, platforms are
On Wed, 2013-08-07 at 17:59 +0200, Phil Sutter wrote:
> The idea behind this patch is that users setting the protocol to
> something else probably do know better and so should be left alone.
Regardless of that, I think that still the skb pointers would be changed
by this patch which would
Overview
With the evolution of technologies, which enables power monitoring and limiting,
more and more devices are able to constrain their power consumption under
certain
limits. There are several use cases for such technologies:
- Power monitoring: Each device can report its power consumption.
401 - 500 of 1724 matches
Mail list logo
