I was looking at the overhead of drmIoctl() in a microbenchmark that
repeatedly did a copy_from_user(.size=8) followed by a
copy_to_user(.size=8) as part of the DRM_IOCTL_I915_GEM_BUSY. I found
that if I forced inlined the get_user/put_user instead the walltime of
the ioctl was improved by about 20
Extend the list of replacements for compile-time known sizes to include
6/12 byte copies. These expand to two movs (along with their exception
table) and are cheaper to inline than the function call (similar to the
10 byte copy already handled).
Signed-off-by: Chris Wilson
Cc: Thomas Gleixner
Cc
On Wed, May 31, 2017 at 04:18:09PM +0200, Andrea Arcangeli wrote:
> On Wed, May 31, 2017 at 03:39:22PM +0300, Mike Rapoport wrote:
> > For the CRIU usecase, disabling THP for a while and re-enabling it
> > back will do the trick, provided VMAs flags are not affected, like
> > in the patch you've se
Hi All,
Recently, I came across an issue with the below call stack.
-000|arch_counter_get_cntvct(inline)
-000|__delay()
-001|__const_udelay(?)
-002|msm_trigger_wdog_bite()
-003|spin_dump(inline)
-003|spin_bug(lock = ?, ?)
-004|current_thread_info(inline)
-004|debug_spin_lock_before(inline)
-004|
How about this slightly easier to read version?
---
>From 75276cd521ccecba244c1ee6c1100e27518c628d Mon Sep 17 00:00:00 2001
From: Nicholas Bellinger
Date: Thu, 1 Jun 2017 06:54:06 +
Subject: target: Avoid target_shutdown_sessions loop during queue_depth change
When target_shutdown_sessions()
On Tue, May 30, 2017 at 04:39:41PM +0200, Michal Hocko wrote:
> On Tue 30-05-17 16:04:56, Andrea Arcangeli wrote:
> >
> > UFFDIO_COPY while not being a major slowdown for sure, it's likely
> > measurable at the microbenchmark level because it would add a
> > enter/exit kernel to every 4k memcpy. I
On Wed, May 31, 2017 at 03:32:17PM +0200, Johannes Thumshirn wrote:
> Allow overriding the announced NVMe Version of a via configfs.
>
> This is particularly helpful when debugging new features for the host
> or target side without bumping the hard coded version (as the target
> might not be fully
Am 31.05.2017 um 16:52 schrieb Mark Rutland:
> On Wed, May 31, 2017 at 08:14:52AM +0200, Oleksij Rempel wrote:
>> Signed-off-by: Oleksij Rempel
>> Cc: ker...@pengutronix.de
>> Cc: linux-arm-ker...@lists.infradead.org
>> Cc: Michael Turquette
>> Cc: Stephen Boyd
>> Cc: Rob Herring
>> Cc: Mark Ru
From: Nicholas Bellinger
When target_shutdown_sessions() is invoked to shutdown all active
sessions associated with a se_node_acl when se_node_acl->queue_depth
is changed via core_tpg_set_initiator_node_queue_depth(), it's
possible that new connections reconnect immediately after explicit
shutdow
As mentioned before I'd prefer a menaingful name that indicates the
purpose of the constant. In fact 4096 is a lot more obvious than SZ_4K,
and shortet as well :)
On Wed, May 31, 2017 at 08:24:40AM +0200, Michal Hocko wrote:
> > # cat /sys/devices/system/memory/memory16/valid_zones
> > Normal Movable
> > # echo online_movable > /sys/devices/system/memory/memory16/state
> > # cat /sys/devices/system/memory/memory16/valid_zones
> > Movable
> > # cat /sys/devic
Looks fine:
Reviewed-by: Christoph Hellwig
> +static void nvme_parse_ns_descs(struct nvme_ns *ns, void *ns_nid)
> +{
> + struct nvme_ns_nid *cur;
> + const u8 *p;
> + int pos = 0;
> + int len;
> +
> + p = (u8 *)ns_nid;
No need for the cast. But we can do void pointer arithmetics in the
kernel anyway, so possible we cou
Add support for battery monitor MAX1721x (power_supply class).
Maxim Semiconductor MAX1721x Standalone Fuel Gauge battery monitor.
MAX17211 used for singlecell, MAX17215 for multicell batteryes.
---
drivers/power/supply/Kconfig| 14 ++
drivers/power/supply/Makefile | 1 +
Add basic support regmap (register map access) API for 1-Wire bus
---
drivers/base/regmap/Kconfig | 6 +-
drivers/base/regmap/Makefile| 1 +
drivers/base/regmap/regmap-w1.c | 245
include/linux/regmap.h | 34 ++
4 files changed, 28
Add support for Maxim Semiconductor MAX17211/MAX17215
Standlone Fuel Gauge chips (1-Wire family 0x26)
---
drivers/w1/slaves/Kconfig | 12 +
drivers/w1/slaves/Makefile | 1 +
drivers/w1/slaves/w1_max1721x.c | 73
drivers/w1/slaves/w1_max1721x.h | 102
Coding style fixes.
Alex A. Mihaylov (3):
regmap: Add 1-Wire bus support
w1: MAX1721x Stanalone Fuel Gauge - add 1-Wire slave drivers
power: supply: Add support MAX1721x battery monitor
drivers/base/regmap/Kconfig | 6 +-
drivers/base/regmap/Makefile| 1 +
drive
On Wed, May 31, 2017 at 03:32:13PM +0200, Johannes Thumshirn wrote:
> A NVMe Identify NS command with a CNS value of '3' is expecting a list
> of Namespace Identification Descriptor structures to be returned to
> the host for the namespace requested in the namespace identify
> command.
>
> This Na
On 05/31, Phil Elwell wrote:
> On 31/05/2017 16:58, Stefan Wahren wrote:
> > Am 31.05.2017 um 17:27 schrieb Stephen Warren:
> >> On 05/30/2017 06:23 AM, Phil Elwell wrote:
> >>> Hi,
> >>>
> >>> I've run into a problem using the fixed-factor clock on Raspberry Pi
> >>> and I'd
> >>> like some advice
Hi,
On Wed, May 31, 2017 at 7:53 PM, Jon Hunter wrote:
>
> On 22/05/17 12:23, Vivek Gautam wrote:
>> Make use of reset_control_array_*() set of APIs to manage
>> an array of reset controllers available with the device.
>>
>> Cc: Jon Hunter
>> Cc: Thierry Reding
>> Cc: Philipp Zabel
>> Signed-o
This code looks fine, but I'd rather move it past adding CNS 3h support
so that it can add all the uuid-related bits in one go.
On Wed, May 31, 2017 at 04:00:03PM +0200, Jonathan Neuschäfer wrote:
> On Wed, Apr 05, 2017 at 10:01:23AM -0700, Bjorn Andersson wrote:
> > On Wed 05 Apr 05:10 PDT 2017, Jonathan Neusch?fer wrote:
> >
> > > Don't use size if info indicates an error condition. Previously a
> > > non-ENOENT error (s
On Wed, May 31, 2017 at 03:32:11PM +0200, Johannes Thumshirn wrote:
> The uuid field in the nvme_ns structure represents the nguid field
> from the identify namespace command. And as NVMe 1.3 introduced an
> UUID in the NVMe Namespace Identification Descriptor this will
> collide.
>
> So rename th
Hi Jia-Ju,
On Wed, 2017-05-31 at 11:26 +0800, Jia-Ju Bai wrote:
> The driver may sleep under a spin lock, and the function call path is:
> iscsit_tpg_enable_portal_group (acquire the lock by spin_lock)
> iscsi_update_param_value
> kstrdup(GFP_KERNEL) --> may sleep
>
> To fix it, the "GFP_KE
Am 31.05.2017 um 22:59 schrieb Andrew Morton:
> On Wed, 31 May 2017 08:14:56 +0200 Oleksij Rempel
> wrote:
>
>> On some boards the SoC can use one pin "PMIC_STBY_REQ" to notify th PMIC
>> about state changes. In this case internal state of PMIC must be
>> preconfigured for upcomming state change
On 05/31, Bjorn Andersson wrote:
> On Wed 31 May 09:27 PDT 2017, Stephen Boyd wrote:
>
> > On 05/26, Bjorn Andersson wrote:
> > > In order to aid post-mortem debugging the Qualcomm platforms provides a
> > > "memory download mode", where the boot loader will provide an interface
> > > for custom t
033fd48
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=2048
> NUMA
> PowerNV
> Modules linked in:
> CPU: 0 PID: 0 Comm: swapper Not tainted
> 4.12.0-rc3-gccN-next-20170531-gf2882f4 #1
> task: c0fb1200 task.stack: c1104000
> NIP:
Hey MNC,
Any comments on this..?
It's been sitting on the list for a while now.. ;)
On Fri, 2017-05-05 at 10:51 +0800, lixi...@cmss.chinamobile.com wrote:
> From: Xiubo Li
>
> The fifo type waiter list will hold the udevs who are waiting for the
> blocks from the data global pool. The unmap t
> -Original Message-
> From: Will Deacon [mailto:will.dea...@arm.com]
> Sent: Wednesday, May 31, 2017 5:45 AM
> To: Pinski, Andrew
> Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org;
> Norov, Yuri ; catalin.mari...@arm.com;
> nathan_ly...@mentor.com; kevin.brod...@arm
This patch series based on v4.12-rc1, include MT2701 ethernet/disp bls/display
function DT nodes.
Sean Wang (1):
arm: dts: mt2701: Add ethernet device node
YT Shen (2):
arm: dts: mt2701: Add display bls related nodes for MT2701
arm: dts: mt2701: Add display subsystem related nodes for MT27
From: YT Shen
This patch adds the device node of display backlight for MT2701
Signed-off-by: Weiqing Kong
Signed-off-by: Erin Lo
---
arch/arm/boot/dts/mt2701-evb.dts | 29 +
arch/arm/boot/dts/mt2701.dtsi| 9 +
2 files changed, 38 insertions(+)
diff --
On 5/31/2017 9:28 PM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
Fix NETDEV WATCHDOG timeout on startup by adding missing register
writes that properly setup SGMII.
Signed-off-by: Thor Thayer
Thanks a lot for this fix.
Acked-by: Giuseppe Cavallaro
---
drivers/net/ethernet/stm
From: YT Shen
This patch adds the device nodes for the DISP function blocks for MT2701
Signed-off-by: YT Shen
Signed-off-by: Erin Lo
---
arch/arm/boot/dts/mt2701.dtsi | 84 +++
1 file changed, 84 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi
From: Sean Wang
Add ethernet device node for MT2701
Signed-off-by: Sean Wang
Signed-off-by: Erin Lo
---
arch/arm/boot/dts/mt2701.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index 8037210..de88bd7
On 05/30, Kiran Gunda wrote:
> diff --git a/drivers/spmi/spmi-pmic-arb.c b/drivers/spmi/spmi-pmic-arb.c
> index 412481d..b755c24 100644
> --- a/drivers/spmi/spmi-pmic-arb.c
> +++ b/drivers/spmi/spmi-pmic-arb.c
> @@ -112,7 +123,8 @@ enum pmic_arb_cmd_op_code {
>
> struct apid_data {
> u16
* Josh Poimboeuf wrote:
> Here's the contents of the undwarf.txt file which explains the 'why' in
> more detail:
Ok, so the code quality looks pretty convincing to me - the new core 'undwarf'
unwinder code is a _lot_ more readable than any of the Dwarf based attempts
before.
That we control
able to handle kernel paging request for data at address 0x04f0
Faulting instruction address: 0xc033fd48
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=2048
NUMA
PowerNV
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted
4.12.0-rc3-gccN-next-
On Thu, Jun 01, 2017 at 12:42:30AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, May 31, 2017 10:41:52 PM Andy Shevchenko wrote:
> > acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16
> > bytes. Instead we convert them to use guid_t type. At the same time we
> > convert current
Hi Priyalee,
[auto build test ERROR on platform-drivers-x86/for-next]
[also build test ERROR on v4.12-rc3 next-20170531]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/priyalee-kushwaha-intel
Hi Jia-Ju,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.12-rc3 next-20170531]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/cx18-Fix-a-sleep-in
Hi Jia-Ju,
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on v4.12-rc3 next-20170531]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Jia-Ju-Bai/ivtv-Fix-a-sleep-in
In preparation for an objtool rewrite which will have broader checks,
whitelist functions and files which cause problems because they do
unusual things with the stack.
These whitelists serve as a TODO list for which functions and files
don't yet have undwarf unwinder coverage. Eventually most of
Now that objtool knows the states of all registers on the stack for each
instruction, it's straightforward to generate debuginfo for an unwinder
to use.
Instead of generating DWARF, generate a new format called undwarf, which
is more suitable for an in-kernel unwinder. See
tools/objtool/Documenta
This is a major rewrite of objtool. Instead of only tracking frame
pointer changes, it now tracks all stack-related operations, including
all register saves/restores.
In addition to making stack validation more robust, this also paves the
way for undwarf generation.
Signed-off-by: Josh Poimboeuf
Some asm (and inline asm) code does special things to the stack which
objtool can't understand. (Nor can GCC or GNU assembler, for that
matter.) In such cases we need a facility for the code to provide
annotations, so the unwinder can unwind through it.
This provides such a facility, in the form
Add CFI hint undwarf annotations to entry_64.S. This will enable the
undwarf unwinder to unwind through any location in the entry code
including syscalls, interrupts, and exceptions.
Signed-off-by: Josh Poimboeuf
---
arch/x86/entry/Makefile | 1 -
arch/x86/entry/calling.h | 5 +
arch/x
Add a new 'undwarf' unwinder which is enabled by
CONFIG_UNDWARF_UNWINDER. It plugs into the existing x86 unwinder
framework.
It relies on objtool to generate the needed .undwarf section.
For more details on why undwarf is used instead of DWARF, see
tools/objtool/Documentation/undwarf.txt.
Signe
The undwarf table needs to be sorted at vmlinux link time, just like the
extable. Extend sorttable's functionality to do so.
Signed-off-by: Josh Poimboeuf
---
init/Kconfig| 4 ++
scripts/Makefile| 2 +-
scripts/link-vmlinux.sh | 7 +-
scripts/sorttable.c | 178
This enables the unwinder to grok the iret in the middle of a C
function.
Signed-off-by: Josh Poimboeuf
---
arch/x86/include/asm/processor.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index 3cada99..9b90129 100644
--
Soon it will be used to sort the undwarf table as well.
Signed-off-by: Josh Poimboeuf
---
Documentation/dontdiff | 2 +-
scripts/.gitignore | 2 +-
scripts/Makefile | 4 ++--
scripts/link-vmlinux.sh| 2 +-
scripts/{sortext
Create a new 'undwarf' unwinder, enabled by CONFIG_UNDWARF_UNWINDER, and
plug it into the x86 unwinder framework. Objtool is used to generate
the undwarf debuginfo. The undwarf debuginfo format is basically a
simplified version of DWARF CFI. More details below.
The unwinder works well in my tes
In preparation for the new 'objtool undwarf generate' command, which
will rely on 'objtool check', move the checking code from
builtin-check.c to check.c where it can be used by other commands.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/Build|1 +
tools/objtool/b
> + case SAS_PROTOCOL_SSP:
> + {
> + unsigned char op = task->ssp_task.cmd->cmnd[0];
> +
> + if (op == READ_6 || op == WRITE_6 ||
> + op == READ_10 || op == WRITE_10 ||
> + op == READ_12 || op == WRITE_12 ||
> +
On Wed, May 31, 2017 at 10:33:05PM +0800, John Garry wrote:
> From: Xiang Chen
>
> Add code to initialise interrupts and add some interrupt handlers.
>
> Signed-off-by: John Garry
> Signed-off-by: Xiang Chen
> ---
> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 281
> +
From: Florian Fainelli Sent: Thursday, June 01, 2017
9:53 AM
>To: Andy Duan ; Rob Herring ;
>Quentin Schulz
>Cc: mark.rutl...@arm.com; net...@vger.kernel.org;
>devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
>thomas.petazz...@free-electrons.com
>Subject: Re: [PATCH v2] net: fec: add po
Hi all,
Changes since 20170531:
The net-next tree gained a conflict against the net tree.
The mfd tree still had its build failure so I used the version from
next-20170530.
The drivers-x86 tree lost its build failure.
The target-bva tree gained a conflict against the target-updates tree.
The
Hi,
In debian wheezy system while writing logs to SSD using tee command , we are
experiencing kernel hung problem.
Can anyone help in avoiding this problem ?
I haven't subscribed to kernel mailing list,so re-ponders please CC me in the
reply.
Kernel trace :
kernel: [ 960.964830] INFO: task
> m...@ox.io hat am 11. Mai 2017 um 07:38 geschrieben:
>
>
>
> > Sinclair Yeh hat am 10. Mai 2017 um 18:46 geschrieben:
> >
> >
> > Hi,
>
> Hi,
>
> > On Wed, May 10, 2017 at 12:31:39PM +0200, m.t wrote:
> > >
> > > > Thomas Hellstrom hat am 10. Mai 2017 um 10:35 geschrieben:
> > > >
> >
On Wed, 31 May 2017 19:07:15 -0500
Larry Finger wrote:
> On 05/31/2017 10:32 AM, Michael Büsch wrote:
> > On Wed, 31 May 2017 13:26:43 +0300
> > Kalle Valo wrote:
> >
> >> Jia-Ju Bai writes:
> >>
> >>> The driver may sleep under a spin lock, and the function call path is:
> >>> b43legacy_o
On Thu, 01 Jun 2017 07:27:20 +0300
Kalle Valo wrote:
> Michael Büsch writes:
>
> >> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c
> >> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c
> >> > @@ -2859,7 +2859,9 @@ static void b43legacy_op_bss_info_changed(struct
> >> > ieee80211_
PERST# must be asserted around ~500ms before
the reboot is applied.
During soft reset (e.g., "reboot" from Linux) on some iProc based SoCs
LCPLL clock and PERST both goes off simultaneously.
This will cause certain Endpoints Intel NVMe not get detected, upon
next boot sequence.
This happens becau
For Configuration Requests only, following reset
it is possible for a device to terminate the request
but indicate that it is temporarily unable to process
the Request, but will be able to process the Request
in the future – in this case, the Configuration Request
Retry Status 10 (CRS) Completion S
PCI: iproc: Retry request when CRS returned from EP
Above patch adds support for CRS in PCI RC driver,
otherwise if not handled at lower level, the user
space PMD (poll mode drivers) can timeout.
PCI: iproc: add device shutdown for PCI RC
This fixes the issue where certian PCI endpoints are
not
On Thu, 2017-06-01 at 05:05 +, Bart Van Assche wrote:
> On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote:
> > but a weeks worth of list silence for your series doesn't mean
> > you're free to push un-reviewed stuff for drivers/target/ into
> > linux-next.
>
> I think this is an e
On Thu, Jun 01, 2017 at 09:48:34AM +0800, Jia-Ju Bai wrote:
> The driver may sleep under a spin lock, and the function call path is:
> post_one_send (acquire the lock by spin_lock_irqsave)
> init_send_wqe
> copy_from_user --> may sleep
>
> To fix it, the lock is released before copy_from_user
On Mon, May 22, 2017 at 02:12:23PM -0700, Rick Altherr wrote:
> Signed-off-by: Rick Altherr
Both patches applied. Thanks.
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
On Wed, 2017-05-31 at 21:27 -0700, Nicholas A. Bellinger wrote:
> but a weeks worth of list silence for your series doesn't mean
> you're free to push un-reviewed stuff for drivers/target/ into
> linux-next.
I think this is an example of the pot calling the kettle black.
Your patch "target: Re-add
On Thu, 2017-06-01 at 04:59 +, Bart Van Assche wrote:
> On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote:
> > Hi Bart,
> >
> > Today's linux-next merge of the target-bva tree got a conflict in:
> >
> > drivers/target/target_core_transport.c
> >
> > between commit:
> >
> > 4ff83
On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote:
> Hi Bart,
>
> Today's linux-next merge of the target-bva tree got a conflict in:
>
> drivers/target/target_core_transport.c
>
> between commit:
>
> 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow
> data"
"clock-freq-min-max" was deprecated. There is only using in rk1108.dtsi.
Use the "max-frequency" for removiing "clock-freq-min-max" in future.
Signed-off-by: Jaehoon Chung
---
arch/arm/boot/dts/rk1108.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dt
Michael Büsch writes:
>> > --- a/drivers/net/wireless/broadcom/b43legacy/main.c
>> > +++ b/drivers/net/wireless/broadcom/b43legacy/main.c
>> > @@ -2859,7 +2859,9 @@ static void b43legacy_op_bss_info_changed(struct
>> > ieee80211_hw *hw,
>> >b43legacy_write32(dev, B43legacy_MMIO_GEN_IRQ_MASK,
On Thu, 2017-06-01 at 14:10 +1000, Stephen Rothwell wrote:
> Hi Bart,
>
> Today's linux-next merge of the target-bva tree got a conflict in:
>
> drivers/target/target_core_transport.c
>
> between commit:
>
> 4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow
> data"
This commit applies upstream change, commit b26cfc48e3e0 ("doc: Update
control-dependencies section of memory-barriers.txt"), to Korean
translation.
Signed-off-by: SeongJae Park
---
Documentation/translations/ko_KR/memory-barriers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
Hello Linus,
Here are the target-pending fixes for v4.12-rc4. Please go ahead and
pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes:
- ibmviscsis ABORT_TASK handling fixes that missed the v4.12 merge
window. (Bryant Ly and Michael Cyr
Jia-Ju Bai writes:
>> Did you actually observe the attempt to sleep under the spin lock,
>> or did you discover this using some tool? In other words, have
>> either of your patches been tested?
>
> In fact, my reported bugs are found by a static analysis tool written
> by me, and they are checked
Hi Bart,
Today's linux-next merge of the target-bva tree got a conflict in:
drivers/target/target_core_transport.c
between commit:
4ff83daa0200 ("target: Re-add check to reject control WRITEs with overflow
data")
from the target-updates tree and commit:
2c0df665 ("target: Fix overf
On Thu, Jun 01, 2017 at 12:46:30PM +0900, Greg KH wrote:
> On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote:
> > Driver ks7010 does not currently have a maintainer.
> >
> > Add maintainers entry for ks7010.
> >
> > Signed-off-by: Tobin C. Harding
> > ---
> > MAINTAINERS | 7
On Thu, Jun 01, 2017 at 12:45:37PM +0900, Greg KH wrote:
> On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote:
> > Current driver implements the WEXT interface. WEXT is in maintenance
> > mode, we need to re-write the driver using cfg80211. The current
> > driver is handy as a referen
On Thu, 2017-06-01 at 12:46 +0900, Greg KH wrote:
> On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote:
> > Add maintainers entry for ks7010.
[]
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -7429,6 +7429,13 @@ F: Documentation/auxdisplay/ks0108
> > F: drivers/auxdisplay/ks0
The driver may sleep under a spin lock, and the function call path is:
rtsx_exclusive_enter_ss (acquire the lock by spin_lock)
rtsx_enter_ss
rtsx_power_off_card
sd_power_off_card3v3
wait_timeout
schedule_timeout --> may sleep
To fix it, "wait_timeout" is replaced with
On Thu, Jun 01, 2017 at 01:27:08PM +1000, Tobin C. Harding wrote:
> Driver ks7010 does not currently have a maintainer.
>
> Add maintainers entry for ks7010.
>
> Signed-off-by: Tobin C. Harding
> ---
> MAINTAINERS | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MA
On Thu, Jun 01, 2017 at 01:27:06PM +1000, Tobin C. Harding wrote:
> Current driver implements the WEXT interface. WEXT is in maintenance
> mode, we need to re-write the driver using cfg80211. The current
> driver is handy as a reference for the new implementation, we can keep
> it in tree for now.
The driver may sleep under a spin lock, and the function call path is:
rtsx_exclusive_enter_ss (acquire the lock by spin_lock)
rtsx_enter_ss
rtsx_power_off_card
sd_cleanup_work
sd_stop_seq_mode
sd_switch_clock
sd_ddr_tuning
sd_ddr_pre_tuning_t
Hi,
On 05/31/2017 05:38 PM, Vlastimil Babka wrote:
> On 05/31/2017 05:27 AM, Lu Baolu wrote:
>> Hi,
>>
>> On 05/30/2017 09:46 PM, Vlastimil Babka wrote:
>>> On 03/21/2017 09:01 AM, Lu Baolu wrote:
XHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI
On 05/31/2017 06:18 PM, Sumit Saxena wrote:
-Original Message-
From: Jia-Ju Bai [mailto:baijiaju1...@163.com]
Sent: Wednesday, May 31, 2017 8:27 AM
To: kashyap.de...@broadcom.com; sumit.sax...@broadcom.com;
shivasharan.srikanteshw...@broadcom.com; j...@linux.vnet.ibm.com;
martin.peter...@
OK, so why cannot we make zero_struct_page 8x 8B stores, other arches
would do memset. You said it would be slower but would that be
measurable? I am sorry to be so persistent here but I would be really
happier if this didn't depend on the deferred initialization. If this is
absolutely a no-go the
Hi,
On 05/31/2017 02:24 PM, Steven Rostedt wrote:
> On Wed, 31 May 2017 11:27:19 +0800
> Lu Baolu wrote:
>
>
+
+#define XDBC_TRACE
+#ifdef XDBC_TRACE
+#define xdbc_trace trace_printk
>>> Did you forget to remove the #define XDBC_TRACE?
>>>
>>> Enabling this driver
Driver ks7010 does not currently have a maintainer.
Add maintainers entry for ks7010.
Signed-off-by: Tobin C. Harding
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9e98464..75250ee 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7429,6
We are in the process of re-writing the current WEXT driver to use the
cfg80211 configuration API. Currently driver root directory is
empty. First step is to implement all the firmware interface in a
single layer of abstraction, Firmware Interface Layer (FIL). We can
add a skeleton implementation f
Current ks7010 driver uses the WEXT interface. This series is the
initial stage of re-writing the driver to use cfg80211.
Patch set applies on Linus' mainline.
5ed02dbb497422bf225783f46e6eadd237d23d6b Linux 4.12-rc3
Throws 4 compiler warnings for functions defined and not used.
As a first step
Hi Dmitry,
[auto build test WARNING on hid/for-next]
[also build test WARNING on v4.12-rc3 next-20170531]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dmitry-Torokhov/HID-Consolidate
The driver may sleep under a spin lock, and the function call path is:
snd_ivtv_pcm_hw_free (acquire the lock by spin_lock_irqsave)
vfree --> may sleep
To fix it, the "substream->runtime->dma_area" is passed to a temporary
value, and mark it NULL when holding the lock. The memory is freed by
vfr
The driver may sleep under a spin lock, and the function call path is:
snd_cx18_pcm_hw_free (acquire the lock by spin_lock_irqsave)
vfree --> may sleep
To fix it, the "substream->runtime->dma_area" is passed to a temporary
value, and mark it NULL when holding the lock. The memory is freed by
v
Add driver for lp87565 PMIC family GPIOs. Three GPIOs are supported
and can be configured in Open-drain output or Push-pull output.
Signed-off-by: Keerthy
---
The latest version of mfd driver for this pmic is posted:
https://lkml.org/lkml/2017/5/30/463
drivers/gpio/Kconfig| 10 +++
On Wed, May 31, 2017 at 03:55:44PM -0400, Jon Mason wrote:
> ARCH_BCM_IPROC includes support for many SoCs, not all of which have the
> same thermal hardware interface as the Northstar/Northstar Plus SoCs.
> This is not a major issue, as this driver will only be probed if the
> relevant device tree
On Sat, 2017-05-27 at 12:13 +0200, Borislav Petkov wrote:
> On Fri, May 26, 2017 at 08:40:26PM -0700, Ricardo Neri wrote:
> > This change was initially intended to only rename the error codes,
> > without functional changes. Would making change be considered a
> change
> > in functionality?
>
> Ho
As part of the Linaro Linux Kernel Functional Test (LKFT)
effort, test failures from kselftest/timer's
inconsistency-check were reported connected to
CLOCK_MONOTONIC_RAW, on the HiKey platform.
Digging in I found that an old issue with how sub-ns accounting
is handled with the RAW time which was f
In some testing on arm64 platforms, I was seeing null ptr
crashes in the kselftest/timers clocksource-switch test.
This was happening in a read function like:
u64 clocksource_mmio_readl_down(struct clocksource *c)
{
return ~(u64)readl_relaxed(to_mmio_clksrc(c)->reg) & c->mask;
}
Where the cal
Hi Dmitry,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.12-rc3 next-20170531]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dmitry-Torokhov/HID-Consolidate-serializing
Due to how the MONOTONIC_RAW accumulation logic was handled,
there is the potential for a 1ns discontinuity when we do
accumulations. This small discontinuity has for the most part
gone un-noticed, but since ARM64 enabled CLOCK_MONOTONIC_RAW
in their vDSO clock_gettime implementation, we've seen fa
1 - 100 of 1025 matches
Mail list logo
