Hello,
I put the IRQF_NO_SUSPEND_SAFE/IRQF_TIMER_SIBLING_OK/WHATEVER_NAME_YOU_CHOOSE
debate aside to concentrate on another problem pointed out by Rafael and
Mark: the fact that we cannot mix IRQF_NO_SUSPEND and wakeup sources on
a shared IRQ line.
This is because the wakeup code is prevailing th
The IRQ line used by the RTC device is often shared with the system timer
(PIT) on at91 platforms.
Since timers are registering their handlers with IRQF_NO_SUSPEND, we should
expect being called in suspended state, and properly wake the system up
when this is the case.
Signed-off-by: Boris Brezill
Add two helper functions to help drivers that are sharing IRQs with
timer devices (or other devices setting the IRQF_NO_SUSPEND flag) deal
with system wakeup and state detection.
Such drivers should expect their IRQ handler to be called in 2 different
contexts:
1/ the system is resumed and the han
Get a loan here at low rate
Amount Needed:
Loan Duration:
Phone Number:
Country
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Tue, Feb 24, 2015 at 08:15:35AM +, Naoya Horiguchi wrote:
> Let me update my explanation about the problem. I wrote the description about
> race window of nmi shoot down threads. That's not wrong, but that's only the
> part of the problem. The more suitable description is that all "shot down
From: Ingo Molnar
...
> So why not trylock and time out here after a few seconds,
> instead of indefinitely supressing some potentially vital
> output due to some other CPU crashing/locking with the lock
> held?
I've used that for status requests that usually lock a table
to get a consistent view.
Mixing IRQF_NO_SUSPEND and !IRQF_NO_SUSPEND on the same IRQ line is highly
discouraged, but in some cases (IRQ shared by a timer and other devices)
you don't have any other choice.
Since some devices sharing the IRQ line might tag it as a wakeup source,
you might end up with your handler that reque
Re-work and fix handling of errors when retrieving power supply
properties:
1. Return errno values directly from get_property() instead of storing
'unknown' as intval for given property.
2. Handle regmap_read() errors when getting 'online' and 'present'
proprties and return errno code. Prev
Re-work and fix handling of errors when retrieving power supply
properties:
1. Return errno values directly from get_property() instead of
storing 'unknown' as intval for given property.
2. Handle regmap_read() errors and return errno code. Previously the
regmap_read() return code was ignor
By calling __nci_request instead of nci_request allows the driver to use
the function while initializing the device (setup stage)
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/nfc/nci/core.c b/net/nfc/nci/core.c
index 9
I am announcing the release of the Linux 3.16.7-ckt7 kernel.
The updated 3.16.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.16.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.16.y;a=shortlog
The diff from v3.16.7-c
This patch adds nci_request_driver and nci_req_complete_driver
as a wrapper for __nci_request. When nci_req_complete_driver is
called it also sets cmd_cnt to 1. This is done because the response is not
sent to the NFC subsystem so cmd_cnt is not decremented there.
nci_send_cmd was previously expor
The device can be enumerated using ACPI using the id INT339A.
The 1st GPIO is the IRQ and the 2nd is the RESET pin.
I can be also enumerated using platform init.
Signed-off-by: Robert Dolca
---
drivers/nfc/Kconfig | 1 +
drivers/nfc/fdp/Kconfig | 22 ++
drivers/nfc/fdp
FDP driver needs to send the firmware as regular packets
(not fragmented). That's whay the driver should have a way to
get the max packet size for a given connection.
Signed-off-by: Robert Dolca
---
include/net/nfc/nci_core.h | 1 +
net/nfc/nci/data.c | 12
2 files changed,
If the previous nci_request (NCI reset) failed the setup function
was being called anyway. It shouldn't be called if the reset failed.
The result of the setup function is taken into consideration. If it
fails the init should fail.
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 4 ++--
1 f
nci_core_conn_create not has a new parameter so it can return
the ID of the new connection. Also not you can't call nci_core_conn_create
without waiting the answer for the previous call.
Signed-off-by: Robert Dolca
---
drivers/nfc/st21nfcb/st21nfcb_se.c | 2 +-
include/net/nfc/nci_core.h
In order to communicate with the device during the setup
phase, the driver may need to initialize the device. After
the setup is done the driver should reset the device to leave
it in the same state that it was before the setup function
call.
Signed-off-by: Robert Dolca
---
include/net/nfc/nci_c
nci_send_cmd was exported in order to send commands to the device from
the driver. For the firmware update the driver may use nci_send_data.
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 1 +
net/nfc/nci/data.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/net/nfc/nci/core.c b/net
diff --git a/Makefile b/Makefile
index cc7535a0f9d0..eff7a4bcda71 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 16
SUBLEVEL = 7
-EXTRAVERSION =-ckt6
+EXTRAVERSION =-ckt7
NAME = Museum of Fishiegoodies
# *DOCUMENTATION*
diff --git a/arch/arm/boot/dts/exynos4.dt
This patch adds support for Intel's FieldsPeak NFC solution.
The device is enumerated with ACPI and platform init.
In order to implement the driver the nci_core_conn_create was
modified in order to report the ID of the newly created connection.
Fixed a bug that prevented to close a connection from
From: Tien Hock Loh
Adds a new driver for Altera soft GPIO IP. The driver is able to do
read/write and allows GPIO to be a interrupt controller.
Tested on Altera GHRD on interrupt handling and IO.
Signed-off-by: Tien Hock Loh
---
MAINTAINERS| 6 +
drivers/gpio/Kconfig
Hi Zhangfei,
On 22/02/15 05:10, zhangfei wrote:
> Hi, Balbi
>
> On 02/22/2015 12:21 AM, Felipe Balbi wrote:
>> Hi,
>>
>> On Sat, Feb 21, 2015 at 11:03:05PM +0800, zhangfei wrote:
>>> +static void hi6220_start_peripheral(struct hi6220_priv *priv, bool on)
>>> +{
>>> +struct usb_otg
On Mon, 23 Feb 2015, Brian Norris wrote:
> On Tue, Feb 10, 2015 at 05:04:33PM +0800, Lee Jones wrote:
> > On Thu, 05 Feb 2015, Brian Norris wrote:
> > > On Wed, Jan 21, 2015 at 01:02:04PM +, Lee Jones wrote:
> > > > On Mon, 12 Jan 2015, Brian Norris wrote:
> > > > > On Mon, Dec 15, 2014 at 11:5
The F81232 bulk-in is RX data + LSR channel, data format is
[LSR+Data][LSR+Data]. , We had implemented in f81232_process_read_urb().
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 69 +++--
1 file changed, 36 insertions(+), 33 deletions(-)
This series patch V7 is changed from V6 as following:
1. The buffer of usb_control_msg() in set_register()/get_register() are change
from local variable to kmalloc(). (PATCH V7 02/11)
2. Change all set_register()/get_register() return value 0 is success,
otherwise are failed. ( return 0 of
Change private struct member name from line_status to modem_status.
It will store MSR for some functions used
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81
We extract TIOCGSERIAL section in f81232_ioctl() to f81232_get_serial_info()
to make it clarify.
Also we fix device type from 16654 to 16550A, and set it's baud_base
to 115200 (1.8432MHz/16).
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 30 +++---
1 file c
We put FCR/IER initial step to f81232_port_enable(). When port is open,
it set MSR interrupt on. Otherwise set it off.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/drivers/usb/serial/f81232.
Add me to co-author and fix no '>' in greg kh's email
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index ee9a2a2..23f0a17 100644
--- a/drivers/usb/serial/f
We remove non-used define in this patch to avoid wrong usage.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index 3b0da70..ee9a2a2 100644
--- a/drivers/usb/ser
The original driver lock with spin_lock_irqsave()/spin_unlock_irqrestore()
because of it's maybe used in interrupt context f81232_process_read_urb().
We had remove it from previous patch "implement RX bulk-in EP", so we can
change it from busying loop spin_lock to sleepable mutex_lock.
Signed-off
The original driver had do not any h/w change in driver.
This patch implements with configure H/W for
baud/parity/word length/stop bits functional in f81232_set_termios().
This patch also implement DTR/RTS control when baudrate B0.
We drop DTR/RTS when B0, otherwise enable it.
Signed-off-by: Pete
The interrupt endpoint will report current IIR. If we got IIR with MSR changed
, We will do read MSR with interrupt_work worker to do f81232_read_msr()
function.
We also confirmd MSR strange delta value is not locking-issue. The issue
is set MCR & get MSR before IIR notice with MSR changed (Loopba
We add f81232_get_register()/f81232_set_register() and necessary defines
for future patch with communication with F81232 USB control endpoint.
Because of this is a preparatory patch, there are unused function warning
with compiling. The functions will used with following patches.
Signed-off-by: P
This patch implement relative MCR/MSR function, such like
tiocmget()/tiocmset()/dtr_rts()/carrier_raised()
original f81232_carrier_raised() compared with wrong value UART_DCD.
It's should compared with UART_MSR_DCD.
Signed-off-by: Peter Hung
---
drivers/usb/serial/f81232.c | 103 +++
On Tue, 24 Feb 2015, Krzysztof Kozlowski wrote:
> On pią, 2015-02-06 at 12:24 +0100, Krzysztof Kozlowski wrote:
> > The WTSR (Watchdog Timer Software Reset) and SMPL (Sudden Momentary
> > Power Loss) were removed from rtc-s5m driver because they were not used.
> > Remove them (and on/off interrupt
Hi,
Simplify the max77693 regulator driver by moving DT parse code out
to regulator core.
This removes also board file support. Exynos based boards are DT-only.
This removal allows bigger simplification of driver so overall diffstat
is nice: -93 deletions, 12 additions.
Dependency: The second p
Hi Inha,
On 02/24/2015 06:31 PM, Inha Song wrote:
> This patch add the CLKOUT register source clock as xusbxti in
> PMU (Power Management Unit) dt node on Exynos3250.
>
> Cc: Kukjin Kim
> Signed-off-by: Inha Song
> ---
> arch/arm/boot/dts/exynos3250.dtsi | 3 +++
> 1 file changed, 3 insertions
On 19 February 2015 at 18:18, Morten Rasmussen wrote:
> On Thu, Feb 19, 2015 at 04:52:41PM +, Peter Zijlstra wrote:
>> On Thu, Jan 15, 2015 at 11:09:25AM +0100, Vincent Guittot wrote:
>> > The average running time of RT tasks is used to estimate the remaining
>> > compute
>> > capacity for CF
Simplify the driver by removing board file support and letting
regulator core to parse DT.
The max77693 regulator driver is used only on Exynos based boards which
are DT-only. Board files for Exynos are not supported.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/max77693.c | 93
The max77693 regulator driver no longer supports board files. Remove the
left-overs. Additionally fix name of device in comment.
Signed-off-by: Krzysztof Kozlowski
---
include/linux/mfd/max77693.h | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/include/linux/mfd/
* Josh Poimboeuf wrote:
> Your upgrade proposal is an *enormous* disruption to the
> system:
>
> - a latency of "well below 10" seconds is completely
> unacceptable to most users who want to patch the kernel
> of a production system _while_ it's in production.
I think this statement is f
On 02/23/2015 01:43 PM, Srinivas Kandagatla wrote:
> Hi Kumar,
>
> Sorry, I should have dropped this patch.. PCIE is still not in the
> mainline.. :-)
>
Srini,
Does it possible to reuse the driver which I'm trying to upstream at [1]
? I'm planing to send v2 soon.
[1] https://lkml.org/lkml/201
On wto, 2015-02-24 at 11:21 +0100, Krzysztof Kozlowski wrote:
> The max77693 regulator driver no longer supports board files. Remove the
> left-overs. Additionally fix name of device in comment.
I just noticed that Lee Jones already acked this:
https://lkml.org/lkml/2015/1/20/552
So if the patchs
(2015/02/24 15:04), Eugene Shatokhin wrote:
> 24.02.2015 06:47, Masami Hiramatsu пишет:
>> No, that is not allowed. I mean, you can do anything you want to do
>> on your handler (enabling preemption/irq etc.) but the result may be
>> not safe (it can crash your kernel, but it's not a kprobes' bug).
* Pavel Machek wrote:
> > More importantly, both kGraft and kpatch are pretty limited
> > in what kinds of updates they allow, and neither kGraft nor
> > kpatch has any clear path towards applying more complex
> > fixes to kernel images that I can see: kGraft can only
> > apply the simplest
On Tuesday 24 February 2015 16:50:18 Mark Brown wrote:
> On Mon, Feb 23, 2015 at 11:01:18PM +0100, Arnd Bergmann wrote:
> > On Saturday 21 February 2015 18:44:58 Mark Brown wrote:
>
> > > In that case a dependency seems wrong, I'd expect to see a select - it's
> > > a bit obscure to have to grovel
Signed-off-by: Daeseok Youn
---
fs/ocfs2/dir.c | 13 +
1 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/fs/ocfs2/dir.c b/fs/ocfs2/dir.c
index c63f2b6..b3ab2a6 100644
--- a/fs/ocfs2/dir.c
+++ b/fs/ocfs2/dir.c
@@ -2043,22 +2043,19 @@ int ocfs2_check_dir_for_entry(struct
The Reduced Serial Bus controller is used to talk to the onboard PMIC.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts
b/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts
in
This patch adds a device node for the Reduced Serial Bus (RSB)
controller and the defacto pinmux setting to the A23 dtsi.
Since there is only one possible pinmux setting for RSB, just
set it in the dtsi.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23.dtsi | 21 +
The RSB controller looks like an SMBus controller which only supports byte
and word data transfers. It can also do double-word data transfers, but the
I2C subsystem does not support this, nor have we seen devices using this.
The RSB differs from standard SMBus protocol on several aspects:
- it use
Hi everyone,
This series adds support for the Reduced Serial Bus (RSB)
controller found on newer Allwinner SoCs, such as the A23
or A80. The RSB is used to communicate with companion ICs,
notably the bundled PMIC.
RSB is an improvement over P2WI that was found on the A31
SoC. The main new feature
Reduced Serial Bus (RSB) is an SMBus like bus used to communicate
with some PMICs (like the AXP223) or other peripherals.
The RSB DT bindings are pretty much the same as the one defined for
the marvell's mv64xxx controller, with the additional RSB specific
"allwinner,rsb-hw-addr" property for slav
On Mon, 23 Feb 2015, Mika Westerberg wrote:
> Lenovo Thinkpad 10 has wacom digitizer connected as a I2C-HID device. Add
> generic support for this.
>
> Signed-off-by: Mika Westerberg
Applied, thanks.
> ---
> drivers/hid/wacom_wac.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git
On 02/23/2015 11:56 PM, Andrew Morton wrote:
On Mon, 23 Feb 2015 14:46:43 -0800 Davidlohr Bueso wrote:
On Mon, 2015-02-23 at 13:58 +0100, Vlastimil Babka wrote:
Recently, there was concern expressed (e.g. [1]) whether the quite aggressive
THP allocation attempts on page faults are a good perf
Commit-ID: 579deee571a755c485ad702ef82c77a98a2ccc05
Gitweb: http://git.kernel.org/tip/579deee571a755c485ad702ef82c77a98a2ccc05
Author: Yannick Guerrini
AuthorDate: Mon, 23 Feb 2015 17:52:38 +0100
Committer: Ingo Molnar
CommitDate: Tue, 24 Feb 2015 08:52:37 +0100
x86/platform/intel-mid:
Commit-ID: 4d3199e4ca8e6670b54dc5ee070ffd54385988e9
Gitweb: http://git.kernel.org/tip/4d3199e4ca8e6670b54dc5ee070ffd54385988e9
Author: Davidlohr Bueso
AuthorDate: Sun, 22 Feb 2015 19:31:41 -0800
Committer: Ingo Molnar
CommitDate: Tue, 24 Feb 2015 08:44:16 +0100
locking: Remove ACCESS_O
On Mon, Feb 23, 2015 at 5:52 PM, Laurent Pinchart
wrote:
> On Sunday 22 February 2015 17:09:06 Vincent Stehlé wrote:
>> LPAE iommu page table makes sense only for ARM architecture. Add the
>> corresponding dependency in Kconfig.
>>
>> This fixes the following runtime warnings on PA-RISC architectu
I have no idea about NFC, but
> +config NFC_FDP
> + tristate "Intel FDP NFC driver"
> + depends on NFC_NCI
> + select CRC_CCITT
> + default n
> + ---help---
> + Intel FDP core driver.
> + This is a driver based on the NCI NFC kernel layers.
> +
> + To compile
Commit bca9690b9426 ("clk: divider: Make generic for usage elsewhere")
returned only the divider value for read-only dividers instead of the
actual rate.
Fixes: bca9690b9426 ("clk: divider: Make generic for usage elsewhere")
Signed-off-by: Heiko Stuebner
---
drivers/clk/clk-divider.c | 2 +-
1 f
On Mon, Feb 23, 2015 at 11:12:22AM -0500, Konrad Rzeszutek Wilk wrote:
> Thank you for posting these patches. I was wondering if you had
> run through some of the different combinations that you can
> load the filesystems/tmem drivers in random order? The #4 patch
> deleted a nice chunk of document
* Jiri Kosina wrote:
> On Sat, 21 Feb 2015, Ingo Molnar wrote:
>
> > (It does have some other requirements, such as making
> > all syscalls interruptible to a 'special' signalling
> > method that only live patching triggers - even syscalls
> > that are under the normal ABI uninterruptible, s
On Tuesday 24 February 2015 18:29:02 Chen-Yu Tsai wrote:
>
> + rsb@01f03400 {
> + compatible = "allwinner,sun8i-a23-rsb";
> + reg = <0x01f03400 0x400>;
> + interrupts = <0 39 4>;
> + clocks = <&apb0_gates 3>;
> + clock-fre
From: Borislav Petkov
We should check the return value of the routines fishing out the proper
microcode and not try to apply if we haven't found a suitable blob.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 14 ++
1 file changed, 10 insertions(+)
From: Borislav Petkov
Hi,
so this is something which got started in the aftermath of a discussion
about some robustifying fixes to the microcode loader by Quentin.
Everyone agrees that current code needs a good rubbing so here's part
one of that. More to come later, let's not overwhelm people wi
On 23 February 2015 at 16:45, Morten Rasmussen wrote:
> On Fri, Feb 20, 2015 at 02:54:09PM +, Vincent Guittot wrote:
>> On 20 February 2015 at 15:35, Morten Rasmussen
>> wrote:
>> > On Fri, Feb 20, 2015 at 02:13:21PM +, Vincent Guittot wrote:
>> >> On 20 February 2015 at 12:52, Morten Ra
From: Borislav Petkov
When doing
echo 1 > /sys/devices/system/cpu/microcode/reload
in order to reload microcode, I get:
microcode: Total microcode saved: 1
BUG: using smp_processor_id() in preemptible [] code: bash/2606
caller is debug_smp_processor_id+0x17/0x20
CPU: 1 PID: 2
From: Borislav Petkov
Shorten variable names and rename it to what it does.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 23 +--
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kernel/cpu/
From: Borislav Petkov
... and do not attempt to load anything in case of error.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kernel/cpu/microcode/intel_early.c
b/
From: Borislav Petkov
... arguments list so that it comes more natural for those functions to
have the signature, processor flags and revision together, before the
rest of the args.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/microcode_intel.h | 5 ++
From: Borislav Petkov
... to revision_is_newer() and push it up into the header and make it an
inline function.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/microcode_intel.h | 8 ++--
arch/x86/kernel/cpu/microcode/intel_early.c | 2 +-
arch/x86/kernel/cpu/microcode/intel_l
From: Borislav Petkov
* remove state variable and out label
* get rid of completely unused mc_size
* shorten variable names
* get rid of local variables
* don't do assignments in local var declarations for less cluttered code
* finally rename it to the shorter and perfectly fine load_microcode_ea
From: Borislav Petkov
... to the header. Split the family acquiring function into a
main one, doing CPUID and a helper which computes the extended
family and is used in multiple places. Get rid of the locally-grown
get_x86_{family,model}().
While at it, rename local variables to something more d
On Thu, Feb 5, 2015 at 4:49 PM, Geert Uytterhoeven
wrote:
> This patch series switches the PCF857x GPIO driver to use the gpiolib
> irqchip helpers, as requested by Linus Walleij, and fixes wake-up by
> propagating the wake-up setting to the parent irq controller.
>
> Note that the conversion to g
Hi,
On 24/02/15 11:37, NeilBrown wrote:
>
>
> commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
> OMAPDSS: rename display-sysfs 'name' entry
>
> broke the xorg X server on my device as it couldn't find the display
> any more. It needs the 'name' file and now there isn't one.
>
> That commit
From: Borislav Petkov
Don't compute start and end from start and size in order to compute size
again down the path in scan_microcode(). So pass size directly instead
and simplify a bunch. Shorten variable names and remove useless ones.
No functionality change.
Signed-off-by: Borislav Petkov
--
From: Borislav Petkov
Shorten local variable names for better readability and flatten loop
indentation levels.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 49 ++---
1 file changed, 23 insertions(+), 26 delet
On 21.02.2015 02:50, Al Viro wrote:
On Fri, Feb 20, 2015 at 03:07:31PM -0800, Andrew Morton wrote:
- It no longer "acquires a reference". All it does is to acquire an rwsem.
- What the heck is a "passive reference" anyway? It appears to be
the situation where we increment s_count without
From: Borislav Petkov
Allocate it on the helper's _load_ucode_intel_bsp() stack instead and do
not hand it down.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/arch/x86/kerne
From: Borislav Petkov
... and only then deref it. Also, shorten some variable names and rename
others so as to diminish the ubiquitous presence of the "mc_" prefix
everywhere and make it a bit more readable.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 37 ++
From: Borislav Petkov
... of microcode patches instead of handing in a pointer which is used
for I/O in an otherwise void function.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/cpu/microcode/intel_early.c | 29 ++---
1 file changed, 14 insertions(+), 15 deletions(
On Tue, Feb 24, 2015 at 01:39:46AM -0800, Arjan van de Ven wrote:
> one of the question is if you want to serialize, or if you just want
> to label. If you take a cookie (could just be a monotonic increasing
> number) at the start of the oops and then prefix/postfix the stack
> printing with that
On Tue, Feb 24, 2015 at 11:33:10AM +0100, Johannes Berg wrote:
> > +config NFC_FDP
> > + tristate "Intel FDP NFC driver"
> > + depends on NFC_NCI
> > + select CRC_CCITT
> > + default n
> > + ---help---
> > + Intel FDP core driver.
> > + This is a driver based on the NCI NFC kernel
This is one of the first places to give out when memory is tight. Handle
it properly rather than with a BUG_ON.
Also fix the comment about the return value, which is an ERR_PTR, not
NULL, on error.
Signed-off-by: Omar Sandoval
---
fs/btrfs/extent-tree.c | 41
Feature detection for pthread_attr_setaffinity_np was failing,
producing this error:
In file included from bench/futex-hash.c:17:0:
bench/futex.h:73:19: error: conflicting types for ‘pthread_attr_setaffinity_np’
static inline int pthread_attr_setaffinity_np(pthread_attr_t *attr,
If io_ctl_prepare_pages fails, the pages in io_ctl.pages are not valid.
When we try to access them later, things will blow up in various ways.
Also fix the comment about the return value, which is an errno on error,
not -1, and update the cases where it was not.
Reviewed-by: Liu Bo
Signed-off-by
On 24/02/15 10:23, Stanimir Varbanov wrote:
On 02/23/2015 01:43 PM, Srinivas Kandagatla wrote:
Hi Kumar,
Sorry, I should have dropped this patch.. PCIE is still not in the
mainline.. :-)
Srini,
Does it possible to reuse the driver which I'm trying to upstream at [1]
Yes, it should be po
Consider the following interleaving of overlapping calls to
alloc_extent_buffer:
Call 1:
- Successfully allocates a few pages with find_or_create_page
- find_or_create_page fails, goto free_eb
- Unlocks the allocated pages
Call 2:
- Calls find_or_create_page and gets a page in call 1's extent_bu
Hi, everyone,
This patch series fixes a few bugs that occur under low memory conditions.
These were exposed by a change in behavior of GFP_NOFS allocations in 3.19-rc7,
by commit 9879de7373fc ("mm: page_alloc: embed OOM killing naturally into
allocation slowpath"). While the mm people sort that ou
Le 24/02/15 08:40, Christian Borntraeger a écrit :
> Am 24.02.2015 um 03:34 schrieb Mike Galbraith:
>> On Mon, 2015-02-23 at 16:43 +0100, Christian Borntraeger wrote:
>>> Am 23.02.2015 um 04:06 schrieb Linus Torvalds:
.. let's see how much, if anything, breaks due to the version number.
P
On Wed, 2015-01-28 at 10:03 +0800, Junjie Mao wrote:
> nl80211_exit should be called in cfg80211_init if cfg80211_init succeeds but
> regulatory_init or create_singlethread_workqueue fails.
Applied, thanks.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
* Jiri Kosina wrote:
> [...] We could optimize the kernel the craziest way we
> can, but hardware takes its time to reinitialize. And in
> most cases, you'd really need to reinitalize it; [...]
If we want to reinitialize a device, most of the longer
initialization latencies during bootup the
On Tue, Feb 24, 2015 at 6:27 PM, Arnd Bergmann wrote:
> On Tuesday 24 February 2015 16:50:18 Mark Brown wrote:
>> On Mon, Feb 23, 2015 at 11:01:18PM +0100, Arnd Bergmann wrote:
>> > On Saturday 21 February 2015 18:44:58 Mark Brown wrote:
>>
>> > > In that case a dependency seems wrong, I'd expect
Hi Gilad,
One more comment :-).
On Thu, 2015-02-19 at 15:54 -0700, Gilad Avidov wrote:
-static int pmic_arb_wait_for_done(struct spmi_controller *ctrl)
+static int pmic_arb_wait_for_done(struct spmi_controller *ctrl,
+ void __iomem *base, u8 sid,
2015-02-24 0:24 GMT+01:00 Rafael J. Wysocki :
> On Sunday, February 22, 2015 01:33:09 PM Jörg Otte wrote:
>> Starting with kernel 3.19.0-05184-g18320f2, I often find my notebook
>> running with 'powersave' policy even if it is on AC.
>>
>> It turned out that /sys/class/ACAD directory is missing and
On 02/24/2015 06:48 PM, Arnd Bergmann wrote:
> On Tuesday 24 February 2015 17:52:01 Chanwoo Choi wrote:
>>
>> But, I have a question.
>> If we put the aliases into the board dts file instaed of SoC dtsi,
>> each board dts file may use the different alias name about same phandle.
>
> Yes, that is t
On Mon, 23 Feb 2015, Mike Turquette wrote:
> Quoting Lee Jones (2015-02-18 08:15:00)
> > Much h/w contain clocks which if turned off would prove fatal. The
> > only way to recover is to restart the board(s). This driver takes
> > references to clocks which are required to be always-on in order t
On Wed, Feb 18, 2015 at 10:20:13PM +0100, Ingo Molnar wrote:
> Do you have any stats about how many such (affected) patch
> sites we have in say the 64-bit defconfig kernel?
It is a good thing I have a tool to dump the alternatives patch sites
and what gets replaced by what. Because now I can cre
2015-02-24 0:18 GMT+01:00 Rafael J. Wysocki :
> On Sunday, February 22, 2015 05:53:11 PM Jörg Otte wrote:
>> When I press backlight keys then normally OSD is shown and
>> backlight follows immediately the keystrokes step by step.
>
> That's how it works in 3.19, right?
Yes.
>
>> Now in v3.20 it be
Hi Prabhakar,
Thanks for the patch!
On Sat, Feb 21, 2015 at 03:22:47PM +, Lad Prabhakar wrote:
> From: Benoit Parrot
>
> this patch adds support for omnivision's ov2659
> sensor, the driver supports following features:
> 1: Asynchronous probing
> 2: DT support
> 3: Media controller support
101 - 200 of 923 matches
Mail list logo
