On 20/10/15 17:08, Stephen Warren wrote:
> On 10/20/2015 05:28 AM, Jon Hunter wrote:
>>
>> On 16/10/15 17:17, Stephen Warren wrote:
>>> On 10/16/2015 03:24 AM, Jon Hunter wrote:
The description of the XUSB_PADCTL_USB3_PAD_MUX_0 register in the
Tegra124
documentation implies that all
On 10/20/15 1:46 AM, Daniel Borkmann wrote:
as we discussed in this thread and earlier during plumbers I think
it would be good to expose key/values somehow in this fs.
'how' is a big question.
Yes, it is a big question, and probably best left to the domain-specific
application itself, which ca
Ping? Does no one care how long BLK_SECDISCARD takes?
ChromeOS has landed this change as a compromise between "fast" (<10
seconds) and "minimize risk" (~90 seconds) for a 23GB partition on
eMMC:
https://chromium-review.googlesource.com/#/c/302413/
This is a generic problem if we care about da
Hi Mika,
On Tue Oct 20 15:51, Mika Westerberg wrote:
> On Mon, Oct 19, 2015 at 03:29:00PM -0700, Dustin Byford wrote:
> > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or
> > device property compatible string match) enumerating I2C client devices
> > connected through a I2C
On Tue, 2015-10-20 at 01:57 +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 10/20/2015 01:40 AM, Kamal Mostafa wrote:
>
> > This is a note to let you know that I have just added a patch titled
> >
> > stmmac: fix check for phydev being open
> >
> > to the linux-3.19.y-queue branch of the 3.19.
Hi Alex,
On 10/19/2015 09:45 PM, Alex Williamson wrote:
> On Sun, 2015-10-18 at 18:00 +0200, Eric Auger wrote:
>> In preparation for subsequent changes in reset function lookup,
>> lets introduce a dynamic list of reset combos (compat string,
>> reset module, reset function). The list can be popula
The Backup integration service on WS2012 has appearently trouble to
negotiate with a guest which does not support the provided util version.
Currently the VSS driver supports only version 5/0. A WS2012 offers only
version 1/x and 3/x, and vmbus_prep_negotiate_resp correctly returns an
empty icframe
On Tue, Oct 20, 2015 at 07:36:39PM +0200, Borislav Petkov wrote:
> On Tue, Oct 20, 2015 at 06:26:55PM +0100, Mark Rutland wrote:
> > > Btw, how much of this is implementing generic A57 functionality?
> >
> > The driver is entirely A57 generic.
> >
> > > If a lot, can we make this a generic a57_ed
2015-08-21 7:29 GMT+03:00 Dāvis Mosāns :
> When pci_pool_alloc fails in mvs_task_prep then task->lldd_task stays
> NULL but it's later used in mvs_abort_task as slot which is passed
> to mvs_slot_task_free causing NULL pointer dereference.
>
> Just return from mvs_slot_task_free when passed with NU
On 10/04/2015 05:00 AM, Geliang Tang wrote:
> Just fix a typo in the code comment.
>
> Signed-off-by: Geliang Tang
This has been picked up for the 4.4 merge window.
--
Doug Ledford
GPG KeyID: 0E572FDD
signature.asc
Description: OpenPGP digital signature
On Tue, Oct 20, 2015 at 11:22 AM, Johan Hovold wrote:
> On Tue, Oct 20, 2015 at 09:19:05AM -0500, Konstantin Shkolnyy wrote:
>> On Tue, Oct 20, 2015 at 8:02 AM, Johan Hovold wrote:
>> > On Tue, Oct 20, 2015 at 07:52:31AM -0500, Konstantin Shkolnyy wrote:
>> >> On Tue, Oct 20, 2015 at 2:45 AM, Joh
Forgot to say...
Another question is why PTRACE_TRACEME succeeds in this case. I guess
it is to late to change (break) the rules, but I never understood the
security checks. The comment above cap_ptrace_traceme() says:
Determine whether another process may trace the current
and "another
On 10/01/2015 10:54 AM, Sasha Levin wrote:
> On 09/17/2015 06:59 PM, Jason Gunthorpe wrote:
>> On Thu, Sep 17, 2015 at 04:04:19PM -0400, Sasha Levin wrote:
>>> Allocating a workqueue might fail, which wasn't checked so far and would
>>> lead to NULL ptr derefs when an attempt to use it was made.
>>
"Hongjie Fang (方洪杰)" writes:
> The oom_adj's value reading through /proc//oom_adj is different
> with the value written into /proc//oom_adj.
> Fix this by adding a adjustment factor.
*Scratches my head*
Won't changing the interpretation of what is written break existing
userspace applications
On Tue, Oct 20, 2015 at 06:26:55PM +0100, Mark Rutland wrote:
> > Btw, how much of this is implementing generic A57 functionality?
>
> The driver is entirely A57 generic.
>
> > If a lot, can we make this a generic a57_edac driver so that multiple
> > vendors can use it?
>
> Yes.
Ok, cool.
> >
* H. Nikolaus Schaller [151020 09:48]:
>
> We have our own OMAP5 board in the pipeline and there it will help
> as well to rebase it using arch/arm/boot/dts/omap5-board-common.dts
Yes and then we can hopefully fix up the regulators properly and get
rid of the fixed-regulator flags..
Regards,
T
Hi Felipe,
On lun., oct. 05 2015, Felipe Balbi wrote:
>> So after many tests on different devices, 200ms is enough for most of
>> them, but for one, 2000ms (2s) was needed!
>>
>> I see several option:
>> - adding a sysfs entry to setup the time
>> - adding a debugs entry entry
>> - adding con
* Javier Martinez Canillas [151020 10:26]:
>
> Thanks, I'm planning to convert the remaining OMAP dts but I'm quite busy
> this week and traveling the next one so that would have to wait for v4.5
OK sounds good to me.
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kerne
On 10/20/2015 06:39 AM, Hans de Goede wrote:
Hi,
On 19-10-15 17:55, Larry Finger wrote:
On 10/19/2015 03:08 AM, Hans de Goede wrote:
Hi,
On 19-10-15 01:59, Larry Finger wrote:
Hi,
I recently upgraded the kernel in a Dell Latitude D600 and found that the
touchpad clicks failed. The problem w
> Perf can call this function from !interrupt context (imagine a
> tracepoint or other software event), should we therefore not add a
> pagefault_disable()/enable() pair around the entire while() loop?
That's true. I'll add the pagefault_disable/enable.
-Andi
--
To unsubscribe from this list: sen
On 20 October 2015 at 03:56, Alexander Shishkin
wrote:
> Mathieu Poirier writes:
>
>> Implementing perf related APIs to activate and terminate
>> a trace session. More specifically dealing with the sink
>> buffer's internal mechanic along with perf's API to start
>> and stop interactions with th
On Tue, Oct 20, 2015 at 11:22 AM, Johan Hovold wrote:
> On Tue, Oct 20, 2015 at 09:19:05AM -0500, Konstantin Shkolnyy wrote:
>> On Tue, Oct 20, 2015 at 8:02 AM, Johan Hovold wrote:
>> > On Tue, Oct 20, 2015 at 07:52:31AM -0500, Konstantin Shkolnyy wrote:
>> >> On Tue, Oct 20, 2015 at 2:45 AM, Joh
On Tue, Oct 20, 2015 at 06:57:44PM +0200, Borislav Petkov wrote:
> On Tue, Oct 20, 2015 at 11:44:46AM -0500, Brijesh Singh wrote:
> > > This second property doesn't describe the hardware in any way. It should
> > > be runtime-configurable and dpesn't belong in the DT.
> > >
> > > Regardless, the b
On Tue, Oct 20, 2015 at 11:44:46AM -0500, Brijesh Singh wrote:
> Hi Mark,
>
> Thanks for review.
>
> -Brijesh
>
> On 10/19/2015 03:52 PM, Mark Rutland wrote:
> > Hi,
> >
> > Please Cc the devicetree list (devicet...@vger.kernel.org) when sending
> > binding patches. I see you've added the peop
Hello Tony,
On 10/20/2015 06:26 PM, Tony Lindgren wrote:
> * Javier Martinez Canillas [151019 08:39]:
>> Hello,
>>
>> This series use the IOPAD pinmux macros for the remaining IGEP boards that
>> still used the register offset instead of the physical address using these
>> macros so the DTS match
I see no reason why waitid() can't support other linux-specific flags
allowed in sys_wait4().
Signed-off-by: Oleg Nesterov
---
kernel/exit.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/kernel/exit.c b/kernel/exit.c
index 819f51e..c090738 100644
--- a/kernel/exit.c
The following program (simplified version of generated by syzkaller)
#include
#include
#include
#include
#include
void *thread_func(void *arg)
{
ptrace(PTRACE_TRACEME, 0,0,0);
return 0;
}
On Tue, Oct 20, 2015 at 10:06:51AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Oct 20, 2015 at 02:19:50PM +0200, Frederic Weisbecker escreveu:
> > On Tue, Oct 20, 2015 at 09:00:34AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Mon, Oct 19, 2015 at 05:16:53PM -0700, Brendan Gregg escreveu:
>
Damn. I simply do not know what should/can we do. From the change
log:
And I can only hope that this won't break something.
yet this patch cc's -stable.
Please see the changelog, but in short: this is not a kernel bug
but unlikely we can fix all distributions, so I think we have to
chan
Hi all,
I dropped the check of the firmware file entirely and let the hardware
figure out if there's no sync word in there.
As Mike suggested I tested with streaming random garbage files to the
device and the hardware dealt with it just fine.
Cheers,
Moritz
Moritz Fischer (1):
fpga: zynq-
This gets rid of the code to strip away the header and byteswap,
as well as the check for the sync word.
Signed-off-by: Moritz Fischer
---
v2:
- Removed early exit path in case synq seq is not found
---
drivers/fpga/zynq-fpga.c | 24 ++--
1 file changed, 2 insertions(+), 22
On Tue, Oct 20, 2015 at 12:39 AM, Geliang Tang wrote:
> On Mon, Oct 19, 2015 at 10:56:54PM +, Luck, Tony wrote:
>> Thanks for looking to close out this TODO item.
>>
>> The thing that scared me about unloading pstore was what happens to
>> a process that is in the middle of reading some /sys/f
Dne 19.10.2015 v 16:57 Jan Beulich napsal(a):
On 19.10.15 at 16:51, wrote:
>> Signed-off-by: Michal Sojka
>
> Oops - yes of course. Thanks.
>
> Reviewed-by: Jan Beulich
Applied to kbuild.git#kconfig.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On Tue, 20 Oct 2015, Tomeu Vizoso wrote:
> On 20 October 2015 at 18:04, Alan Stern wrote:
> > On Tue, 20 Oct 2015, Mark Brown wrote:
> >
> >> On Tue, Oct 20, 2015 at 10:40:03AM -0400, Alan Stern wrote:
> >>
> >> > Furthermore, that applies only to devices that use synchronous suspend.
> >> > Asyn
On Tue, Oct 20, 2015 at 06:53:31PM +0200, Peter Zijlstra wrote:
> Also, would it not be better to fix WARN_ON_ONCE() instead?
>
Clearly I'm an idiot and should stay away from the computer...
---
include/asm-generic/bug.h | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff
On Tue, Oct 20, 2015 at 09:58:18AM -0700, H. Peter Anvin wrote:
> I would like to keep nosmap until SMAP hardware is more ubiquitous
> since SMAP is vulnerable to kernel bugs. We have already had a case
> where a maintainer pushed "cleanup" code straight to Linus, bypassing
> the x86 maintainers, w
Add the on-board XO oscillator. This patch prepares for adding support
for RPM controlled clocks. In order to do smooth transition and support
both cases (RPM clock driver is enabled or nor), we first move the XO to
the DT and change the GCC fixed-rate root clock to a dummy pass-through
clock. Then
On 10/20/2015 06:46 AM, Marc Titinger wrote:
On 20/10/2015 15:30, Guenter Roeck wrote:
On 10/20/2015 06:17 AM, Marc Titinger wrote:
On 20/10/2015 14:54, Guenter Roeck wrote:
On 10/20/2015 01:20 AM, Marc Titinger wrote:
With the current implementation, the driver will prevent a readout at a
pa
Hi Mark,
Thanks for review.
-Brijesh
On 10/19/2015 03:52 PM, Mark Rutland wrote:
> Hi,
>
> Please Cc the devicetree list (devicet...@vger.kernel.org) when sending
> binding patches. I see you've added the people from the MAINTAINERS
> entry; the list should also be Cc'd.
>
Noted.
> On Mon, Oc
This adds initial support for clocks controlled by the Resource
Power Manager (RPM) processor found on some Qualcomm SoCs.
The RPM is a dedicated hardware engine for managing the shared
SoC resources in order to keep the lowest power profile. It
communicates with other hardware subsystems via shar
We are moving the sleep clock to the DT. While all patches
are merged, we will ignore sleep_clk_src registration errors.
By ignoring this error, the msm8916 boards will continue booting
during this transition period, otherwise the clock controller
initialization will fail.
Signed-off-by: Georgi Dj
The sleep clock oscillator should be in the DT instead of being
hard-coded into the clock drivers.
Signed-off-by: Georgi Djakov
---
arch/arm64/boot/dts/qcom/msm8916.dtsi |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
b/arch/arm64/boot/dts/qco
Add support for clocks that are controlled by the RPM processor
on Qualcomm msm8916 based platforms.
Signed-off-by: Georgi Djakov
---
.../devicetree/bindings/clock/qcom,rpmcc.txt | 35
drivers/clk/qcom/Kconfig |8 +
drivers/clk/qcom/Makefile
On October 20, 2015 9:33:30 AM PDT, Borislav Petkov wrote:
>From: Borislav Petkov
>
>Those were added as, well, chicken bits in case some of those features
>are b0rked and as a way for us to "chicken" out and disable them.
>Remove
>those chicken bits now, as they're not needed anymore.
>
>Request
This patchset adds initial support for the clocks controlled by
the RPM (Resource Power Manager) processor on Qualcomm platforms.
The RPM is a dedicated hardware engine for managing the shared
SoC resources in order to keep the lowest power profile. It
communicates with other hardware subsystems v
The RPM clock controller driver takes care of registering the
xo clock. Do not register it in this driver if RPM is enabled.
Signed-off-by: Georgi Djakov
---
drivers/clk/qcom/gcc-msm8916.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/clk/qcom/gcc
The sleep_clk_src has been moved to DT, so we do not need to
register it in the GCC driver anymore.
Signed-off-by: Georgi Djakov
---
drivers/clk/qcom/gcc-msm8916.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/clk/qcom/gcc-msm8916.c b/drivers/clk/qcom/gcc-msm8916.c
index 3e106
Remove the hard-coded clock rate from the driver and set the XO
parent to the on-board XO oscillator that is defined in the DT.
Signed-off-by: Georgi Djakov
---
drivers/clk/qcom/gcc-msm8916.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/qcom/gcc-msm8916.c b/
On Tue, Oct 20, 2015 at 11:44:46AM -0500, Brijesh Singh wrote:
> > This second property doesn't describe the hardware in any way. It should
> > be runtime-configurable and dpesn't belong in the DT.
> >
> > Regardless, the binding is wrong. This is in no way specific to AMD
> > Seattle, and per the
On Tue, Oct 20, 2015 at 12:46:28PM -0400, Steven Rostedt wrote:
> On Tue, 20 Oct 2015 18:39:52 +0200
> Peter Zijlstra wrote:
>
> > On Tue, Oct 20, 2015 at 12:21:03PM -0400, Steven Rostedt wrote:
> > > +++ b/kernel/module.c
> > > @@ -284,11 +284,25 @@ static void module_assert_mutex(void)
> > > s
On Tue, Oct 20, 2015 at 06:39:52PM +0200, Peter Zijlstra wrote:
> On Tue, Oct 20, 2015 at 12:21:03PM -0400, Steven Rostedt wrote:
> > +++ b/kernel/module.c
> > @@ -284,11 +284,25 @@ static void module_assert_mutex(void)
> > static void module_assert_mutex_or_preempt(void)
> > {
> > #ifdef CONFIG
On Thu, Oct 08, 2015 at 02:38:21PM -0700, Yinghai Lu wrote:
> After we add 64bit mmio parsing, we got some "no compatible bridge window"
> warning on anther new model that support 64bit resource.
>
> It turns out that we can not use mem_space.start as 64bit mem space
> offset, aka mem_space.start
Hi,
Am 20.10.2015 um 18:24 schrieb Tony Lindgren :
> Hi,
>
> * H. Nikolaus Schaller [151016 05:58]:
>> Signed-off-by: H. Nikolaus Schaller
>> ---
>> arch/arm/boot/dts/omap5-uevm.dts | 10 ++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/omap5-uevm.dts
>> b/a
On 10/19/15 22:26, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20151019:
>
on x86_64:
when CONFIG_DW_DMAC is not enabled.
sound/built-in.o: In function `sst_dma_new':
(.text+0xd7b38): undefined reference to `dw_dma_probe'
sound/built-in.o: In function `sst_dma_free':
(.text+0xd7c0a):
On Tue, 20 Oct 2015 18:39:52 +0200
Peter Zijlstra wrote:
> On Tue, Oct 20, 2015 at 12:21:03PM -0400, Steven Rostedt wrote:
> > +++ b/kernel/module.c
> > @@ -284,11 +284,25 @@ static void module_assert_mutex(void)
> > static void module_assert_mutex_or_preempt(void)
> > {
> > #ifdef CONFIG_LOCK
On 19 October 2015 at 09:37, Alexander Shishkin
wrote:
> Mathieu Poirier writes:
>
>> +static int etm_event_pmu_start(struct perf_event *event)
>> +{
>> + int cpu, ret;
>> + cpumask_t mask;
>> + struct coresight_device *csdev;
>> +
>> + cpumask_clear(&mask);
>> + if (event->cp
On Thu, Oct 08, 2015 at 02:38:20PM -0700, Yinghai Lu wrote:
> Found "no compatible bridge window" warning in boot log from T5-8.
>
> pci :00:01.0: can't claim BAR 15 [mem 0x1-0x4afff pref]: no
> compatible bridge window
>
> That resource is above 4G, but does not get offset corre
On 19 October 2015 at 07:44, Alexander Shishkin
wrote:
> Mathieu Poirier writes:
>
>> Adding an ETB10 specific auxiliary area setup operation to be
>> used by the perf framework when events are initialised.
>>
>> Part of this operation involves modeling the mmap'ed area based
>> on the specific w
On Sun, Oct 18, 2015 at 11:31:13PM +0800, Geliang Tang wrote:
> s/regsiter/register/
>
> Signed-off-by: Geliang Tang
Applied, thank you.
> ---
> drivers/input/keyboard/nomadik-ske-keypad.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/nomadik-
On 20 October 2015 at 11:13, Chaotian Jing wrote:
> Change in v2:
> Drop the 400mhz and use assigned-clock-parents to instead
> Split the original tune patch to several independent patches
> Re-write the mmc_send_tuning()
> Fix GPD checksum error
> Move the HS400 setting to ops->prepare_hs400_tuni
On Tue, Oct 20, 2015 at 12:21:03PM -0400, Steven Rostedt wrote:
> +++ b/kernel/module.c
> @@ -284,11 +284,25 @@ static void module_assert_mutex(void)
> static void module_assert_mutex_or_preempt(void)
> {
> #ifdef CONFIG_LOCKDEP
> + static int once;
> +
> if (unlikely(!debug_locks))
>
I mailed it from LMO 'upstream-sfr'.
I pulled it last week.
I will check it again.
- Leonid.
On Tue, Oct 13 2015 at 11:14:23 AM, Andrew wrote:
> On 2015-10-12 21:39, Mitchel Humpherys wrote:
>> On Tue, Oct 06 2015 at 05:35:41 PM, Rob Herring
>> wrote:
>>> On Tue, Oct 6, 2015 at 3:47 PM, Laura Abbott
>>> wrote:
>>
>> [...]
>>
+Example:
+
+ ion {
+
From: Borislav Petkov
Those were added as, well, chicken bits in case some of those features
are b0rked and as a way for us to "chicken" out and disable them. Remove
those chicken bits now, as they're not needed anymore.
Requested-by: "H. Peter Anvin"
Signed-off-by: Borislav Petkov
---
Docume
Hi,
This series is based on v4.3-rc6.
Adds support for the Imagination University Program MIPSfpga platform.
See the first dt-bindings patch for details about the platform.
These patches allow the kernel to boot with UART and gpio support.
Acks from DT (patch 1/4) welcome.
Regards,
ZubairLK
Add device tree files for the MIPSfpga platform.
See Documentation/devicetree/bindings/mips/img/xilfpga.txt
for details about MIPSfpga
Signed-off-by: Zubair Lutfullah Kakakhel
---
V1 -> V2
Reformatted git log for 80 column
Added nexys4ddr compatible
Fixed some whitespace
Removed a redundant sta
2015-10-20 12:06 GMT+02:00 Daniel Thompson :
> On 17/10/15 18:23, Maxime Coquelin wrote:
>>
>> Signed-off-by: Maxime Coquelin
>> ---
>> include/dt-bindings/pinctrl/pinctrl-stm32.h | 12 +
>> include/dt-bindings/pinctrl/stm32f429-pinfunc.h | 1241
>> +++
>> 2 files cha
The xilfpga platform will be DT only.
Add required platform code.
DT files have already been added separately.
Signed-off-by: Zubair Lutfullah Kakakhel
---
V1 -> V2
Minor nitpicks. Nothing functional.
Removed some redundant select 8250 serial.
Removed a newline
Added description of platform in
Xilfpga boots only with device-tree. Document the required properties
and the unique boot style
Signed-off-by: Zubair Lutfullah Kakakhel
---
V1->V2
Reformatted to 80 char column
Correct clock phandle description
Added digilent,nexys4ddr to get more specific about platform
Added compatible strin
Add defconfig for MIPSfpga
Signed-off-by: Zubair Lutfullah Kakakhel
---
V1 -> V2
Reduced redundant options that had crept in
---
arch/mips/configs/xilfpga_defconfig | 40 +
1 file changed, 40 insertions(+)
create mode 100644 arch/mips/configs/xilfpga_defcon
Not all switch chips support a Get Next operation to iterate on its FDB.
So add a more simple port_fdb_dump function for them.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 4
net/dsa/slave.c | 3 +++
2 files changed, 7 insertions(+)
diff --git a/include/net/dsa.h b/include/net/d
I tested again with a 4.2 kernel but the bug is still present and
happens more often. So far nobody has responded.
I don't know what to do, and whether it's related to usb, mmc or mfd.
Please advise.
When using the RTS5129 card reader (USB2 but internal to Samsung
NP7230U3E series 7 ultrabook) and
There is no need to write the VLAN ID before every Get Next operation,
since the VTU VID register is not cleared between calls.
Move the VID write call in a _mv88e6xxx_vtu_vid_write function outside
of _mv88e6xxx_vtu_getnext so future code could call VTU Get Next
multiple times and save a few regi
Not all switch chips provide a Get Next kind of operation to dump FDB entries.
It is preferred to let the driver handle the dump operation the way it works
best for the chip. Thus, drop port_fdb_getnext and implement the port_fdb_dump
operation in DSA, which pushes the switchdev FDB dump callback d
There is no need to write the MAC address before every Get Next
operation, since ATU MAC registers are not cleared between calls.
Move the _mv88e6xxx_atu_mac_write call outside of _mv88e6xxx_atu_getnext
so future code could call ATU Get Next multiple times and save a few
register access.
---
driv
No driver implements port_fdb_getnext anymore, and port_fdb_dump is
preferred anyway, so remove this function from DSA.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 3 ---
net/dsa/slave.c | 25 +
2 files changed, 1 insertion(+), 27 deletions(-)
diff --git a/i
* Javier Martinez Canillas [151019 08:39]:
> Hello,
>
> This series use the IOPAD pinmux macros for the remaining IGEP boards that
> still used the register offset instead of the physical address using these
> macros so the DTS matches what is in the Technical Reference Manual.
>
> The changes a
Hi,
* H. Nikolaus Schaller [151016 05:58]:
> Signed-off-by: H. Nikolaus Schaller
> ---
> arch/arm/boot/dts/omap5-uevm.dts | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts
> b/arch/arm/boot/dts/omap5-uevm.dts
> index 0e8128b..63f81bb 100644
On Tue, Oct 20, 2015 at 09:19:05AM -0500, Konstantin Shkolnyy wrote:
> On Tue, Oct 20, 2015 at 8:02 AM, Johan Hovold wrote:
> > On Tue, Oct 20, 2015 at 07:52:31AM -0500, Konstantin Shkolnyy wrote:
> >> On Tue, Oct 20, 2015 at 2:45 AM, Johan Hovold wrote:
> >> [...]
> >> > Instead of adding the ne
On 20 October 2015 at 18:04, Alan Stern wrote:
> On Tue, 20 Oct 2015, Mark Brown wrote:
>
>> On Tue, Oct 20, 2015 at 10:40:03AM -0400, Alan Stern wrote:
>>
>> > Furthermore, that applies only to devices that use synchronous suspend.
>> > Async suspend is becoming common, and there the only restric
On Tue, 20 Oct 2015 12:50:26 -0300
Arnaldo Carvalho de Melo wrote:
> Cool, Steven, can I take that as an Acked-by for this patch?
>
Acked-by: Steven Rostedt
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
* Vignesh R [151014 06:59]:
> On am437x-gp-evm, pixcir_i2c_ts can wakeup the system from low power
> state via pinctrl and IO daisy chain using generic wakeirq framework.
> With commit 3fffd1283927 ("i2c: allow specifying separate wakeup
> interrupt in device tree") i2c core allows optional wakeir
The stack tracer triggered the assert in
module_assert_mutex_or_preempt(), which checks that rcu_sched is used
as protection, as __module_address() is protect with a
synchronize_sched().
The problem with this, is that the WARN_ON() triggers a stack dump
which also calls __module_address() and trig
* Javier Martinez Canillas [151014 03:05]:
> I see that people are still sending emails to my old address (that no
> longer exists) since is the one mentioned in the IGEP DTS. Replace it
> with my current email address to avoid this.
Applying this into omap-for-v4.4/dt thanks.
Tony
--
To unsubsc
Implement the port_fdb_dump DSA operation.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6171.c | 1 +
drivers/net/dsa/mv88e6352.c | 1 +
drivers/net/dsa/mv88e6xxx.c | 65 +
drivers/net/dsa/mv88e6xxx.h | 3 +++
4 files changed, 70 insertion
Hi all,
* Dave Gerlach [150922 17:20]:
> Hi,
> This series is version 3 of the code to introduce a wkup_m3_ipc driver
> to handle communication between the MPU and Cortex M3 present on TI AM335x
> and AM437x SoCs. v2 of this series can be found at [1]. Only patch 3
> has been changed based on a r
Now that port_fdb_dump is implemented and even simpler, get rid of
port_fdb_getnext.
Signed-off-by: Vivien Didelot
---
drivers/net/dsa/mv88e6171.c | 1 -
drivers/net/dsa/mv88e6352.c | 1 -
drivers/net/dsa/mv88e6xxx.c | 73 -
drivers/net/dsa/mv88e6xxx
On 20 October 2015 at 16:05, Greg Kroah-Hartman
wrote:
> On Tue, Oct 20, 2015 at 09:40:48AM +0200, Tomeu Vizoso wrote:
>> On 19 October 2015 at 17:19, Greg Kroah-Hartman
>> wrote:
>> > On Mon, Oct 19, 2015 at 05:13:22PM +0200, Tomeu Vizoso wrote:
>> >> To smooth the transition to late probes, mak
On Tue, Oct 20, 2015 at 03:16:26PM +0100, Luis de Bethencourt wrote:
> Hello,
>
> This is a resend of this patch series. It was posted on September 17. [0]
>
> These patches add the missing MODULE_DEVICE_TABLE() for OF to export
> the information so modules have the correct aliases built-in and
>
Kbuild test robot reported some Sparse warnings to the tune of:
sparse: incorrect type in argument 6 (different address spaces)
expected void const *buf
got void [noderef] *mmio
This was due to passing variables tagged with the Sparse cookie
'__iomem' through into memcpy() and print_hex
Paul,
I've spent a couple of days debugging this, and finally found that my
stack tracer was calling the stack trace code, which calls
__module_address() which asserts the below.
Is just calling rcu_irq_enter() and rcu_irq_exit() safe to do
everywhere (with interrupts always disabled)? This patc
On 10/20/2015 05:28 AM, Jon Hunter wrote:
On 16/10/15 17:17, Stephen Warren wrote:
On 10/16/2015 03:24 AM, Jon Hunter wrote:
The description of the XUSB_PADCTL_USB3_PAD_MUX_0 register in the
Tegra124
documentation implies that all functions (pcie, usb3 and sata) can be
muxed onto to all lanes
On Tue, Oct 20, 2015 at 05:40:36PM +0200, Paolo Bonzini wrote:
>
>
> On 20/10/2015 16:00, Peter Zijlstra wrote:
> >> > -prepare_to_wait(&vcpu->wq, &wait, TASK_INTERRUPTIBLE);
> >> > +prepare_to_swait(&vcpu->wq, &wait, TASK_INTERRUPTIBLE);
> >> >
> >> >
On Tue, 20 Oct 2015, Mark Brown wrote:
> On Tue, Oct 20, 2015 at 10:40:03AM -0400, Alan Stern wrote:
>
> > Furthermore, that applies only to devices that use synchronous suspend.
> > Async suspend is becoming common, and there the only restrictions are
> > parent-child relations plus whatever
On Mon, Sep 21, 2015 at 12:02 PM, Vinod Koul wrote:
> On Fri, Aug 28, 2015 at 02:32:41PM -0500, Han Xu wrote:
>> @@ -28,7 +28,6 @@
>> #include
>> #include
>> #include
>> -
>
> Pl dont change at random places
It's not a random place, i.MX7D need an extra clock clk_io for APBH
DMA, I will add
On 20/10/15 16:05, Jungseok Lee wrote:
> On Oct 20, 2015, at 7:05 PM, James Morse wrote:
>> On 17/10/15 15:27, Jungseok Lee wrote:
>>> diff --git a/arch/arm64/kernel/irq.c b/arch/arm64/kernel/irq.c
>>> index 9f17ec0..13fe8f4 100644
>>> --- a/arch/arm64/kernel/irq.c
>>> +++ b/arch/arm64/kernel/irq.c
Caesar,
On Tue, Oct 20, 2015 at 2:11 AM, Caesar Wang wrote:
> As the TRM says, the TSHUT default state is high active.
> In general, the TSHUT state can get from the dts. Otherwise
> it gets the state from this.
Can you point at where the TRM says that the default state is high active?
With the
Signed-off-by: Fengguang Wu
---
hns_ae_adapt.c |2 +-
hns_enet.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c
b/drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c
index c3d64ce..bf277c7 100644
--- a/drivers/ne
Hi Salil,
[auto build test WARNING on net-next/master -- if it's inappropriate base,
please suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Salil/net-hns-Add-support-of-Hip06-SoC-to-the-Hislicon-Network-Subsystem/20151020-225151
repr
On Tue, 20 Oct 2015 17:37:43 +0200
Paolo Bonzini wrote:
> However, it frankly seems a bit academic. The parsing _will_ work,
> apart from printing a nonsensical role just like it has always done for
> the past four years.
I'm not going to be too picky about it. But things like this may seem
aca
601 - 700 of 1230 matches
Mail list logo
