Michal Hocko wrote:
> As this behavior is established for many years we cannot change it
> immediately. This patch instead exports a new sysctl/proc knob which
> tells allocator how much to retry. The higher the number the longer will
> the allocator loop and try to trigger OOM killer when the
s/receveiver/receiver/
Signed-off-by: Nicolas Iooss
---
samples/kdbus/kdbus-workers.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/samples/kdbus/kdbus-workers.c b/samples/kdbus/kdbus-workers.c
index d1d8f7a7697b..d331e0186899 100644
--- a/samples/kdbus/kdbus-workers.c
On Sat, 2015-03-14 at 23:44 +, Ian Malone wrote:
> On 18 January 2014 at 16:14, Mike Galbraith wrote:
> > On Sat, 2014-01-18 at 10:33 +0100, Mike Galbraith wrote:
> >> On Fri, 2014-01-17 at 05:20 +0100, Mike Galbraith wrote:
>
> > Signed-off-by: Mike Galbraith
> > Cc: # 3.10+
> > ---
> >
MyungJoo Ham writes:
> On Fri, May 23, 2014 at 1:52 PM, MyungJoo Ham
> wrote:
>> On Thu, May 22, 2014 at 5:37 AM, Paul Bolle wrote:
>>> Checks for CONFIG_EXYNOS_ASV were added in v3.3. But the related Kconfig
>>> symbol has never been added to the tree. Remove these checks, as they
>>> always
Hi Roman,
On Mon, Feb 16, 2015 at 12:11:43AM +0300, Roman Volkov wrote:
> Documentation for 'intel,8042' DT compatible node.
>
> Signed-off-by: Tony Prisk
> Signed-off-by: Roman Volkov
> ---
> .../devicetree/bindings/input/intel-8042.txt | 26
> ++
> 1 file changed,
Dear Friend,
Good Day, I am Dr. Henry Cheng Kar-shun a Director of Non Independent
Non-executive Board Hang Seng Bank Limited, Hong Kong. I have funds worth
$17,500.000.00 to secretly secure (Transfer)
to your account in your country from our affiliated bank for our benefit.
Please if you
Thomas,
Here's a round of fixes for v4.0. They've been in -next for a week without
issue. Please pull.
Linus,
I've heard that Thomas isn't available. I have no other specifics. If you
know his absence is going to last for a while, please consider pulling this
directly. I'd hate to miss
Dear Sir/Madam,
Please refer to the attached PDF document. It is a very important
letter. Please read the letter very carefully, word by word.
The letter details how the Singapore Government led by Prime Minister
Lee Hsien Loong has *subtly* denied me medical treatment for
***SUSPECTED***
On Sat, 2015-03-14 at 15:39 -0700, Davidlohr Bueso wrote:
> + if (test_and_set_mm_exe_file(mm, exefd.file))
> + return 0;
> + return -EPERM;
Bah, this is obviously bogus. We'd need the following folded in:
diff --git a/kernel/sys.c b/kernel/sys.c
index a82d0c4..41b27bd 100644
On 3/14/15 4:51 PM, Daniel Borkmann wrote:
On 03/14/2015 04:55 PM, Alexei Starovoitov wrote:
...
so from there I saw two options: either copy paste all
build_bug_on and have the same *insn=... and build_bug_on in
two places or consolidate them in single helper function.
Obviously single helper
I've had some feedback on a couple of these, so I'll repost a new
version within the next couple of days. Please hold off review until
then.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, Mar 11, 2015 at 11:21:31PM -0700, Stephen Boyd wrote:
> In a uniprocessor implementation the interrupt processor targets
> registers are read-as-zero/write-ignored (RAZ/WI). Unfortunately
> gic_get_cpumask() will print a critical message saying
>
> GIC CPU mask not found - kernel will
On Sun, Mar 15, 2015 at 01:39:21AM +0100, Alexander Holler wrote:
> Am 13.03.2015 um 17:42 schrieb Al Viro:
> > Assorted fixes around AIO on gadgetfs: leaks, use-after-free,
> > troubles caused by ->f_op flipping. Please, pull from
> >
On Sat, 2015-03-14 at 18:03 -0700, Davidlohr Bueso wrote:
> Good analysis, but not quite accurate for one simple fact: mutex
> trylocks _only_ use fastpaths (obviously just depend on the counter
> cmpxchg to 0), so you never fallback to the slowpath you are mentioning,
> thus the race is non
On Sun, 2015-03-15 at 01:05 +0200, Matthias Bonne wrote:
> On 03/10/15 15:03, Yann Droneaud wrote:
> > Hi,
> >
> > Le mercredi 04 mars 2015 à 02:13 +0200, Matthias Bonne a écrit :
> >
> >> I am trying to understand how mutexes work in the kernel, and I think
> >> there might be a race between
Am 13.03.2015 um 17:42 schrieb Al Viro:
> Assorted fixes around AIO on gadgetfs: leaks, use-after-free,
> troubles caused by ->f_op flipping. Please, pull from
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git gadget
>
> Shortlog:
> Al Viro (8):
> new helper: dup_iter()
>
Correct the indentation of two lines in rtw_tkip_encrypt23a function in
rtl8723au's rtw_security.c.
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Adjust the whitespace in the signature, local variable declaration and
initialization parts of a number of functions to increase readability
in rtl8723au's rtw_security.c.
v2: Make sure that the arcfour_encrypt function's argument list is split
according to the kernel code style.
Correct a number of "space(s) required before/around/after" checkpatch.pl
issues in a number of functions in rtl8723au's rtw_security.c.
v2: Correct one more whitespace issue ("length-4") in
rtw_tkip_decrypt23a.
Signed-off-by: M. Vefa Bicakci
---
These commits address a number of checkpatch.pl warnings and errors
in rtl8723au's rtw_security.c.
Prior to this set of commits, checkpatch.pl reported the following:
total: 77 errors, 138 warnings, 1621 lines checked
After applying this set of commits, checkpatch.pl reports the
Correct a typo in rtl8723au's rtw_security.c which was most likely
caused by a copy and paste mistake. Prior to this commit, the TKIP
decryption function referred to WEP in its trace log output.
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 2 +-
1 file
Prior to this commit, a large block of constants used to represent
an AES S-box table were indented with spaces in rtl8723au's
rtw_security.c. Correct the checkpatch.pl warnings indicating that
spaces should not be used to indent lines:
WARNING: please, no spaces at the start of a line
Correct a number of checkpatch.pl warnings in rtl8723au's rtw_security.c
related to the existence of unnecessary curly braces around single
statement blocks:
WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: M. Vefa Bicakci
---
On 14/03/15 05:55 PM, Joe Perches wrote:
> On Sat, 2015-03-14 at 16:16 -0400, M. Vefa Bicakci wrote:
>> On 13/03/15 12:24 PM, Joe Perches wrote:
>>> On Fri, 2015-03-13 at 10:44 -0500, Larry Finger wrote:
On 03/12/2015 10:15 PM, M. Vefa Bicakci wrote:
> Improve the readability of an if
Correct a number of checkpatch.pl errors in rtl8723au's rtw_security.c
related to trailing statements:
ERROR: trailing statements should be on next line
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 25 +
1 file changed, 17
Correct two instances of the checkpatch.pl error indicating that the
opening curly braces should not be on new lines:
ERROR: that open brace { should be on the previous line
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 6 ++
1 file changed, 2
As the subject indicates, adjust whitespace in and around comments
in rtl8723au's rtw_security.c.
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 114 +-
1 file changed, 57 insertions(+), 57 deletions(-)
diff --git
Correct a number of indentation-with-spaces-and-tabs issues in
rtl8723au's rtw_security.c, according to checkpatch.pl:
WARNING: suspect code indent for conditional statements
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 36
Prior to this commit, rtl8723au's rtw_security.c had two instances of
byte array comparisons (for CRC checks) where the individual elements
of the byte arrays were compared one by one and an error trace would
be output if the byte arrays were determined to be different.
This commit improves the
This commit removes a number of unneeded comments. Two of the
aforementioned comments were most likely meant to aid with version
control, whereas the remaining two comments relate to (now unused)
local variable names.
Signed-off-by: M. Vefa Bicakci
---
Prior to this commit, a static integer named bcrc32initialized in
rtl8723au's rtw_security.c was explicitly initialized to zero, even
though this is not necessary. Remove the unneeded initialization.
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c | 2 +-
1 file
Correct a checkpatch.pl warning regarding rtl8723au's
rtw_security.c::crc32_init pointing out that having an else statement
after a break or a return is not useful.
drivers/staging/rtl8723au/core/rtw_security.c:105:
WARNING: else is not generally useful after a break or return
Prior to this commit, functions rtw_tkip_encrypt23a and rtw_tkip_decrypt23a had
large if blocks which contained the majority of the logic in the functions.
Rework these functions so that if the negated version of the aforementioned if
blocks' conditions are true, we return from the function with
Correct checkpatch.pl errors in rtl8723au's rtw_security.c indicating
that an else statement should follow the closing brace of the previous
if/else if code block:
ERROR: else should follow close brace '}'
Signed-off-by: M. Vefa Bicakci
---
drivers/staging/rtl8723au/core/rtw_security.c
Optional fields are set to -1 by various preprocessor macros. Make
sure the struct fields can actually store them.
Signed-off-by: Stefan Agner
---
This lead to a lot of warnings when compiling the Tegra pinctrl drivers
using LLVM/clang:
drivers/pinctrl/pinctrl-tegra124.c:2048:2: warning:
On Sat, Mar 14, 2015 at 3:55 PM, Andy Lutomirski wrote:
> It occurs to me that my previous reply was unnecessarily long and
> missed the point. Trying again:
>
> On Sat, Mar 14, 2015 at 3:17 PM, Andrew G. Morgan wrote:
>> On Sat, Mar 14, 2015 at 2:45 PM, Andy Lutomirski wrote:
>>> On Sat, Mar
Jason does an excellent job reviewing the TPM stuff, so we add him to
the designated reviewer list (with his consent :)
Jason Gunthorpe
Signed-off-by: Peter Huewe
Signed-off-by: Peter Huewe
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
I got a lot of requests lately about whether the new TPM2.0 support
includes the FIFO interface for TPM2.0 as well.
The FIFO interface is handled by tpm_tis since FIFO=TIS (more or less).
-> Update the helptext and headline
Signed-off-by: Peter Huewe
---
drivers/char/tpm/Kconfig | 9 +
On 03/14/2015 04:55 PM, Alexei Starovoitov wrote:
...
so from there I saw two options: either copy paste all
build_bug_on and have the same *insn=... and build_bug_on in
two places or consolidate them in single helper function.
Obviously single helper function is a preferred method.
I'm not sure
On 18 January 2014 at 16:14, Mike Galbraith wrote:
> On Sat, 2014-01-18 at 10:33 +0100, Mike Galbraith wrote:
>> On Fri, 2014-01-17 at 05:20 +0100, Mike Galbraith wrote:
> Signed-off-by: Mike Galbraith
> Cc: # 3.10+
> ---
> arch/x86/kernel/process.c |9 ++---
> 1 file changed, 6
On 03/10/15 16:59, valdis.kletni...@vt.edu wrote:
On Tue, 10 Mar 2015 14:03:59 +0100, Yann Droneaud said:
Consider the following sequence of events:
0. Suppose a mutex is locked by task A and has no waiters.
1. Task B calls mutex_trylock().
2. mutex_trylock() calls the architecture-specific
On 03/10/15 15:03, Yann Droneaud wrote:
Hi,
Le mercredi 04 mars 2015 à 02:13 +0200, Matthias Bonne a écrit :
I am trying to understand how mutexes work in the kernel, and I think
there might be a race between mutex_trylock() and mutex_unlock(). More
specifically, the race is between the
It occurs to me that my previous reply was unnecessarily long and
missed the point. Trying again:
On Sat, Mar 14, 2015 at 3:17 PM, Andrew G. Morgan wrote:
> On Sat, Mar 14, 2015 at 2:45 PM, Andy Lutomirski wrote:
>> On Sat, Mar 14, 2015 at 2:09 PM, Andrew G. Morgan wrote:
>>> My Nack remains
On Sat, Mar 14, 2015 at 3:17 PM, Andrew G. Morgan wrote:
> On Sat, Mar 14, 2015 at 2:45 PM, Andy Lutomirski wrote:
>> On Sat, Mar 14, 2015 at 2:09 PM, Andrew G. Morgan wrote:
>>> On Fri, Mar 13, 2015 at 10:57 AM, Andy Lutomirski
>>> wrote:
On Mar 13, 2015 6:24 AM, "Andrew G. Morgan"
We currently use the mmap_sem to serialize the mm exe_file.
This is atrocious and a clear example of the misuses this
lock has all over the place, making any significant changes
to the address space locking that much more complex and tedious.
This also has to do of how we used to check for the
... everyone else does.
Signed-off-by: Davidlohr Bueso
Cc: Alexander Viro
Cc: Cyrill Gorcunov
Cc: Oleg Nesterov
CC: Konstantin Khlebnikov
---
kernel/fork.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index 54b0b91..fc5d4f3 100644
---
Given the introduction of the exe_file structure, this
functionality should be associated with. Because this is
a very specific prctl property, it is easily to do so. As
of now, when the file has already changed, mmap_sem is not
taken at all (however we do need it of course to check the
old
This is a set I created on top of patch 1/4 which also includes mm_struct
cleanups
and dealing with prctl exe_file functionality. Specific details are in each
patch.
Patch 4 is an extra trivial one I found while going through the code.
Applies on top of next-20150313.
Thanks!
Davidlohr Bueso
This patch isolates exe_file handling into its own data
structure, tiding up the mm_struct bits (which must remain
there as we provide prctl thread interfaces to change it).
Note that none of the interfaces have changed, users will
continue dealing with the actual backing struct file, but
The following changes since commit 13a7a6ac0a11197edcd0f756a035f472b42cdf8b:
Linux 4.0-rc2 (2015-03-03 09:04:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to
On Saturday 14 March 2015 15:03:08 Josh Triplett wrote:
> I had to think about this for a while, but I think it makes sense now.
> wait should *not* ever return the PID of an autoreaped process, because
> that would introduce a race condition (the caller cannot safely do
> *anything* with the PID
On Sat, Mar 14, 2015 at 2:45 PM, Andy Lutomirski wrote:
> On Sat, Mar 14, 2015 at 2:09 PM, Andrew G. Morgan wrote:
>> On Fri, Mar 13, 2015 at 10:57 AM, Andy Lutomirski
>> wrote:
>>> On Mar 13, 2015 6:24 AM, "Andrew G. Morgan" wrote:
> It's to preserve the invariant that pA is always
On Sat, Mar 14, 2015 at 09:30:29PM +0100, Oleg Nesterov wrote:
> On 03/14, Josh Triplett wrote:
> >
> > What I was proposing was that a task that isn't yet dead, but that is
> > going to be autoreaped, is not eligible for waiting either. All the
> > various wait* familiy of system calls should
On Sat, Mar 14, 2015 at 03:14:14PM +0100, Oleg Nesterov wrote:
> Again, again, I didn't read this series yet. But the proper solution (afaics)
> should move this "autoreap" check in release_task/__ptrace_detach(). If the
> task is traced. Debugger should check ->autoreap and skip another
>
On Sat, Mar 14, 2015 at 07:54:24PM +0100, Oleg Nesterov wrote:
> On 03/14, Thiago Macieira wrote:
> > On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > > It is not clear to me what do_wait() should do with ->autoreap child, even
> > > ignoring ptrace.
> > >
> > > Just suppose that
On Fri, Mar 13, 2015 at 10:31 PM, Thomas Niederprüm
wrote:
> Am Tue, 10 Mar 2015 13:28:25 +0200
> schrieb Tomi Valkeinen :
>> Also, isn't doing __pa() for the memory returned by vmalloc plain
>> wrong?
>
>> What was the crash about when using kmalloc? It would be good to fix
>> defio, as I don't
On Sat, 2015-03-14 at 16:16 -0400, M. Vefa Bicakci wrote:
> On 13/03/15 12:24 PM, Joe Perches wrote:
> > On Fri, 2015-03-13 at 10:44 -0500, Larry Finger wrote:
> >> On 03/12/2015 10:15 PM, M. Vefa Bicakci wrote:
> >>> Improve the readability of an if statement and its very long trace
> >>> output
Hi Linus,
misc i915, vmwgfx and radeon fixes along with a fix for one of those sleep
mutex debug log in the mst code.
Dave.
The following changes since commit 9eccca0843205f87c00404b663188b88eb248051:
Linux 4.0-rc3 (2015-03-08 16:09:09 -0700)
are available in the git repository at:
On Sat, Mar 14, 2015 at 2:09 PM, Andrew G. Morgan wrote:
> On Fri, Mar 13, 2015 at 10:57 AM, Andy Lutomirski wrote:
>> On Mar 13, 2015 6:24 AM, "Andrew G. Morgan" wrote:
>>>
>>> > It's to preserve the invariant that pA is always a subset of pI.
>>>
>>> But since a user can always raise a bit in
Linus Walleij writes:
> On Fri, Feb 20, 2015 at 4:40 PM, Greg Kroah-Hartman
> wrote:
>> On Wed, Feb 18, 2015 at 05:12:18PM +0100, Linus Walleij wrote:
>>> This fixes a regression from the net subsystem:
>>> After commit d52fdbb735c36a209f36a628d40ca9185b349ba7
>>> "smc91x: retrieve IRQ and
Hello,
In about one out of 10 resumes from hibernation, my system resets after
the hibernation image has been loaded. I am hibernating using
# echo platform > /sys/power/disk
# echo disk > /sys/power/state
When testing hibernation using
# echo core > /sys/power/pm_test
# echo platform >
On Fri, Mar 13, 2015 at 10:57 AM, Andy Lutomirski wrote:
> On Mar 13, 2015 6:24 AM, "Andrew G. Morgan" wrote:
>>
>> > It's to preserve the invariant that pA is always a subset of pI.
>>
>> But since a user can always raise a bit in pI if it is present in pP,
>> what does this invariant add to
On Thu, 2015-03-12 at 14:12 -0700, Paul E. McKenney wrote:
>
> Are there any architectures left that use hardware-assisted global
> TLB invalidation?
ARM and PowerPC at least...
Cheers,
Ben.
> On such an architecture, you might not get a memory
> barrier except on the CPU executing the
On 13 March 2015 at 20:30, Tony Lindgren wrote:
> Hmm OK have to check that. It could also be that dm816x documentation
> is copy-paste from da850 or am3517 and the PHY got changed in the
> hardware as the registers don't match the documentation. Only the
> dm816x errata has right documentation
Hi David
12.03.2015, 03:54, "David Fries" :
> Would that be removing all four refcnt, w1_slave, w1_master,
> w1_family, w1_cb_block, or just some of them? It sounds good to me,
> if that had bugs there would be much more than just the w1 system
> relying on it. I don't know enough about that
Makefile that can actually build the example, and allow selecting
device to work on.
Signed-off-by: Pavel Machek
diff --git a/samples/hidraw/Makefile b/samples/hidraw/Makefile
index 382eeae..a9ab961 100644
--- a/samples/hidraw/Makefile
+++ b/samples/hidraw/Makefile
@@ -8,3 +8,5 @@
Usage of __uX types is unneccessary in the kernel, replace it with uX.
Signed-off-by: Pavel Machek
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index 1896c01..f65e334 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -57,7 +57,7 @@
#define MAX_LEDS 4
Hi!
> Second "sony motion controller" (part of ps/3 move with the big
> LED). The LED is something I'd really like to work.
>
> It is detected:
>
> [ 741.363723] input: Sony Computer Entertainment Motion Controller as
>
Add support for Measurement Specialities MS5611 pressure
and temperature sensor.
Signed-off-by: Tomasz Duszynski
---
Changes in v3:
- Fix coding style
- Use spi_write_then_read instead of spi_write to ensure that
data send to device is in it's own cacheline
Changes
On 03/14, Josh Triplett wrote:
>
> What I was proposing was that a task that isn't yet dead, but that is
> going to be autoreaped, is not eligible for waiting either. All the
> various wait* familiy of system calls should pretend it doesn't exist at
> all, because returning an autoreaped task
On 03/14, Josh Triplett wrote:
>
> On Sat, Mar 14, 2015 at 08:18:36PM +0100, Oleg Nesterov wrote:
>
> Is there any information somewhere on how this state machine of doom is
> *supposed* to work? :)
This looks as if you think that other parts of this kernel differ ;)
> Why would "p->task_state
Hello.
On 03/14/2015 11:55 AM, Nicholas Mc Guire wrote:
All of the bringup/init functions called in ath10k_core_start return 0 on
success and != 0 on failure - ath10k_wmi_wait_for_service_ready and
ath10k_wmi_wait_for_unified_ready were adjusted to fit this model and the
call sites here fixed
On Mon, Mar 9, 2015 at 12:30 AM, NeilBrown wrote:
> On Sun, 08 Mar 2015 18:14:39 +0100 Prakash Punnoor wrote:
>
>> Hi,
>>
>> I noticed the udisks daemon (version 2.1.4) suddenly started using high
>> cpu (one core at 100%) with linux 4.0 git kernel. I bisected it to:
>>
>>
On 13/03/15 12:24 PM, Joe Perches wrote:
> On Fri, 2015-03-13 at 10:44 -0500, Larry Finger wrote:
>> On 03/12/2015 10:15 PM, M. Vefa Bicakci wrote:
>>> Improve the readability of an if statement and its very long trace
>>> output line in rtl8723au's rtw_security.c.
> []
>>> diff --git
On Sat, Mar 14, 2015 at 08:47:21PM +0100, Oleg Nesterov wrote:
> On 03/14, Oleg Nesterov wrote:
> >
> > On 03/14, Josh Triplett wrote:
> > >
> > > On Sat, Mar 14, 2015 at 11:38:29AM -0700, Thiago Macieira wrote:
> > > > On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > > > > It is not
Hi!
Intel desktop machine:
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High
Definition Audio Controller (rev 01)
Sound worked ok in both in previous kernel versions.
Any ideas?
Thanks,
Pavel
--
(english)
On Sat, Mar 14, 2015 at 08:18:36PM +0100, Oleg Nesterov wrote:
> On 03/14, Josh Triplett wrote:
> >
> > On Sat, Mar 14, 2015 at 11:38:29AM -0700, Thiago Macieira wrote:
> > > On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > > > It is not clear to me what do_wait() should do with
From: Jason Ekstrand
On Wed, 11 Mar 2015 22:50:47, Matthew Garrett wrote:
> The ACPI spec describes _REV as:
>
> "This predefined object evaluates to the revision of the ACPI Specification
> that the specified \_OS implements"
>
> We've been assuming that this should increment as ACPICA
>
> i2c_smbus_read_word_data() returns data in native endianess. But it
> interprets the word on the bus as little-endian (As specified by the SMBus
> spec). If your chip returns data in big-endian use
> i2c_smbus_read_word_data_swapped().
>
> - Lars
Ah, good to know. I'll update the patch
On 03/14, Oleg Nesterov wrote:
>
> On 03/14, Josh Triplett wrote:
> >
> > On Sat, Mar 14, 2015 at 11:38:29AM -0700, Thiago Macieira wrote:
> > > On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > > > It is not clear to me what do_wait() should do with ->autoreap child,
> > > > even
> > >
On Sat, Mar 14, 2015 at 08:24:56PM +0100, Oleg Nesterov wrote:
> On 03/14, Josh Triplett wrote:
> >
> > On Sat, Mar 14, 2015 at 03:35:58PM +0100, Oleg Nesterov wrote:
> > > On 03/12, Josh Triplett wrote:
> > > >
> > > > @@ -598,7 +600,9 @@ static void exit_notify(struct task_struct *tsk,
> > > >
Hi!
> After oopsing kernel with ps/3 peripherals, I decided to play some
> more.
>
> First "sony motion controller" (part of ps/3 move without the
I meant "navigation controller".
I enabled CONFIG_HID_SONY_FF, and fftest now works with the other
controller, but not work this one:
Setting
The coraid.com email address is defunct. The old aoe support area
hosted at coraid.com is no longer up. These changes update the email
and website to current ones.
Signed-off-by: Ed Cashin
---
The docs need updating as well, but I want to fix the email before
tackling that.
MAINTAINERS | 4
Hi!
After oopsing kernel with ps/3 peripherals, I decided to play some
more.
Third, regular controller. The one you don't have to dance with.
/sys/class/power_supply/*/capacity works.
again, evtest reports funny-looking multitouch events:
Event: time 1426361100.640824, -- EV_SYN
On Sat, Mar 14, 2015 at 12:03:12PM -0700, Thiago Macieira wrote:
> On Friday 13 March 2015 18:11:32 Thiago Macieira wrote:
> > On Friday 13 March 2015 14:51:47 Andy Lutomirski wrote:
> > > In any event, we should find out what FreeBSD does in response to
> > > read(2) on the fd.
> >
> > I've just
On 03/14, Josh Triplett wrote:
>
> On Sat, Mar 14, 2015 at 03:35:58PM +0100, Oleg Nesterov wrote:
> > On 03/12, Josh Triplett wrote:
> > >
> > > @@ -598,7 +600,9 @@ static void exit_notify(struct task_struct *tsk, int
> > > group_dead)
> > > if (group_dead)
> > >
Hi!
Second "sony motion controller" (part of ps/3 move with the big
LED). The LED is something I'd really like to work.
It is detected:
[ 741.363723] input: Sony Computer Entertainment Motion Controller as
/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:03D5.000A/input/input19
[
On 03/14, Josh Triplett wrote:
>
> On Sat, Mar 14, 2015 at 11:38:29AM -0700, Thiago Macieira wrote:
> > On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > > It is not clear to me what do_wait() should do with ->autoreap child, even
> > > ignoring ptrace.
> > >
> > > Just suppose that
Hi!
After oopsing kernel with ps/3 peripherals, I decided to play some
more.
First "sony motion controller" (part of ps/3 move without the
led). Good news is that it no longer oopses. After pressing the PS
button, it seems to work, but it produces endless stream of events in
evtest:
Event: time
[top posting, sorry]
Jason made some interesting progress today:
with the patch in https://lkml.org/lkml/2015/3/12/149, the sound card
is not switched in the I2S mode and works while the touchpad keeps
using I2C.
It looks like suspend/resume is also fixed by that :)
I thought it was worth
On Sat, Mar 14, 2015 at 03:35:58PM +0100, Oleg Nesterov wrote:
> On 03/12, Josh Triplett wrote:
> >
> > @@ -598,7 +600,9 @@ static void exit_notify(struct task_struct *tsk, int
> > group_dead)
> > if (group_dead)
> > kill_orphaned_pgrp(tsk->group_leader, NULL);
> >
> > - if
Andreas Färber writes:
> Kukjin,
>
> Am 28.07.2014 14:18, schrieb Andreas Färber:
>> Hello,
>>
>> This series adds a dedicated ODROID-XU device tree and enhances it with
>> LED configuration, to match the downstream 3.14 based behavior.
>>
>> It had turned out less trivial than I initially
Hi!
> return -ENOSYS;
> Index: linux/include/linux/cred.h
> ===
> --- linux.orig/include/linux/cred.h 2015-02-25 13:43:06.929973954 -0600
> +++ linux/include/linux/cred.h2015-02-25 13:43:06.925972078 -0600
>
Minimal implementation providing raw light intensity
and integration time attribute.
Userspace applications can use GREEN channel for raw
illuminance readings following this table:
Integration Time | G Sensitivity
40 ms| 0.18
80 ms| 0.09
On Friday 13 March 2015 18:11:32 Thiago Macieira wrote:
> On Friday 13 March 2015 14:51:47 Andy Lutomirski wrote:
> > In any event, we should find out what FreeBSD does in response to
> > read(2) on the fd.
>
> I've just successfully installed FreeBSD and compiled qtbase (main package
> of Qt 5)
On Sat, Mar 14, 2015 at 11:38:29AM -0700, Thiago Macieira wrote:
> On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > It is not clear to me what do_wait() should do with ->autoreap child, even
> > ignoring ptrace.
> >
> > Just suppose that real_parent has a single "autoreap" child.
On 03/14, Thiago Macieira wrote:
>
> On Saturday 14 March 2015 15:32:35 Oleg Nesterov wrote:
> > It is not clear to me what do_wait() should do with ->autoreap child, even
> > ignoring ptrace.
> >
> > Just suppose that real_parent has a single "autoreap" child. Should
> > wait(NULL) hanf then?
>
>
On 03/13/2015 05:42 PM, Benjamin Tissoires wrote:
No need to retrieve the USB handle in input_mapping() when we already
do that in probe. It also allows to use the quirk without having to
add the product ID matching.
Signed-off-by: Benjamin Tissoires
---
Nick,
no need to cc DIGImend-devel
On Fri, Mar 06, 2015 at 06:14:42PM -0700, Azael Avalos wrote:
> Add the missing toshiba_bluetooth and toshiba_haps entries and add
> myself as their maintainer.
>
> Also add the Maintainers entry for toshiba_acpi driver and change its
> status to maintained.
>
> Signed-off-by: Azael Avalos
On Fri, Mar 06, 2015 at 06:14:41PM -0700, Azael Avalos wrote:
> This patch adds a few more events sent to TOS devices, some of
> them are already identified, while some others simply print a message
> informing the type of event received.
>
> Also, a netlink event is generated so that
1 - 100 of 460 matches
Mail list logo