On Mon, 2015-11-16 at 16:48 +0100, Arnd Bergmann wrote:
> The Intel MID support got split out from the PCI 8250 driver,
> and that now causes a build error when no other driver selects
> CONFIG_RATIONAL:
Already published.
https://lkml.org/lkml/2015/11/12/272
It's not first time you send patches
The newly added scpi thermal support is broken when the scpi driver
is built-in but the thermal driver is a loadable module:
drivers/built-in.o: In function `scpi_hwmon_probe':
(.text+0x444d70): undefined reference to `thermal_zone_of_sensor_unregister'
(.text+0x444d94): undefined reference to `th
On Mon, Nov 16, 2015 at 6:41 AM, Jan Kara wrote:
> On Fri 13-11-15 17:06:39, Ross Zwisler wrote:
>> This patch series adds support for fsync/msync to DAX.
>>
>> Patches 1 through 7 add various utilities that the DAX code will eventually
>> need, and the DAX code itself is added by patch 8. Patche
On 11/16/2015 08:53 AM, Boris Brezillon wrote:
On Mon, 16 Nov 2015 07:59:23 -0800
Guenter Roeck wrote:
On 11/16/2015 12:56 AM, Boris Brezillon wrote:
Use pwm_get_xxx() helpers instead of directly accessing the pwm->xxx field.
Doing that will ease adaptation of the PWM framework to support ato
Commit-ID: a946e8c717f9355d1abd5408ed0adc0002d1aed1
Gitweb: http://git.kernel.org/tip/a946e8c717f9355d1abd5408ed0adc0002d1aed1
Author: Sudeep Holla
AuthorDate: Wed, 4 Nov 2015 18:32:37 +
Committer: Thomas Gleixner
CommitDate: Mon, 16 Nov 2015 17:55:55 +0100
genirq: Delay incrementi
On Thu, Oct 29, 2015 at 09:21:25AM +0100, Jens Wiklander wrote:
> Introduces optee prefix and adds bindings for ARM TrustZone based OP-TEE
> implementation.
>
> Signed-off-by: Jens Wiklander
> ---
> .../bindings/arm/firmware/optee,optee-tz.txt | 29
> ++
> .../devicetr
On 2015-11-15 08:36, Aleksa Sarai wrote:
If so, could you share little more insight on how that time measure
outside of the cpu's cgroup cycles? Just so that its helpful to wider
audience.
Well, there are a number of things that I can think of that the kernel does
on behalf of processes that ca
Am Montag, 16. November 2015, 16:52:06 schrieb Liviu Dudau:
> On Mon, Nov 16, 2015 at 04:30:16PM +, Russell King - ARM Linux wrote:
> > I've tweaked your patch to make the above (buggy) change a little clearer.
> >
> > On Mon, Nov 16, 2015 at 02:44:53PM +, Liviu Dudau wrote:
> > > - for (i
The newly added zx power domain code causes build errors in
some configurations:
warning: (PM_RMOBILE && SOC_ZX296702) selects PM_GENERIC_DOMAINS which has
unmet direct dependencies (PM)
warning: (ARCH_EXYNOS) selects EXYNOS_THERMAL which has unmet direct
dependencies (THERMAL && (ARCH_EXYNOS ||
In cases of duplicate symbols, old_sympos will be used to disambiguate
instead of old_addr. By default old_sympos will be 0, and patching will
only succeed if the symbol is unique. Specifying a positive value will
ensure that occurrence of the symbol in kallsyms for the patched object
will be used
The following directory structure will allow for cases when the same
function name exists in a single object.
/sys/kernel/livepatch///
The sympos number corresponds to the nth occurrence of the symbol name in
kallsyms for the patched object.
An example of patching multiple symbols can be
In cases of duplicate symbols, sympos will be used to disambiguate instead
of val. By default sympos will be 0, and patching will only succeed if
the symbol is unique. Specifying a positive value will ensure that
occurrence of the symbol in kallsyms for the patched object will be used
for patching
On Monday 16 November 2015 18:56:02 Andy Shevchenko wrote:
> On Mon, 2015-11-16 at 16:48 +0100, Arnd Bergmann wrote:
> > The Intel MID support got split out from the PCI 8250 driver,
> > and that now causes a build error when no other driver selects
> > CONFIG_RATIONAL:
>
> Already published.
> ht
BIT macro is used for defining BIT location instead of
shifting operator, usleep_range is preferred over
udelay - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/dmm32at.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/st
Hi,
LABBE Corentin writes:
> of_match_device could return NULL, and so cause a NULL pointer
> dereference later. Renaming id to of_id (like all others do) in the
> process.
>
> Reported-by: coverity (CID 1324133)
> Signed-off-by: LABBE Corentin
> ---
> drivers/usb/phy/phy-msm-usb.c | 9 ++-
On Wed, 2015-10-28 at 15:21 -0600, Alex Williamson wrote:
> There is really no way to safely give a user full access to a DMA
> capable device without an IOMMU to protect the host system. There is
> also no way to provide DMA translation, for use cases such as device
> assignment to virtual machin
On Mon, 2015-11-16 at 21:46 +0800, Geliang Tang wrote:
> list_next_entry has been defined in list.h, so I replace list_entry_next
> with it.
>
Thanks for the cleanup.
Reviewed-by: Sudeep Dutt
> Signed-off-by: Geliang Tang
> ---
> drivers/misc/mic/scif/scif_dma.c | 27 +++-
On 11/16/2015 07:06 PM, Alex Williamson wrote:
On Wed, 2015-10-28 at 15:21 -0600, Alex Williamson wrote:
There is really no way to safely give a user full access to a DMA
capable device without an IOMMU to protect the host system. There is
also no way to provide DMA translation, for use cases s
Hi Julia,
On 11/16/2015 3:33 AM, Julia Lawall wrote:
for_each_available_child_of_node performs an of_node_get on each iteration,
so a return from the middle of the loop requires an of_node_put.
A simplified version of the semantic patch that finds this problem is as
follows (http://coccinelle.l
BIT macro is used for defining BIT location instead of
shifting operator, usleep_range is preferred over
udelay - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/dmm32at.c | 100 +++---
1 file changed, 50 insertions(+), 50 deletions
BIT macro is used for defining BIT location instead of
shifting operator, usleep_range is preferred over
udelay - coding style issue
Signed-off-by: Ranjith Thangavel
---
drivers/staging/comedi/drivers/dmm32at.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/st
On Mon, Nov 16, 2015 at 04:46:36PM +, Will Deacon wrote:
> On Mon, Nov 16, 2015 at 08:44:43AM -0800, Paul E. McKenney wrote:
> > On Mon, Nov 16, 2015 at 04:24:53PM +, Will Deacon wrote:
> > > On Mon, Nov 16, 2015 at 05:04:45PM +0100, Peter Zijlstra wrote:
> > > > On Mon, Nov 16, 2015 at 04:
On Mon, 9 Nov 2015, Qais Yousef wrote:
> On 11/07/2015 02:51 PM, Thomas Gleixner wrote:
> Generally it's hard to know whether a real device is connected to a hwirq or
> not. I am saving a patch where we get a set of free hwirqs from DT as only the
> SoC designer knows what hwirq are actually free a
Hello Brian and Mark,
Sorry for the delay, I was quite busy at the end of last week and didn't
have time to look at my email closely.
On 11/13/2015 08:48 PM, Brian Norris wrote:
> Hi,
>
> On Fri, Nov 13, 2015 at 11:14:10PM +, Mark Brown wrote:
>> On Fri, Nov 13, 2015 at 02:51:13PM -0800, Bri
Added a blank line after declarations to remove the coding
style error detected by the checkpatch.pl.
WARNING: Missing a blank line after declarations
Signed-off-by: Anjali Menon
---
drivers/staging/rdma/ehca/ehca_av.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/staging/rdma/
On Monday, November 16, 2015 10:09 AM, Ranjith Thangavel wrote:
> BIT macro is used for defining BIT location instead of
> shifting operator, usleep_range is preferred over
> udelay - coding style issue
>
> Signed-off-by: Ranjith Thangavel
> ---
> drivers/staging/comedi/drivers/dmm32at.c |4 +
Felipe,
On Mon, Nov 16, 2015 at 8:28 AM, Felipe Balbi wrote:
>
> Hi,
>
> Douglas Anderson writes:
>> In general it is wise to clear interrupts before processing them. If
>> you don't do that, you can get:
>> 1. Interrupt happens
>> 2. You look at system state and process interrupt
>> 3. A ne
Hi,
Peter Chen writes:
> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote:
>>
>>
>> On 11/10/2015 07:14 PM, Peter Chen wrote:
>> > On Tue, Nov 10, 2015 at 04:46:51PM -0800, Tim Bird wrote:
>> >> This fixes a bug where if you disconnect and re-connect the USB cable,
>> >> the gadget dri
Hi Jan,
Jens Axboe writes:
> On 11/16/2015 08:11 AM, Jan Kara wrote:
>> Hello,
>>
>> lately I was looking into a big performance hit we take when blkio
>> controller is enabled and jbd2 thread ends up in a different cgroup than
>> user process. E.g. dbench4 throughput drops from ~140 MB/s to ~20
Please sensibly wrap your messages. Your lines are longer than 80 characters
which makes it exceedingly difficult for some people to reply to your very very
very very very very very very very very very very very very very very very very
very very very very very very very very very very very ver
On Mon, Nov 16, 2015 at 12:08:17PM +0100, Ulf Hansson wrote:
> On 16 November 2015 at 10:07, Maruthi Srinivas Bayyavarapu
> > Drivers which can be built as loadable module needs
> > symbol - pm_genpd_add_device to be exported. Those drivers
> > create platform devices which comes under a powerdoma
On Thu, 12 Nov 2015, Qais Yousef wrote:
> Issues I'm seeing:
>
> - Device domain would be identical to GIC domain and it would defer
> everything to the parent domain except for the extra level of indirection. No?
It's not identical. It's a subset of the GIC domain and it has
different seman
Hello Mark,
On 11/16/2015 10:53 AM, Mark Brown wrote:
> On Fri, Nov 13, 2015 at 03:48:57PM -0800, Brian Norris wrote:
>
>> I suspect we'll have to fully support both spi_device_id tables (fully
>> supported already; if nothing else, to keep wildcard matching) and
>> of_match_tables (not fully sup
On 16 November 2015 09:31:17 GMT+00:00, Marc Titinger
wrote:
>On 14/11/2015 19:59, Jonathan Cameron wrote:
>> On 12/11/15 12:57, Marc Titinger wrote:
>>> Basic support or direct IO raw read, with averaging attribute.
>>> Values are RAW, INT_PLUS_MICRO (Volt/Ampere/Watt).
>>>
>>> Output of iio_i
On Mon, Nov 16, 2015 at 6:05 AM, Jan Kara wrote:
> On Mon 16-11-15 14:37:14, Jan Kara wrote:
[..]
> But a question: Won't it be better to do sfence + pcommit only in response
> to REQ_FLUSH request and don't do it after each write? I'm not sure how
> expensive these instructions are but in theory
Hello all,
I'm not sure if USB hung because RCU died, or actually caused the RCU
death itself. Hopefully the below is useful in determining the issue.
I have a pretty standard system with a Haswell i7-4790 CPU, and these
USB controllers:
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C
On 16/11/2015 07:07, Eric Dumazet wrote:
On Sun, 2015-11-15 at 16:58 -0800, Grant Zhang wrote:
Hi Patrick,
Have you tried the two patches Eric mentioned? One of my 4.1.11 server
just hanged with very similar stack trace and I am wondering whether the
aforementioned patches would help.
Thanks,
On 16 November 2015 at 17:22, Russell King - ARM Linux
wrote:
> Please sensibly wrap your messages. Your lines are longer than 80
> characters which makes it exceedingly difficult for some people to reply
> to your very very very very very very very very very very very very
> very very very very
On Mon, Nov 16, 2015 at 01:29:47PM +0100, Pavel Machek wrote:
> > > Ok, so you are saying that if I fix mfd initialization, sound will
> > > automagically switch from global regulators to device-specific
> > > regulators and things will start working?
> > Yes.
> Ok, so something like this should
Hi John,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.4-rc1 next-20151116]
url:
https://github.com/0day-ci/linux/commits/John-Garry/HiSilicon-SAS-driver/20151116-215304
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: i386
When a new virtual memory area is added to the process's virtual address
space and this vma causes the process's virtual address space limit
(RLIMIT_AS) to be exceeded then kernel behaves incorrectly. Incorrect
behavior is a result of a kernel bug. The kernel in most cases
unnecessarily scans the e
On Sat, Oct 24, 2015 at 12:15:51AM +0200, Linus Walleij wrote:
> The GIC bindings for the ARM11MPCore need to differentiate between
> the GIC on the Test Chip and the one on the evaluation baseboard.
> Split the binding in two and define new compatible-strings.
>
> Cc: Thomas Gleixner
> Cc: Jason
This fixes typo in comment and fixes mcasp_set_ctl_reg to actually
printk on error as author wanted, and cleans it up. Yes, i will end up
being 1001 in the old code.
Signed-off-by: Pavel Machek
diff --git a/sound/soc/davinci/davinci-mcasp.c
b/sound/soc/davinci/davinci-mcasp.c
index b960e62..a7
Dan Carpenter writes:
> On Thu, Nov 12, 2015 at 12:32:13PM +0100, Vitaly Kuznetsov wrote:
>> @@ -85,10 +86,10 @@ static ssize_t hvt_op_write(struct file *file, const
>> char __user *buf,
>> return PTR_ERR(inmsg);
>>
>> if (hvt->on_msg(inmsg, count))
>> -return -EF
On Mon, Nov 16, 2015 at 05:32:05PM +, Daniel Stone wrote:
> On 16 November 2015 at 17:22, Russell King - ARM Linux
> wrote:
> > Please sensibly wrap your messages. Your lines are longer than 80
> > characters which makes it exceedingly difficult for some people to reply
> > to your very very
Hi,
(replying here for the context of why I think this is NOT the smallest
patch possible for the -rc)
Douglas Anderson writes:
> If you've got your interrupt signals bouncing a bit as you insert your
> USB device, you might end up in a state when the device is connected but
> the driver doesn'
Hi Boris
(Adding Ariel for pwm-lpc18xx-sct)
On 16 November 2015 at 09:56, Boris Brezillon
wrote:
> Use pwm_get_xxx() helpers instead of directly accessing the pwm->xxx field.
> Doing that will ease adaptation of the PWM framework to support atomic
> update.
>
> Signed-off-by: Boris Brezillon
>
On 16 November 2015 at 17:43, Russell King - ARM Linux
wrote:
> On Mon, Nov 16, 2015 at 05:32:05PM +, Daniel Stone wrote:
>> On 16 November 2015 at 17:22, Russell King - ARM Linux
>> wrote:
>> > Please sensibly wrap your messages. Your lines are longer than 80
>> > characters which makes it
On Mon, Nov 16, 2015 at 02:19:27PM -0300, Javier Martinez Canillas wrote:
> On 11/13/2015 08:48 PM, Brian Norris wrote:
> > (I believe I avoided this in the first place for mostly-aesthetic
> > reasons; technically this allows people to put garbage in their DT, like
> > "garbage,spi-nor". It's unc
2015-11-15 18:00+0200, Michael S. Tsirkin:
> This patch adds a new parameter: eptp_switching_test, which enables
>
> testing EPT switching on VMX if supported by hardware. All EPT entries
> are initialized to the same value so this adds no useful functionality
> by itself, but can be used to test
On Mon, Nov 16, 2015 at 02:26:49PM -0300, Javier Martinez Canillas wrote:
> On 11/16/2015 10:53 AM, Mark Brown wrote:
> > What I don't really understand here is why we've decided to push all
> > this stuff into the subsystems, it seems like if we're managing to do
> > the matching based on the com
On Sat, Nov 14, 2015 at 07:33:10PM +0300, Vladimir Davydov wrote:
> On Thu, Nov 12, 2015 at 06:41:24PM -0500, Johannes Weiner wrote:
> > Move the jump-label from sock_update_memcg() and sock_release_memcg()
> > to the callsite, and so eliminate those function calls when socket
> > accounting is not
On Mon, Nov 16, 2015 at 05:48:32PM +, Daniel Stone wrote:
> On 16 November 2015 at 17:43, Russell King - ARM Linux
> wrote:
> > On Mon, Nov 16, 2015 at 05:32:05PM +, Daniel Stone wrote:
> >> On 16 November 2015 at 17:22, Russell King - ARM Linux
> >> wrote:
> >> > Please sensibly wrap you
On 11/16/2015 08:56 AM, Arnd Bergmann wrote:
The newly added scpi thermal support is broken when the scpi driver
is built-in but the thermal driver is a loadable module:
drivers/built-in.o: In function `scpi_hwmon_probe':
(.text+0x444d70): undefined reference to `thermal_zone_of_sensor_unregiste
On Fri, 2015-11-13 at 10:08 +, Luis Henriques wrote:
> This is the start of the review cycle for the Linux 3.16.7-ckt20 stable
> kernel.
>
> This version contains 94 new patches, summarized below. The new patches are
> posted as replies to this message and also available in this git branch:
Hello Mark,
On 11/16/2015 02:49 PM, Mark Brown wrote:
> On Mon, Nov 16, 2015 at 02:19:27PM -0300, Javier Martinez Canillas wrote:
>> On 11/13/2015 08:48 PM, Brian Norris wrote:
>
>>> (I believe I avoided this in the first place for mostly-aesthetic
>>> reasons; technically this allows people to p
On Wed, Oct 28, 2015 at 05:17:31PM +, Sudeep Holla wrote:
> Currently it's assumed that firmware exports only the class of sensors
> supported by the driver. However with newer firmware or SCPI protocol
> revision, support for newer classes of sensors can be present.
>
> The driver fails to pr
These MMRs get mapped in correctly using the new EFI memmap scheme on
recent BIOSes, so we no longer need to set up these extra mappings for
them.
Signed-off-by: Alex Thorlton
Acked-by: Mike Travis
Acked-by: Russ Anderson
Cc: Matt Fleming
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: "H. Peter Anv
Commit a5d90c923bcf ("x86/efi: Quirk out SGI UV") added a quirk to
efi_apply_memmap_quirks to force SGI UV systems to fall back to the old
EFI memmap mechanism. We have a BIOS fix for this issue now, so we no
longer need this quirk in the kernel. This commit removes the quirk
from the function in
On Mon, Nov 16, 2015 at 06:51:06PM +0100,
=?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?= wrote:
> 2015-11-15 18:00+0200, Michael S. Tsirkin:
> > This patch adds a new parameter: eptp_switching_test, which enables
> >
> > testing EPT switching on VMX if supported by hardware. All EPT entries
> > are i
Hello Mark,
On 11/16/2015 02:51 PM, Mark Brown wrote:
> On Mon, Nov 16, 2015 at 02:26:49PM -0300, Javier Martinez Canillas wrote:
>> On 11/16/2015 10:53 AM, Mark Brown wrote:
>
>>> What I don't really understand here is why we've decided to push all
>>> this stuff into the subsystems, it seems li
Hi Guenter,
Guenter Roeck writes:
> On Wed, Oct 28, 2015 at 05:17:31PM +, Sudeep Holla wrote:
>> Currently it's assumed that firmware exports only the class of sensors
>> supported by the driver. However with newer firmware or SCPI protocol
>> revision, support for newer classes of sensors c
On Sat, 14 Nov 2015, Lee, Zhuo-hao wrote:
> (1). alarmtimer create a rtc wake up timer however alarmtimer won't
> remove that timer if the system wake up earlier
That's hardly a bug. That's a slight incorrectness which needs to be
fixed.
> (2). rtc wake up timer will trigger hpet_rtc_interr
On Mon, 16 Nov 2015, Alex Thorlton wrote:
CC'ing Matt under his correct e-mail address.
> Commit a5d90c923bcf ("x86/efi: Quirk out SGI UV") added a quirk to
> efi_apply_memmap_quirks to force SGI UV systems to fall back to the old
> EFI memmap mechanism. We have a BIOS fix for this issue now, so
From: Markus Elfring
Date: Mon, 16 Nov 2015 19:01:44 +0100
The dma_pool_destroy() function tests whether its argument is NULL
and then returns immediately. Thus the test around the calls is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
- Original Message -
> From: Markus Elfring
> Date: Wed, 4 Nov 2015 21:23:43 +0100
>
> The iput() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected by using the Coccinelle software.
>
> Si
Felipe,
On Mon, Nov 16, 2015 at 9:44 AM, Felipe Balbi wrote:
>> extern void dwc2_hcd_start(struct dwc2_hsotg *hsotg);
>> #else
>> static inline int dwc2_hcd_get_frame_number(struct dwc2_hsotg *hsotg)
>> { return 0; }
>> -static inline void dwc2_hcd_disconnect(struct dwc2_hsotg *hsotg) {}
>> +
Hi Joachim,
On Mon, 16 Nov 2015 18:46:44 +0100
Joachim Eastwood wrote:
> Hi Boris
>
> (Adding Ariel for pwm-lpc18xx-sct)
>
> On 16 November 2015 at 09:56, Boris Brezillon
> wrote:
> > Use pwm_get_xxx() helpers instead of directly accessing the pwm->xxx field.
> > Doing that will ease adaptat
On Mon, Nov 16, 2015 at 4:09 AM, Yigal Korman wrote:
> DAX handling of COW faults has wrong locking sequence:
> dax_fault does i_mmap_lock_read
> do_cow_fault does i_mmap_unlock_write
>
> Ross's commit[1] missed a fix[2] that Kirill added to Matthew's
> commit[3].
>
> Original COW
On Mon, Nov 16, 2015 at 04:59:25PM +0100, Michal Hocko wrote:
> On Thu 12-11-15 18:41:32, Johannes Weiner wrote:
> > Socket memory can be a significant share of overall memory consumed by
> > common workloads. In order to provide reasonable resource isolation in
> > the unified hierarchy, this type
2015-11-16 19:59+0200, Michael S. Tsirkin:
> On Mon, Nov 16, 2015 at 06:51:06PM +0100,
> =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?= wrote:
>> 2015-11-15 18:00+0200, Michael S. Tsirkin:
>> (And I think that eptp switching is expected to be used in conjuction
>> with #VE, so it'd then make sense to
sigsuspend() is nowhere used except in signal.c itself,
so we can mark it static do not pollute the global namespace.
But this patch is more than a boring cleanup patch,
it fixes a real issue on UserModeLinux.
UML has a special console driver to display ttys using xterm,
or other terminal emulator
Commit 08d78658f393 ("panic: release stale console lock to always get the
logbuf printed out") introduced unwanted bad unlock balance report when
panic() is called directly and not from OOPS (e.g. from out_of_memory()).
The difference is that in case of OOPS we disable locks debug in
oops_enter() a
On Mon, Nov 16, 2015 at 05:49:23PM +0100, Arnd Bergmann wrote:
> It turns out that the commit that introduced this used the cpu_to_le32()
> incorrectly on an 8-bit field, which results in the sense_len to always
> be set to zero, as the SCSI_SENSE_BUFFERSIZE value gets moved to upper
> byte of the
From: Douglas Gilbert
Following changes that appeared in lk 4.0.0, the gadget udc driver for
some ARM based Atmel SoCs (e.g. at91sam9x5 and sama5d3 families)
incorrectly deduced full-speed USB link speed even when the hardware
had negotiated a high-speed link. The fix is to make sure that the
UDP
Hi,
Doug Anderson writes:
> Felipe,
>
> On Mon, Nov 16, 2015 at 9:44 AM, Felipe Balbi wrote:
>>> extern void dwc2_hcd_start(struct dwc2_hsotg *hsotg);
>>> #else
>>> static inline int dwc2_hcd_get_frame_number(struct dwc2_hsotg *hsotg)
>>> { return 0; }
>>> -static inline void dwc2_hcd_disco
This adds a driver for the Aurora VLSI NB8800 Ethernet controller.
It is an almost complete rewrite of a driver originally found in
a Sigma Designs 2.6.22 tree.
Signed-off-by: Mans Rullgard
---
Changes:
- Use napi_gro_receive()
- Ignore xmit_more if using last tx descriptor
- Perform tx cleanup f
On Tue, Nov 10, 2015 at 01:40:38PM -0600, Andrew F. Davis wrote:
> On 11/10/2015 12:44 PM, Mark Brown wrote:
> >There's also the third option where we don't have any compatible strings
> >in the subnodes at all.
> Ok, two, but would you really want to go that way? Matching by node name costs
> us
Yunzhi
On Mon, Nov 16, 2015 at 7:25 AM, Yunzhi Li wrote:
> When checking dwc2 host channel interrupts, handle qh in
> periodic_sched_queued list at first, then we could make sure CSPLIT
> packets scheduled in the same order as SSPLIT packets.
>
> Signed-off-by: Yunzhi Li
> ---
> drivers/usb/dwc
On Mon 16 Nov 08:41 PST 2015, Arnd Bergmann wrote:
> When building pinctrl-ssbi-gpio and pinctrl-ssbi-mpp for ARM64, we get
> a compile warning about invalid types:
>
> drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c: In function 'pm8xxx_gpio_probe':
> drivers/pinctrl/qcom/pinctrl-ssbi-gpio.c:675:17: wa
> -Original Message-
> From: Steve Wise [mailto:sw...@opengridcomputing.com]
> Sent: Monday, November 16, 2015 10:38 AM
> To: Sagi Grimberg; Christoph Hellwig; linux-r...@vger.kernel.org
> Cc: bart.vanass...@sandisk.com; ax...@fb.com; linux-s...@vger.kernel.org;
> linux-kernel@vger.kerne
On 13/11/15 09:36, Phil Edworthy wrote:
> Hi Marc,
>
> On 12 November 2015 20:31, Marc Zyngier wrote:
>> Phil Edworthy wrote:
>>> On 11 November 2015 16:38, Marc Zyngier wrote:
On Tue, 10 Nov 2015 16:52:33 +0100
Thierry Reding wrote:
> On Mon, Nov 09, 2015 at 06:01:49PM +,
On Mon, 16 Nov 2015, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 16 Nov 2015 19:01:44 +0100
>
> The dma_pool_destroy() function tests whether its argument is NULL
> and then returns immediately. Thus the test around the calls is not needed.
>
> This issue was detected by using
On Thu, Nov 12, 2015 at 09:19:09AM +0100, Uwe Kleine-König wrote:
> I really wonder there is no helper
> function like:
>
> #define of_sensible_name(dev)
> of_match_device(dev->driver->of_match_table, dev)
How about of_device_get_match_data()?
It's not exactly what you asked for, but it
On Mon, Nov 16, 2015 at 10:15:56AM -0800, Dan Williams wrote:
> On Mon, Nov 16, 2015 at 4:09 AM, Yigal Korman wrote:
> > DAX handling of COW faults has wrong locking sequence:
> > dax_fault does i_mmap_lock_read
> > do_cow_fault does i_mmap_unlock_write
> >
> > Ross's commit[1] mis
On Mon, Nov 16, 2015 at 06:20:31PM +, Russell King - ARM Linux wrote:
> On Mon, Nov 16, 2015 at 05:49:23PM +0100, Arnd Bergmann wrote:
> > It turns out that the commit that introduced this used the cpu_to_le32()
> > incorrectly on an 8-bit field, which results in the sense_len to always
> > be
After looking at the nes driver, I don't see any common way to support drain
w/o some serious driver mods. Since SRP is the only
user, perhaps we can ignore iWARP for this function...
But iser/isert essentially does it too (and I think xprtrdma will have
it soon)...
the modify_qp is invoked
Em Mon, 16 Nov 2015 01:02:56 +0200
Sakari Ailus escreveu:
> Hi Shuah,
>
> On Thu, Nov 12, 2015 at 07:41:47AM -0700, Shuah Khan wrote:
> > Media core drivers (dvb, v4l2, bridge driver) unregister
> > their entities calling media_device_unregister_entity()
> > during device removal from their unre
Add functions acpi_nfit_ctl_passthru and __nd_ioctl_passthru which allow
kernel to call a nvdimm's _DSM as a passthru without the marshaling code
of the nd_cmd_desc.
Signed-off-by: Jerry Hoemann
---
drivers/acpi/nfit.c | 93 +++-
drivers/nvdimm/bu
Change nd_ioctl and nvdimm_ioctl access mode check to use O_RDONLY.
Signed-off-by: Jerry Hoemann
---
drivers/nvdimm/bus.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
index 7e2c43f..1c81203 100644
--- a/drivers/nvdim
The NVDIMM code in the kernel supports an IOCTL interface to user
space based upon the Intel Example DSM:
http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf
This interface cannot be used by other NVDIMM DSMs that support
incompatible functions.
This patch set adds a generic "pass
Add struct nd_passthru_pkg which serves as a warapper for
the data being passed via a pass thru to a NVDIMM DSM.
This wrapper specifies the extra information in a uniform
manner allowing the kenrel to call a DSM without knowing
specifics of the DSM.
Signed-off-by: Jerry Hoemann
---
include/uapi/
On Mon, Nov 16, 2015 at 05:25:48PM +0100, Arnd Bergmann wrote:
> Including linux/acpi.h from asm/dma-mapping.h causes tons of compile-time
> warnings, e.g.
>
> drivers/isdn/mISDN/dsp_ecdis.h:43:0: warning: "FALSE" redefined
> drivers/isdn/mISDN/dsp_ecdis.h:44:0: warning: "TRUE" redefined
> driv
It is theoretically possible to probe this driver without a matching
device tree, so let's guard against this.
Also, use the of_device_get_match_data() helper to make this a bit
simpler.
Coverity complained about this one.
Signed-off-by: Brian Norris
Cc: Han Xu
---
drivers/mtd/spi-nor/fsl-qua
On Tue, Nov 10, 2015 at 02:12:06AM +, Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> Probe error operation and remove operation are same.
> Let's use same function.
I am picking this one and sending for next rc cycle. The second patch
is still under discussion and the issue may be s
On Mon, Nov 16, 2015 at 02:22:18PM +0100, mho...@kernel.org wrote:
> From: Michal Hocko
>
> __alloc_pages_high_priority doesn't do anything special other than it
> calls get_page_from_freelist and loops around GFP_NOFAIL allocation
> until it succeeds. It would be better if the first part was don
On Mon, Nov 16, 2015 at 01:23:59PM +0100, Boris Brezillon wrote:
> Mark Brown wrote:
> > On Mon, Nov 16, 2015 at 09:56:32AM +0100, Boris Brezillon wrote:
> > > - pwm_reg_period = pwm_get_period(drvdata->pwm);
> > > + pwm_reg_period = pwm_get_default_period(drvdata->pwm);
> > It's not clear to me
Felipe,
On Mon, Nov 16, 2015 at 10:22 AM, Felipe Balbi wrote:
>> I added "force" in v2 of the patch in response to John's feedback to
>> v1. He pointed out that when you unload the module when you have a
>> device connected that my v1 patch would not properly disconnect the
>> device (or, rather
Hello, Oleg.
Sorry about the delay.
On Tue, Nov 10, 2015 at 09:20:17PM +0100, Oleg Nesterov wrote:
> > We simply need to reimplement cgroup freezer so that its userland
> > visible state is well defined (most likely jobctl stop). Right now,
> > it's allowing userland to trigger "stuck somewhere
It is theoretically possible to probe this driver without a matching
device tree, so let's guard against this.
Also, use the of_device_get_match_data() helper to make this a bit
simpler.
Coverity complained about this one.
Signed-off-by: Brian Norris
Cc: Han Xu
---
v2:
* missed a 'const' warn
501 - 600 of 1077 matches
Mail list logo
