Add devicetree bindings for Rockchip cru which found on
Rockchip SoCs.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v5: None
Changes in v3: None
Changes in v2: None
.../bindings/clock/rockchip,rk3399-cru.txt | 83
1 f
Add the clock tree definition for the new RK3399 SoC.
Signed-off-by: Xing Zheng
---
Changes in v5:
- add clock IDs to drivers reference
- fix some important bugs
- fix configuration for cpu tables
Changes in v3:
- rename pclkin_cif to pclkin_cifmux, add diagram and comment for
pclkin_cifmux
-
Add the dt-bindings header for the rk3399, that gets shared between
the clock controller and the clock references in the dts.
Signed-off-by: Xing Zheng
Signed-off-by: Jianqun Xu
Acked-by: Rob Herring
---
Changes in v5:
- add some necessary clock IDs
- keep PPLL independent into the part of the
Hi,
The patch series add support more mux parameters and multiple
clock providers for the rockchip features of the clock framework,
and support the clock controller for the RK3399.
Changes in v5:
- add some necessary clock IDs
- keep PPLL independent into the part of the PMUCRU
- fix PMUCRU ID
On the RK3399, the order of the core's parents are LPLL/BPLL/DPLL/GPLL,
there is incorrect to select bit_0 and bit_1 as the main and alternate
parents for LPLL/BPLL. They should be configurable.
Signed-off-by: Xing Zheng
---
Changes in v5: None
Changes in v3: None
Changes in v2: None
drivers/c
The functions rtw_enqueue_recvbuf23a and rtw_enqueue_recvbuf23a_to_head
are never used anywhere in the kernel. So, remove their definition and
prototype.
Grepped to find occurences.
Signed-off-by: Bhumika Goyal
---
drivers/staging/rtl8723au/core/rtw_recv.c| 25 -
driv
On 26.03.2016 00:28, Mark Brown wrote:
On Fri, Mar 25, 2016 at 09:19:12PM +0100, Sebastian Reichel wrote:
On Fri, Mar 25, 2016 at 06:20:17PM +, Mark Brown wrote:
Then there is a constraint that the regulators must be in normal mode
and this needs to be expressed in the machine constrain
The functions rtw_get_oper_bw23a and rtw_get_oper_ch23aoffset are never
used anywhere in the kernel. So, remove their definition and prototype.
Grepped to find occurences.
Signed-off-by: Bhumika Goyal
---
drivers/staging/rtl8723au/core/rtw_wlan_util.c | 10 --
drivers/staging/rtl8723au
Why was the XTS tweak initialization changed in commit 0b81d0779072 ("fs crypto:
move per-file encryption from f2fs tree to fs/crypto")?
Old code:
memcpy(xts_tweak, &index, sizeof(index));
memset(&xts_tweak[sizeof(index)], 0,
F2FS_XTS_TWEAK_SIZE - sizeof(index
On 2016/3/26 3:22, Andrew Morton wrote:
> On Fri, 25 Mar 2016 14:56:04 +0800 Xishi Qiu wrote:
>
>> It is incorrect to use next_node to find a target node, it will
>> return MAX_NUMNODES or invalid node. This will lead to crash in
>> buddy system allocation.
>>
>> ...
>>
>> --- a/mm/page_isolatio
There are known problems with media device life time management. When media
device is released while an media ioctl is in progress, ioctls fail with
use-after-free errors and kernel hangs in some cases.
Media Device can be in any the following states:
- Allocated
- Registered (could be tied to mo
Change au0828, uvcvideo, snd-usb-audio to use Media Device Allocator and
new Media Controller API media_device_unregister_put().
Signed-off-by: Shuah Khan
---
drivers/media/usb/au0828/au0828-core.c | 7 +--
drivers/media/usb/au0828/au0828.h | 1 +
drivers/media/usb/uvc/uvc_driver.c
Add Media Device Allocator API documentation.
Signed-off-by: Shuah Khan
---
include/media/media-dev-allocator.h | 32
1 file changed, 32 insertions(+)
diff --git a/include/media/media-dev-allocator.h
b/include/media/media-dev-allocator.h
index 2932c90..174840c
Add refcount to keep track of media device registrations to avoid release
of media device when one of the drivers does unregister when media device
belongs to more than one driver. Also add a new interfaces to unregister
a media device allocated using Media Device Allocator and a hold register
refc
Add Media Device Allocator API to manage Media Device life time problems.
There are known problems with media device life time management. When media
device is released while an media ioctl is in progress, ioctls fail with
use-after-free errors and kernel hangs in some cases.
Media Allocator API p
2016-03-25 23:45 GMT+09:00 Boris Brezillon :
> On Thu, 24 Mar 2016 21:24:37 +0900
> Masahiro Yamada wrote:
>
>> Commit 271707b1d817 ("mtd: nand: denali: max_banks calculation
>> changed in revision 5.1") supported the new encoding of the "n_banks"
>> bits of the "features" register, but there is a
Hi Emese,
2016-03-24 9:07 GMT+09:00 Emese Revfy :
> On Fri, 11 Mar 2016 15:25:19 +0900
> Masahiro Yamada wrote:
>
>> You sprinkle "gcc-plugins" target in the top Makefile, which I do not like.
>>
>> Can you descend into scripts/gcc-plugins from scripts/Makefile?
>>
>>
>> subdir-$(CONFIG_MODVER
On Fri, Mar 25, 2016 at 04:17:30PM -0700, Bjorn Andersson wrote:
> On Tue, Jan 19, 2016 at 2:02 AM, Sricharan R wrote:
> > Signed-off-by: Sricharan R
> > Reviewed-by: Andy Gross
> > + blsp2_dma: dma-controller@f9944000 {
> > + compatible = "qcom,bam-v1.4.0"
This patchset adds gpio-signaled acpi events support for power button on
hisilicon
D02 board.
The two patches respectively:
- convert device node to fwnode
- add gpio-signaled acpi event support
This patchset is based on
https://git.kernel.org/pub/scm/linux/kernel/git/linus
This patch converts device node to fwnode for dwapb driver,
so as to provide a unified node for DT and ACPI bindings.
Acked-by: Andy Shevchenko
Signed-off-by: qiujiang
---
drivers/gpio/gpio-dwapb.c| 48 +++-
drivers/mfd/intel_quark_i2c_gpio.c |
This patch adds gpio-signaled acpi event support. It is used for
power button on hisilicon D02 board, an arm64 platform.
Corresponding DSDT file is defined as follows:
Device(GPI0) {
Name(_HID, "HISI0181")
Name(_ADR, 0)
Name(_UID, 0)
Name (_CRS, ResourceTemplate (
On Sat, Mar 26, 2016 at 2:12 AM, Steve Muckle wrote:
> Hi Rafael,
>
> On 03/21/2016 06:54 PM, Rafael J. Wysocki wrote:
> ...
>> +config CPU_FREQ_GOV_SCHEDUTIL
>> + tristate "'schedutil' cpufreq policy governor"
>> + depends on CPU_FREQ
>> + select CPU_FREQ_GOV_ATTR_SET
>> + select
On 3/25/16, Stephen Rothwell wrote:
> Hi Jeff,
>
> On Fri, 25 Mar 2016 17:01:27 -0600 Jeffrey Merkey
> wrote:
>>
>> I went back and checked the code and as it turns out, none of the
>> patches you nak'd are in the current branch, there are different
>> patches there now. There are two patches y
Hi Ingo,
On Fri, 25 Mar 2016 09:36:21 +0100 Ingo Molnar wrote:
>
> So neither the x86 nor other affected maintainers have acked these changes or
> have
> agreed to merge it - in fact there are outstanding NAKs against this tree,
> which
> were not mentioned in the pull request.
>
> Here's on
Hi Jeff,
On Fri, 25 Mar 2016 17:01:27 -0600 Jeffrey Merkey wrote:
>
> I went back and checked the code and as it turns out, none of the
> patches you nak'd are in the current branch, there are different
> patches there now. There are two patches you ignored that are in it,
> but no record of a
On Sat, Mar 26, 2016 at 2:12 AM, Steve Muckle wrote:
> Hi Rafael,
>
> On 03/21/2016 06:53 PM, Rafael J. Wysocki wrote:
>> Add two new policy flags, fast_switch_possible, to be set by the
>> cpufreq driver if fast frequency switching can be used for the
>> given policy and fast_switch_enabled, to b
Hi Linus,
Please pull the following Ceph updates from
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
There is quite a bit here, including some overdue refactoring and cleanup
on the mon_client and osd_client code from Ilya, scattered writeback
support for CephFS
Hi Rafael,
On 03/21/2016 06:54 PM, Rafael J. Wysocki wrote:
...
> +config CPU_FREQ_GOV_SCHEDUTIL
> + tristate "'schedutil' cpufreq policy governor"
> + depends on CPU_FREQ
> + select CPU_FREQ_GOV_ATTR_SET
> + select IRQ_WORK
> + help
> + The frequency selection formula us
Hi Rafael,
On 03/21/2016 06:53 PM, Rafael J. Wysocki wrote:
> Add two new policy flags, fast_switch_possible, to be set by the
> cpufreq driver if fast frequency switching can be used for the
> given policy and fast_switch_enabled, to be set by the governor
> if it is going to use fast frequency s
On Thu, Mar 24, 2016 at 5:07 AM, Srinivas Pandruvada
wrote:
> There are several reports of freeze on enabling HWP (Hardware PStates)
> feature on Skylake based systems by Intel P states driver. The root
> cause is identified as the HWP interrupts causing BIOS code to freeze.
> HWP interrupts uses
Fix variable assignment inside if statement. It is error-prone and hard to read.
Signed-off-by: Cosmin-Gabriel Samoila
---
drivers/isdn/hisax/isac.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/isdn/hisax/isac.c b/drivers/isdn/hisax/isac.c
index 7f
On Fri, Mar 25, 2016 at 10:01:26AM +0800, Yaowei Bai wrote:
> This patch refactors __mnt_is_readonly and makes it return bool to
> improve readability due to this particular function only using either
> one or zero as its return value.
Improve in which way, if I may ask?
On Fri, Mar 25, 2016 at 04:42:45PM +0800, Zhang Zhuoyu wrote:
> > This one is for ilookup5. ilookup5() wants function pointer "int
> > (*test)(struct
> > inode *, void *)”. The rest change looks good.
> >
> > Regards
> > Yan, Zheng
> >
>
> Yes, you are right, I will send another version.
...
On 26.03.2016 00:56, Alexey Khoroshilov wrote:
> On 26.03.2016 01:03, Vladimir Zapolskiy wrote:
>> On 25.03.2016 22:23, Alexey Khoroshilov wrote:
>>> Fixing checks for dma mapping error in qset_fill_page_list(),
>>> I have missed two similar problems in qset_add_urb_sg() and
>>> in qset_add_urb_sg_
On Sat, Mar 26, 2016 at 12:55 AM, Linus Torvalds
wrote:
> On Fri, Mar 25, 2016 at 3:08 PM, Rafael J. Wysocki wrote:
>>
>> One of commits in my previous pull request changed the permissions
>> of drivers/power/avs/rockchip-io-domain.c to executable by mistake.
>
> Hmm. The signed tag contents was
On Fri, 25 Mar 2016, Kirill A. Shutemov wrote:
> On Thu, Mar 24, 2016 at 12:08:55PM -0700, Hugh Dickins wrote:
> > On Thu, 24 Mar 2016, Kirill A. Shutemov wrote:
> > > On Wed, Mar 23, 2016 at 01:09:05PM -0700, Hugh Dickins wrote:
> > > > The small files thing formed my first impression. My second
On Thursday, March 24, 2016 03:52:01 PM Aleksey Makarov wrote:
> 'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port
> Console Redirection Table) [2] as a mandatory ACPI table that
> specifies the configuration of serial console.
>
> Defer initialization of DT earlycon until ACPI/DT
On Fri, Mar 25, 2016 at 3:08 PM, Rafael J. Wysocki wrote:
>
> One of commits in my previous pull request changed the permissions
> of drivers/power/avs/rockchip-io-domain.c to executable by mistake.
Hmm. The signed tag contents was garbage - it was your previous
message. The commit it pointed to
It was observed that minimum size accounting associated with the
hugetlbfs min_size mount option may not perform optimally and as
expected. As huge pages/reservations are released from the filesystem
and given back to the global pools, they are reserved for subsequent
filesystem use as long as the
On Tue, Jan 19, 2016 at 2:02 AM, Sricharan R wrote:
> Signed-off-by: Sricharan R
> Reviewed-by: Andy Gross
> ---
> arch/arm/boot/dts/qcom-msm8974.dtsi | 12 +++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
> b/arch/arm/boot/dts
On 03/23, Lars Persson wrote:
> Michael & Stephen,
>
> Should we resubmit this series for 4.7 ?
>
> Also to follow up on your previous request to use the platform
> driver framework. We have noticed recent submissions use a style
> that mixes early clocks registered with CLK_OF_DECLARE and the
>
From: Andi Kleen
Implement printing full disassembled sequences for branch stacks in perf
script. This allows to directly print hot paths for individual samples,
together with branch misprediction and even cycle count information.
% perf record -b ...
% perf script -F brstackasm
...
From: Andi Kleen
Add autoprobing for the udev86 disassembler library.
Signed-off-by: Andi Kleen
---
tools/build/Makefile.feature | 6 --
tools/build/feature/Makefile | 8 ++--
tools/build/feature/test-all.c| 5 +
tools/build/feature/test-udis86.c | 8
tools/p
From: Andi Kleen
When dumping PT traces with perf script it is very useful to see the
assembler for each sample, so that it is easily possible to follow
the control flow.
As using objdump is difficult and inefficient from perf script this
patch uses the udis86 library to implement assembler outp
From: Andi Kleen
When using perf script to look at PT traces it is often
useful to ignore the initialization code at the beginning.
On larger traces which may have many millions of instructions
in initialization code doing that in a pipeline can be very
slow, with perf script spending a lot of C
On 3/25/16, Jeffrey Merkey wrote:
> On 3/25/16, Jeffrey Merkey wrote:
>> On 3/25/16, Jeffrey Merkey wrote:
>>> On 3/25/16, Ingo Molnar wrote:
* Stephen Rothwell wrote:
> Hi Joe,
>
> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches
> wrote:
> >
> > On Mon,
On 3/25/16, Jeffrey Merkey wrote:
> On 3/25/16, Jeffrey Merkey wrote:
>> On 3/25/16, Ingo Molnar wrote:
>>>
>>> * Stephen Rothwell wrote:
>>>
Hi Joe,
On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches wrote:
>
> On Mon, 2016-03-14 at 17:50 -0600, Jeffrey Merkey wrote:
On 26.03.2016 01:03, Vladimir Zapolskiy wrote:
On 25.03.2016 22:23, Alexey Khoroshilov wrote:
Fixing checks for dma mapping error in qset_fill_page_list(),
I have missed two similar problems in qset_add_urb_sg() and
in qset_add_urb_sg_linearize().
Found by Linux Driver Verification project (lin
Am 17.03.2016 um 10:57 schrieb Vlastimil Babka:
> +CC Hugh, Mel
>
> On 03/16/2016 11:55 PM, Richard Weinberger wrote:
>> From: "Kirill A. Shutemov"
>>
>> When using CMA during page migrations UBIFS might get confused
>
> It shouldn't be CMA specific, the same code runs from compaction, autonuma
This driver needs io memory but not all archs offer it.
Fixes the following build error:
drivers/built-in.o: In function `rockchip_mbox_probe':
rockchip-mailbox.c:(.text+0x4b19c): undefined reference to
`devm_ioremap_resource'
Cc: Jassi Brar
Signed-off-by: Richard Weinberger
---
drivers/mailb
Not all archs have io memory.
Instead of selecting I2C_MUX (and bypassing the HAS_IOMEM dependency)
depend directly on it.
Fixes the following kconfig warning:
warning: (MEDIA_SUBDRV_AUTOSELECT && VIDEO_CX231XX && INV_MPU6050_I2C) selects
I2C_MUX which has unmet direct dependencies (I2C && HAS_IO
Not all archs have io memory.
Fixes the following build error:
ERROR: "devm_ioremap_resource" [drivers/phy/phy-omap-control.ko] undefined!
Cc: Kishon Vijay Abraham I
Signed-off-by: Richard Weinberger
---
drivers/phy/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/phy/Kconfi
Not all archs have DMA.
Fixes the following build error:
ERROR: "devm_ioremap_resource" [drivers/fpga/zynq-fpga.ko] undefined!
Cc: Alan Tull
Cc: Moritz Fischer
Signed-off-by: Richard Weinberger
---
drivers/fpga/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/fpga/Kconfig b
Not all archs have io memory.
Fixes the following build error:
ERROR: "devm_ioremap_resource" [drivers/iio/adc/at91-sama5d2_adc.ko] undefined!
Cc: Jonathan Cameron
Cc: Hartmut Knaack
Cc: Lars-Peter Clausen
Cc: Peter Meerwald
Cc: Ludovic Desroches
Fixes: b9cd7a25 ("MAINTAINERS: add entry for
This driver needs io memory.
Fixes the following Kconfig warning:
warning: (ST_IRQCHIP && STMMAC_PLATFORM && DWMAC_IPQ806X && DWMAC_LPC18XX &&
DWMAC_ROCKCHIP && DWMAC_SOCFPGA && DWMAC_STI && TI_CPSW && PINCTRL_ROCKCHIP &&
PINCTRL_DOVE && POWER_RESET_KEYSTONE && S3C2410_WATCHDOG && VIDEO_OMAP3 &&
Not all archs have io memory.
Fixes the following build error:
ERROR: "devm_ioremap_resource" [drivers/phy/phy-bcm-cygnus-pcie.ko] undefined!
Cc: Kishon Vijay Abraham I
Signed-off-by: Richard Weinberger
---
drivers/phy/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/phy/Kco
Not all archs have io memory.
Fixes the following build error:
ERROR: "devm_ioremap_resource" [drivers/nvmem/nvmem_mtk-efuse.ko] undefined!
ERROR: "devm_ioremap_resource" [drivers/nvmem/nvmem_lpc18xx_eeprom.ko]
undefined!
Cc: Srinivas Kandagatla
Cc: Maxime Ripard
Signed-off-by: Richard Weinber
If erasing or writing the BBT fails, we should mark the current BBT
block as bad and use the BBT descriptor to scan for the next available
unused block in the BBT. We should only return a failure if there isn't
any space left.
Based on original code implemented by Jeff Westfahl
.
Signed-off-by: K
On Fri, Mar 25, 2016 at 09:19:12PM +0100, Sebastian Reichel wrote:
> On Fri, Mar 25, 2016 at 06:20:17PM +, Mark Brown wrote:
> > Then there is a constraint that the regulators must be in normal mode
> > and this needs to be expressed in the machine constraints.
> As in adding "regulator-initi
Now that pmem internals have been disentangled from pfn setup, that code
can move to the core. This is in preparation for adding another user of
the pfn-device capabilities.
Signed-off-by: Dan Williams
---
Changes in v2:
* Cleaned up the -ENODEV checking in nd_pfn_init() (Johannes)
drivers/nvd
The mm-of-the-moment snapshot 2016-03-25-15-13 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
In preparation for providing an alternative (to block device) access
mechanism to persistent memory, convert pmem_rw_bytes() to
nsio_rw_bytes(). This allows ->rw_bytes() functionality without
requiring a 'struct pmem_device' to be instantiated.
In other words, when ->rw_bytes() is in use i/o is d
Hi Linus,
One of commits in my previous pull request changed the permissions
of drivers/power/avs/rockchip-io-domain.c to executable by mistake.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.6-rc1-3
to receive the fix as commit 8e653b654497350f
From: Steve Shih
This patch fixes the issues for disabling auto-negotiation and forcing
speed and duplex settings for the fiber media.
For fiber media, e1000_get_settings should return ETH_TP_MDI_INVALID for
eth_tp_mdix_ctrl instead of ETH_TP_MDI_AUTO so subsequent e1000_set_settings
call would
Consolidate the information for issuing i/o to a blk-namespace, and
eliminate some pointer chasing.
Reviewed-by: Johannes Thumshirn
Signed-off-by: Dan Williams
---
Changes in v2:
* rebased with the "dev_info => dev_dbg" change moved to its own patch.
drivers/nvdimm/blk.c | 137 ++
On 25.03.2016 22:23, Alexey Khoroshilov wrote:
> Fixing checks for dma mapping error in qset_fill_page_list(),
> I have missed two similar problems in qset_add_urb_sg() and
> in qset_add_urb_sg_linearize().
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alex
On Fri, Mar 25, 2016 at 09:24:14PM +, Chatre, Reinette wrote:
> Hi Paul,
>
> On 2016-03-23, Paul E. McKenney wrote:
> > Please boot with the following parameters:
> >
> > rcu_tree.rcu_kick_kthreads ftrace
> > trace_event=sched_waking,sched_wakeup,sched_wake_idle_without_ipi
>
> With the
we allocate most data structure in device's node, but some data
structures are not for DMA and mostly used by specific cpus/node which
could diff from device's node. Allocating such hot data in device's
node doesn't make sense. Add an API to estimate hardware queue node.
This can be used before blk
These two patches add support for pm8994 regulators. The second patch
is necessary to get things working because pm8994 has some regulators
that can't typically be read/written due to the security policy.
Stephen Boyd (2):
regulator: qcom_spmi: Add support for pm8994
regulator: qcom_spmi: Keep
blk_mq_tags/requests of specific hardware queue are mostly used in
specific cpus, which might not be in the same numa node as disk. For
example, a nvme card is in node 0. half hardware queue will be used by
node 0, the other node 1.
Signed-off-by: Shaohua Li
---
block/blk-mq.c | 14 ++---
Document the regulators available on pm8994 and add support for
this PMIC to the SPMI PMIC regulator driver.
Signed-off-by: Stephen Boyd
---
.../bindings/regulator/qcom,spmi-regulator.txt | 37
drivers/regulator/qcom_spmi-regulator.c| 51 ++
2
On some designs, a handful of the regulators can't be read via
SPMI transactions because they're "secure" and not intended to be
touched by non-secure processors. This driver unconditionally
attempts to read the id registers of all the regulators though,
leading to probe failing and no regulators b
The msm_find_best_baud() function is written with the assumption
that the port->uartclk rate is fixed to a particular rate at boot
time, but now this driver changes that clk rate at runtime when
the baud is changed.
The way the hardware works is that an input clk rate comes from
the clk controller
nvme_queue is per-cpu queue (mostly). Allocating it in node where blk-mq
will use it.
Signed-off-by: Shaohua Li
---
drivers/nvme/host/pci.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index f8db70a..8d2470
On Wed 23 Mar 15:04 PDT 2016, Matthew McClintock wrote:
> For this SoC the register offsets changed from previous versions to be
> separated by a larger amount.
>
> CC: linus.wall...@linaro.org
So the HW guys changed the register layout of the TLMM block? Matches
the layout of contemporary MSMs,
Hi!
> OK, so at last I finished charging of my N900; found 1.8V USB
> to UART adapter and soldered it to the phone.
>
> I managed to boot N900 with working USB gadget (builtin g_ether)
> in boardfile mode, can ping it from PC and transfer data. I don't
> see any issue (except of musb name issue i
This patch convert usb_prism_tbl[] into a const array
since it is not modified anywhere in prism2usb.c file.
Signed-off-by: Claudiu Beznea
---
drivers/staging/wlan-ng/prism2usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/prism2usb.c
b/drivers/st
On 03/24/2016 06:01 PM, Steve Muckle wrote:
> Hi Sai,
>
> On 03/24/2016 04:47 PM, Sai Gurrappadi wrote:
>>> @@ -2850,7 +2851,8 @@ static inline int update_cfs_rq_load_avg(u64 now,
>>> struct cfs_rq *cfs_rq)
>>> cfs_rq->load_last_update_time_copy = sa->last_update_time;
>>> #endif
>>>
>>> -
Hi Paul,
On 2016-03-23, Paul E. McKenney wrote:
> Please boot with the following parameters:
>
> rcu_tree.rcu_kick_kthreads ftrace
> trace_event=sched_waking,sched_wakeup,sched_wake_idle_without_ipi
With these parameters I expected more details to show up in the kernel logs but
cannot fi
On Wed 23 Mar 15:04 PDT 2016, Matthew McClintock wrote:
> Without this, we would fail to set the mode to gpio if trying to
> configure for that mode
>
> CC: linus.wall...@linaro.org
Linus is the maintainer of the pinctrl subsystem, as such you should
have him as recipient of these patches - so t
I am announcing the release of the Linux 3.13.11-ckt37 kernel.
The updated 3.13.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.13.y
and can be browsed at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.13.y
The diff from v3.13.11-ckt36 is poste
diff --git a/Makefile b/Makefile
index f2025b1..dad16cf 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 13
SUBLEVEL = 11
-EXTRAVERSION = -ckt36
+EXTRAVERSION = -ckt37
NAME = King of Alienated Frog Porn
# *DOCUMENTATION*
diff --git a/arch/mips/kernel/traps.c b/ar
On Wed 23 Mar 15:04 PDT 2016, Matthew McClintock wrote:
> This should have been bumped to 100 when the extra pins
> were added in the original pinctrl patch
>
> CC: linus.wall...@linaro.org
Sorry for missing this in the initial review of this driver.
Acked-by: bjorn.anders...@linaro.org
Regard
Hi!
> OK, so at last I finished charging of my N900; found 1.8V USB
> to UART adapter and soldered it to the phone.
>
> I managed to boot N900 with working USB gadget (builtin g_ether)
> in boardfile mode, can ping it from PC and transfer data. I don't
> see any issue (except of musb name issue i
Hi!
> OK, so at last I finished charging of my N900; found 1.8V USB
> to UART adapter and soldered it to the phone.
>
> I managed to boot N900 with working USB gadget (builtin g_ether)
> in boardfile mode, can ping it from PC and transfer data. I don't
> see any issue (except of musb name issue i
On 26/03/2016 3:20 AM, Boris Ostrovsky wrote:
> On 03/25/2016 12:04 PM, Steven Haigh wrote:
>> It may not actually be the full logs. Once the system gets really upset,
>> you can't run anything - as such, grabbing anything from dmesg is not
>> possible.
>>
>> The logs provided above is all that get
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive 2nd round of updates for the input subsystem. The BYD PS/2
protocol driver now uses absolute reporting mode and should behave more
like other touchpads; Synaptics driver needed t
This patch removes the memcpy() for two variables which were
previously tested with memcmp(). The result of memcmp() was
zero which means that the previously tested variables were
already equal.
Signed-off-by: Claudiu Beznea
---
drivers/staging/wlan-ng/p80211conv.c | 1 -
1 file changed, 1 delet
On Fri, 25 Mar 2016, Christoph Hellwig wrote:
> On Fri, Mar 25, 2016 at 08:51:51AM -0700, Weongyo Jeong wrote:
> > Each irq_desc only supports one IRQ affinity notifier at current
> > implementation so when we try to register another notifier, it silently
> > unregister previous entry and register
On Mon, Mar 14, 2016 at 09:58:43PM +0100, Miklos Szeredi wrote:
> On Wed, Mar 9, 2016 at 6:07 PM, Seth Forshee
> wrote:
> > On Wed, Mar 09, 2016 at 04:51:42PM +0100, Miklos Szeredi wrote:
> >> On Wed, Mar 9, 2016 at 4:25 PM, Seth Forshee
> >> wrote:
> >> > On Wed, Mar 09, 2016 at 03:48:22PM +01
On Fri, Mar 25, 2016 at 11:22 AM, Williams, Dan J
wrote:
> Hi Linus, please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> libnvdimm-for-next
>
> Now that mcsafe_memcpy() has landed, and the return value was been
> clarified in commit cbf8b5a2b649 "x86/mm, x86/mce:
Fixing checks for dma mapping error in qset_fill_page_list(),
I have missed two similar problems in qset_add_urb_sg() and
in qset_add_urb_sg_linearize().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/usb/host/whci/qset.c | 6 +-
Hi Mark,
On Fri, Mar 25, 2016 at 06:20:17PM +, Mark Brown wrote:
> On Fri, Mar 25, 2016 at 07:22:45PM +0200, Ivaylo Dimitrov wrote:
>
> > On Nokia N900 regulators are left in the mode last set by the bootloader or
> > by the stock kernel, depends on whether it is power-on or reboot from stock
So what is the status of the below?
I haven't seen any NAKs or objections, yet it seems not
applied 3 weeks later. What should I do now?
07.03.2016 19:52, Stas Sergeev пишет:
The following patches make it possible to use swapcontext()
in a sighandler that works on sigaltstack.
The approach is in
On Fri, Mar 25, 2016 at 05:51:20PM +0900, Inki Dae wrote:
> Hi Dan,
>
> 2016년 03월 17일 19:39에 Dan Carpenter 이(가) 쓴 글:
> > We know "ret" is zero and the test makes static checkers complain so
> > let's delete this printk.
> >
> > Signed-off-by: Dan Carpenter
> >
> > diff --git a/drivers/gpu/drm/e
-request-processing/20160325-162204
base: https://git.linaro.org/people/ulf.hansson/mmc next
config: x86_64-rhel (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
&g
The "ret = regmap_write()" assignment was missing so this error message
is never printed.
Signed-off-by: Dan Carpenter
---
v2: in v1 I just deleted the error message
diff --git a/drivers/gpu/drm/exynos/exynos_drm_mic.c
b/drivers/gpu/drm/exynos/exynos_drm_mic.c
index 9869d70..ea2ea17 100644
---
of_node_put is iterating through all terms in the tbps array even though
the bind has failed. We need to only iterate through the terms that have
already passed the binding step.
Cc: Zhang Rui
Cc: Eduardo Valentin
Cc: linux...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ulise
There are two different pieces of code for starting a CPU: start_cpu0()
and the end of secondary_startup_64(). They're identical except for the
stack setup. Combine the common parts into a shared start_cpu()
function.
Signed-off-by: Josh Poimboeuf
---
arch/x86/kernel/head_64.S | 19 +--
When core_kernel_text() is used to determine whether an address on a
task's stack trace is a kernel text address, it incorrectly returns
false for early text addresses for the head code between the _text and
_stext markers.
Head code is text code too, so mark it as such. This seems to match the
i
1 - 100 of 352 matches
Mail list logo
