On Mon 17 Oct 08:49 PDT 2016, Matt Redfearn wrote:
> Since there is now an always available state file in sysfs with the same
> function as this one in debugfs, remove the redundant entry.
>
> Signed-off-by: Matt Redfearn
Acked-by: Bjorn Andersson
Regards,
Bjorn
> ---
>
> Changes in v2: Non
On Mon 17 Oct 08:49 PDT 2016, Matt Redfearn wrote:
> This patch adds a sysfs interface to rproc allowing the firmware name
> and processor state to be changed dynamically.
>
> State was previously available in debugfs, and is replicated here. The
> firmware file allows retrieval of the running fi
Add documentation for the iopmem PCIe device driver.
Signed-off-by: Stephen Bates
Signed-off-by: Logan Gunthorpe
---
Documentation/blockdev/00-INDEX | 2 ++
Documentation/blockdev/iopmem.txt | 62 +++
2 files changed, 64 insertions(+)
create mode 100644 D
Hi,
> From: Yisheng Xie [mailto:xieyishe...@huawei.com]
> Sent: Tuesday, October 18, 2016 4:47 AM
> To: Zheng, Lv ; Moore, Robert ;
> Wysocki, Rafael J
> ; l...@kernel.org; wmi...@sgl.com
> Cc: linux-a...@vger.kernel.org; de...@acpica.org;
> linux-kernel@vger.kernel.org; guohan...@huawei.com;
>
On Tue, Oct 18, 2016 at 2:36 PM, Emese Revfy wrote:
> On Tue, 18 Oct 2016 13:57:35 -0700
> Kees Cook wrote:
>
>> This is controlled by CONFIG_FRAME_WARN. I don't think this is a
>> particular problem or should be avoided, but perhaps we can set the
>> default to 2048 (as done on 64BIT) if we're b
On 10/18/2016 11:10 PM, David Oberhollenzer wrote:
> On 10/18/2016 09:15 PM, Boris Brezillon wrote:
>> On Tue, 18 Oct 2016 11:46:51 -0700
>> Brian Norris wrote:
>>
>>> + others
>>>
>>> On Tue, Oct 18, 2016 at 06:15:23PM +0200, Richard Weinberger wrote:
On 18.10.2016 17:55, Cyrille Pitchen wro
On Mon 17 Oct 08:48 PDT 2016, Matt Redfearn wrote:
> Storage of the firmware name was inconsistent, either storing a pointer
> to a name stored with unknown ownership, or a variable length tacked
> onto the end of the struct proc allocated in rproc_alloc.
>
> In preparation for allowing the firmw
ptdump_register currently initializes a set of page table information and
registers debugfs. There are uses for the ptdump option without wanting the
debugfs options. Split this out to make it a separate option.
Reviewed-by: Kees Cook
Reviewed-by: Mark Rutland
Tested-by: Mark Rutland
Signed-of
The page table dumping code always assumes it will be dumping to a
seq_file to userspace. Future code will be taking advantage of
the page table dumping code but will not need the seq_file. Make
the seq_file optional for these cases.
Reviewed-by: Kees Cook
Reviewed-by: Mark Rutland
Tested-by: M
Page mappings with full RWX permissions are a security risk. x86
has an option to walk the page tables and dump any bad pages.
(See e1a58320a38d ("x86/mm: Warn on W^X mappings")). Add a similar
implementation for arm64.
Reviewed-by: Kees Cook
Reviewed-by: Mark Rutland
Tested-by: Mark Rutland
S
max_addr was added as part of struct ptdump_info but has never actually
been used. Remove it.
Reviewed-by: Kees Cook
Reviewed-by: Mark Rutland
Tested-by: Mark Rutland
Signed-off-by: Laura Abbott
---
v3: No changes
---
arch/arm64/include/asm/ptdump.h | 1 -
1 file changed, 1 deletion(-)
diff
Hi,
This is v3 of the implementation to check for writable and executable pages on
arm64. This is a basically a rebase + acks.
Laura Abbott (4):
arm64: dump: Make ptdump debugfs a separate option
arm64: dump: Make the page table dumping seq_file optional
arm64: dump: Remove max_addr
arm64
On 10/18/2016 04:56 AM, Vincent Guittot wrote:
Le Tuesday 18 Oct 2016 à 12:34:12 (+0200), Peter Zijlstra a écrit :
On Tue, Oct 18, 2016 at 11:45:48AM +0200, Vincent Guittot wrote:
On 18 October 2016 at 11:07, Peter Zijlstra wrote:
So aside from funny BIOSes, this should also show up when cr
On Tue, Oct 18, 2016 at 03:30:45PM +0200, Daniel Wagner wrote:
> On 10/10/2016 10:37 PM, Luis R. Rodriguez wrote:
>
> > > fw_get_fileystem_firmware()
> > > fw_finish_direct_load()
> > > complete_all()
> > >
> > >
> > > 2nd request (waiter context)
> > >
> > > _request_firmware()
> >
> It's multiple values per file, so it has no business being in sysfs,
> besides it was assuming seqfile anyway.
>
> Introduced by
> commit d806f30e639b ("staging: lustre: osc: revise unstable pages accounting")
Tested it manually to make sure it was right this time.
Reviewed-by: James Simmons
On 10/18/2016 02:37 PM, Peter Zijlstra wrote:
Have you read this thread:
lkml.kernel.org/r/20161018115651.ga20...@linaro.org
Yeah... I noticed the thread... I'm replying to the thread too.
Thanks,
Joonwoo
Have you read this thread:
lkml.kernel.org/r/20161018115651.ga20...@linaro.org
On Tue, 18 Oct 2016 13:57:35 -0700
Kees Cook wrote:
> This is controlled by CONFIG_FRAME_WARN. I don't think this is a
> particular problem or should be avoided, but perhaps we can set the
> default to 2048 (as done on 64BIT) if we're building with the entropy
> plugin.
This is probably a gcc co
On 18.10.2016 23:26, Ryan Swan wrote:
> As per discusion with Lino Sanfilippo, memcpy is the proper way to copy
> across dma memory, which also removes sparse warning that triggered
> inquiry.
>
> Signed-off-by: Ryan Swan
> ---
> drivers/staging/slicoss/slicoss.c | 2 +-
> 1 file changed, 1 inse
On Tue, Oct 18, 2016 at 12:16:10AM +0200, Arnd Bergmann wrote:
> apm_bios_call() can fail, and return a status in its argument
> structure. If that status however is zero during a call from
> apm_get_power_status(), we end up using data that may have
> never been set, as reported by "gcc -Wmaybe-un
As per discusion with Lino Sanfilippo, memcpy is the proper way to copy
across dma memory, which also removes sparse warning that triggered
inquiry.
Signed-off-by: Ryan Swan
---
drivers/staging/slicoss/slicoss.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/
When a new cgroup is created, scheduler attaches the child cgroup
to its parent and also increases the parent's task_group load_avg to
account increased load with following path :
sched_create_group()
alloc_fair_sched_group()
sched_online_group()
online_fair_sched_group()
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
Hello,
I noticed that module autoload won't be working in some of the qcom
remoteproc drivers. This patch series contains the fixes for these.
Best regards,
Javier
Javier Martinez Canillas (3):
remoteproc: qcom: q6v5_pil: Fix module autoload
remoteproc: qcom: wcnss: Fix module autoload
re
On 10/18/2016 07:28 AM, Vivek Gautam wrote:
> From: Yaniv Gardi
>
> Since in future UFS Phy's the tx_iface_clk and rx_iface_clk
> are no longer exist, we should not fail when their initialization
> fail, but rather just report with debug message.
>
> Signed-off-by: Yaniv Gardi
> Signed-off-by: Vi
On Tue, Oct 18, 2016 at 10:08:44AM +0200, Vegard Nossum wrote:
>
Vegard, thanks for bringing this to attention!
Including this hunk for those that were originally not CC'd
on the original patch.
> diff --git a/include/linux/extarray.h b/include/linux/extarray.h
> new file mode 100644
> index 000
When the user namespace support was merged the need to prevent
ptracing an executable that is not readable was overlooked.
Correct this oversight by not letting exec succeed if during exec an
executable is not readable and the current user namespace capabilities
do not apply to the executable's f
On Tue, 2016-10-18 at 13:48 -0700, Kees Cook wrote:
> On Mon, Oct 17, 2016 at 6:44 AM, Mark Rutland
> wrote:
> > Hi,
> >
> > Attempt to revive discussions below...
> >
> > On Wed, Jul 27, 2016 at 07:45:46AM -0700, Jeff Vander Stoep wrote:
> > > When kernel.perf_event_paranoid is set to 3 (or gre
When building with the latent_entropy plugin, set the default
CONFIG_FRAME_WARN to 2048, since some __init functions have many basic
blocks that, when instrumented by the latent_entropy plugin, grow beyond
1024 byte stack size on 32-bit builds.
Reported-by: kbuild test robot
Cc: Emese Revfy
Sign
On 10/18/2016 09:15 PM, Boris Brezillon wrote:
> On Tue, 18 Oct 2016 11:46:51 -0700
> Brian Norris wrote:
>
>> + others
>>
>> On Tue, Oct 18, 2016 at 06:15:23PM +0200, Richard Weinberger wrote:
>>> On 18.10.2016 17:55, Cyrille Pitchen wrote:
Le 18/10/2016 à 17:30, Richard Weinberger a écri
Jann Horn writes:
> On Tue, Oct 18, 2016 at 10:35:23AM -0500, Eric W. Biederman wrote:
>> Jann Horn writes:
>>
>> > On Tue, Oct 18, 2016 at 09:56:53AM -0500, Eric W. Biederman wrote:
>> >> Michal Hocko writes:
>> >>
>> >> > On Mon 17-10-16 11:39:49, Eric W. Biederman wrote:
>> >> >>
>> >> >>
Group index is incremented on every new group parsed. Since the
field is part of struct imx_pinctrl_soc_info, which is typically
a global variable passed by the individual pinctrl-imx.c based
driver, it does not get cleared automatically when re-probing the
driver. This lead imx_pinctrl_parse_funct
On some systems the sdhci capabilty registers are incorrect for one
reason or another.
The sdhci-cap-speed-modes-broken property will let the driver know that
the sdhci capability registers should not be relied on for speed modes.
Instead the driver should check the mmc generic DT bindings.
Signe
Add Knights Mill (KNM) to the list of CPUIDs supported by turbostat.
Change-Id: I616e3232e985fba4080a65e982604bd03d6dfb9f
Signed-off-by: Piotr Luc
Reviewed-by: Dave Hansen
Cc: Borislav Petkov
Cc: Len Brown
---
v2: Remove trailing comments.
tools/power/x86/turbostat/turbostat.c | 7 +++
1
This patchset is rebased onto 08328814256d888634ff15ba8fb67e2ae4340b64.
First patch improves code style by replacing raw numbers
of CPUID with descriptive macros of processor names.
The second patch adds Knights Mill (KNM) to the list of CPUIDs supported
by turbostat.
Both patches come in new v
Use macros of Intel processor families instead of raw numbers.
Change-Id: I033e40bcea6bde66284e2217e9231f856c827d20
Signed-off-by: Piotr Luc
Reviewed-by: Dave Hansen
Cc: Borislav Petkov
Cc: Len Brown
---
v2: Include Intel family header.
v3: Remove trailing comments.
tools/power/x86/turbostat
Colin King writes:
> From: Colin Ian King
>
> Several line wrapped literal strings are missing white spaces, add the
> whitespace to fix this.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/power/avs/smartreflex.c | 20 ++--
> 1 file changed, 10 insertions(+), 10 deletions(-
When the sdhci-cap-speed-modes-broken DT property is set, the driver
will ignore the bits of the capability registers that correspond to
speed modes and will read the of properties of the device to determine
which speeds are supported.
Signed-off-by: Zach Brown
---
drivers/mmc/host/sdhci.c | 31
The first patch add documentation about a new devicetree property
sdhci-cap-speed-modes-broken.
The second patch makes the sdhci use the DT binding instead of the caps
register for determining which speed modes are supported by the controller.
This RFC is an alternative to another patch set I sen
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
Hello Wolfram,
I noticed that module autoload won't be working in some of the i2c
busses drivers. This patch series contains the fixes for these.
Best regards,
Javier
Javier Martinez Canillas (4):
i2c: jz4780: Fix module autoload
i2c: xlp9xx: Fix module autoload
i2c: xlr: Fix module autol
On Mon, Oct 17, 2016 at 11:09:41AM -0500, Alan Tull wrote:
> Add low level driver to support reprogramming FPGAs for Altera
> SoCFPGA Arria10.
>
> Signed-off-by: Alan Tull
Reviewed-by: Moritz Fischer
> ---
> v19: Added to this patchset as has been changed to use
>fpga image information
On 11.10.2016 07:50, Dan Carpenter wrote:
> We removed hppfs in commit f74a14e870c8 ('um: Remove hppfs') so we can
> remove the MAINTAINERS entry as well.
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 63f15c9..116729a 100644
> --- a/MAINTAINERS
> +++ b/MAINT
On Monday, October 17, 2016 07:46:06 PM Tim Walberg wrote:
> May or may not be related to similar reports, but here's what I've just
> observed
> on my system. Built a stock kernel from tags/v4.8.1, relevant cpufreq bits:
>
> CONFIG_ACPI_CPU_FREQ_PSS=y
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_GOV_AT
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
On Tue, 18 Oct 2016 16:56:48 -0400
Steven Rostedt wrote:
> Is releasing the lock within a llist_for_each_entry_safe() actually safe? Is
> vmap_area_lock the one to protect the valist?
>
> That is llist_for_each_entry_safe(va, n_va, valist, purg_list) does:
>
> for (va = llist_entry(valis
Hi,
Le mardi 18 octobre 2016 à 11:21 +0200, Heiko Stübner a écrit :
> Am Sonntag, 16. Oktober 2016, 21:49:43 schrieb Paul Kocialkowski:
> >
> > Hi,
> >
> > Le mardi 27 septembre 2016 à 13:53 -0700, Vagrant Cascadian a écrit :
> > >
> > > This essentially mimics what was done with rk3288-veyron-
On Mon, Oct 17, 2016 at 2:37 PM, Emese Revfy wrote:
> On Sun, 16 Oct 2016 06:52:16 +0800
> kbuild test robot wrote:
>
>>drivers/pci/hotplug/ibmphp_ebda.c: In function 'ibmphp_access_ebda':
>> >> drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108
>> >> bytes is larger th
These GPU drivers only depend on the RESET_CONTROLLER config
option to fix build issues that existed when there weren't stub
reset APIs for reset controller consumers. Given that these
drivers aren't providing any reset controllers themselves, they
don't actually depend on the API to build (just to
On Tue, Oct 18, 2016 at 08:56:11AM +0200, Christoph Hellwig wrote:
> From: Joel Fernandes
>
> Use cond_resched_lock to avoid holding the vmap_area_lock for a
> potentially long time.
>
> Signed-off-by: Joel Fernandes
> [hch: split from a larger patch by Joel, wrote the crappy changelog]
> Signe
Thanks,
//richard
[PATCH 1/2] fscrypto: Fix log string in do_crypto()
[PATCH 2/2] fscrypto: Fix fscrypt_decrypt_page() doc string
Most likely a copy&paste error from the f2fs import.
Signed-off-by: Richard Weinberger
---
fs/crypto/crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
index 1637a0450b9f..d789ddbc0a46 100644
--- a/fs/crypto/crypto.c
+++ b/fs/cryp
The operations supports both encryption and decryption.
Signed-off-by: Richard Weinberger
---
fs/crypto/crypto.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
index 61057b7dbddb..1637a0450b9f 100644
--- a/fs/crypto/crypto.c
+++ b
Hi Bartosz,
Thank you for the patch.
On Monday 17 Oct 2016 18:30:49 Bartosz Golaszewski wrote:
> Create the driver for the da8xx System Configuration and implement
> support for writing to the three Master Priority registers.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> .../devicetree/bindin
On Mon, Oct 17, 2016 at 6:04 AM, Mark Rutland wrote:
> On Fri, Aug 26, 2016 at 02:57:58PM -0400, Kees Cook wrote:
>> On Fri, Aug 26, 2016 at 10:31 AM, Mark Rutland wrote:
>> > The strncpy_from_user() accessor is effectively a copy_from_user()
>> > specialised to copy strings, terminating early at
On Mon, Oct 17, 2016 at 6:44 AM, Mark Rutland wrote:
> Hi,
>
> Attempt to revive discussions below...
>
> On Wed, Jul 27, 2016 at 07:45:46AM -0700, Jeff Vander Stoep wrote:
>> When kernel.perf_event_paranoid is set to 3 (or greater), disallow
>> all access to performance events by users without CA
On Tue, Oct 18, 2016 at 1:38 PM, Scott Branden
wrote:
> Hi Olof,
>
> On 16-10-17 05:04 PM, Olof Johansson wrote:
>>
>> On Mon, Oct 17, 2016 at 4:24 PM, Scott Branden
>> wrote:
>>>
>>> Hi Olof,
>>>
>>> On 16-10-17 02:58 PM, Olof Johansson wrote:
Hi,
On Wed, Oct 12, 2016 at
When the operation fails we also have to undo the changes
we made to ->xattr_names. Otherwise listxattr() will report
wrong lengths.
Cc: sta...@vger.kernel.org
Signed-off-by: Richard Weinberger
---
fs/ubifs/xattr.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/ubifs/xattr.c b/fs/ubifs
Since ->rename2 is gone, rename ubifs_rename2() to ubifs_rename().
Suggested-by: Linus Torvalds
Signed-off-by: Richard Weinberger
---
fs/ubifs/dir.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/ubifs/dir.c b/fs/ubifs/dir.c
index c8f60df2733e..668ec3b90ea1
Hi Bartosz,
Thank you for the patch.
On Monday 17 Oct 2016 18:30:48 Bartosz Golaszewski wrote:
> Create a new driver for the da8xx DDR2/mDDR controller and implement
> support for writing to the Peripheral Bus Burst Priority Register.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> .../memory-c
On Tue, Oct 18, 2016 at 10:25 AM, SF Markus Elfring
wrote:
> Can it be that the passing of the adjusted parameter "HOSTCFLAGS" has got a
> significant
> influence (with unwanted side effects) in this use case?
That's probably it. If I strip down your advanced original example to just
make def
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the module alias information using the MODULE_DEVICE_TABLE() macro.
Before this patch:
$ modinfo drive
Enable support for on board SPI EEPROM by setting
CONFIG_EEPROM_AT25=m
Signed-off-by: Scott Branden
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index eadf485..4c62662 100644
--- a/arch/arm64/conf
On 2016.10.18 at 22:29 +0200, Markus Trippelsdorf wrote:
> On 2016.10.18 at 22:23 +0200, Borislav Petkov wrote:
> > Hey Al,
> >
> > I see the gazillion warnings below when building -rc1 here.
> >
> > When I revert
> >
> > 784d5699eddc ("x86: move exports to actual definitions")
> >
> > the warn
Hi Olof,
On 16-10-17 05:04 PM, Olof Johansson wrote:
On Mon, Oct 17, 2016 at 4:24 PM, Scott Branden
wrote:
Hi Olof,
On 16-10-17 02:58 PM, Olof Johansson wrote:
Hi,
On Wed, Oct 12, 2016 at 11:51 AM, Scott Branden
wrote:
Enable support for on board SPI EEPROM by turning on
CONFIG_EEPROM_A
On Sun, Oct 16, 2016 at 10:40 AM, Joel Fernandes wrote:
> Hi Kees,
>
> On Mon, Oct 10, 2016 at 4:59 PM, Kees Cook wrote:
>> On Sun, Oct 9, 2016 at 10:15 AM, Joel Fernandes wrote:
>>> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
If FTRACE_PER_CPU flag is passed to ramoops pdata, s
On Sat, Oct 15, 2016 at 9:31 AM, Mickaël Salaün wrote:
> Could someone push this please?
>
> On 20/09/2016 19:39, Mickaël Salaün wrote:
>> Fix struct seccomp_filter and seccomp_run_filters() signatures.
>>
>> Signed-off-by: Mickaël Salaün
>> Cc: Andy Lutomirski
>> Cc: James Morris
>> Cc: Kees C
On 2016.10.18 at 22:23 +0200, Borislav Petkov wrote:
> Hey Al,
>
> I see the gazillion warnings below when building -rc1 here.
>
> When I revert
>
> 784d5699eddc ("x86: move exports to actual definitions")
>
> the warnings are gone.
I'm seeing the same thing on ppc64le with an allmodconfig.
-
Dan,
On Tue, Oct 18, 2016 at 6:44 AM, Daniel Kurtz wrote:
> Hi Doug,
>
> On Tue, Oct 11, 2016 at 5:04 AM, Douglas Anderson
> wrote:
>> Users of usleep_range() expect that it will _never_ return in less time
>> than the minimum passed parameter. However, nothing in any of the code
>> ensures th
>> Oct 16 06:41:33 nasl003b kernel: [4903207.577484] 3w-sas: scsi0: ERROR:
>> (0x06:0x000D): Microcontroller Error: clearing.
Microcontroller Error = FW crashed and will be reset on the next I/O
timeout or ioctl() timeout, whichever happens first.
It could be the iSCSI target code or initiator s
Hey Al,
I see the gazillion warnings below when building -rc1 here.
When I revert
784d5699eddc ("x86: move exports to actual definitions")
the warnings are gone.
I'm attaching my .config. Let me know if you need more info from me.
Thanks.
WARNING: "__fentry__" [virt/lib/irqbypass.ko] has no
Hi Linus,
Could you please pull this bug fix patch?
Thanks,
The following changes since commit 4c1fad64eff481982349f5795b9c198c532b0f13:
Merge tag 'for-f2fs-4.9' of
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs (2016-10-06 15:30:40
-0700)
are available in the git repository at
On 2016-10-18 07:28, Vivek Gautam wrote:
Do a phy_exit() over the ufs phy in the ufs qcom exit path
to de-initialize the phy.
Signed-off-by: Vivek Gautam
---
New patch added in v2 series.
drivers/scsi/ufs/ufs-qcom.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/ufs/ufs-qco
On 18.10.2016 21:59, Moritz Fischer wrote:
> Hi all,
>
> On Tue, Oct 18, 2016 at 6:15 PM, Richard Weinberger wrote:
>
>>> I totally agree with you so if Marek and you volunteer as well, your help
>>> will be precious!
>
> I had talked to Richard about helping out during ELCE, but tbh I think
>
Hi Neil,
On Tue, 18 Oct 2016 11:09:27 +0200
Neil Armstrong wrote:
> Add NAND driver to support the Oxford Semiconductor OX820 NAND Controller.
> This is a simple memory mapped NAND controller with single chip select and
> software ECC.
>
> Signed-off-by: Neil Armstrong
> ---
> .../devicetree/
Hi Doug,
Leon has finished review as well in [7].
Christoph Acked too in [8].
Can you please advise whether
(1) I should rebase and resend PatchV12?
(2) If so for which branch - master/4.9 or?
Tejun and Christoph mentioned that it might be late for 4.9.
Can we atleast merge to linux-rdma tree, s
On 2016-10-18 07:28, Vivek Gautam wrote:
Add phy clock enable code to phy_power_on/off callbacks, and
remove explicit calls to enable these phy clocks from the
ufs-qcom hcd driver.
Signed-off-by: Vivek Gautam
---
Changes since v1:
- staticized ufs_qcom_phy_enable(/disable)_ref_clk(),
- stati
Hi Rob,
On 16-10-18 06:16 AM, Rob Herring wrote:
On Wed, Oct 12, 2016 at 11:35:51AM -0700, Scott Branden wrote:
Adds brcm,sdhci-iproc compat string to DT bindings document for
the iProc SDHCI driver.
Signed-off-by: Anup Patel
Signed-off-by: Scott Branden
---
Documentation/devicetree/binding
Instead of using timer and spinlocks, use delayed_work and
mutexes for rockchip psr. This allows us to make blocking
calls when enabling/disabling psr (which is sort of important
given we're talking over dpcd to the display).
Cc: zain wang
Signed-off-by: Sean Paul
---
drivers/gpu/drm/rockchip/a
On Tue, Oct 18, 2016 at 12:14:08PM -0700, Babu Moger wrote:
> During our testing we noticed that nmi watchdogs in sparc could not be
> disabled or
> enabled dynamically using sysctl/proc interface. Sparc uses its own arch
> specific
> nmi watchdogs. There is a sysctl and proc
> interface(proc/sy
Hi all,
On Tue, Oct 18, 2016 at 6:15 PM, Richard Weinberger wrote:
>> I totally agree with you so if Marek and you volunteer as well, your help
>> will be precious!
I had talked to Richard about helping out during ELCE, but tbh I think
Marek is the better choice ;-)
He has way more experience i
> Is that fixed by http://patchwork.ozlabs.org/patch/683728/ ?
Yup.
On 10/18/2016 09:41 PM, Boris Brezillon wrote:
[...]
>> Patchwork is nice, it helps keeping track of the patch status real well.
>> But there is always the problem of keeping the patchwork up-to-date when
>> the status of patch changes, esp. if one is offline (or maybe I didn't
>> look hard enoug
On Tue, 18 Oct 2016 18:12:32 +0800
RogerCC.Lin wrote:
> On Tue, 2016-10-18 at 07:19 +0200, Boris Brezillon wrote:
> > On Tue, 18 Oct 2016 00:05:31 +0200
> > Arnd Bergmann wrote:
> >
> > > When building with -Wmaybe-uninitialized, gcc produces a silly false
> > > positive
> > > warning for th
On Tue, 18 Oct 2016 21:31:06 +0200
Marek Vasut wrote:
> On 10/18/2016 08:46 PM, Brian Norris wrote:
>
> [...]
>
> >> Boris Brezillon has already stepped up as a maintainer for the NAND
> >> sub-subsystem in MTD, and the SPI NOR sub-subsystem could be handled in
> >> the same way: I
On Tue, Oct 18, 2016 at 7:08 AM, Mugunthan V N wrote:
> Hi
>
> I am seeing some junk characters on uart boot console on DRA72x platform
> [1] and even on other TI platforms, did a bisect and found the commit
> "761ed4a94582" broke it first.
>
> By reverting below two commit, I don't see the issue
On 10/18/2016 06:15 PM, Richard Weinberger wrote:
> On 18.10.2016 17:55, Cyrille Pitchen wrote:
>> Le 18/10/2016 à 17:30, Richard Weinberger a écrit :
>>> On Tue, Oct 18, 2016 at 5:17 PM, Marek Vasut wrote:
On 10/18/2016 04:58 PM, Cyrille Pitchen wrote:
> I would like to volunteer as a ma
On 10/18/2016 08:46 PM, Brian Norris wrote:
[...]
>> Boris Brezillon has already stepped up as a maintainer for the NAND
>> sub-subsystem in MTD, and the SPI NOR sub-subsystem could be handled in
>> the same way: I would be reviewing patches touching this area, collecting
>> them
On 16.10.2016 17:38, Boris Brezillon wrote:
> On Sat, 15 Oct 2016 17:00:11 +0100
> Colin King wrote:
>
>> From: Colin Ian King
>>
>> Static analysis by CoverityScan detected the ec and pnum
>> arguments are in the wrong order on a call to ubi_alloc_aeb.
>> Swap the order to fix this.
>>
>> Fixes
Hi Ryan,
On 18.10.2016 20:03, Ryan Swan wrote:
> sparse produced
> warning: incorrect type in argument 2 (different address spaces)
> expected void const volatile [noderef] *src
> got struct slic_stats *stats
>
> casting argument 2 to what is expected by memcpy_fromio() fixed this
>
> Signed-off
Hi,
Thanks for the report!
On 18/10/2016 at 14:47:55 -0400, CAI Qian wrote :
> It turns out this panic can only be reproduced with
> CONFIG_DEBUG_TEST_DRIVER_REMOVE
> enabled. There are some errors in dmesg when the config is enabled.
>
> [ 71.215937] rtc_cmos 00:00: RTC can wake from S4
> [
On Tue, 18 Oct 2016 11:46:51 -0700
Brian Norris wrote:
> + others
>
> On Tue, Oct 18, 2016 at 06:15:23PM +0200, Richard Weinberger wrote:
> > On 18.10.2016 17:55, Cyrille Pitchen wrote:
> > > Le 18/10/2016 à 17:30, Richard Weinberger a écrit :
> > >> On Tue, Oct 18, 2016 at 5:17 PM, Marek Va
Implement functions arch_watchdog_nmi_enable and arch_watchdog_nmi_disable
to enable/disable nmi watchdog. Sparc uses arch specific nmi watchdog
handler. Currently, we do not have a way to enable/disable nmi watchdog
dynamically. With these patches we can enable or disable arch
specific nmi watchdo
Currently we do not have a way to enable/disable arch specific
watchdog handlers if it was implemented by any of the architectures.
This patch introduces new functions arch_watchdog_nmi_enable and
arch_watchdog_nmi_disable which can be used to enable/disable architecture
specific NMI watchdog hand
During our testing we noticed that nmi watchdogs in sparc could not be disabled
or
enabled dynamically using sysctl/proc interface. Sparc uses its own arch
specific
nmi watchdogs. There is a sysctl and proc
interface(proc/sys/kernel/nmi_watchdog)
to enable/disable nmi watchdogs. However, that is
201 - 300 of 883 matches
Mail list logo
