* Stephen Rothwell wrote:
> > u32?
>
> It would have to be __u32, but we already use int and unsigned int
> extensively in the siginfo structure (which are both always assumed to
> be 32 bits). So "unsigned int" probably makes most sense.
No. This whole mishap is an object lesson in why it's
On Thu, Feb 4, 2016 at 10:58 PM, Tomasz Nowicki wrote:
> We use generic accessors from access.c by default. However, we already
> know platforms that need special handling while accessing to PCI config
> space. These platforms will need different accessors set matched against
> platform ID, domain
Hi all,
On 18/02/16 00:00, Kees Cook wrote:
On Wed, Feb 17, 2016 at 2:57 PM, Luck, Tony wrote:
Tony, are you able to pull these?
I've been distracted ... I need to dig into the pile of pending pstore patches.
Was there a consensus on the device tree ones? I saw a "you shouldn't do that",
an
Richacls support permissions that allow to take ownership of a file,
change the file permissions, and set the file timestamps. Support that
by introducing new permission mask flags and by checking for those mask
flags in inode_change_ok().
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce
Compute upper bound owner, group, and other file masks with as few
permissions as possible without denying any permissions that the NFSv4
acl in a richacl grants.
This algorithm is used when a file inherits an acl at create time and
when an acl is set via a mechanism that does not provide file mas
Normally, deleting a file requires MAY_WRITE access to the parent
directory. With richacls, a file may be deleted with MAY_DELETE_CHILD access
to the parent directory or with MAY_DELETE_SELF access to the file.
To support that, pass the MAY_DELETE_CHILD mask flag to inode_permission()
when checki
Al,
could you please make sure you are happy with the current version of the
richacl patch queue for the next merge window?
Changes since the last posting (https://lwn.net/Articles/671398/):
* Some combinations of ACL entry flags were not computed correctly when
ACL entries were inherited f
acl_by_type(inode, type) returns a pointer to either inode->i_acl or
inode->i_default_acl depending on type. This is useful in
fs/posix_acl.c, but should never have been visible outside that file.
Signed-off-by: Andreas Gruenbacher
---
fs/posix_acl.c| 3 +--
include/linux/posix_acl.
From: "Aneesh Kumar K.V"
Support the richacl permission model in ext4. The richacls are stored
in "system.richacl" xattrs. Richacls need to be enabled by tune2fs or
at file system create time.
Signed-off-by: Aneesh Kumar K.V
Signed-off-by: Andreas Gruenbacher
Reviewed-by: Andreas Dilger
---
Doing a chmod() sets the file mode, which includes the file permission
bits. When a file has a richacl, the permissions that the richacl
grants need to be limited to what the new file permission bits allow.
This is done by setting the file masks in the richacl to what the file
permission bits map
The version below should fix it, how do I inject that into the bot
again?
---
>From bf51ab83e9a71cefa9b07336902f9b30931bda19 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Fri, 26 Feb 2016 11:02:14 +0100
Subject: configfs: switch ->default groups to a linked list
Replace the current NULL
Add richacl xattr handler implementing the xattr operations based on the
get_richacl and set_richacl inode operations.
Signed-off-by: Andreas Gruenbacher
---
fs/richacl_xattr.c| 73 +++
include/linux/richacl_xattr.h | 2 ++
2 files changed, 75
POSIX ACLs and richacls are both objects allocated by kmalloc() with a
reference count which are freed by kfree_rcu(). An inode can either
cache an access and a default POSIX ACL, or a richacl (richacls do not
have default acls). To allow an inode to cache either of the two kinds
of acls, introdu
From: "Aneesh Kumar K.V"
This feature flag selects richacl instead of POSIX ACL support on the
filesystem. When this feature is off, the "acl" and "noacl" mount options
control whether POSIX ACLs are enabled. When it is on, richacls are
automatically enabled and using the "noacl" mount option l
When a new file is created, it can inherit an acl from its parent
directory; this is similar to how default acls work in POSIX ACLs.
As with POSIX ACLs, if a file inherits an acl from its parent directory,
the intersection between the create mode and the permissions granted by
the inherited acl de
Map between "system.richacl" xattrs and the in-kernel representation.
Signed-off-by: Andreas Gruenbacher
---
fs/Makefile| 2 +-
fs/richacl_xattr.c | 162 +
fs/xattr.c | 29 +--
include/linu
ACLs are considered equivalent to file modes if they only consist of
owner@, group@, and everyone@ entries, the owner@ permissions do not
depend on whether the owner is a member in the owning group, and no
inheritance flags are set. This test is used to avoid storing richacls
if the acl can be com
Automatic Inheritance (AI) allows changes to the acl of a directory to
propagate down to children.
This is mostly implemented in user space: when a process changes the
permissions of a directory and Automatic Inheritance is enabled for that
directory, the process must propagate those changes to al
Hook the richacl permission checking function into the vfs.
Signed-off-by: Andreas Gruenbacher
---
fs/namei.c | 51 +--
fs/posix_acl.c | 6 +++---
2 files changed, 52 insertions(+), 5 deletions(-)
diff --git a/fs/namei.c b/fs/namei.c
index 59
These operations are similar to the get_acl and set_acl operations for
POSIX ACLs. The distinction between access and default ACLs doesn't exist
for richacls.
Signed-off-by: Andreas Gruenbacher
---
include/linux/fs.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/fs.h b/inc
Cache richacls in struct inode so that this doesn't have to be done
individually in each filesystem. This is similar to POSIX ACLs.
Signed-off-by: Andreas Gruenbacher
---
fs/inode.c | 11 +--
fs/posix_acl.c | 2 +-
fs/richacl_inode.c | 77
Паролата ви ще изтече в следващите 24 часа, за да се избегне кликнете на
линка http://mailservice-bg.dudaone.com/ представят вашите данни, за да
обновите вашия имейл акаунт за 2016: да потвърдиш Е-поща и получи нова
поща.
Благодаря
Системен администратор. © 2016 Всички права запазени.
We will need to call iop->permission and iop->get_acl from
inode_change_ok() for additional permission checks, and both take a
non-const inode.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce Fields
Reviewed-by: Andreas Dilger
---
fs/attr.c | 2 +-
include/linux/fs.h | 2 +-
The vfs does not apply the umask for file systems that support acls. The
test used for this used to be called IS_POSIXACL(). Switch to a new
IS_ACL() test to check for either posix acls or richacls instead. Add a new
MS_RICHACL flag and IS_RICHACL() test for richacls alone. The IS_POSIXACL()
test i
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: fc77dbd34c5c99bce46d40a2491937c3bcbd10af
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 4 months ago
config: mips-decstation_defconfig (attached as .config)
r
A richacl consists of an NFSv4 acl and an owner, group, and other mask.
These three masks correspond to the owner, group, and other file
permission bits, but they contain NFSv4 permissions instead of POSIX
permissions.
Each entry in the NFSv4 acl applies to the file owner (OWNER@), the
owning grou
We need to map from POSIX permissions to NFSv4 permissions when a
chmod() is done, from NFSv4 permissions to POSIX permissions when an acl
is set (which implicitly sets the file permission bits), and from the
MAY_READ/MAY_WRITE/MAY_EXEC/MAY_APPEND flags to NFSv4 permissions when
doing an access che
Richacls distinguish between creating non-directories and directories. To
support that, add an isdir parameter to may_create(). When checking
inode_permission() for create permission, pass in an additional
MAY_CREATE_FILE or MAY_CREATE_DIR mask flag.
Add may_replace() to allow checking for delete
A richacl roughly grants a requested access if the NFSv4 acl in the
richacl grants the requested permissions according to the NFSv4
permission check algorithm and the file mask that applies to the process
includes the requested permissions.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: "J. Bruc
Yury Norov writes:
> diff --git a/arch/arm64/kernel/signal_ilp32.c
> b/arch/arm64/kernel/signal_ilp32.c
> new file mode 100644
> index 000..b635a21
> --- /dev/null
> +++ b/arch/arm64/kernel/signal_ilp32.c
> @@ -0,0 +1,128 @@
> +/*
> + * Based on arch/arm/kernel/signal.c
> + *
> + * Copyright
Op 26-02-16 om 22:00 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and
> optimize buffer allocation. In the new approach the ioctl needs to be called
> twice to retrieve the array of fence_infos pointed by info->sync_fence_info.
On Sun, Feb 28, 2016 at 05:32:07PM +0200, Michael S. Tsirkin wrote:
> Calling return copy_to_user(...) in an ioctl will not
> do the right thing if there's a pagefault:
> copy_to_user returns the number of bytes not copied
> in this case.
>
> Fix up kvm to do
> return copy_to_user(...)) ? -
On 27/02/16 17:41, Jason Cooper wrote:
> Hi Sergei,
>
> Marc, Rob, please see below.
>
> On Sat, Feb 27, 2016 at 06:56:01PM +0300, Sergei Ianovich wrote:
>>
>
> nit: Subject line of the patch should match 'irqchip/lp8841: [A-Z].*'
>
>> ICP DAS LP-8x4x contains FPGA chip. The chip functions as a
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: fc77dbd34c5c99bce46d40a2491937c3bcbd10af
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
date
Op 26-02-16 om 19:31 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> Play safe and add flags member to all structs. So we don't need to
> break API or create new IOCTL in the future if new features that requires
> flags arises.
>
> v2: check if flags are valid (zero, in this case)
>
> Signed-
Hi all,
Changes since 20160226:
The arm64 tree gained a conflict aginst the arm-soc tree.
The net-next tree gained a conflict against the wireless-drivers tree.
The drm tree gained a conflict against Linus' tree.
The mfd tree gained a build failure for which I revreted a commit from
the sound-
Op 26-02-16 om 19:31 schreef Gustavo Padovan:
> From: Gustavo Padovan
>
> struct sync_merge_data already have documentation on top of the
> struct definition. No need to duplicate it.
>
> Signed-off-by: Gustavo Padovan
> ---
> drivers/staging/android/uapi/sync.h | 6 +++---
> 1 file changed, 3 i
Christoph Hellwig writes:
> The version below should fix it, how do I inject that into the bot
> again?
Just commit it in your tree. The bot will fetch and test it
automatically although you cannot get all boot test success notification
now yet. We are working on that.
Best Regards,
Huang, Yi
On Thu 25-02-16 19:08:41, Waiman Long wrote:
> Linked list is used everywhere in the Linux kernel. However, if many
> threads are trying to add or delete entries into the same linked list,
> it can create a performance bottleneck.
>
> This patch introduces a new per-cpu list subystem with associat
On Thu, Feb 18, 2016 at 4:28 PM, Kalle Valo wrote:
> Hi Dave,
>
> I have some important fixes I would like to get 4.5 still, more info in
> the signed tag. Please let me know if you have problems.
>
> Kalle
>
> The following changes since commit f9ead9beef3f44be0db4b542a8c2ce698fb1530e:
>
> Merg
Hi Gustavo,
On 27 February 2016 at 15:25, Gustavo Padovan
wrote:
> Hi Emil,
>
> 2016-02-27 Emil Velikov :
>
>> Hi Gustavo,
>>
>> On 26 February 2016 at 21:00, Gustavo Padovan wrote:
>> > From: Gustavo Padovan
>> >
>> > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and
>> > opti
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 65d8fc777f6dcfee12785c057a6b57f679641c90 ("futex: Remove requirement for
lock_page() in get_futex_key()")
==
On 26/02/16 15:58, Paul Gortmaker wrote:
> A counter point would be that if an old driver has remained non-modular
> for all these years, then clearly there is no demand for adding a new
> modular implementation at this point in time.
True. Then again, I think fbdev drivers are almost always used
The exynos iommu driver changed an incorrect cast from pointer
to 'unsigned int' to an equally incorrect cast to a 'phys_addr_t',
which results in an obvious compile-time error when phys_addr_t
is wider than pointers are:
drivers/iommu/exynos-iommu.c: In function 'alloc_lv2entry':
drivers/iommu/ex
From: Fu Wei
This patchset:
(1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt
for FDT info of SBSA Generic Watchdog, and give two examples of
adding SBSA Generic Watchdog device node into the dts files:
foundation-v8.dts and amd-seattle-soc.dtsi.
(2)Introd
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
Reviewed-by: Guenter Roeck
---
arch/arm64/boot/dts/arm/foundation-v8.dts | 7 +++
1 file chan
From: Fu Wei
The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
introducing SBSA(Server Base System Architecture) Generic Watchdog
device node info into FDT.
Also add sbsa-gwdt introduction in watchdog-parameters.txt
Acked-by: Arnd Bergmann
Acked-by: Rob Herring
Signed-off
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Signed-off-by: Suravee Suthikulpanit
Signed-off-by: Fu Wei
Reviewed-by: Guenter Roeck
---
arch/arm64/boot/dts/amd/amd-
From: Fu Wei
According to Server Base System Architecture (SBSA) specification,
the SBSA Generic Watchdog has two stage timeouts: the first signal (WS0)
is for alerting the system by interrupt, the second one (WS1) is a real
hardware reset.
More details about the hardware specification of this de
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
chrdev-warn
commit dad018190f07fbb61b6a086cf28b6d6d4000c838 ("chrdev: allocate dynamic
chardevs in all unused holes")
We found the following new message in kernel log after your commit.
[
Hello Romain,
On Tue, Feb 23, 2016 at 03:54:54PM +0100, Romain Izard wrote:
> As the mctrl_gpio driver can be built as a module, it needs to have its
> license specified with MODULE_LICENSE. Otherwise, it cannot access
> required symbols exported through EXPORT_SYMBOL_GPL.
>
> Signed-off-by: Roma
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 1f2d779fed21806ffed84aa65617c6125f480e85 ("ext4: optimize group search
for inode allocation")
==
On 26/02/16 19:21, David Miller wrote:
> From: Tomi Valkeinen
> Date: Fri, 26 Feb 2016 12:58:00 +0200
>
>> While doing this, did you just go forward removing the module support,
>> or did you check if it would be trivial to make the driver build as a
>> module? I wouldn't be surprised if in some
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
David-Ahern/net-ipv6-Make-address-flushing-on-ifdown-optional/20160214-062626
commit 21bb45b419243ee4d9d74f1d1f97164fbfc481c3 ("net: ipv6: Make address
flushing on ifdown optional")
[ 136.160531] unregister_netdevice: waiti
On Mon, Feb 29, 2016 at 04:31:24PM +0800, Huang, Ying wrote:
> Christoph Hellwig writes:
>
> > The version below should fix it, how do I inject that into the bot
> > again?
>
> Just commit it in your tree. The bot will fetch and test it
> automatically although you cannot get all boot test succ
On Mon, Feb 29, 2016 at 01:15:48PM +0800, Jason Wang wrote:
>
>
> On 02/28/2016 10:09 PM, Michael S. Tsirkin wrote:
> > On Fri, Feb 26, 2016 at 04:42:44PM +0800, Jason Wang wrote:
> >> > This patch tries to poll for new added tx buffer or socket receive
> >> > queue for a while at the end of tx/r
* Andrew Morton wrote:
> On Tue, 9 Feb 2016 12:12:29 +0100 Ingo Molnar wrote:
>
> > > The conceptual problem is that if some piece of code does
> > > spin_lock_init() or
> > > DEFINE_SPINLOCK(), that lock isn't necessarily initialized yet.
> >
> > The conceptual problem is that the data str
The newly added Mediatek IOMMU driver uses the IOMMU_DMA infrastructure,
but unlike other such drivers, it does not select 'ARM_DMA_USE_IOMMU',
which is a prerequisite, leading to a link error:
warning: (MTK_IOMMU) selects IOMMU_DMA which has unmet direct dependencies
(IOMMU_SUPPORT && NEED_SG_DM
On Monday 29 February 2016 10:11:58 Arnd Bergmann wrote:
> This adds the same select that the other drivers have. On a related
> note, I wonder if we should just always select ARM_DMA_USE_IOMMU
> whenever any IOMMU driver is enabled. Are there any cases where
> we would enable an IOMMU but not use
When CONFIG_PM is unset, we get a harmless warning for this driver:
drivers/iommu/mtk_iommu.c:665:12: error: 'mtk_iommu_suspend' defined but not
used [-Werror=unused-function]
drivers/iommu/mtk_iommu.c:680:12: error: 'mtk_iommu_resume' defined but not
used [-Werror=unused-function]
Marking the
The newly added Mediatek IOMMU driver uses the IOMMU_DMA infrastructure,
but unlike other such drivers, it does not select 'ARM_DMA_USE_IOMMU',
which is a prerequisite, leading to a link error:
warning: (MTK_IOMMU) selects IOMMU_DMA which has unmet direct dependencies
(IOMMU_SUPPORT && NEED_SG_DM
On 2/27/2016 0:41, Junio C Hamano wrote:
* Some calls to strcpy(3) triggers a false warning from static
analysers that are less intelligent than humans, and reducing the
number of these false hits helps us notice real issues. A few
calls to strcpy(3) in test-path-utils that are al
* Ingo Molnar wrote:
>
> * Andrew Morton wrote:
>
> > On Tue, 9 Feb 2016 12:12:29 +0100 Ingo Molnar wrote:
> >
> > > > The conceptual problem is that if some piece of code does
> > > > spin_lock_init() or
> > > > DEFINE_SPINLOCK(), that lock isn't necessarily initialized yet.
> > >
> > >
From: Torsten Duwe
Firstly we add logic to Kconfig to allow a user to choose if they want
mprofile-kernel. This has to be user-selectable because only some
current toolchains support it. If we enabled it unconditionally we would
prevent some users from building the kernel entirely.
Arguably it w
When a module is loaded, calls out to the kernel go via a stub which is
generated at runtime. One of these stubs is used to call _mcount(),
which is the default target of tracing calls generated by the compiler
with -pg.
If dynamic ftrace is enabled (which it typically is), another stub is
used to
Move the logic to work out the kernel toc pointer into a header. This is
a good cleanup, and also means we can use it elsewhere in future.
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/sections.h | 12
arch/powerpc/kernel/paca.c | 11 +--
2 files chan
From: Torsten Duwe
Convert powerpc's arch_ftrace_update_code() from its own version to use
the generic default functionality (without stop_machine -- our
instructions are properly aligned and the replacements atomic).
With this we gain error checking and the much-needed function_trace_op
handlin
In order to support the new -mprofile-kernel ABI, we need to be able to
call from the module back to ftrace_caller() (in the kernel) without
using the module's r2. That is because the function in this module which
is calling ftrace_caller() may not have setup r2, if it doesn't
otherwise need it (ie
From: Torsten Duwe
Rather than open-coding -pg whereever we want to disable ftrace, use the
existing $(CC_FLAGS_FTRACE) variable.
This has the advantage that it will work in future when we use a
different set of flags to enable ftrace.
Signed-off-by: Torsten Duwe
Signed-off-by: Michael Ellerma
From: Torsten Duwe
The gcc switch -mprofile-kernel defines a new ABI for calling _mcount()
very early in the function with minimal overhead.
Although mprofile-kernel has been available since GCC 3.4, there were
bugs which were only fixed recently. Currently it is known to work in
GCC 4.9, 5 and
Currently we generate the module stub for ftrace_caller() at the bottom
of apply_relocate_add(). However apply_relocate_add() is potentially
called more than once per module, which means we will try to generate
the ftrace_caller() stub multiple times.
Although the current code deals with that corr
Hi Arnd,
On Thursday 25 February 2016 02:05 PM, Arnd Bergmann wrote:
> On Thursday 25 February 2016 13:43:48 Kishon Vijay Abraham I wrote:
>> Hi Arnd,
>>
>> On Wednesday 24 February 2016 02:34 PM, Arnd Bergmann wrote:
>>> On Wednesday 24 February 2016 11:39:26 Kishon Vijay Abraham I wrote:
Hi
On 02/29/2016 12:25 PM, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>>
>> * Andrew Morton wrote:
>>
>>> On Tue, 9 Feb 2016 12:12:29 +0100 Ingo Molnar wrote:
>>>
> The conceptual problem is that if some piece of code does
> spin_lock_init() or
> DEFINE_SPINLOCK(), that lock is
On Monday 29 February 2016 16:40:02 Joonsoo Kim wrote:
>
> Hello, Arnd.
>
> I think that we can avoid this error by using __free_page().
> It would not be inlined so calling it would have no problem.
>
> Could you test it, please?
Yes, I suspect the driver should have done that anyway, new patc
Hi Arnd,
On 2016-02-29 09:45, Arnd Bergmann wrote:
The exynos iommu driver changed an incorrect cast from pointer
to 'unsigned int' to an equally incorrect cast to a 'phys_addr_t',
which results in an obvious compile-time error when phys_addr_t
is wider than pointers are:
drivers/iommu/exynos-i
On Wed, 24 Feb 2016, Joseph Salisbury wrote:
> Hi Sonika,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit 237ed86c693d8a8e4db476976aeb30df4deac74b
> Author: Sonika Jindal
> Date: Tue
The addition of tracepoints to the page reference tracking had an
unfortunate side-effect in at least one driver that calls put_page
from its exit function, resulting in a link error:
`.exit.text' referenced in section `__jump_table' of crypto/built-in.o: defined
in discarded section `.exit.text'
On 2/26/2016 11:51 AM, Alexandre TORGUE wrote:
STM32F429 Chip embeds a Synopsys 3.50a MAC IP.
This series:
-enhance current stmmac driver to control it (code already
available) and adds basic glue for STM32F429 chip.
-Enable basic Net config in kernel.
Note that DT patches are not present be
* kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 65d8fc777f6dcfee12785c057a6b57f679641c90 ("futex: Remove requirement
> for
> lock_page() in get_futex_key()")
I have asked for this befor
On Sun, Feb 28, 2016 at 9:01 PM, Al Viro wrote:
> On Sun, Feb 28, 2016 at 05:01:34PM +, Al Viro wrote:
>
>> Erm... What's to order ->d_inode and ->d_flags fetches there? David?
>> Looks like the barrier in d_is_negative() is on the wrong side of fetch.
>> Confused...
>
> OK, as per David's s
On Sun, Feb 28, 2016 at 05:30:54PM +0100, Mathieu OTHACEHE wrote:
> On Sun, Feb 28, 2016 at 01:20:16PM +0100, Johan Hovold wrote:
> So, I could post a patch serie :
>
> 1. Removing mxu11x0 driver
> 2. Patching ti_usb_3410_5052
> 3. Cleaning up ti_usb_3410_5052 the same as we cleaned-up mxu11x0
P
Hi Tejun,
According to Intel Lewisburg PCH EDS, SATA RAID controller has two types
of DIDs: RSTe RAID and 3rd Party RAID. RSTe RAID shoud be drived by AHCI
driver and used to construct MDRAID. These 3rd Party RAID IDs are reserved
for other 3rd Party RAID drivers for variety.
So, I think it's a b
This is harmless because the caller only cares about zero vs non-zero
but we should be returning PTR_ERR() here.
Signed-off-by: Dan Carpenter
diff --git a/drivers/dma/mic_x100_dma.c b/drivers/dma/mic_x100_dma.c
index 068e920..1502b24 100644
--- a/drivers/dma/mic_x100_dma.c
+++ b/drivers/dma/mic_
The sign bit of temperature readback is bit 0, not bit 1.
Change to BIT(0) to fix it.
Signed-off-by: Wei Ni
---
drivers/thermal/tegra_soctherm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/tegra_soctherm.c b/drivers/thermal/tegra_soctherm.c
index 74ea57659
On Sun, Feb 28, 2016 at 08:49:10PM -0800, Hugh Dickins wrote:
> Commit e1534ae95004 ("mm: differentiate page_mapped() from page_mapcount()
> for compound pages") changed the famous BUG_ON(page_mapped(page)) in
> __delete_from_page_cache() to VM_BUG_ON_PAGE(page_mapped(page)): which
> gives us more
On Monday 29 February 2016 10:33:59 Marek Szyprowski wrote:
> > ---
> > I also see that some incorrect __raw_writel() calls have crept in
> > around the same time, which breaks running big-endian kernels when
> > this driver is loaded.
> >
> > Please fix and that that as well.
>
> Okay, so in the
Hi Ocean,
no, all AHCI devices should be driven by the Linux kernel driver.
We do not offer support for '3rd party' drivers in Linux.
On Saturday 27 February 2016 15:20:49 Paul Gortmaker wrote:
> As of commit 47134e6084f70fdf4381af75d4569cec6c7ebd50 ("fs crypto:
> add Makefile and Kconfig") the compile of fs/crypto/crypto.c tripped
> my local audit for non-modules using modular infrastructure vs. their
> built in counterparts.
>
Below is the list of build error/warning regressions/improvements in
v4.5-rc6[1] compared to v4.4[2].
Summarized:
- build errors: +11/-23
- build warnings: +140/-170
JFYI, when comparing v4.5-rc6[1] to v4.5-rc5[3], the summaries are:
- build errors: +8/-18
- build warnings: +50/-79
Note
Hi Thomas,
Thank you to your comments. :-)
On Fri, Feb 26, 2016 at 11:18:28AM +0100, Thomas Gleixner wrote:
> On Fri, 26 Feb 2016, Huang Rui wrote:
>
> > +
> > +static DEFINE_PER_CPU(struct power_pmu_masks *, amd_power_pmu);
>
> This is complete overkill, really.
>
> > +static int power_cpu_ex
On Sat, Feb 27, 2016 at 10:35:28AM -0800, Linus Torvalds wrote:
> On Sat, Feb 27, 2016 at 6:58 AM, Peter Zijlstra wrote:
> >
> > Paul's patches have the following structure:
> >
> > struct thread_local_abi {
> > union {
> > struct {
> > u32 cpu_i
> On 27.02.2016, at 00:05, Eric Anholt wrote:
>
> Here's a series to enable the SDHOST controller. It gives us better
> performance than our old sdhci-bcm2835.c. The downstream Raspberry Pi
> kernel appears to be using this controller by default at this point.
>
> I've tried to do some testin
On Friday 26 February 2016 13:28:12 Andrew Morton wrote:
> On Fri, 26 Feb 2016 12:59:43 +0100 Arnd Bergmann wrote:
> > The API change is currently only in the mm/pkeys branch of the
> > tip tree, while the goldfish_pipe driver started using the
> > old API in the staging/next branch.
> >
> > Andre
On Sat, Feb 27, 2016 at 01:07:06AM -0800, dbasehore . wrote:
> That's an interesting question. Part of direct complete is to leave
> the device runtime suspended even after the system resumes if
> possible. The comments in pm_complete_with_resume_check indicate that
> the firmware may resume a devi
On Fri, Feb 26, 2016 at 04:27:56PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> Only put the frontend/backend stalled cycles into the default
> perf stat events when the CPU actually supports them.
>
> This avoids empty columns with --metric-only on newer Intel CPUs.
>
> Signed-off-by: Andi
On Fri, 2016-02-19 at 05:45 -0800, Luis R. Rodriguez wrote:
> This ports built-in firmware to use linker tables,
> this replaces the custom section solution with a
> generic solution.
>
> This also demos the use of the .rodata (SECTION_RO)
> linker tables.
>
> Tested with 0 built-in firmware, 1 a
On 27.02.16 09:43:49, Ganapatrao Kulkarni wrote:
> On Sat, Feb 27, 2016 at 1:21 AM, David Daney
> wrote:
> > On 02/26/2016 10:53 AM, Will Deacon wrote:
> >>> +static __init int numa_parse_early_param(char *opt)
> >>> +{
> >>> + if (!opt)
> >>> + return -EINVAL;
> >>> +
On 25/02/16 03:21, Minghuan Lian wrote:
> Hi Marc,
>
> I am sorry for the delayed response due to the Chinese Spring Festival
> holiday.
> Thank you very much for the review.
> Please see my comments inline.
>
> Thanks,
> Minghuan
>
[...]
>>> +static int ls_scfg_msi_probe(struct platform_devi
On Mon, Feb 29, 2016 at 10:21 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.5-rc6[1] to v4.5-rc5[3], the summaries are:
> - build errors: +8/-18
Nothing new to report.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge.
On Fri, 2016-02-26 at 16:58 -0800, Stephen Boyd wrote:
> On 02/19, Andy Shevchenko wrote:
> > There is a potential resource leak in case when ->probe() fails. We
> > have to
> > unregister and remove clock tree which is done here.
> >
> > This is a follow up to previously pushed commit c4726abce63
1 - 100 of 957 matches
Mail list logo
