* Brian Gerst wrote:
> >> So if wakeup_pmode_return is really the first thing called then the whole
> >> premise of shadow descriptor corruption goes out the window: we reload all
> >> relevant segment registers.
> >
> > True, but it still leaves the fact that we're loading __KERNEL_DS instead
> diff --git a/scripts/coccinelle/api/timeout_HZ_dependent.cocci
> b/scripts/coccinelle/api/timeout_HZ_dependent.cocci
> new file mode 100644
> index 000..9ec00cc
> --- /dev/null
> +++ b/scripts/coccinelle/api/timeout_HZ_dependent.cocci
> @@ -0,0 +1,121 @@
> +/// Check for hardcoded numeric ti
>
> On Sat, Jun 13, 2015 at 10:11:34PM +0300, Tomas Winkler wrote:
> > the variables of type mei_cl_device are now cldev
> > the variables of type mei_cl_driver are now cldrv
>
> You are saying what you did, but not why you are doing it. Renaming
> variables for no good reason means I have to
From: Noam Camus
Simple LAN device for debug or management purposes.
Device supports interrupts for RX and TX(completion).
Device does not have DMA ability.
Signed-off-by: Noam Camus
Signed-off-by: Tal Zilcer
Acked-by: Alexey Brodkin
---
Change log for v4:
1) replace macros with generic ones
On Sat, 13 Jun 2015, Jes Sorensen wrote:
> Nicholas Mc Guire writes:
> > scanning for trivial bug-patters with coccinelle spatches returned:
> > ./drivers/staging/rtl8723au/hal/rtl8723a_hal_init.c:1395
> > WARNING: condition with no effect (if branch == else)
> >
> > drivers/staging/rtl8723au
Slimbus devices use value-element, and information elements to
control device parameters (e.g. value element is used to represent
gain for codec, information element is used to represent interrupt
status for codec when codec interrupt fires).
Messaging APIs are used to set/get these value and infor
OF helper routine scans the SLIMbus DeviceTree, allocates resources,
and creates slim_devices according to the hierarchy.
Signed-off-by: Sagar Dharia
---
drivers/slimbus/slimbus.c | 77 +++
include/linux/slimbus.h | 19
2 files changed,
SLIMbus (Serial Low Power Interchip Media Bus) is a specification
developed by MIPI (Mobile Industry Processor Interface) alliance.
SLIMbus is a 2-wire implementation, which is used to communicate with
peripheral components like audio-codec.
SLIMbus uses Time-Division-Multiplexing to accommodate mu
SLIMbus (Serial Low Power Interchip Media Bus) is a specification
developed by MIPI (Mobile Industry Processor Interface) alliance.
SLIMbus is a 2-wire implementation, which is used to communicate with
peripheral components like audio-codec.
SLIMbus uses Time-Division-Multiplexing to accommodate mu
Hello, Christoph.
On Sat, Jun 13, 2015 at 09:16:08AM -0700, Christoph Hellwig wrote:
> On Fri, Jun 12, 2015 at 04:57:33PM -0500, Tejun Heo wrote:
> > FS_CGROUP_WRITEBACK indicates whether a file_system_type supports
> > cgroup writeback; however, different super_blocks of the same
> > file_system_
> On 12 June 2015 at 19:17 Joe Perches wrote:
>
>
> On Fri, 2015-06-12 at 18:58 +0200, Fabian Frederick wrote:
> > Use kernel.h macro definition.
>
> A lot of these conversions seem to be for bubble sorts.
> Maybe it'd be useful to add a generic one somewhere.
Of course but those swap() convers
This patch add the needed clocks into power-controller.
There are several reasons as follows:
Firstly, the clocks need be turned off to save power when
the system enter the suspend state. So we need to enumerate the clocks
in the dts. In order to power domain can turn on and off.
Secondly, the r
At the moment, we can support these power-domain type on RK3288.
We can add more types on RK3288 in the future, that's need to do.
Signed-off-by: Caesar Wang
---
Changes in v15:
- change the comment.
Changes in v9: None
include/dt-bindings/power-domain/rk3288.h | 11 +++
1 file chang
In order to meet high performance and low power requirements, a power
management unit is designed or saving power when RK3288 in low power
mode.
The RK3288 PMU is dedicated for managing the power ot the whole chip.
Signed-off-by: jinkun.hong
Signed-off-by: Caesar Wang
---
Changes in v15:
- As
Add power domain drivers based on generic power domain for
Rockchip platform, and support RK3288.
Verified on url =
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/v3.14
The following is the easy example.
vopb: vop@ff93 {
compatible = "rockchip,rk3288-vop";
...
This add the necessary binding documentation for the power domain
found on Rockchip Socs.
Signed-off-by: jinkun.hong
Signed-off-by: Caesar Wang
---
Changes in v15: None
Changes in v9:
- add document decription.
Series-changes:8
- document go back to v2.
Series-changes:3
- DT structure has chan
Dear Winner,
You have been awarded the sum of 8,000,000.00 (Eight Million Pounds sterling)
with reference number 77100146. This compensation funds from the United
Nation.Send us your personal details to deliver your funds.
Gloria Peter
--
To unsubscribe from this list: send the line "unsubscri
From: Joglekar Tejas
This patch removes the warning "space prohibited between
function name and open parenthesis"given by checkpatch.pl
Signed-off-by: Joglekar Tejas
---
drivers/staging/rtl8723au/core/rtw_ap.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/
On Sun, 2015-06-14 at 11:13 +0800, Daniel J Blueman wrote:
> On Sunday, June 14, 2015 at 4:00:06 AM UTC+8, Christoph Fritz wrote:
> > Hi,
> >
> > on following computer configuration, I do get hard lockup under heavy
> > IO-Load (using rsync):
> >
> > - CONFIG_HIGH_RES_TIMERS=y
> > - CPU: AMD FX(
2014-03-26 19:07 GMT+09:00 Robert Baldyga :
> This patch adds IRQ line specification for the MAX8997 chip and necessary
> pinctrl group to configure pull-up and driver strength of the pin.
> It's needed for proper handling of IRQs coming from MAX8997 multifunction
> device (IRQs are used by PMIC, M
Dear Winner,
You have been awarded the sum of 8,000,000.00 (Eight Million Pounds sterling)
with reference number 77100146. This compensation funds from the United
Nation.Send us your personal details to deliver your funds.
Gloria Peter
--
To unsubscribe from this list: send the line "unsubscri
On 06/13/2015 04:05 AM, Waiman Long wrote:
On 06/12/2015 08:31 AM, Stephen Smalley wrote:
On 06/12/2015 02:26 AM, Raghavendra K T wrote:
On 06/12/2015 03:01 AM, Waiman Long wrote:
The inode_free_security() function just took the superblock's isec_lock
before checking and trying to remove the i
On Thu, Jun 11, 2015 at 8:13 PM, Rob Herring wrote:
> On Thu, Jun 11, 2015 at 7:37 PM, Stephen Boyd wrote:
>> Add support for over current protection (OCP), pin control
>> selection, soft start and soft start strength, auto-mode, input
>> current limiting, and pull down.
>>
>> Cc:
>> Signed-off-
Dear Winner,
You have been awarded the sum of 8,000,000.00 (Eight Million Pounds sterling)
with reference number 77100146. This compensation funds from the United
Nation.Send us your personal details to deliver your funds.
Gloria Peter
--
To unsubscribe from this list: send the line "unsubscri
Ulf,
Thanks for your comments.:-)
在 2015年05月28日 18:38, Ulf Hansson 写道:
On 24 April 2015 at 10:07, Caesar Wang wrote:
In order to meet high performance and low power requirements, a power
management unit is designed or saving power when RK3288 in low power
mode.
The RK3288 PMU is dedicated f
From: Joglekar Tejas
This patch removes the error given by checkpatch.pl
" spaces required around that '>' "
Signed-off-by: Joglekar Tejas
---
drivers/staging/rtl8723au/os_dep/ioctl_cfg80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723au/os_dep/
On 14 June 2015 at 02:30, Jonathan Cameron wrote:
> On 11/06/15 09:22, Gergely Imreh wrote:
>> The Xilinx XADC driver has both a temperature channel and 8 voltage
>> channels. The voltage channels have no offset, but actually were still
>> set the same offset as the temperature channel. This did n
On Sunday, June 14, 2015 at 4:00:06 AM UTC+8, Christoph Fritz wrote:
> Hi,
>
> on following computer configuration, I do get hard lockup under heavy
> IO-Load (using rsync):
>
> - CONFIG_HIGH_RES_TIMERS=y
> - CPU: AMD FX(tm)-8350 Eight-Core Processor (family 0x15 model 0x2)
> - Motherboard: 'GA
Hi Linus,
I apologize for the tardiness of this request. Below are a couple of last
minute NTB bug fixes for v4.1. Please consider pulling them.
Thanks,
Jon
The following changes since commit d4a4f75cd8f29cd9464a5a32e9224a91571d6649:
Linux 4.1-rc7 (2015-06-07 20:23:50 -0700)
are available i
On 06/11/2015 11:06 PM, Frederic Weisbecker wrote:
> This is a leftover from old days to avoid conflicts with dynticks idle
> code. Now full dynticks and idle dynticks are better integrated and
> interact without known issue.
I am sorry but I fail to understand why the check on idle task was there
On 06/13, Tycho Andersen wrote:
>
> This patch is the first step in enabling checkpoint/restore of processes
> with seccomp enabled.
So just in case, I am fine with this version.
> One of the things CRIU does while dumping tasks is inject code into them
> via ptrace to collect information that is
Dear Sir/Ma,
I need your consent to transfer $25.5M that has remained unclaimed since 1999.
The funds will be moved to any of our correspondent Banks in "YOUR NAME"
immediately to secure the funds first. The Principal will be shared on a 50/50
basis.
Yours Faithfully,
Mr. Harrison Ken.
--
To u
Hey, Petr.
On Fri, Jun 12, 2015 at 03:24:40PM +0200, Petr Mladek wrote:
> > * While hibernating, freezing writeback workers and whoever else which
> > might issue IOs. This is because we have to thaw devices to issue
> > IOs to write out the prepared hibernation image. If new IOs are
> > i
Mischa, Vineet,
Looking at ARC PMU driver I've got an impression that its static arc_pmu
is left uninitialized, which possibly leads to Oops once registered
callbacks are invoked. I don't have neither ARC toolchain nor hardware to
test it, so I may be missing something. Below is the fix for it.
T
Hello.
On 06/12/2015 04:30 PM, Pankaj Gupta wrote:
Macvtap should be compatible with tuntap for maximum number
of queues. '1059590254fa9dce9cafc4f07d1103dbec415e76' removes
Please also specify that commit's summary line in parens.
the limitation and increases number of queues in tuntap.
Nicholas Mc Guire writes:
> scanning for trivial bug-patters with coccinelle spatches returned:
> ./drivers/staging/rtl8723au/hal/rtl8723a_hal_init.c:1395
> WARNING: condition with no effect (if branch == else)
>
> drivers/staging/rtl8723au/hal/rtl8723a_hal_init.c - line numbers from 4.1-rc7
On Sat, Jun 13, 2015 at 04:34:00PM +0300, Dmitry Kalinkin wrote:
> This reorders patches so that Greg can take first three, while fourth awaits
> maintainer's approval.
>
> Dmitry Kalinkin (4):
> staging: vme_user: remove forward declarations
> staging: vme_user: remove open/release
> stagin
The semantic patch below considers the problem from another point of view,
to find functions that may have a handler as an argument. The results
that are different than those considered already are as follows:
arch/x86/platform/uv/uv_irq.c:106 irq_domain_set_info
has a possible handler
On Sat, Jun 13, 2015 at 2:23 PM, Andy Lutomirski wrote:
> On Sat, Jun 13, 2015 at 12:03 AM, Ingo Molnar wrote:
>>
>> * Brian Gerst wrote:
>>
>>> On Fri, Jun 12, 2015 at 4:36 AM, Ingo Molnar wrote:
>>> >
>>> > * H. Peter Anvin wrote:
>>> >
>>> >> %es is used implicitly by string instructions.
>
On Sat, Jun 13, 2015 at 10:11:39PM +0300, Tomas Winkler wrote:
> Always call mei_cl_register_event_cb explicitly so the events
> are enabled only when needed. The nfc driver is already using
> it that way so no need for further changes.
This doesn't seem to match up with the code being changed her
On Sat, Jun 13, 2015 at 10:11:38PM +0300, Tomas Winkler wrote:
> 1. Rename uevent handler to mei_cl_device_uevent
> 2. Add kdoc for uevent and mod alias functions
2 things in one patch? No, please make these separate patches.
And why add kdoc to static functions? That makes no sense.
greg k-h
On Sat, Jun 13, 2015 at 10:11:37PM +0300, Tomas Winkler wrote:
> To make the file more organize move mei client driver api
> to the start of the file and add Kdoc
>
> There are no functional changes in this patch
/me hands Tomas some extra '.' characters to use in changelogs...
--
To unsubscribe
On Sat, Jun 13, 2015 at 10:11:36PM +0300, Tomas Winkler wrote:
> In nfc.c we just create device name on the mei client bus
> we make it more generic in the following patches
That doesn't make sense, please reword to justify renaming the file.
greg k-h
--
To unsubscribe from this list: send the li
On Sat, Jun 13, 2015 at 10:11:35PM +0300, Tomas Winkler wrote:
> Signed-off-by: Tomas Winkler
No changelog entry? Sorry, can't accept it.
And why are you doing this patch? renames for no reason isn't ok.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
On Sat, Jun 13, 2015 at 10:11:34PM +0300, Tomas Winkler wrote:
> the variables of type mei_cl_device are now cldev
> the variables of type mei_cl_driver are now cldrv
You are saying what you did, but not why you are doing it. Renaming
variables for no good reason means I have to reject this patch
Hi Caesar,
Am Dienstag, 9. Juni 2015, 17:49:56 schrieb Caesar Wang:
> Verified on url =
>
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos->
> 3.14 Tested by 179200 cycles are pass with CPU up/dowm test scripts.
I've applied this series to my soc branch for 4.3 ..
Add a new options to gpio Kconfig, CONFIG_GPIO_TRACING, that is used
for enabling/disabling compilation of gpio function trace events.
Signed-off-by: Tal Shorer
---
drivers/gpio/Kconfig| 6 ++
include/trace/events/gpio.h | 4
2 files changed, 10 insertions(+)
diff --git a/drive
Allow a trace events header file to disable compilation of its
trace events by defining the preprocessor macro NOTRACE.
This could be done, for example, according to a Kconfig option.
Signed-off-by: Tal Shorer
---
include/linux/tracepoint.h | 6 +++---
include/trace/define_trace.h | 2 +-
2 f
Currently, enabling CONFIG_TRACING on a system comes as all-or-nothing: either
tracepoints for all subsystems are compiled (with CONFIG_TRACING) or none of
them do (without it).
This caused me an unacceptable performance penalty (obviously SOME penalty was
expected, but not one so severe) which ma
On Sat, 2015-06-13 at 22:19 +0200, Heinz Diehl wrote:
> On 13.06.2015, Christoph Fritz wrote:
>
> > - add kernel parameter "idle=halt" -> system runs fine
> > - disable CONFIG_HIGH_RES_TIMERS -> system runs fine
> > - change motherboard and disable C1E -> system runs fine
> > - change CPU to
On Sat, 13 Jun 2015, Thomas Gleixner wrote:
> On Sat, 13 Jun 2015, Julia Lawall wrote:
>
> > The following are the cases that require some manual attention, either
> > because the handler is a local variable or because it is some other kind
> > of expression.
>
> yep, found it in the logs al
On Sat, 13 Jun 2015, Julia Lawall wrote:
> The following are the cases that require some manual attention, either
> because the handler is a local variable or because it is some other kind
> of expression.
yep, found it in the logs already and found a missing search expression:
|
gpiochip_set_
On 13.06.2015, Christoph Fritz wrote:
> - add kernel parameter "idle=halt" -> system runs fine
> - disable CONFIG_HIGH_RES_TIMERS -> system runs fine
> - change motherboard and disable C1E -> system runs fine
> - change CPU to AMD Phenom II X6 Processor -> system runs fine
I encountered quit
The following are the cases that require some manual attention, either
because the handler is a local variable or because it is some other kind
of expression.
julia
Local variable: arch/x86/kernel/apic/io_apic.c:932 hdl
Local variable: arch/sparc/kernel/leon_kernel.c:232 flow_handler
Local vari
Attached International Basic Sciences Programmer (IBSP) Award Letter for Claim
Mr. F. T. Fagebuder
2015 IBSP PROJECT LETTER.pdf
Description: Adobe PDF document
Hi,
on following computer configuration, I do get hard lockup under heavy
IO-Load (using rsync):
- CONFIG_HIGH_RES_TIMERS=y
- CPU: AMD FX(tm)-8350 Eight-Core Processor (family 0x15 model 0x2)
- Motherboard: 'GA-970A-UD3P (rev. 1.0)' AMD 970/SB950
- BIOS: C1E enabled (on 'GA-970A-UD3P' there
A while back, the message queue implementation in the kernel was
improved to use btrees to speed up retrieval of messages (commit
d6629859b36). The patch introducing the improved kernel handling of
message queues has, as a by-product, changed the meaning of the
QSIZE field in the pseudo-file creat
On 06/13, Ingo Molnar wrote:
>
> @@ -169,29 +169,40 @@ void sync_global_pgds(unsigned long start, unsigned
> long end, int removed)
>
> for (address = start; address <= end; address += PGDIR_SIZE) {
> const pgd_t *pgd_ref = pgd_offset_k(address);
> - struct page *pa
Mika Westerberg wrote:
> On Thu, Jun 11, 2015 at 02:08:22AM +0200, Tobias Diedrich wrote:
> > In create_gpio_led only the legacy pass propagates the label by passing it
> > into
> > devm_gpio_request_one.
> >
> > On the newer devicetree/acpi path the label is lost as far as the GPIO
> > subsystem
we will need this simplification when name build will
be just part of the fixup rutine
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus-fixup.c | 116 ---
drivers/misc/mei/bus.c | 2 +-
drivers/misc/mei/mei_dev.h | 2 +-
3 files changed, 5
1. Rename uevent handler to mei_cl_device_uevent
2. Add kdoc for uevent and mod alias functions
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 43 +++
1 file changed, 39 insertions(+), 4 deletions(-)
diff --git a/drivers/misc/mei/bus.c b/driver
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 36 ++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index fa3eff216eff..33898bed6209 100644
--- a/drivers/misc/mei/bus.c
+++ b/drivers/misc
MEI bus was designed around nfc and was hard to extend.
Instead of the hard coded way of adding the devices on the mei bus
we scan the whole me client list and create a device for each
eligible me client (mei_cl_bus_rescan); currently we support
only clients with single connection and fixed address
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index 9069d89b93d7..5bd16d4417bb 100644
--- a/drivers/misc/mei/bus.c
+++ b/drivers/misc/mei/bus.c
@@ -255,6 +255,8 @@ vo
We split the device registration to allocation and device struct
initialization , setup, and final registration.
This way we can run fixups and quirks during the setup stage on
an initialized device. If a fixup sets do_match flag to false
the device won't be registered on the bus.
Signed-off-by: T
Instead of holding the list of host clients (me_cl)
we want to keep the list me client devices (mei_cl_device)
This way we may postpone the creating of connection only when needed
Add list head to mei_cl_device and cl_bus_lock
Add bus_added flag to the me client (mei_me_client) to track if
the appr
Add reference to the bus device (mei_device) for easier access.
To ensures that referencing cldev->bus is valid during cldev life time
we increase the bus ref counter on a client device creation and drop it
on the device release.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 17 +
Currently we support only clients with single connection
and fixed address clients so all other clients are blacklisted
Blacklist nfc info client which is only used for retrieval
of the NFC radio version
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus-fixup.c | 42
Instead of generating device id on the fly during probing we
find the matching id entry on the device id table.
Get bus the module reference counter so it cannot
be unloaded after the driver has bounded to the client
device
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 41 +++
Always call mei_cl_register_event_cb explicitly so the events
are enabled only when needed. The nfc driver is already using
it that way so no need for further changes.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/misc/mei/b
mei_cl_device_match now calls mei_cl_device_find that returns
the matching device id in the device id table
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 63 +++---
1 file changed, 44 insertions(+), 19 deletions(-)
diff --git a/drivers/mis
MEI bus was designed around nfc and was hard to extend.
Instead of hard coded way of adding the devices on the mei bus
we scan whole me client list and create a device for each
eligible me client
Tomas Winkler (17):
MAINTAINERS: mei: add mei_cl_bus.h to maintained file list
mei: bus: fix driv
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 4 ++--
drivers/misc/mei/init.c| 2 +-
drivers/misc/mei/mei_dev.h | 5 ++---
drivers/misc/mei/nfc.c | 4 ++--
4 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/drivers/misc/mei/bus.c b/drivers/misc/mei/bus.c
index
mei_cl_bus.h was overlooked when we added the mei bus
Signed-off-by: Tomas Winkler
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f6ba62c3db82..c58e2f0612e7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5279,6 +5279,7 @@ M:Tomas Winkl
To make the file more organize move mei client driver api
to the start of the file and add Kdoc
There are no functional changes in this patch
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 798 +++--
1 file changed, 443 insertions(+), 355 d
In nfc.c we just create device name on the mei client bus
we make it more generic in the following patches
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/Makefile | 2 +-
drivers/misc/mei/{nfc.c => bus-fixup.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename drivers/
the variables of type mei_cl_device are now cldev
the variables of type mei_cl_driver are now cldrv
the variables of type mei_device are now bus in the
bus layer context
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/bus.c | 272 ++---
drivers/misc/
I didn't read v2 yet, but I'd like to ask a question.
Why do we need vmalloc_sync_all()?
It has a single caller, register_die_notifier() which calls it without
any explanation. IMO, this needs a comment at least.
I am not sure I understand the changelog in 101f12af correctly, but
at first glance
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
A single fix for an off by one bug in the sunxi irqchip driver.
Thanks,
tglx
-->
Axel Lin (1):
irqchip: sunxi-nmi:
2015-04-24 10:27 GMT-07:00 Florian Fainelli :
> MIPS64 kernels builds will produce a vmlinux.32 kernel image for
> compatibility, ignore them.
Ralf, Michal, which one of you should take this patch?
>
> Signed-off-by: Florian Fainelli
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
SI5338 is a programmable clock generator. It has 4 sets of inputs,
PLL, multisynth and dividers to make 4 outputs. This driver splits
them into multiple clocks to comply with common clock framework.
See Documentation/devicetree/bindings/clock/silabs,si5338.txt for
details.
Signed-off-by: York Sun
On Sat, Jun 13, 2015 at 9:21 PM, Jonathan Cameron wrote:
> On 12/06/15 08:40, Vlad Dogaru wrote:
>> On Thu, Jun 11, 2015 at 06:49:34PM +0300, Daniel Baluta wrote:
>>> Because of the ABI confusion proximity value exposed by SX9500
>>> was inverted.
>>>
>>> Signed-off-by: Daniel Baluta
>>
>> Review
On 11/06/15 09:22, Gergely Imreh wrote:
> The Xilinx XADC driver has both a temperature channel and 8 voltage
> channels. The voltage channels have no offset, but actually were still
> set the same offset as the temperature channel. This did not cause
> problems in /sys/bus/iio/ but can cause probl
Am 12.06.2015 um 13:36 schrieb Alexander Holler:
Am 12.06.2015 um 13:19 schrieb Alexander Holler:
Am 12.06.2015 um 09:25 schrieb Linus Walleij:
On Thu, Jun 11, 2015 at 6:40 PM, Alexander Holler
wrote:
Am 11.06.2015 um 14:30 schrieb Linus Walleij:
Certainly it is possible to create deadlock
On Sat, Jun 13, 2015 at 1:57 AM, Borislav Petkov wrote:
> On Fri, Jun 12, 2015 at 04:44:53PM -0700, Andy Lutomirski wrote:
>> Now that there is no paravirt TSC, the "native" is inappropriate.
>> The fact that rdtsc is not ordered can catch people by surprise, so
>> call it rdtsc_unordered().
>>
>>
On Sat, Jun 13, 2015 at 2:02 AM, Borislav Petkov wrote:
> On Fri, Jun 12, 2015 at 04:44:55PM -0700, Andy Lutomirski wrote:
>> barrier_before_rdtsc(); rdtsc_unordered() is an unnecessary mouthful and
>> requires more thought than should be necessary. Add an rdtsc_ordered()
>> helper and replace th
On Sat, Jun 13, 2015 at 12:03 AM, Ingo Molnar wrote:
>
> * Brian Gerst wrote:
>
>> On Fri, Jun 12, 2015 at 4:36 AM, Ingo Molnar wrote:
>> >
>> > * H. Peter Anvin wrote:
>> >
>> >> %es is used implicitly by string instructions.
>> >
>> > Ok, so we are probably better off reloading ES as well ear
On 12/06/15 08:40, Vlad Dogaru wrote:
> On Thu, Jun 11, 2015 at 06:49:34PM +0300, Daniel Baluta wrote:
>> Because of the ABI confusion proximity value exposed by SX9500
>> was inverted.
>>
>> Signed-off-by: Daniel Baluta
>
> Reviewed-by: Vlad Dogaru
>
> Sorry for causing the confusion, it was t
From: Alexander Usyskin
The FW resets the flow control for single buffer clients when the last
host client disconnects, also the driver has to follow this policy and
zero the flow control counter in such case.
Cc: #4.1
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers
On 06/13, Ingo Molnar wrote:
>
> * Oleg Nesterov wrote:
>
> > > So we could add tsk->mm_leader or so,
> >
> > No, no, please do not. Just do something like
> >
> > for_each_process(p) {
> >
> > for_each_thread(p, t) {
>
> So far that's what the for_each_process_thread() iterations
On 12/06/15 16:10, Adriana Reus wrote:
> Export the available scales for accel and gyro in order
> to hint the user-space as to what are the available valid values.
>
> Signed-off-by: Adriana Reus
Applied to the togreg branch of iio.git - initially pushed out
as testing for the autobuilders to pl
On 11/06/15 18:31, Ge Gao wrote:
> These code looks good to me.
> Thanks.
>
> Best Regards,
>
> Ge GAO
Ge, formal Ack definitely preferred, but thanks for taking a look.
Adriana, please put fixes at the start of such a series. It didn't
matter here as the two changes were non overlapping but th
Something prevents me from following the thread, replying to myself.
> В Sat, 14 Mar 2015 20:20:38 -0700
> Dmitry Torokhov wrote:
>
> >
> > Hi Roman,
> >
> > On Mon, Feb 16, 2015 at 12:11:43AM +0300, Roman Volkov wrote:
> > > Documentation for 'intel,8042' DT compatible node.
> > >
> >
On 06/13, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > * Oleg Nesterov wrote:
> >
> > >
> > > Afaics, we need to ensure that:
> > >
> > > > + if (pgd_val(*pgd_src))
> > > > + WRITE_ONCE(*pgd_dst, *pgd_src);
> > >
> > > either we notice the
Hi Jari,
On Sat, Jun 13, 2015 at 07:01:31PM +0300, Jari Ruusu wrote:
> When Al Viro's VFS deadlock fix "deal with deadlock in d_walk()" was
> backported to 3.10.y 3.4.y and 3.2.y stable kernel brances, the deadlock fix
> was copied to 3 different places. Later, a bug in that code was discovered.
>
On Sat, 2015-06-13 at 09:28 -0700, Greg KH wrote:
> On Sat, Jun 13, 2015 at 02:16:18PM +0530, Sudip Mukherjee wrote:
[]
> > Your reply above was for a different thread but my doubt started from
> > this. I was working on adding the Dual-Head support to sm7xxfb. So that
> > is also a new functionali
On Fri, Jun 12, 2015 at 7:52 PM, Rafael J. Wysocki wrote:
> Below is a more sophisticated, so to speak, version of it with a changelog and
> all. It works for me, but more testing would be much appreciated.
Great, I'm convinced by your reasoning that this makes sense. I'm
building 3.10.80 patch
On 2015/6/13 22:53, Julia Lawall wrote:
> Better formatted diff.
Great thanks to you, Julia!
It seems really attractively, I will try to figure out
whether I have caught all the cases.
BTW, a new version of these patch set has been posted at:
http://comments.gmane.org/gmane.linux.kernel.pci/42320
Hi experts,
I have trouble about interrupt. I need low level trigger the interrupt. My
control flow is that when data is less than a threshold, it needs keeping
interrupt until data is supplied.
So I use the flag `IRQ_TYPE_LEVEL_LOW `, but it doesn’t work. I have also tried
`IRQF_TRIGGER_LOW
On Sat, Jun 13, 2015 at 02:16:18PM +0530, Sudip Mukherjee wrote:
> On Fri, Jun 12, 2015 at 05:18:49PM -0700, Greg KH wrote:
> > On Tue, Jun 09, 2015 at 04:59:01PM -0500, J. German Rivera wrote:
> > > This patch series includes new functionality for the Freescale fsl-mc
> > > bus driver.
> >
> > Wh
1 - 100 of 184 matches
Mail list logo