Hi,
The following patch causes 'perf stat --repeat 0' to be interpreted as
'forever', displaying the stats for every run.
We act as if a single run was asked, and reset the stats in each
iteration. In this mode SIGINT is passed to perf to be able to stop the
loop with Ctrl+C.
Regards,
Frederik
On Fri, Feb 15, 2013 at 04:50:28PM +0100, Ingo Molnar wrote:
> Dave, one thing that might be worth trying is to disable
> CONFIG_BUG and see whether the system manages to limp through to
> get console output?
Didn't make any difference. Black screen, blinky power light.
Dave
--
T
On Fri, 15 Feb 2013 17:28:03 -0500
Johannes Weiner wrote:
> > Yes, and there will be immediate calmour to add more goodies to the
> > other seven bits. PageDirty, referenced state, etc. We should think
> > about this now, at the design stage rather than grafting things on
> > later.
>
> I'm in
On Mon, Feb 11, 2013 at 7:48 AM, David Engraf wrote:
> I have encountered a problem when a linux system uses a clocksource with
> mult = 1 and shift = 0 (clocksource cycle = nanoseconds). It may happen that
> the function timekeeping_adjust reduces the value of mult to 0 when error is
> lower than
Am Fri, 15 Feb 2013 14:26:52 -0800
schrieb a...@linux-foundation.org:
> --
> From: Paul Gortmaker
> Subject: futex: avoid kernel taint caused by get_robust_list
>
> Commit ec0c4274e33c0373e4 ("futex: Mark get_robust_list as
> deprecated") added
On Fri, 15 Feb 2013 13:38:24 +0100
Michal Hocko wrote:
> Fenguang Wu has reported the following compile time issue
> arch/ia64/kernel/topology.c:278:16: error: conflicting types for 'cache_show'
> include/linux/slab.h:224:5: note: previous declaration of 'cache_show' was
> here
>
> which has be
On Wed, Feb 13, 2013 at 7:58 AM, Christian Gmeiner
wrote:
> 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
On 02/15/2013 05:21 PM, Seiji Aguchi wrote:
> Rik, Satoru,
>
> Do you have any comments?
>
> Seiji
Hmm, this seems what we wanted to know in the previous thread.
Because extra_free_kbytes is quite simple and it fixes the problem,
it should be merged into upstream.
Regards,
Satoru
>> -Ori
Thank You for your response.
Comments inline.
I will throughly inspect the other 52% that wasn't reviewed for the same
simple mistakes that were missed :)
Testing changes before submitting.
A patch will be coming soon.
On Thu, Feb 14, 2013 at 03:56:14PM -0800, Andrew Morton wrote:
> On Fri, 1
On Tue, 15 Jan 2013 12:51:54 +0100, Roland Stigge wrote:
> There is a race condition between creating a gpio or gpiochip device and
> adding
> default attributes. This patch fixes this by defining the default attributes
> as
> dev_attrs of the class. For this, it was necessary to create a separa
This is the start of the stable review cycle for the 3.0.65 release.
There are 4 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:56 UTC 2013.
Anything received
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
Hi
Booted on Toshiba laptop, x86_64, NVIDIA Corporation GT218 [GeForce
310M], latest rc, and got this.
Please let me know if you need additional information.
[ 16.595094] [TTM] Zone dma32: Available graphics memory: 2097152
kiB
[ 16.595096] [TTM] Initializing pool allocator
[ 16.5951
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
Instead
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 9977f0f164d46613288e0b5778eae500dfe06f31 upstream.
With commit 8e72033f2a48 ("thp: make MADV_HUGEPAGE check for
mm->def_flags") the VM_NOHUGEPAGE flag may be set on s390
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Satoru Takeuchi
commit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.
There was a serious problem in samsung-laptop that its platform driver is
designed to run under BIOS and running under
Driver twl4030-madc has hardcoded channel types (10 - battery current,
1 - battery temperature) and also conversation data in variable
twl4030_divider_ratios. These hardcoded channels are incorrect for
Nokia RX-51 board (where is channel 0 - battery temperature).
For Nokia RX-51 there is rx51_batt
Tell twl4030_madc_conversion that this driver needs raw values.
Driver twl4030_madc has some hardcoded values and conversation
functions which are incorrect for Nokia RX-51 board. This driver
rx51_battery expects raw values which convert itself.
This patch fixing values reported by power supply in
This is the start of the stable review cycle for the 3.7.9 release.
There are 10 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:54:03 UTC 2013.
Anything received
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting T
On Fri, 15 Feb 2013 23:44:44 +0100
Richard Weinberger wrote:
> As stated in [0], I'd simply revert commit ec0c4274 ("futex: Mark
> get_robust_list as deprecated")
Too much talk, not enough patches. I typed it all in again.
--
To unsubscribe from this list: send the line "unsubscribe linux-kerne
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Stoney Wang
commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.
When a HP ProLiant DL980 G7 Server boots a regular kernel,
there will be intermittent lost interrupts which could
result in
3.7-stable review patch. If anyone has any objections, please let me know.
--
This reverts commit a56040731e5b00081c6d6c26b99e6e257a5d63d7 which was
commit eb178619f930fa2ba2348de332a1ff1c66a31424 upstream.
It has been reported to cause problems:
http://bugzilla.redhat.c
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d911e03d097bdc01363df5d81c43f69432eb785c upstream.
Since ed4f209 "s390/time: fix sched_clock() overflow" a new helper function
is used to avoid overflows when converting T
This is the start of the stable review cycle for the 3.4.32 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:47 UTC 2013.
Anything received
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.
Without this patch, it is trivial to determine kernel page
mappings by examining the error code reported to dmesg[1].
Instead
3.7-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 3399cfb5df9594495b876d1843a7165f77366b2b upstream.
Commit e7e034e18a0a ("drivers/rtc/rtc-pl031.c: fix the missing operation
on enable") accidentally broke the ST variants o
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Beulich
commit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.
This fixes CVE-2013-0228 / XSA-42
Drew Jones while working on CVE-2013-0190 found that that unprivileged guest
user
in 32
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Duyck
commit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.
For some reason the reading of the RQDPC register was being artificially
limited to 4K. Instead of limiting the value
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.
Devices are added to pci_pme_list when drivers use pci_enable_wake()
or pci_wake_from_d3(), but they aren't removed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.
A user reported the following oops when a backup process reads
/proc/kcore:
BUG: unable to handle kernel paging request at
Hi
Worked for a while on 3.8.0-rc7, generally it is fine, then suddenly
laptop stopped responding to keyboard and mouse.
Sure it can be memory corruption by some other module, but maybe not.
Worth to report i guess.
After reboot checked logs and found this:
Feb 16 00:40:17 localhost kernel: [
On Fri, Feb 15, 2013 at 1:59 PM, Al Viro wrote:
> On Fri, Feb 15, 2013 at 12:02:50PM -0800, Linus Torvalds wrote:
>> On Wed, Feb 13, 2013 at 9:36 PM, Al Viro wrote:
>> >
>> > The only problem is that some suicides do SIGKILL, some SIGSEGV.
>> > AFAICS, it started as SIGSEGV and had been s
On Fri, Feb 15, 2013 at 01:27:38PM -0800, Andrew Morton wrote:
> On Fri, 15 Feb 2013 01:34:50 -0500
> Johannes Weiner wrote:
>
> > + * The status is returned in a vector of bytes. The least significant
> > + * bit of each byte is 1 if the referenced page is in memory, otherwise
> > + * it is zer
On Fri, 15 Feb 2013 16:45:38 +0900
Jingoo Han wrote:
> Fixed build warning as below:
>
> drivers/rtc/rtc-max77686.c: In function 'max77686_rtc_update':
> drivers/rtc/rtc-max77686.c:147:6: warning: 'data' may be used uninitialized
> in this function [-Wuninitialized]
>
> Signed-off-by: Jingoo H
Wolfram,
On Fri, Feb 15, 2013 at 11:53 AM, Wolfram Sang wrote:
>
>> I'll re-send with I2C subsystem wide. I probably won't attempt the
>> whole kernel wide at this point, but would be very happy if someone
>> else wanted to! :)
>
> Thanks. Please double check that setting NULL is really unneede
On Thu, 14 Feb 2013 15:38:16 -0800
Mandeep Singh Baines wrote:
> From: Ben Chan
>
> This patch makes wait_for_dump_helpers() not to abort piping the core
> dump data when the crashing process has received any but a fatal signal
> (SIGKILL). The rationale is that a crashing process may still rec
On Thu, 14 Feb 2013 15:38:14 -0800
Mandeep Singh Baines wrote:
> Replace the for loop with a simple if.
Well OK, but why? Presumably the loop was added for a reason and
presumably you believe that reason to be (no longer?) correct. Please
describe all these things.
> --- a/kernel/exit.c
> +++
Zhang Rui intel.com> writes:
>
> Hi, Roberto,
>
> please attach the acpidump output.
>
> On Tue, 2012-12-04 at 13:57 +0100, Roberto Oppedisano wrote:
> > Hello,
> > with recent kernels after a suspend/resume cycle on my laptop (HP
> > 6730b) the fans stays at full speed.
> does the fan k
This property is meant to be used in device nodes which represent
power_supply devices that wish to provide a list of supplies to
which they provide power. A common case is a AC Charger with
the batteries it powers.
Signed-off-by: Rhyland Klein
---
.../bindings/power_supply/power_supply.txt
With the growing support for dt, it make sense to try to make sure of
dt features as to make the general code cleaner. This patch is an
attempt to commonize how chargers receive their "supplied_to" list
of supplicants. This was previously done via passing an array of
strings.
Currently, charger dr
With the addition of the device_nodes to use similar to how
supplied_to works, add a helper function which will parse out the
phandles for the supplied-nodes directly from the node. This
implmentation requires the property name to be "supplied-nodes".
Signed-off-by: Rhyland Klein
---
drivers/pow
This series is an attempt to define a common way for devicetree
initialized power_supplies to define their list of supplicants
in a common manner.
Instead of relying on custom properties which contain is list of
strings, use the much more direct method of phandles to reference
the supplicants and
On 02/15/2013 04:12 PM, Andrew Morton wrote:
On Fri, 15 Feb 2013 14:47:54 -0600
Nathan Zimmer wrote:
I am currently tracking a hotlock reported by a customer on a large system,
512 cores. I am currently running 3.8-rc7 but the issue looks like it has been
this way for a very long time.
The of
On Fri, 15 Feb 2013 18:13:04 -0500
Johannes Weiner wrote:
> On Fri, Feb 15, 2013 at 01:27:38PM -0800, Andrew Morton wrote:
> > On Fri, 15 Feb 2013 01:34:50 -0500
> > Johannes Weiner wrote:
> >
> > > + * The status is returned in a vector of bytes. The least significant
> > > + * bit of each by
On Fri, 15 Feb 2013 17:39:38 -0600
Nathan Zimmer wrote:
> > So are all these games with local variable `llseek' still needed?
> > afaict the increment of pde_users will stabilize ->fops?
> We still are setting de->proc_fops to NULL to prevent new callers.
> Also we still have to save fops-> since
On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
> > + send_sig(SIGSEGV, current, 0);
>
> This might be a stupid miscue on my part, but shouldn't it be
> force_sig instead of send_sig?
>
> I've got this crazy hunch that having SEGV masked might muck somethin
From: Ben Chan
Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal. The abort still occurs
in the case of SIGKILL.
Addresses http://crosbug.com/21559
Changes since v1:
* Mandeep Singh Baines
* To prevent blocking suspend,
On 02/04/2013 02:49 PM, Seiji Aguchi wrote:
> +
> +static void switch_to_trace_idt(void *arg)
> +{
> + store_idt(this_cpu_ptr(&orig_idt_descr));
> + load_idt(&trace_idt_descr);
> +
> + return;
> +}
> +
> +static void restore_original_idt(void *arg)
> +{
> + if (this_cpu_read(orig_id
On 02/04/2013 02:50 PM, Seiji Aguchi wrote:
> [Issue]
>
> Currently, irq vector handlers for tracing are just
> copied non-trace handlers by simply inserting tracepoints.
>
> It is difficult to manage the codes.
>
> [Solution]
>
> This patch shares common codes between non-trace and trace handl
Remove the printing of warning in case of failed mappings. Sometimes
they are expected as in case of Qemu mapping pages during HVM guest
creation.
Signed-off-by: Mukesh Rathor
---
arch/x86/xen/mmu.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/x86/xen/mmu.c b/
On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> How would you manage to have it masked at that point? setup_new_exec()
> is inevitable after success of flush_old_exec() and it will do
> flush_signal_handlers() for us.
I wouldn't know for sure but I read somewhere that even if execve
resets han
On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
>> On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
>>> Peter Hurley found "irq 18 nobody cared" with pci-next, and dmesg has
>>>
>>> [8.983246] pci :00:1e.0: can't d
On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
>> > + send_sig(SIGSEGV, current, 0);
>>
>> This might be a stupid miscue on my part, but shouldn't it be
>> force_sig instead of send_sig?
>>
>> I've got this
On Sat, 16 Feb 2013, Al Viro wrote:
> > > + send_sig(SIGSEGV, current, 0);
> >
> > This might be a stupid miscue on my part, but shouldn't it be
> > force_sig instead of send_sig?
> >
> > I've got this crazy hunch that having SEGV masked might muck something up.
>
On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
>> How would you manage to have it masked at that point? setup_new_exec()
>> is inevitable after success of flush_old_exec() and it will do
>> flush_signal_handlers() for us.
>
> I wouldn't know fo
From: Ben Chan
Make wait_for_dump_helpers() not abort piping the core dump data when the
crashing process has received a non-fatal signal. The abort still occurs
in the case of SIGKILL.
Testing:
localhost ~ # echo "|/usr/bin/sleep 1d" > /proc/sys/kernel/core_pattern
localhost ~ # sleep 1d &
[1
On Wed, Feb 13, 2013 at 5:59 AM, Rafael J. Wysocki wrote:
> On Tuesday, February 12, 2013 05:54:08 PM Yinghai Lu wrote:
>> On Tue, Feb 12, 2013 at 4:16 PM, Rafael J. Wysocki wrote:
>> > From: Rafael J. Wysocki
>> >
>> > After commit 1aeae82 (ACPI / PCI: avoid building pci_slot as module)
>> > th
On Fri, Feb 15, 2013 at 7:01 AM, Oleg Nesterov wrote:
> On 02/14, Mandeep Singh Baines wrote:
>>
>> This patch makes wait_for_dump_helpers() not to abort piping the core
>> dump data when the crashing process has received any but a fatal signal
>> (SIGKILL). The rationale is that a crashing proces
Hello,
On Fri, 15 Feb 2013 08:52:12 -0800, Eric Dumazet wrote:
> Driver is buggy, as TX completion can happen both from ndo_start_xmit()
> and a timer, and there is no spinlock or appropriate synchro.
Yes, it is a known issue. I did post a patch fixing the problem on
netdev@ a while ago [1], but
On Fri, Feb 15, 2013 at 04:40:18PM -0800, Linus Torvalds wrote:
> On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> > On Fri, Feb 15, 2013 at 03:12:30PM -0800, Shentino wrote:
> >> > + send_sig(SIGSEGV, current, 0);
> >>
> >> This might be a stupid miscue on my part,
On Fri, 2013-02-15 at 16:13 -0800, H. Peter Anvin wrote:
> How important is it that the tracepoint is *inside* the enter/exit
> handling? If not, it would be simpler to just do:
>
> smp_trace_irq_handler()
> {
> trace_irq_entry();
> smp_irq_handler();
> trace_irq_exit();
> }
>
On Fri, Feb 15, 2013 at 4:39 PM, Bjorn Helgaas wrote:
> On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
>> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
>>> On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
Peter Hurley found "irq 18 nobody cared" with pci-next, an
On Fri, Feb 15, 2013 at 5:26 PM, Yinghai Lu wrote:
> On Fri, Feb 15, 2013 at 4:39 PM, Bjorn Helgaas wrote:
>> On Thu, Feb 14, 2013 at 5:50 PM, Yinghai Lu wrote:
>>> On Tue, Feb 12, 2013 at 12:22 PM, Rafael J. Wysocki wrote:
On Tuesday, February 12, 2013 11:11:23 AM Yinghai Lu wrote:
>
On Fri, Feb 15, 2013 at 5:22 PM, Al Viro wrote:
>
> Fine by me - the variant I'd posted simply moved these calls in one
> place; I've no problem with replacing them with force_sig() (or
> force_sigsegv(SIGSEGV, current), for paranoia sake). OTOH, I'd probably
> prefer to make it a separate commit
On Fri, Feb 15, 2013 at 04:46:43PM -0800, Shentino wrote:
> On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> > On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> >> How would you manage to have it masked at that point? setup_new_exec()
> >> is inevitable after success of flush_old_exec() and it
Hi Linus,
If you're doing another RC, please grab these two. Otherwise I'll send
them off to -stable.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
This fixes a long standing problem where the btrfs scan ioctl was racing
with mkfs.btrfs and dropping dirty pages c
On 2013/2/13 18:07, Matt Fleming wrote:
>> In efi_init() memory aligns in IA64_GRANULE_SIZE(16M). If set
>> "crashkernel=1024M-:600M"
>> and use sparse memory model, when crash kernel booting it changes
>> [128M-728M] to [128M-720M].
>> But initrd memory is in [709M-727M], and virt_addr_valid()
On Fri, 2013-02-15 at 16:09 -0800, H. Peter Anvin wrote:
> On 02/04/2013 02:49 PM, Seiji Aguchi wrote:
> > +
> > +static void switch_to_trace_idt(void *arg)
> > +{
> > + store_idt(this_cpu_ptr(&orig_idt_descr));
> > + load_idt(&trace_idt_descr);
> > +
> > + return;
> > +}
> > +
> > +static vo
This fixes an inconsistent behavior between list_voltage() and get_voltage()
because current implementation of get_voltage() does not check the case
IS_UNSUP() is true.
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
This switch should always be outside the funny NMI and debug zone.
I think you missed a patch that I sent you to deal with exactly this:
https://lkml.org/lkml/2013/2/1/532
I sent it directly to you, maybe it got buried in your INBOX.
I saw it. It had a:
Not-yet-signed-off-by: Steven Rosted
On Sat, Feb 16, 2013 at 01:50:24AM +, Al Viro wrote:
> On Fri, Feb 15, 2013 at 04:46:43PM -0800, Shentino wrote:
> > On Fri, Feb 15, 2013 at 4:38 PM, Shentino wrote:
> > > On Fri, Feb 15, 2013 at 4:04 PM, Al Viro wrote:
> > >> How would you manage to have it masked at that point? setup_new_e
On Fri, 2013-02-15 at 18:11 -0800, H. Peter Anvin wrote:
> >
> > This switch should always be outside the funny NMI and debug zone.
> > I think you missed a patch that I sent you to deal with exactly this:
> >
> > https://lkml.org/lkml/2013/2/1/532
> >
> > I sent it directly to you, maybe it got bu
On Fri, Feb 15, 2013 at 11:07:16AM +0100, Guennadi Liakhovetski wrote:
> Add device-tree bindings to the AS3711 regulator and backlight drivers.
Hi,
at this stage I do not expect this code to go through the renesas tree.
However, in order to provide a basis for work on renesas SoCs I have added
t
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index d62604c0..2b3dc5b 100644
--- a/drivers/regulator/twl-regulator.c
+++ b/driv
On Fri, 2013-02-15 at 18:11 -0800, H. Peter Anvin wrote:
> Not-yet-signed-off-by: Steven Rostedt
Also note that the "Not-yet-signed-off-by" was to let people know that,
even though I ran it through various tests, I did not run it through my
main test suite.
I probably wont change it much, if at
Many i2c users consider short transfers to be an error and would prefer
getting -EIO instead of a positive return value and having to convert
it to error code by themselves. So let's add the following new helpers:
i2c_master_send_exact()
i2c_master_recv_exact()
i2c_transfer
Many i2c users consider short transfers to be an error and would prefer
getting -EIO instead of a positive return value and having to convert
it to error code by themselves. So let's add the following new helpers:
i2c_master_send_exact()
i2c_master_recv_exact()
i2c_transfer
On Fri, 2013-02-15 at 11:46 -0800, Sukadev Bhattiprolu wrote:
>
> POWER could use an additional field:
>
> mem_deratmiss:1
If you want to make that field more "generic" make it "lvl1_tlb_miss",
ie, a miss in the internal "level 1" TLB which is the smallest/fastest
TLB lev
On Fri, Feb 15, 2013 at 5:19 PM, Axel Lin wrote:
> Add enable_pulldown flag to indicate pulldown on EN input when using
> regulator_enable_regmap and friends APIs.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/core.c | 24
> include/linux/regulator/driv
On Fri, Feb 15, 2013 at 8:36 PM, Axel Lin wrote:
> The info parameter is not used at all, remove it.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/max8925-regulator.c |5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/regulator/max8925-regulator.c
>
TWL6030_FIXED_RESOURCE is not used now, remove it.
TWL6030_FIXED_RESOURCE is not used since commit e76ab829cc
"regulator: twl: Remove references to the twl4030 regulator"
twl6030_fixed_resource is removed by commit 029dd3cef
"regulator: twl: Remove another unused variable warning".
Signed-off-by
On Fri, Feb 15, 2013 at 08:36:21PM +0100, Henrik Rydberg wrote:
> To properly setup event parameters for emulated events, pass
> the appropriate flag to the slot initialization function. Also,
> all MT-related events should be setup before initialization.
>
> Incidentally, this solves the issue of
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get 2 small driver
fixups and a documentation update for
On 02/14/2013 02:38 AM, Seth Jennings wrote:
Lots of changes this time around. Hopefully I collected and acted on
all the feedback. I apologize ahead of time if I missed something.
Please let me know if I did.
Changelog:
v5:
* zsmalloc patch converted from promotion to "new code" (for review
On 15 February 2013 23:51, Arnd Bergmann wrote:
> diff --git a/Documentation/devicetree/bindings/dma/snps-dma.txt
> b/Documentation/devicetree/bindings/dma/snps-dma.txt
> +- #dma-cells: must be <3>
> +DMA clients connected to the Designware DMA controller must use the format
> +described in the
On 02/14/2013 02:38 AM, Seth Jennings wrote:
=
DO NOT MERGE, FOR REVIEW ONLY
This patch introduces zsmalloc as new code, however, it already
exists in drivers/staging. In order to build successfully, you
must select EITHER to driver/staging version OR this version.
Once zsmalloc is revie
On 15 February 2013 23:51, Arnd Bergmann wrote:
> As Andy pointed out today, we don't have a good solution for the
> dw_dmac DT binding in linux-next yet. I have posted my series
> once before and then got distracted after getting feedback from
> Viresh, Andy and Russell. I have now updated my ear
On 2013/2/13 17:15, Ingo Molnar wrote:
>
> * Namhyung Kim wrote:
>
>> Hi,
>>
>> On Mon, 11 Feb 2013 10:54:58 +0100, Ingo Molnar wrote:
>>> * Clark Williams wrote:
>>>
I figured that was coming. :)
>>>
>>> ;-)
>>>
I'll look at it again and see about pulling the
autogroup/cgroup s
Sjur Brændeland writes:
> How about supporting struct vringh_kiov and struct kvec as well?
> I currently get the following complaints with my V2 patch-set:
>
> drivers/net/caif/caif_virtio.c:486:2: warning: passing argument 1 of
> ‘vringh_iov_init’ from incompatible pointer type [enabled by defaul
On Tue, Feb 12, 2013 at 11:47 PM, Artem Bityutskiy wrote:
> On Mon, 2013-01-28 at 12:57 +0800, Huang Shijie wrote:
>> + {"SmartMedia 256MiB 3,3V", {0, 0x71}, 512, 256, 0x4000 },
>> + {"SmartMedia 256MiB 3,3V ROM", {0, 0x5b}, 512, 256, 0x4000,
>> NAND_ROM},
>
> Sorry for a possibl
Hi Dmitry,
On Thu, Feb 14, 2013 at 9:31 AM, Dmitry Torokhov
wrote:
> On Wed, Feb 13, 2013 at 10:45:07PM -0800, Simon Glass wrote:
>> >>
>> >> +config KEYBOARD_CROS_EC
>> >> + tristate "ChromeOS EC keyboard"
>> >> + select INPUT_MATRIXKMAP
>> >> + select MFD_CROS_EC
>> >
>> > Is this s
501 - 600 of 642 matches
Mail list logo
