Signed-off-by: Arjun Sreedharan
---
tools/power/cpupower/bench/parse.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/tools/power/cpupower/bench/parse.c
b/tools/power/cpupower/bench/parse.c
index f503fb5..058a351 100644
--- a/tools/power/cpupower/bench/parse.c
+++
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit d5422bd64ebb5b03bcf148f5b58c29a9ad7e990f ("x86: also use
debug_pagealloc_enabled() for free_init_pages")
[9.917676] kasan: WARNING: KASAN doesn't support memory hot-add
[
On 13 February 2016 at 22:57, Nicolas Pitre wrote:
> On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
>
>> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
>> > However, I did stumble over an older patch I did now, which I could
>> > not remember what it was good for. It does fix the problem, and
>>
On Wed, Feb 10, 2016 at 06:08:18PM -0800, Stefan Agner wrote:
> Enable configuration options useful for Vybrid:
> - NFC NAND driver
> - USB dual-role controller support
> - FTM PWM driver
> - DSPI SPI driver
> - Colibri VF50 Touchscreen support.
>
> Beside that, enable useful configurations such a
On Wed, Feb 10, 2016 at 04:02:25PM -0800, Stefan Agner wrote:
> Assign Ethernet clock parents explicitly. The VF610 Tower Board
> uses the external Ethernet clock input which is connected to
> a 50MHz clock.
>
> The Vybrid SoC has two ethernet interfaces (fec0 and fec1) which
> use the same clock
On Wed, Feb 10, 2016 at 10:39:47AM +0530, Rajesh Bhagat wrote:
> Add "snps,quirk-frame-length-adjustment" property to USB3 node for erratum
> A009116.
> This property provides value of GFLADJ_30MHZ for post silicon frame length
> adjustment.
The commit log should be generally wrapped around colu
On Tue, Feb 09, 2016 at 05:08:07PM -0600, Lijun Pan wrote:
> Add "snps,quirk-frame-length-adjustment" property to
> USB3 node for erratum A009116. This property provides
> value of GFLADJ_30MHZ for post silicon frame length
> adjustment.
>
> Signed-off-by: Lijun Pan
Applied, thanks.
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs dev-test
commit 974b5afbf16ecd3e01cefd5d52e3090b6d967693 ("f2fs: use writepages->lock
for WB_SYNC_ALL")
=
com
On Sat, Feb 13, 2016 at 10:39:11AM -0500, Stefan Berger wrote:
> >@@ -347,8 +347,8 @@ static int i2c_nuvoton_recv(struct tpm_chip *chip, u8
> >*buf, size_t count)
> > */
> > static int i2c_nuvoton_send(struct tpm_chip *chip, u8 *buf, size_t len)
> > {
> >-struct device *dev = chip->pdev;
On Sun, 14 Feb 2016, Nicolai Stange wrote:
> In order to protect them against file removal issues, debugfs_create_file()
> creates a lifetime managing proxy around each struct file_operations
> handed in.
>
> In cases where this struct file_operations is able to manage file lifetime
> by itself
On Mon, Feb 08, 2016 at 01:55:08AM +0100, Heinrich Schuchardt wrote:
> Downstream packages like Debian flash-kernel use
> /proc/device-tree/model
> to determine which dtb file to install.
>
> Hence each dts in the Linux kernel should provide a unique model
> identifier.
>
> Commit 8536239e371f ("
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git chardev
commit 3c702e9987e261042a07e43460a8148be254412e ("gpio: add a userspace chardev
ABI for GPIOs")
[1.951191] user_verbs: couldn't register device number
[1.952527] ucm: could
On Sun, Feb 14, 2016 at 07:24:14AM +0200, Jarkko Sakkinen wrote:
> > This should take care of it for all drivers including vtpm.
> >
> > https://github.com/jgunthorpe/linux/commits/for-jarkko
> >
> > At the very least this turns silent use after free into a null pointer
> > oops.
> >
> > We shou
On Fri, Feb 05, 2016 at 05:12:19PM +0100, Marcel Ziswiler wrote:
> Petr Štetiar (2):
> ARM: dts: imx6: Add support for Toradex Apalis iMX6Q/D SoM
> ARM: dts: imx6: Add support for Toradex Ixora carrier board
Applied both, thanks.
W dniu 12.02.2016 o 13:14, Javier Martinez Canillas pisze:
> The max77686 and max77802 regulator drivers are for sub-devices of a MFD
> driver for some PMIC blocks. But the same object file name (max77686.o)
> was used for both the common MFD driver and the max77686 regulator one.
>
> This confuse
Tracepoints use RCU for protection and they must not be called on
offline CPUS. So make this tracepoint conditional.
INFO: suspicious RCU usage. ]
[ 99.749382] 4.4.0-6-g0fe53e8-dirty #34 Tainted: G S
[ 99.749383] ---
[ 99.749385] include/trace/events/kmem.h:14
Tracepoints use RCU for protection and they must not be called on
offline CPUS. So make this tracepoint conditional.
NFO: suspicious RCU usage. ]
[ 413.344670] 4.4.0-6-g0fe53e8-dirty #33 Tainted: G S
[ 413.344672] ---
[ 413.344673] include/trace/events/rcu.h:457
On Sun, Feb 14, 2016 at 06:55:12AM +0200, Jarkko Sakkinen wrote:
> On Fri, Feb 12, 2016 at 05:04:29PM -0700, Jason Gunthorpe wrote:
> > This was missed during the struct device conversion, we
> > need to hold a kref on the chip to make sure it isn't freed.
> >
> > Signed-off-by: Jason Gunthorpe
>
W dniu 10.02.2016 o 03:30, Javier Martinez Canillas pisze:
> All Exynos SoCs have the same syscon reboot and poweroff device nodes so
> there is no need to duplicate the same on each SoC dtsi and can be moved
> to a common dtsi that can be included by all the SoCs dtsi files.
>
> Signed-off-by: Ja
W dniu 10.02.2016 o 02:23, Javier Martinez Canillas pisze:
> The S3C Real Time Clock driver requires the clock and source clock to
> be defined in the device node but that requirement is not documented.
+Cc: Alessandro Zummo
No, not entirely. The samsung,s3c6410-rtc needs rtc and rtc_src clocks
b
The patch sets add support for Hi6220 PMIC Hi655x MFD core and its
regulator driver.
Current testing and support board is Hikey which is one of 96boards.
It is an arm64 open source board. For more information about this board,
please access https://www.96boards.org.
This is hardware layout for acc
Add PMIC MFD driver to support hisilicon hi665x.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian Zhuang
Acked-by: Lee Jones
---
drivers/mfd/Kconfig | 10 +++
drivers/mfd/Makefile| 1 +
drivers/mfd/hi655x-pmic.c
Add the regulator driver for hi655x PMIC.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian Zhuang
---
drivers/regulator/Kconfig| 8 ++
drivers/regulator/Makefile | 1 +
drivers/regulator/hi655x-regulator.c | 227 +++
Add the mfd hi655x dts node and regulator support on
hi6220 platform.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian Zhuang
---
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 87 ++
1 file changed, 87 insertions(+)
d
DT bindings for hisilicon hi655x MFD PMIC chip.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian Zhuang
---
.../devicetree/bindings/mfd/hisilicon,hi655x.txt | 27 ++
1 file changed, 27 insertions(+)
create mode 100644 Docu
This patch adds the device tree binding documentation for
hi655x PMIC regulator.
Signed-off-by: Chen Feng
Signed-off-by: Fei Wang
Signed-off-by: Xinwei Kong
Reviewed-by: Haojian Zhuang
---
.../regulator/hisilicon,hi655x-regulator.txt | 29 ++
1 file changed, 29 inser
On Tue, Feb 9, 2016 at 6:12 PM, Alexander Shishkin
wrote:
> Chunyan Zhang writes:
>
>> It would be broken if stm_data->sw_start isn't zero, because that
>> stp_master_free() get the 'master' with __stm_master()/stm_master(),
>> in which the masterID is the second input parameter minus
>> stm_data
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 3c1da7b02560cd0f0c66c5a59fce3c6746e3 ("mm/vmpressure.c: fix subtree
pressure detection")
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Robert-Baldyga/usb-gadget-composite-introduce-new-function-API/20160203-205850
commit 2203f6a8922a447a364b12ec60b0fe4d7b15a4f9 ("usb: gadget: f_acm:
conversion to new API")
[5.782015] usb 1-1: config 2 has an invalid int
Hi Ma,
[auto build test ERROR on tip/irq/core]
[also build test ERROR on v4.5-rc3 next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/MaJun/irqchip-Add-support-for-Hisilicon-mbigen-v
Hi all,
With recent addition of cpufreq-dt support to Exynos5422
it is very easy to over-heat the Odroid XU3 leading to critical shutdown:
[ 132.622032] thermal thermal_zone3: critical temperature reached(121
C),shutting down
Reproduction:
0. next-20160212 (with recent fix for OPP from Viresh)
On Wed, Feb 10, 2016 at 05:48:04AM +0200, Jarkko Sakkinen wrote:
> Hi James,
>
> As we discussed I'm sending now a revised pull request with a couple
> of new fixes to the one that I sent with the tag:
>
> tags/tpmdd-next-20160120
Forgot to say that these are for -rc4 (rebased on top of securi
W dniu 14.02.2016 o 14:22, Viresh Kumar pisze:
> On 14-02-16, 13:56, Krzysztof Kozlowski wrote:
>> Hi all,
>>
>> Recently Odroid XU3 failed to boot on linux-next
>> on multi_v7 defconfig. exynos defconfig boots fine.
>>
>> Probably the "cpufreq: dt: Use dev_pm_opp_set_rate() to
>> switch frequency"
Michael Ellerman writes:
> On Tue, 2016-09-02 at 01:20:31 UTC, "Aneesh Kumar K.V" wrote:
>> With ppc64 we use the deposited pgtable_t to store the hash pte slot
>> information. We should not withdraw the deposited pgtable_t without
>> marking the pmd none. This ensure that low level hash fault ha
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On Behalf
> Of Dexuan Cui
> Sent: Tuesday, January 26, 2016 17:40
> ...
> Dexuan Cui (8):
> Drivers: hv: vmbus: add a helper function to set a channel's pending
> send size
> Drivers: hv: vmbus: define the new offer type
On Fri, Feb 12, 2016 at 08:33:20PM -0700, Jason Gunthorpe wrote:
> On Fri, Feb 12, 2016 at 08:31:21PM -0500, Stefan Berger wrote:
> > > I'll send you something else that might work for vtpm...'
> >
> > The vtpm driver will introduce chip->priv, which will point to vtpm_dev. For
> > this reason we
On 14-02-16, 13:56, Krzysztof Kozlowski wrote:
> Hi all,
>
> Recently Odroid XU3 failed to boot on linux-next
> on multi_v7 defconfig. exynos defconfig boots fine.
>
> Probably the "cpufreq: dt: Use dev_pm_opp_set_rate() to
> switch frequency" is important here:
> commit 78c3ba5df96c875b1668e1cd3
On Fri, Feb 12, 2016 at 05:04:31PM -0700, Jason Gunthorpe wrote:
> Now that we have a proper struct device just use dev_name() to
> access this value instead of keeping two copies.
>
> Signed-off-by: Jason Gunthorpe
Reviewed-by: Jarkko Sakkinen
/Jarkko
> ---
> drivers/char/tpm/tpm-chip.c
On Fri, Feb 12, 2016 at 05:04:30PM -0700, Jason Gunthorpe wrote:
> This is a hold over from before the struct device conversion.
>
> - All prints should be using &chip->dev, which is the Linux
> standard. This changes prints to use tpm0 as the device name,
> not the PnP/etc ID.
> - The few pla
Hi Chen,
[auto build test WARNING on tip/x86/core]
[also build test WARNING on v4.5-rc3 next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Chen-Yucong/x86-kernel-use-pr_-level-and-d
W dniu 05.02.2016 o 15:04, Alim Akhtar pisze:
> Exynos7 based espresso board uses S2MPS15, a multifunction device.
> This patch enables S2MPS1X regulator, pmic-clk and rtc drivers utilized by
> the same.
>
> Signed-off-by: Alim Akhtar
> Reviewed-by: Krzysztof Kozlowski
> ---
> Changes since v2:
Hi all,
Recently Odroid XU3 failed to boot on linux-next
on multi_v7 defconfig. exynos defconfig boots fine.
Probably the "cpufreq: dt: Use dev_pm_opp_set_rate() to
switch frequency" is important here:
commit 78c3ba5df96c875b1668e1cd3ee0a69e62454f32
Author: Viresh Kumar
Date: Tue Feb 9 10:30:4
On Fri, Feb 12, 2016 at 05:04:29PM -0700, Jason Gunthorpe wrote:
> This was missed during the struct device conversion, we
> need to hold a kref on the chip to make sure it isn't freed.
>
> Signed-off-by: Jason Gunthorpe
I'm bit confused about this patch. What is the regression if this needs
to
On Sun, Feb 14, 2016 at 12:32 AM, Julia Lawall wrote:
> There is another return -1 at the end of the function that should be
> addressed. Maybe -EINVAL would be an appropriate value, if you don't find
> evidence of anything else.
>
> julia
Okay. Will redo and send v2.
Amitoj
Hi Chen,
[auto build test WARNING on tip/x86/core]
[also build test WARNING on v4.5-rc3 next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Chen-Yucong/x86-kernel-use-pr_-level-and-d
arch/x86/kernel/* use a mixture of printk(KERN_ ) and pr_().
This patch converts the bulk of printk(KERN_ ) to pr_() and
uses dev_dbg() instead of the dev_printk(KERN_DEBUG,). All pr_warning()
calls have been replaced with pr_warn().
Not sure what to do about the printk(KERN_DEFAULT) and printk()
I'm announcing the release of the 3.2.77 kernel.
All users of the 3.2 kernel series should upgrade.
The updated 3.2.y git tree can be found at:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.2.y
and can be browsed at the normal kernel.org git web browser:
On Wed, Feb 03, 2016 at 04:16:44PM +0800, Alison Wang wrote:
> According to the new mapping table, the partition for NOR flash
> is added.
How do you know that everyone using the board wants the NOR flash to be
partitioned this way? It's really a matter of software configuration
and may vary from
On Sun, Feb 14, 2016 at 05:27:12AM +0200, Jarkko Sakkinen wrote:
> On Sat, Feb 13, 2016 at 02:55:56PM -0700, Jason Gunthorpe wrote:
> > Hi Peter,
> >
> > Please don't grab my patch in this pull, it is broken.
>
> Please send an updated fix. I'll check it through and include it to the
> final pul
On Wed, Feb 03, 2016 at 09:37:45AM -0800, Joshua Clayton wrote:
> Uniwest evi is a portable electrical eddy current non-destructive
> testing device.
>
> Signed-off-by: Joshua Clayton
Applied, thanks.
On Sat, Feb 13, 2016 at 02:55:56PM -0700, Jason Gunthorpe wrote:
> Hi Peter,
>
> Please don't grab my patch in this pull, it is broken.
Please send an updated fix. I'll check it through and include it to the
final pull request.
> Thanks
> Jason
/Jarkko
>
> On Feb 13, 2016 6:47 AM, Jarkko Sak
Fix the following warning generated about type casting by sparse
warning: cast removes address space of expression
The current implementation casts the structure pointers with (char *)
without __user annotation and then adds sizeof struct to it, thereby
generating the sparse warning. Fixed this b
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Amit-Pundir/usb-gadget-u_ether-Add-workqueue-as-bottom-half-handler-for-rx-data-path/20160209-052012
commit daa556cb5d704ad9b4159dc56dd0161e85b3a596 ("usb: gadget: u_ether: Add
workqueue as bottom half handler for rx data path
Maintainer informations of Documentation/ko_KR is outdated. This commit
update the informations to the latest ones.
Signed-off-by: SeongJae Park
---
Documentation/ko_KR/HOWTO | 4 ++--
Documentation/ko_KR/stable_api_nonsense.txt | 4 ++--
2 files changed, 4 insertions(+), 4 del
On Sun, Feb 14, 2016 at 3:19 AM, Dan Carpenter wrote:
> On Sat, Feb 13, 2016 at 11:34:35PM +0530, Niranjan Dighe wrote:
>> diff --git a/drivers/staging/lustre/lnet/selftest/console.c
>> b/drivers/staging/lustre/lnet/selftest/console.c
>> index 366211e..64b6a70 100644
>> --- a/drivers/staging/lust
From: Ma Jun
This patch set is used to support the mbigen v1 chip.
Compared to mbigen v2 chip, the main difference between them is
register layout(address,format)
As a sequence of this difference, the functions used to get or calculate
register address are also changed for this reason.
I posted
From: Ma Jun
Add the interrupt controller chip operation functions of mbigen chip.
Signed-off-by: Ma Jun
---
drivers/irqchip/irq-mbigen-v1.c | 75 +++
1 files changed, 75 insertions(+), 0 deletions(-)
diff --git a/drivers/irqchip/irq-mbigen-v1.c b/drivers
From: Ma Jun
Because added the mbigen-v1 compatible string, the origin name is
not suitable any more. So,I remove the version number from file name.
Signed-off-by: Ma Jun
---
.../interrupt-controller/hisilicon,mbigen-v2.txt | 74
.../interrupt-controller/hisilicon,mbig
From: Ma Jun
Add the platform device driver for mbigen chip v1.
This patch just same as mbigen v2.
Signed-off-by: Ma Jun
---
drivers/irqchip/Makefile|2 +-
drivers/irqchip/irq-mbigen-v1.c | 76 +++
2 files changed, 77 insertions(+), 1 deletions
From: Ma Jun
For peripheral devices which connect to mbigen,mbigen is a interrupt
controller. So, we create irq domain for each mbigen device and add
mbigen irq domain into irq hierarchy structure.
Signed-off-by: Ma Jun
---
drivers/irqchip/irq-mbigen-v1.c | 144 +++
From: Ma Jun
Add the "hisilicon,mbigen-v1" string in binding file.
Signed-off-by: Ma Jun
---
.../interrupt-controller/hisilicon,mbigen-v2.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
a/Documentation/devicetree/bindings/interrupt-controller/hisilicon,mbigen-v2.t
On Fri, Feb 05, 2016 at 05:36:28AM +, Bhupesh Sharma wrote:
> > From: Shi, Yang
> > Sent: Friday, February 05, 2016 5:19 AM
> >
> > On 2/4/2016 2:37 PM, Bjorn Helgaas wrote:
> > > On Wed, Jan 27, 2016 at 10:05:40AM -0800, Shi, Yang wrote:
> > >> Correct FSL folks email address to nxp.com, sorr
>> static inline void ceph_encode_timespec(struct ceph_timespec *tv,
>> const struct timespec *ts)
>> {
>> tv->tv_sec = cpu_to_le32((u32)ts->tv_sec);
>> tv->tv_nsec = cpu_to_le32((u32)ts->tv_nsec);
>> }
Pointed to decode function change in pr
On Sat, Feb 13, 2016 at 2:08 PM, Dave Chinner wrote:
> On Fri, Feb 12, 2016 at 01:36:05AM -0800, Deepa Dinamani wrote:
>> The VFS inode timestamps are not y2038 safe as they use
>> struct timespec. These will be changed to use struct timespec64
>> instead and that is y2038 safe.
>> But, since the
Currently, the struct file_operations associated with the attribute style
files created through the debugfs_create_*() helpers are not file
lifetime aware as they are defined by means of DEFINE_SIMPLE_ATTRIBUTE().
Thus, a lifetime managing proxy is created around the original fops each
time such a
The struct file_operations u32_array_fops associated with files created
through debugfs_create_u32_array() has been lifetime aware already:
everything needed for subsequent operation is copied to a ->f_private
buffer at file opening time in u32_array_open(). Now, ->open() is always
protected agains
Thanks for your review.
On 2016/2/12 0:59, Lee Jones wrote:
> On Mon, 01 Feb 2016, Chen Feng wrote:
>
>> DT bindings for hisilicon hi655x MFD PMIC chip.
>>
>> Signed-off-by: Chen Feng
>> Signed-off-by: Fei Wang
>> Signed-off-by: Xinwei Kong
>> Reviewed-by: Haojian Zhuang
>> ---
>> .../device
Currently, the struct file_operations fops_blob associated with files
created through the debugfs_create_blob() helpers are not file
lifetime aware.
Thus, a lifetime managing proxy is created around fops_blob each time such
a file is opened which is an unnecessary waste of resources.
Implement fi
Currently, the struct file_operations fops_bool associated with files
created through the debugfs_create_bool() helpers are not file
lifetime aware.
Thus, a lifetime managing proxy is created around fops_bool each time such
a file is opened which is an unnecessary waste of resources.
Implement fi
In order to protect them against file removal issues, debugfs_create_file()
creates a lifetime managing proxy around each struct file_operations
handed in.
In cases where this struct file_operations is able to manage file lifetime
by itself already, the proxy created by debugfs is a waste of resou
Add myself as co-maintainer for the remote processor related subsystems,
as agreed with Ohad.
Signed-off-by: Bjorn Andersson
---
MAINTAINERS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4ebe2e886d36..f51056b02fcd 100644
--- a/MAINTAINERS
+++ b/MAINTAINER
Upon return of debugfs_remove()/debugfs_remove_recursive(), it might
still be attempted to access associated private file data through
previously opened struct file objects. If that data has been freed by
the caller of debugfs_remove*() in the meanwhile, the reading/writing
process would either enc
Nothing prevents a dentry found by path lookup before a return of
__debugfs_remove() to actually get opened after that return. Now, after
the return of __debugfs_remove(), there are no guarantees whatsoever
regarding the memory the corresponding inode's file_operations object
had been kept in.
Sin
Original v2 thread is here:
http://lkml.kernel.org/g/87fux3memd@gmail.com
In the discussion of v2, it turned out that touching each and every of
the ~1000 debugfs users in order to make them save against file
removals is unfeasible.
Thus, v3 takes a different approach: every struct file_op
On 02/11/2016 04:10 PM, Konrad Rzeszutek Wilk wrote:
This patch fixes the issue by:
1) Use kzalloc to initialize to a well known state.
2) Put 'struct pci_sysdata' at the start of 'pcifront_sd'. That
way access to the 'node' will access the right offset.
CC: sta...@vger.kernel.org
Sign
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Robert-Baldyga/usb-gadget-composite-introduce-new-function-API/20160203-205850
commit 368540a661833b00a81b0e9c7741d8dfd89c13f0 ("usb: gadget: f_printer:
conversion to new API")
+--
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
for-4.6/drivers
commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef ("blk-mq: dynamic h/w context
count")
+---+++
|
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 82607adcf9cdf40fb7b5331269780c8f70ec6e35 ("workqueue: implement lockup
detector")
[ 75.684302] virtio-pci :00:06.0: virtio_pci: leaving for legacy driver
[ 88.791869] AC
Jonathan Corbet writes:
> Asciidoc is a credible solution to the formatted documentation problem,
> but it's not the only such; I'd like to be sure that we pick the right
> one. I worry that asciidoc seems to be aimed mostly at small documents,
> and that the project itself seems a little lifele
Signed int - unsigned int comparison fixed in mpssd, prctl, ptp, and
timers in Documentation. In places where 'int argc' and 'const char
**argv' are not used, they are replaced with void
Documentation/mic/mpssd/mpssd.c: Fixed comparison in sum_iovec_len and
disp_iovec
Documentation/prctl/disable-
On Fri, Feb 12, 2016 at 10:11:18AM -0600, Tom Zanussi wrote:
> Hi,
>
> As promised in previous threads, this patchset shares some common
> functionality with the hist triggers code and enables trace events to
> be accessed from eBPF programs.
great that you've started working on BPF!
> It needs
From: Colin Ian King
active_vlans is an unsigned long array, hence a null check on this
array is superfluous and can be removed.
Detected with static analysis by smatch:
drivers/net/ethernet/intel/i40e/i40e_debugfs.c:386
i40e_dbg_dump_vsi_seid() warn: this array is probably
non-NULL. 'vsi->
In commit 8a0044846115e74552b671a7073cffeec14b9316 ("staging/android:
create a 'sync' dir for debugfs information"), modular references were
introduced to this file. However if we look, we find:
drivers/staging/android/Makefile:obj-$(CONFIG_SYNC) += sync.o sync_debug.o
drivers/staging/android/Kc
From: Colin Ian King
alias_map is an unsigned long array, hence a null check on this
array is superfluous and can be removed.
Detected with static analysis by smatch:
fs/logfs/readwrite.c:1282 fill_shadow_tree() warn: this array
is probably non-NULL. 'block->alias_map'
Signed-off-by: Colin I
replace module_init with subsys_initcall ; which will be two
levels earlier, but mm smells like a subsystem to me.
Compile tested only.
Cc: Vlastimil Babka
Cc: Andrew Morton
Signed-off-by: Paul Gortmaker
---
[Feel free to squash this into the original, if desired.]
mm/compaction.c | 4 +---
On Wed, Feb 3, 2016 at 9:15 PM, William Breathitt Gray
wrote:
> By the time request_region is called in several GPIO drivers, a
> corresponding device structure has already been allocated. The
> devm_request_region function should be used to help simplify the cleanup
> code and reduce the possibl
Hi Sudip,
[auto build test ERROR on v4.5-rc2]
[cannot apply to next-20160212]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Sudip-Mukherjee/ocfs2-fix-build-warning/20160202-144936
config: i38
On Tue, Feb 2, 2016 at 12:51 AM, William Breathitt Gray
wrote:
> Several of the GPIO drivers have a copyright boilerplate lacking the "or
> later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
> string should reflect the actual copyright license terms used.
>
> William Breathi
On Wed, Feb 10, 2016 at 10:54 AM, Masahiro Yamada
wrote:
> CONFIG_PINCTRL_MTK is more suitable than CONFIG_ARCH_MEDIATEK
> to guard the drivers/pinctrl/mediatek/ directory.
> (I renamed CONFIG_PINCTRL_MTK_COMMON to CONFIG_PINCTRL_MTK.)
>
> This allows COMPILE_TEST to descend into drivers/pinctrl/
On Fri, Feb 5, 2016 at 8:21 PM, John Stultz wrote:
> This patch adds a dts file to support the Nexus7 2013
> device. Its based off of the qcom-apq8064-ifc6410.dts
> which is similar hardware.
>
> Also includes some comments and context folded in
> from Vinay Simha BN
>
> Cc: Rob Herring
> Cc: A
On Tue, Feb 9, 2016 at 9:15 AM, Arnd Bergmann wrote:
> The newly added kcompactd code introduces multiple build errors:
>
> include/linux/compaction.h:91:12: error: 'kcompactd_run' defined but not used
> [-Werror=unused-function]
> mm/compaction.c:1953:2: error: implicit declaration of function
On 12.02.2016 21:54, Wolfram Sang wrote:
> On Mon, Feb 01, 2016 at 04:44:05PM +0200, Andy Shevchenko wrote:
>> On Mon, 2016-02-01 at 16:21 +0200, Jarkko Nikula wrote:
>>> On 01/30/2016 12:31 AM, Alexey Khoroshilov wrote:
It seems clk_disable_unprepare() is missed in dw_i2c_plat_remove(),
In several drivers in the pxa architecture, it was found that the
platform_get_irq() was not propagated. This breaks the the device-tree
probe deferral path, if -EPROBE_DEFER is returned. Unfortunately, the
error return in this case is transformed into -ENXIO, breaking the
deferral mechanism.
Even
On Fri, Feb 12, 2016 at 01:36:05AM -0800, Deepa Dinamani wrote:
> The VFS inode timestamps are not y2038 safe as they use
> struct timespec. These will be changed to use struct timespec64
> instead and that is y2038 safe.
> But, since the above data type conversion will break the end
> file systems
On Sat, 13 Feb 2016, Ard Biesheuvel wrote:
> On 12 February 2016 at 22:01, Arnd Bergmann wrote:
> > However, I did stumble over an older patch I did now, which I could
> > not remember what it was good for. It does fix the problem, and
> > it seems to be a better solution.
> >
> > Arnd
>
Hi Peter,
Please don't grab my patch in this pull, it is broken.
Thanks
Jason
On Feb 13, 2016 6:47 AM, Jarkko Sakkinen
wrote:
>
> These are critical to get to Linux 4.5 in order to get the chip refcount
> management stabilized and API/ABI for policy based sealing correct.
>
> Harald Hoyer (
So I fear you all are going to hate me for this...
Asciidoc is a credible solution to the formatted documentation problem,
but it's not the only such; I'd like to be sure that we pick the right
one. I worry that asciidoc seems to be aimed mostly at small documents,
and that the project itself see
Add support for United Radiant Technology UMSH-8596MD-xT
7.0" WVGA TFT LCD panels in DRM panel-simple driver.
Signed-off-by: Maciej S. Szmigiero
---
This replaces "drm: panel-simple: implement URT UMSH-8596MD-xT panel support"
submission.
drivers/gpu/drm/panel/panel-simple.c | 54 ++
Add DT bindings for United Radiant Technology
UMSH-8596MD-xT 7.0" WVGA TFT LCD panels.
Signed-off-by: Maciej S. Szmigiero
---
This replaces "of: add URT UMSH-8596MD-xT panel DT bindings"
submission.
.../bindings/display/panel/urt,umsh-8596md.txt | 16
1 file changed,
On Sat, Feb 13, 2016 at 11:34:35PM +0530, Niranjan Dighe wrote:
> diff --git a/drivers/staging/lustre/lnet/selftest/console.c
> b/drivers/staging/lustre/lnet/selftest/console.c
> index 366211e..64b6a70 100644
> --- a/drivers/staging/lustre/lnet/selftest/console.c
> +++ b/drivers/staging/lustre/lne
1 - 100 of 182 matches
Mail list logo
