This patch adds support for Si-En SN3218 18 Channel LED Driver.
Signed-off-by: Stefan Wahren
---
drivers/leds/Kconfig | 12 ++
drivers/leds/Makefile |1 +
drivers/leds/leds-sn3218.c | 297
3 files changed, 310 insertions(+)
create m
Si-En Technology is a fabless design house which offers
audio amplifiers, LED drivers and sensors.
Signed-off-by: Stefan Wahren
Acked-by: Rob Herring
---
.../devicetree/bindings/vendor-prefixes.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/v
This patch series implements support for the Si-En SN3218
18 Channel LED Driver connected through I2C. The SN3218
doesn't support reading so the LED states are cached in a
regmap.
The driver has been tested on a Raspberry Pi B.
Changes since RFC:
* using regmap instead of direct I2C
* add new
This patch adds the binding for Si-En Technology SN3218
18-Channel LED driver.
Signed-off-by: Stefan Wahren
Acked-by: Rob Herring
---
.../devicetree/bindings/leds/leds-sn3218.txt | 42
1 file changed, 42 insertions(+)
create mode 100644 Documentation/devicetree/bin
Am Samstag, 30. Januar 2016, 17:38:28 schrieb Dan Carpenter:
Hi Dan,
> We're clearing the wrong memory. The memory corruption is likely
> harmless because we weren't going to use that stack memory again but not
> zeroing is a potential information leak.
>
> Fixes: e28facde3c39 ('crypto: keywrap
Hello!
In current linux-mips master branch from
git://git.linux-mips.org/pub/scm/ralf/linux
there are two commits
commit 76654c7be21c1704607e9ed22cf5d18d430fd828
Author: Alban Bedel
Date: Mon Nov 16 22:22:04 2015 +0100
MIPS: ath79: Enable the USB port on the TL-WR1043ND
After rename file dentry still holds reference to lower dentry from
previous location. This doesn't matter for data access because data
cames from upper dentry. But this stale lower dentry taints dentry
at new location and turns it into non-pure upper. Such file leaves
visible whiteout entry after
This fixes some cases of missing atime update for overlayfs.
Signed-off-by: Konstantin Khlebnikov
---
fs/inode.c | 15 +--
include/linux/fs.h |6 +-
2 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/fs/inode.c b/fs/inode.c
index 9f62db3bcc3e..6a4dd94c0
Overlayfs must update uid/gid after chown, otherwise functions
like inode_owner_or_capable() will check user against stale uid.
Catched by xfstests generic/087, it chowns file and calls utimes.
Signed-off-by: Konstantin Khlebnikov
---
fs/overlayfs/inode.c |2 ++
1 file changed, 2 insertions(
Catched by xfstests generic/319
Signed-off-by: Konstantin Khlebnikov
---
fs/overlayfs/super.c |4
1 file changed, 4 insertions(+)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index ba28b007005e..e6ae59c7119c 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -9
This adds missing .d_select_inode into alternative dentry_operations.
Signed-off-by: Konstantin Khlebnikov
Fixes: 7c03b5d45b8e ("ovl: allow distributed fs as lower layer")
Fixes: 4bacc9c9234c ("overlayfs: Make f_path always point to the overlay and
f_inode to the underlay")
---
fs/overlayfs/sup
For example fuse root dentry has no dentry operations.
Signed-off-by: Konstantin Khlebnikov
Fixes: 7c03b5d45b8e ("ovl: allow distributed fs as lower layer")
---
fs/overlayfs/super.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/fs/overlayfs/super.c b/fs/over
On Tue, Jan 26, 2016 at 9:01 AM, Felipe Ferreri Tonello
wrote:
> Actually yes, thanks! I didn't know about the existence of fsl-asoc-card.
>
> I get some errors but I don't think they actually matter:
> [ 19.734494] fsl-asrc 2034000.asrc: driver registered
> [ 19.738707] fsl-asoc-card sound:
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/i2c/busses/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 0299dfa..a2e456a 100644
--- a/drivers/i2c/busse
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/uniphier/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/uniphier/Kconfig b/drivers/pinctrl/uniphier/Kconfig
index 7abd614..43f689f 100644
--- a/dri
Hi Eric, Alex, Antonios;
On 1/29/2016 5:35 PM, Sinan Kaya wrote:
> The code is using the compatible DT string to associate a reset driver with
> the actual device itself. The compatible string does not exist on ACPI
> based systems. HID is the unique identifier for a device driver instead.
> The c
Julian Calaby writes:
> Hi Bhaktipriya,
>
> On Sat, Jan 30, 2016 at 5:00 AM, Jes Sorensen wrote:
>> Bhaktipriya Shridhar writes:
>> If you insist on pushing this rather unncessary change, please do it
>> properly, and remove the blank line before the return statement as well.
>
> As Jes said, yo
Bhaktipriya Shridhar writes:
> This patch fixes checkpatch.pl warning in rtw_mlme_ext.c file.
> WARNING: void function return statements are not generally useful
>
> Signed-off-by: Bhaktipriya Shridhar
> ---
> Changes in v2:
>- Removed the unnecessary blank lines.
> drivers/staging/rtl8723a
Commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly") always
reports positive value when Apple hardware queries _OSI("Darwin").
But sometimes the users might want to tell the hardware they don't
need the Darwin feature, for example, users may leverage the hardware
to power off the Thunderb
On Sat, 30 Jan 2016, Maciej W. Rozycki wrote:
> > % echo 2.24.51.20140217 | ld-version.sh
> > 22451000
>
> So the above version is a non-release snapshot from the development tree
> as the repository trunk is switched to x.y+1.51 once a release branch for
> x.y has been made. Then the release
Commit 16da306849d0 ("um: kill pfn_t")
introduced a compile warning for defconfig (SUBARCH=i386):
arch/um/kernel/skas/mmu.c:38:206:
warning: right shift count >= width of type [-Wshift-count-overflow]
Aforementioned patch changes the definition of the phys_to_pfn() macro from
((pfn_t)
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.5-rc2
for you to fetch changes up to 16ab8a5cbea463e4d14bf0ce698f11
Some I2C devices have multiple addresses assigned, for example each address
corresponding to a different internal register map page of the device.
So far drivers which need support for this have handled this with a driver
specific and non-generic implementation, e.g. passing the additional address
On Sun, Jan 31, 2016 at 12:00:41PM +0100, Matthias Brugger wrote:
>
>
> On 26/01/16 05:12, Yong Wu wrote:
> >This patch add SMI(Smart Multimedia Interface) driver. This driver
> >is responsible to enable/disable iommu and control the power domain
> >and clocks of each local arbiter.
> >
> >Signed
Use list_for_each_entry*() instead of list_for_each*() to simplify
the code. Fix coding style by the way.
Signed-off-by: Geliang Tang
---
drivers/staging/rtl8723au/core/rtw_ap.c | 166 --
drivers/staging/rtl8723au/core/rtw_mlme.c | 38 ++---
drivers/staging
BUFFER_TRACE info "call ext4_handle_dirty_metadata" doesn't match the
code, so drop it.
Signed-off-by: Geliang Tang
---
fs/ext4/inline.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c
index dfe3b9b..cbcb907 100644
--- a/fs/ext4/inline.c
+++ b/fs/ext4/inlin
-when-acpi_osi-Darwin-provided/20160131-224855
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
config: i386-randconfig-s0-201605 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new
Use list_for_each_entry() instead of list_for_each() to simplify the code.
Signed-off-by: Geliang Tang
---
init/main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/init/main.c b/init/main.c
index 68ec07b..3cf30ec 100644
--- a/init/main.c
+++ b/init/main.c
@@ -728,7 +728
Hi,
On Sun, Jan 31, 2016 at 12:24:34PM +0100, Pali Rohár wrote:
> On Sunday 31 January 2016 02:19:46 Sebastian Reichel wrote:
> > Disabled power management means, that the driver can only be
> > used together with further out-of-tree kernel patches. There
> > is no reason to support this in the ma
The following patches add the self-test for
sigaltstack(SS_DISABLE) inside the signal handler,
and allow an app to temporarily disable and re-enable
the sigaltstack within a sighandler.
This is needed to make sigaltstack() compatible with
swapcontext(): before using swapcontext() inside
the sighan
sigaltstack needs to be disabled before the signal handler can
safely use swapcontext(). Unfortunately linux implementation of
sigaltstack() returns EPERM in that case.
Re-enabling is also needed and tested.
CC: Shuah Khan
CC: linux-kernel@vger.kernel.org
CC: linux-...@vger.kernel.org
CC: Andy
Currently get_sigframe() checks only
(ka->sa.sa_flags & SA_ONSTACK) && (!on_sig_stack(sp))
to determine whether the switch to sigaltstack is needed.
It forgets to checks whether the sigaltstack was previously set.
This patch replaces the !on_sig_stack(sp) with the standard check
sas_ss_flags(sp)
Currently x86's get_sigframe() checks for "current->sas_ss_size"
to determine whether there is a need to switch to sigaltstack.
The common practice used by all other arches is to check for
sas_ss_flags(sp) == 0
This patch makes the code consistent with other arches and also
allows for the furthe
linux implements the sigaltstack() in a way that makes it impossible to
use with swapcontext(). Per the man page, sigaltstack is allowed to return
EPERM if the process is altering its sigaltstack while running on
sigaltstack.
This is likely needed to consistently return oss->ss_flags, that indica
On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox wrote:
> On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:
>> > I did probably 70% of the work needed to switch the radix tree over to
>> > storing PFNs instead of sectors. It seems viable, though it's a big
>> > change from where we are
Rule r is only used in org or report mode, so only execute it in those
cases.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/api/pm_runtime.cocci |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccinelle/api/pm_runtime.cocci
b/scripts/coccinelle/api/pm_runti
On Sun, Jan 31, 2016 at 8:24 AM, Stas Sergeev wrote:
>
> Currently x86's get_sigframe() checks for "current->sas_ss_size"
> to determine whether there is a need to switch to sigaltstack.
> The common practice used by all other arches is to check for
> sas_ss_flags(sp) == 0
>
> This patch makes the
On Mon, Jan 25, 2016 at 8:15 AM, Chen-Yu Tsai wrote:
> sun6i's AR100 clock is a classic factors clk case:
>
> AR100 = ((parent mux) >> p) / (m + 1)
>
> Signed-off-by: Chen-Yu Tsai
This patch adds a ".remove" function to a driver that is controlled by
a bool Kconfig, and hence the remove code can
On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote:
>
> linux implements the sigaltstack() in a way that makes it impossible to
> use with swapcontext(). Per the man page, sigaltstack is allowed to return
> EPERM if the process is altering its sigaltstack while running on
> sigaltstack.
> This is
Hi!
> So far power management had to be done in uerspace using exported
"userspace"
> This patch adds kernel based power management, which will bind the
> modem's power state to the state of the phonet network interface.
Ok, so I have ofonod that already does power management in
userspace. What
sys_iopl both reads and writes pt_regs->flags. Mark it as using ptregs.
This isn't strictly necessary, as pt_regs->flags is available even
in the fast path, but this is very lightweight now that we have
syscall qualifiers and it could avoid some pain down the road.
Signed-off-by: Andy Lutomirski
I messed up the IRQ state when jumping off the fast path due to
invocation of a ptregs-using syscall. This bug shouldn't have had
any impact yet, but it would have caused problems with subsequent
context tracking cleanups.
Fixes: 1e423bff959e x86/entry/64: ("Migrate the 64-bit syscall slow path t
31.01.2016 20:00, Andy Lutomirski пишет:
On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote:
linux implements the sigaltstack() in a way that makes it impossible to
use with swapcontext(). Per the man page, sigaltstack is allowed to return
EPERM if the process is altering its sigaltstack while
I was fishing RIP (i.e. RCX) out of pt_regs->cx and RFLAGS (i.e. R11)
out of pt_regs->r11. While it usually worked (pt_regs started out
with cx == ip and r11 == flags), it was very fragile. In particular,
it broke iopl because iopl forgot to mark itself as using ptregs.
Undo that part of the sys
I broke iopl(2) with my syscall rework. Fix it up. While debugging
it, I found a bug in my IRQ state handling. Fix that, too.
Andy Lutomirski (3):
x86/entry/64: Fix an IRQ state error on ptregs-using syscalls
x86/entry/64: Fix fast-path syscall return register state
x86/syscalls/64: Mark
On Sun 2016-01-31 02:19:45, Sebastian Reichel wrote:
> Currently userspace knows about the rapuyama version by
> checking, which gpios have been exported. This does no
> longer work with kernel based power management, so export
> a sysfs file, which provides the rapuyama generation. Also
Umm. So p
hild process #0: join parent cgroupns
The test does not change the mount namespace and does not mount any
new cgroup2 filesystem. Therefore this does not test that the cgroup2
mount is correctly rooted to the cgroupns root at mount time.
Signed-off-by: Alban Crequy
Acked-by: Serge E. Hallyn
Hi Nicolin,
On 29/01/16 18:02, Nicolin Chen wrote:
> On Fri, Jan 29, 2016 at 11:01:01AM +, Felipe F. Tonello wrote:
>> Signed-off-by: Felipe F. Tonello
>> ---
>> Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --gi
Geliang Tang writes:
> Use list_for_each_entry*() instead of list_for_each*() to simplify
> the code. Fix coding style by the way.
>
> Signed-off-by: Geliang Tang
> ---
> drivers/staging/rtl8723au/core/rtw_ap.c | 166
> --
> drivers/staging/rtl8723au/core/rtw_mlme.
Hi Doug, Liran, Jason,
How would you like to see RDMA verb resources being defined - in RDMA
cgroup or in IB stack?
In current patch v5, its defined by the IB stack which is often
shipped as different package due to high amount of changes, bug fixes,
features.
In v0 patch it was defined by the RDM
Hi,
On Sun, Jan 31, 2016 at 06:29:48PM +0100, Pavel Machek wrote:
> > So far power management had to be done in uerspace using exported
>
> "userspace"
Right, thanks.
> > This patch adds kernel based power management, which will bind the
> > modem's power state to the state of the phonet networ
The "man gcc" says .i extension represents the file is C source code
that should not be preprocessed. Here, .s should be used.
For clarification,
.c ---(preprocess)---> .i
.S ---(preprocess)---> .s
Signed-off-by: Masahiro Yamada
---
tools/build/Makefile.build | 2 +-
1 file changed, 1
31.01.2016 19:58, Andy Lutomirski пишет:
On Sun, Jan 31, 2016 at 8:24 AM, Stas Sergeev wrote:
Currently x86's get_sigframe() checks for "current->sas_ss_size"
to determine whether there is a need to switch to sigaltstack.
The common practice used by all other arches is to check for
sas_ss_flags
On Sat, Jan 30, 2016 at 03:26:35PM -0800, David Miller wrote:
> From: Jarod Wilson
> Date: Sat, 30 Jan 2016 15:53:05 -0500
>
> > On Sat, Jan 30, 2016 at 03:39:01PM -0500, Jarod Wilson wrote:
> >> Ew, no, it won't work correctly on 32-bit. The for loop is going to copy
> >> data into dst from beyo
On Sun, Jan 31, 2016 at 08:38:20AM -0800, Dan Williams wrote:
> On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox wrote:
> > On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:
> >> Is there a reason to store pnfs instead of kaddrs in the radix tree?
> >
> > Once ARM, MIPS and SPARC get su
On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox wrote:
> On Sun, Jan 31, 2016 at 08:38:20AM -0800, Dan Williams wrote:
>> On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox
>> wrote:
>> > On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:
>> >> Is there a reason to store pnfs instead of
On Sun, Jan 31, 2016 at 10:18:46AM -0800, Dan Williams wrote:
> On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox
> wrote:
> > Yes. This is just the default implementation of dax_map_pfn() which works
> > for most situations. We can introduce more complex implementations of
> > dax_map_pfn() as
Hi Pavel,
On Sun, Jan 31, 2016 at 06:36:05PM +0100, Pavel Machek wrote:
> On Sun 2016-01-31 02:19:45, Sebastian Reichel wrote:
> > Currently userspace knows about the rapuyama version by
> > checking, which gpios have been exported. This does no
> > longer work with kernel based power management,
On Sun, 31 Jan 2016 13:15:06 +1100
Stephen Rothwell wrote:
> Hi Jesper,
>
> On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer
> wrote:
> >
> > Let me know, if the linux-next tree need's an explicit fix?
>
> It would be a good idea if you could send a fix against linux-next to
> me a
The following patches add the self-test for
sigaltstack(SS_DISABLE) inside the signal handler,
and allow an app to temporarily disable and re-enable
the sigaltstack within a sighandler.
This is needed to make sigaltstack() compatible with
swapcontext(): before using swapcontext() inside
the sighan
On Sun, Jan 31, 2016 at 10:27 AM, Matthew Wilcox wrote:
> On Sun, Jan 31, 2016 at 10:18:46AM -0800, Dan Williams wrote:
>> On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox
>> wrote:
>> > Yes. This is just the default implementation of dax_map_pfn() which works
>> > for most situations. We can
sigaltstack needs to be disabled before the signal handler can
safely use swapcontext(). Unfortunately linux implementation of
sigaltstack() returns EPERM in that case.
Re-enabling is also needed and tested.
CC: Shuah Khan
CC: linux-kernel@vger.kernel.org
CC: linux-...@vger.kernel.org
CC: Andy
Currently get_sigframe() checks only
(ka->sa.sa_flags & SA_ONSTACK) && (!on_sig_stack(sp))
to determine whether the switch to sigaltstack is needed.
It forgets to checks whether the sigaltstack was previously set.
This patch replaces the !on_sig_stack(sp) with the standard check
sas_ss_flags(sp)
Currently x86's get_sigframe() checks for "current->sas_ss_size"
to determine whether there is a need to switch to sigaltstack.
The common practice used by all other arches is to check for
sas_ss_flags(sp) == 0
This patch makes the code consistent with other arches and also
allows for the furthe
linux implements the sigaltstack() in a way that makes it impossible to
use with swapcontext(). Per the man page, sigaltstack is allowed to return
EPERM if the process is altering its sigaltstack while running on
sigaltstack.
This is likely needed to consistently return oss->ss_flags, that indica
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-4.5-rc2
for you to fetch changes up to 25cad
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.5-rc2
for you to fetch changes up to 6c55d9b98335f7f6bd5f06
The following changes since commit 9f9499ae8e6415cefc4fe0a96ad0e27864353c89:
Linux 4.4-rc5 (2015-12-13 17:42:58 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.5-rc2
for you to fetch changes up to 88867e3d0b7ee
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.5-rc2
for you to fetch changes up to a89a798a010e8fef66d1a8
On Sun, Jan 31, 2016 at 9:33 AM, Stas Sergeev wrote:
> 31.01.2016 20:00, Andy Lutomirski пишет:
>>
>> On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote:
>>>
>>> linux implements the sigaltstack() in a way that makes it impossible to
>>> use with swapcontext(). Per the man page, sigaltstack is a
On Fri, Jan 29, 2016 at 11:01:00AM +, David Woodhouse wrote:
> Also, wasn't Christoph looking at making per-device DMA ops more
> generic instead of an 'archdata' thing on basically every platform? Or
> did I just imagine that part?
What I've done for 4.5 is to switch all architectures to use
On Thu, Jan 28, 2016 at 05:57:35PM +, Luis Henriques wrote:
> On Wed, Jan 27, 2016 at 10:15:18AM -0800, Greg Kroah-Hartman wrote:
> > 3.14-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Oliver Neukum
> >
> > commit 1eaf35e4dd
On Wed, Jan 27, 2016 at 07:21:27PM -0800, Guenter Roeck wrote:
> On 01/27/2016 06:23 PM, Guenter Roeck wrote:
> >On 01/27/2016 10:11 AM, Greg Kroah-Hartman wrote:
> >>-
> >>NOTE:
> >> There are still a lot of pending stable patches in the queue, well
> >> over 400 of the
On Thu, Jan 28, 2016 at 09:17:10AM +0100, Ard Biesheuvel wrote:
> On 28 January 2016 at 03:14, Guenter Roeck wrote:
> > On 01/27/2016 10:12 AM, Greg Kroah-Hartman wrote:
> >>
> >> -
> >> NOTE:
> >>There are still a lot of pending stable patches in the queue, well
> >>
On Wed, Jan 27, 2016 at 06:14:22PM -0800, Guenter Roeck wrote:
> On 01/27/2016 10:12 AM, Greg Kroah-Hartman wrote:
> >-
> >NOTE:
> > There are still a lot of pending stable patches in the queue, well
> > over 400 of them to be specific, so some of your favorite/pet patch
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
1/ Fixes to the libnvdimm 'pfn' device that establishes a reserved area
for storing a struct page array.
2/ Fixes for dax operations on a raw block device to prevent pagecache
collisions wit
I'm announcing the release of the 4.1.17 kernel.
All users of the 4.1 kernel series must upgrade.
The updated 4.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.1.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.3.5 kernel.
All users of the 4.3 kernel series must upgrade.
The updated 4.3.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.3.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/ABI/testing/sysfs-bus-usb
b/Documentation/ABI/testing/sysfs-bus-usb
index 3a4abfc44f5e..136ba17d2da0 100644
--- a/Documentation/ABI/testing/sysfs-bus-usb
+++ b/Documentation/ABI/testing/sysfs-bus-usb
@@ -134,19 +134,21 @@ Description:
enabled for the devi
I'm announcing the release of the 4.4.1 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
From: Greg Kroah-Hartman
Sasha has volunteered to maintain the 4.1-longterm kernel for some
strange and insane reason. So quick, before he comes to his senses,
mark 4.1 as being maintained by him publicly so that the world will
know.
Cc: Sasha Levin
Signed-off-by: Greg Kroah-Hartman
---
cont
On Sun, Jan 31, 2016 at 10:07 AM, Matthew Wilcox wrote:
> One option that I've been looking at (primarily for x86-32) is
> having an rbtree of PFN ranges that drivers add to when they register
> peristent memory.
On this specific point we do already have find_dev_pagemap().
31.01.2016 22:03, Andy Lutomirski пишет:
On Sun, Jan 31, 2016 at 9:33 AM, Stas Sergeev wrote:
31.01.2016 20:00, Andy Lutomirski пишет:
On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote:
linux implements the sigaltstack() in a way that makes it impossible to
use with swapcontext(). Per the
On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote:
> On 29/01/16 02:31, Andy Lutomirski wrote:
> > Signed-off-by: Andy Lutomirski
> > ---
> > drivers/virtio/virtio_ring.c | 12
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/drivers/virtio/virtio_ring.c b/driver
On Sat, Jan 30, 2016 at 06:44:33PM +0100, Mathieu OTHACEHE wrote:
> This series of patches fixes all coccinelle warnings in
> USB serial subsystem
>
> Mathieu OTHACEHE (14):
> USB: serial: safe_serial: fix assignment of bool to 0/1
> USB: serial: safe_serial: fix assignment of bool to non 0/1
On Sun, Jan 31, 2016 at 12:08 PM, Stas Sergeev wrote:
> 31.01.2016 22:03, Andy Lutomirski пишет:
>> Also, consider a use case like yours but with *two* contexts that use
>> their own altstack. If you go to context A, enable sigaltstack, get a
>> signal, temporarily disable, then swapcontext to B,
On Fri, Jan 29, 2016 at 12:07:30AM +0300, Andrey Skvortsov wrote:
> $ lsusb:
> Bus 001 Device 101: ID 1e0e:9001 Qualcomm / Option
>
> $ usb-devices:
> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=101 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 2
> P: Vendor=1e0e
On Thu, Jan 28, 2016 at 06:31:13PM -0800, Andy Lutomirski wrote:
> This switches virtio to use the DMA API on Xen and if requested by
> module option.
>
> This fixes virtio on Xen, and it should break anything because it's
> off by default on everything except Xen PV on x86.
>
> To the Xen people
On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote:
> On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote:
>> On 29/01/16 02:31, Andy Lutomirski wrote:
>> > Signed-off-by: Andy Lutomirski
>> > ---
>> > drivers/virtio/virtio_ring.c | 12
>> > 1 file changed, 12 inser
On Sun, Jan 31, 2016 at 12:12 PM, Michael S. Tsirkin wrote:
> On Thu, Jan 28, 2016 at 06:31:13PM -0800, Andy Lutomirski wrote:
>> This switches virtio to use the DMA API on Xen and if requested by
>> module option.
>>
>> This fixes virtio on Xen, and it should break anything because it's
>> off by
On Sun, Jan 31, 2016 at 12:13:58PM -0800, Andy Lutomirski wrote:
> On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote:
> > On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote:
> >> On 29/01/16 02:31, Andy Lutomirski wrote:
> >> > Signed-off-by: Andy Lutomirski
> >> > ---
> >> >
On Jan 28, 2016 6:33 PM, "Andy Lutomirski" wrote:
>
> On Thu, Jan 28, 2016 at 5:06 PM, Kees Cook wrote:
> > Tracing processes for syscall usage can be done one step at a time with
> > SECCOMP_RET_TRAP, but this will block the syscall. Alternatively, using
> > a ptrace manager to handle SECCOMP_RE
On Sun, Jan 31, 2016 at 12:18 PM, Michael S. Tsirkin wrote:
> On Sun, Jan 31, 2016 at 12:13:58PM -0800, Andy Lutomirski wrote:
>> On Sun, Jan 31, 2016 at 12:09 PM, Michael S. Tsirkin wrote:
>> > On Fri, Jan 29, 2016 at 10:34:59AM +, David Vrabel wrote:
>> >> On 29/01/16 02:31, Andy Lutomirski
On Sun, Jan 31, 2016 at 09:13:19PM +0100, Johan Hovold wrote:
> On Fri, Jan 29, 2016 at 12:07:30AM +0300, Andrey Skvortsov wrote:
> > $ lsusb:
> > Bus 001 Device 101: ID 1e0e:9001 Qualcomm / Option
> >
> > $ usb-devices:
> > T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=101 Spd=480 MxCh= 0
> > D:
Hi Jesper,
On Sun, 31 Jan 2016 19:40:48 +0100 Jesper Dangaard Brouer
wrote:
>
> On Sun, 31 Jan 2016 13:15:06 +1100
> Stephen Rothwell wrote:
>
> > On Sat, 30 Jan 2016 18:46:46 +0100 Jesper Dangaard Brouer
> > wrote:
> > >
> > > Let me know, if the linux-next tree need's an explicit fix?
The initialization of interrupt controller for devicetree platform was
done for pxa2xx platforms, but not for pxa3xx ones.
Fix this my adding the missing initialization call.
Fixes: 089d03629b04 ("ARM: pxa: add devicetree code for irq handling")
Signed-off-by: Robert Jarzmik
---
arch/arm/mach-p
Mathieu OTHACEHE writes:
> This patch fixes the following coccinelle warnings:
>
> drivers/usb/serial/mos7840.c:2042:4-10: Move constant to right.
> drivers/usb/serial/mos7840.c:2062:16-22: Move constant to right.
>
> Signed-off-by: Mathieu OTHACEHE
> ---
> drivers/usb/serial/mos7840.c | 4 ++--
On Fri, Jan 29, 2016 at 11:45 PM, Rafael J. Wysocki wrote:
> On Friday, January 29, 2016 12:56:14 PM Joe Lawrence wrote:
>> On 01/29/2016 12:01 PM, Steven Rostedt wrote:
>> > On Thu, Jan 28, 2016 at 02:13:04PM -0600, Corey Minyard wrote:
>> >> Tomeu, you added that check in
>> >>
>> >> [989561de9b
On Sun, Jan 31, 2016 at 09:33:25AM -0800, Andy Lutomirski wrote:
> I broke iopl(2) with my syscall rework. Fix it up. While debugging
> it, I found a bug in my IRQ state handling. Fix that, too.
>
> Andy Lutomirski (3):
> x86/entry/64: Fix an IRQ state error on ptregs-using syscalls
> x86/e
Regmap config max_register field should contain number of
device last register, however num_reg_defaults_raw field
should be set to register count instead
(usually one register more than max_register).
as3711 driver had both of these fields set to the same value,
fix this by introducing separate d
1 - 100 of 298 matches
Mail list logo
