Add a generic function for raising MSI irqs that can be used by all
DWC based controllers.
Note that certain controllers, like DRA7xx, have a special convenience
register for raising MSI irqs that doesn't require you to explicitly map
the MSI address. Therefore, it is likely that certain drivers w
Use BIT and GENMASK macros to improve readability.
Signed-off-by: Niklas Cassel
---
drivers/pci/dwc/pcie-artpec6.c | 34 +-
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/drivers/pci/dwc/pcie-artpec6.c b/drivers/pci/dwc/pcie-artpec6.c
index 4b8ef2
The PCIe controller integrated in ARTPEC-6 SoCs is capable of operating in
endpoint mode. Add endpoint mode support to the artpec6 driver.
Signed-off-by: Niklas Cassel
---
drivers/pci/dwc/Kconfig| 23 +--
drivers/pci/dwc/pcie-artpec6.c | 152 +++--
There is no need to hard code the cpu to bus address fixup mask.
The PCIe controller has a global address on the AXI bus, however,
from the perspective of the PCIe controller, its base starts at 0x0,
so the local address is 0x0. To get the bus address, simply subtract
the global address from the cp
The dra7xx driver supports both host and ep mode.
When enabling support for only one of the modes, help the compiler
to remove code for the mode that we have not enabled in the driver.
By adding if (!IS_ENABLED(CONFIG_PCI_DRA7XX_HOST)) return -ENODEV;
anything after that statement will get silentl
Waiting for the PHY while the core was held in reset worked for artpec6,
but for artpec7, in order to read the required registers, the core has to
be out of reset.
Refactor the code so we always wait for the PHY after the core has been
deasserted, since this works for both artpec6 and artpec7.
Sig
Split artpec6_pcie_establish_link() into smaller functions
to better match other drivers such as dra7xx and imx6.
This is also done to prepare for endpoint mode support.
Signed-off-by: Niklas Cassel
---
drivers/pci/dwc/pcie-artpec6.c | 55 ++
1 file change
Commit b015b37e6693 ("PCI: artpec6: Stop enabling writes to
DBI read-only registers") removed the only write using these
defines, but it did not remove the defines.
Remove the defines since they are now unused.
Signed-off-by: Niklas Cassel
---
drivers/pci/dwc/pcie-artpec6.c | 3 ---
1 file chang
Add support for the ARTPEC-7 SoC in the artpec6 driver.
The ARTPEC-6 SoC and the ARTPEC-7 SoC are very similar.
Unfortunately, some fields in the PCIECFG and PCIESTAT
register have changed.
Signed-off-by: Niklas Cassel
---
drivers/pci/dwc/pcie-artpec6.c | 187
Add support for the ARTPEC-7 SoC in the artpec6 driver.
The ARTPEC-6 SoC and the ARTPEC-7 SoC are very similar.
Unfortunately, some fields in the PCIECFG and PCIESTAT
register have changed.
Signed-off-by: Niklas Cassel
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/axis,artpec6
The PCIe controller integrated in ARTPEC-6 SoCs is capable of operating in
endpoint mode. Add endpoint mode support to the artpec6 driver.
Signed-off-by: Niklas Cassel
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt | 3 ++-
1 file changed, 2 insertions(+),
Assign pp->ops in *_add_pcie_port() to match how it is done in other
drivers like exynos, imx7, keystone, armada8k, artpec6, designware-plat,
hisi, kirin and spear13xx.
This is probably a remainder since when dev and ops were assigned as
members to pp. Since we now assign them as members to struct
Refactor the Kconfig and Makefile handling for host/ep mode, since
the previous handling was a bit unorthodox and would have been a bit
bloated once more DWC based controllers added support for ep mode.
Signed-off-by: Niklas Cassel
Acked-by: Kishon Vijay Abraham I
---
drivers/pci/dwc/Kconfig |
Remove the static keyword from dw_pcie_ep_reset_bar() so that
pci-dra7xx.c does not need its own copy of dw_pcie_ep_reset_bar().
Signed-off-by: Niklas Cassel
Acked-by: Kishon Vijay Abraham I
---
drivers/pci/dwc/pci-dra7xx.c | 9 -
drivers/pci/dwc/pcie-designware-ep.c | 2 +-
dri
Certain SoCs need to map the MSI address in raise_irq.
To map an address, you first need to call pci_epc_mem_alloc_addr(),
however, pci_epc_mem_alloc_addr() calls ioremap() (which can sleep).
Since raise_irq is only called from atomic context, we can't call
pci_epc_mem_alloc_addr() from raise_irq.
This is a series that adds:
- PCI endpoint mode support in the ARTPEC-6 driver.
- ARTPEC-7 SoC support in the ARTPEC-6 driver (the SoCs are very similar).
- Small fixes for MSI in designware-ep and designware-host,
needed to get endpoint mode support working for ARTPEC-6.
- Cleanups in pci-dra7xx
On Wed, Nov 8, 2017 at 9:40 AM, Peter Zijlstra wrote:
> On Wed, Nov 08, 2017 at 09:19:53AM +0100, Dmitry Vyukov wrote:
>
>> > R13: 00402260 R14: 004022f0 R15:
>> > kasan: CONFIG_KASAN_INLINE enabled
>> > kasan: GPF could be caused by NULL-ptr deref or user memory a
On Sat, Nov 18, 2017 at 10:25 AM, Takashi Iwai wrote:
> On Sat, 18 Nov 2017 01:01:55 +0100,
> Pierre-Louis Bossart wrote:
>>
>> At the risk of being scolded for the third time in two days by
>> Linux overlords (no hard feelings), here's an attempt to clean
>> things up.
>>
>> The first patch *shou
There are two consumers of apic=: the APIC debug level and the low
level generic architecture code, but Linux just documented the first
one.
Append the second description.
Signed-off-by: Dou Liyang
---
Documentation/admin-guide/kernel-parameters.txt | 5 -
1 file changed, 4 insertions(+), 1
There are two consumers of apic=:
apic_set_verbosity() for setting the APIC debug level;
parse_apic() for registering APIC driver by hand.
In X86-32 arch, when kernel was booted up with 'apic=bigsmp' in command
line, early_param would warn like that:
...
[0.00] APIC Verbosity level bi
On Sat, Nov 18, 2017 at 07:02:16AM +0800, Yang Shi wrote:
> Preempt counter APIs have been split out, currently, hardirq.h just
> includes irq_enter/exit APIs which are not used by btrfs at all.
>
> So, remove the unused hardirq.h.
>
> Signed-off-by: Yang Shi
> Cc: Chris Mason
> Cc: Josef Bacik
default_acpi_madt_oem_check() is just called when ACPI parse the MADT
table and doesn't return anything.
So make it void. also add identifier names for definition arguments.
Signed-off-by: Dou Liyang
---
arch/x86/include/asm/apic.h | 2 +-
arch/x86/kernel/apic/probe_32.c | 5 ++---
arch/x86
On Mon, Nov 20, 2017 at 12:23 AM, Lukasz Majewski wrote:
> Hi Alexander,
>
>> Hello Lukasz!
>>
>> On 17/11/17 00:22, Lukasz Majewski wrote:
>> > This patch series adds support for Liebherr's BK3 board, being
>> > a derivative of TS72XX design.
>> >
>> > This patchset consists of following patches:
> Last week I was working on the TMIO driver
> and I have more bug-fix and clean-up patches in hand now.
> (about 20 patches)
>
> The patch order is getting a mess,
> so I am planning to put all patches in one series.
>
> If not in hurry, can you wait for a little?
So, did I get this correct: a
On 11/20/2017 02:13 PM, Geert Uytterhoeven wrote:
> Hi Richard,
>
> On Mon, Nov 20, 2017 at 1:55 PM, Richard Leitner
> wrote:
>> On 11/20/2017 11:35 AM, Andy Duan wrote:
>>> 3. add reset gpio descriptor for common phy device driver.
>>
>> ... if I understood it correctly the patch called "Teach
On Mon, 20 Nov 2017 13:47:28 +0100,
Dmitry Vyukov wrote:
>
> On Wed, Nov 1, 2017 at 8:49 PM, Takashi Iwai wrote:
> > On Wed, 01 Nov 2017 19:39:46 +0100,
> > Dmitry Vyukov wrote:
> >>
> >> On Wed, Nov 1, 2017 at 9:38 PM, syzbot
> >>
> >> wrote:
> >> > Hello,
> >> >
> >> > syzkaller hit the follow
On Mon, Nov 20, 2017 at 01:39:31PM +0100, Daniel Vetter wrote:
> On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
> > Hi all,
> >
> > Since I'm going slightly off-topic, I've tweaked the subject line and
> > trimmed some of the conversation.
> > I believe everyone in the CC list might
Hi Richard,
On Mon, Nov 20, 2017 at 1:55 PM, Richard Leitner
wrote:
> On 11/20/2017 11:35 AM, Andy Duan wrote:
>> 3. add reset gpio descriptor for common phy device driver.
>
> ... if I understood it correctly the patch called "Teach phylib
> hard-resetting devices" by Geert and Sergei is exactly
On 10/07/2017, 09:33 AM, Ulf Hansson wrote:
> Here's a PR with a couple of MMC fixes intended for v4.14-rc4. Details about
> the
> highlights are as usual found in the signed tag.
...
>
> MMC core:
> - Delete bounce buffer handling:
On Fri, Nov 17, 2017 at 10:02 PM, Al Viro wrote:
> On Thu, Nov 16, 2017 at 02:56:00AM -0800, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 5515cf16e270538121e4fa9283fed86c6cfd8c9c
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
>> compiler: gcc (
2017-11-20 20:39 GMT+08:00 Michal Hocko :
> On Mon 20-11-17 20:16:15, Yafang Shao wrote:
>> 2017-11-20 20:04 GMT+08:00 Michal Hocko :
>> > On Fri 17-11-17 09:49:54, Shakeel Butt wrote:
>> >> On Fri, Nov 17, 2017 at 9:41 AM, Yafang Shao wrote:
>> > [...]
>> >> > Of couse that is the best way.
>> >>
On Mon, 20 Nov 2017, Johan Hovold wrote:
> On Wed, Nov 15, 2017 at 03:39:09PM +0100, Johan Hovold wrote:
> > On Wed, Nov 15, 2017 at 02:32:11PM +, Lee Jones wrote:
> > > On Wed, 15 Nov 2017, Johan Hovold wrote:
> > >
> > > > On Tue, Nov 14, 2017 at 07:48:09PM +, Daniel Thompson wrote:
> >
Hi,
Please kindly check the new kbuild/runtime test reports uploaded to Test Report
Center.
Test Configurations
===
kernel tree/branch: linus/master
kernel commit/tag: 39dae59d/v4.14-rc8
test boxes: lkp-kblr01
test cases: kbuild/runtime
Test Reports
On Mon, Nov 20, 2017 at 12:17:11PM +0100, Juergen Gross wrote:
> On 20/11/17 11:49, Wei Liu wrote:
> > CC netfront maintainers.
> >
> > On Mon, Nov 20, 2017 at 11:41:09AM +0100, Eduardo Otubo wrote:
> >> When unloading module xen_netfront from guest, dmesg would output
> >> warning messages like b
On Mon, Nov 20, 2017 at 10:55:55AM +, Paul Durrant wrote:
> > -Original Message-
> > From: Eduardo Otubo [mailto:ot...@redhat.com]
> > Sent: 20 November 2017 10:41
> > To: xen-de...@lists.xenproject.org
> > Cc: net...@vger.kernel.org; Paul Durrant ; Wei
> > Liu ; linux-kernel@vger.kerne
On 11/20/2017 11:35 AM, Andy Duan wrote:
> From: Richard Leitner Sent: Monday, November
> 20, 2017 5:57 PM
>> To: Andy Duan ; f.faine...@gmail.com;
>> and...@lunn.ch
>> Cc: Richard Leitner ; net...@vger.kernel.org; linux-
>> ker...@vger.kernel.org
>> Subject: Re: [PATCH v2 3/3] net: ethernet: fec
On Sat, Nov 18, 2017 at 7:07 PM, Boris Ostrovsky
wrote:
>
>
> On 11/18/2017 12:39 PM, Trond Myklebust wrote:
>>
>> On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote:
>>>
>>> A similar bug was fixed by e0714ec4f9efe7b86828b0dcc077fd8f5d8e5e91
>>> but
>>> I don't think the same approach can
On Mon, Nov 20, 2017 at 1:47 PM, Dmitry Vyukov wrote:
> On Wed, Nov 1, 2017 at 8:49 PM, Takashi Iwai wrote:
>> On Wed, 01 Nov 2017 19:39:46 +0100,
>> Dmitry Vyukov wrote:
>>>
>>> On Wed, Nov 1, 2017 at 9:38 PM, syzbot
>>>
>>> wrote:
>>> > Hello,
>>> >
>>> > syzkaller hit the following crash on
>
On Wed, Nov 1, 2017 at 8:49 PM, Takashi Iwai wrote:
> On Wed, 01 Nov 2017 19:39:46 +0100,
> Dmitry Vyukov wrote:
>>
>> On Wed, Nov 1, 2017 at 9:38 PM, syzbot
>>
>> wrote:
>> > Hello,
>> >
>> > syzkaller hit the following crash on
>> > fc2e8b1a47c14b22c33eb087fca0db58e1f4ed0e
>> > git://git.kernel
Jason,
As was discussed in September and October, add Jason along with
Doug to have a team maintainership model for the RDMA subystem.
Happy to see this happening, thanks for stepping up. Thanks to everyone
who allowed it to happen (especially Doug).
Good Luck!
On Mon, 2017-11-20 at 11:53 +0100, Sebastian Siewior wrote:
>
> To your question whether or not delaying IO can cause any deadlocks is
> something that I can't answer and this something that would affect !RT,
> too. I tried to add lockdep to bit-spinlocks but this does not work
> because one conte
Allow URL to exceed the 80 char limit for improved interaction in
adaption to ongoing but undocumented practice.
$ git grep -E '://\S{77}.*' -- '*.[ch]'
The patch checks that the URL is indeed on its own line in that it
allows a maximal prefix of 3 characters to account for a URL after a
comment
On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
> Hi all,
>
> Since I'm going slightly off-topic, I've tweaked the subject line and
> trimmed some of the conversation.
> I believe everyone in the CC list might be interested in the
> following, yet feel free to adjust.
>
> Above all,
On Mon 20-11-17 20:16:15, Yafang Shao wrote:
> 2017-11-20 20:04 GMT+08:00 Michal Hocko :
> > On Fri 17-11-17 09:49:54, Shakeel Butt wrote:
> >> On Fri, Nov 17, 2017 at 9:41 AM, Yafang Shao wrote:
> > [...]
> >> > Of couse that is the best way.
> >> > But we can not ensue all applications will do i
On Sun, 2017-11-19 at 10:00 +0100, SF Markus Elfring wrote:
> From: Markus Elfring
get_maintainter.pl --git-min-percent=67 will do a nice job to make at
least me not seeing this stuff.
--
Andy Shevchenko
Intel Finland Oy
Hi,
On Thu, Nov 16, 2017 at 06:27:28AM +, Jia He wrote:
> Sometimes userspace need a high resolution cycle counter by reading
> pmccntr_el0.
>
> In commit da4e4f18afe0 ("drivers/perf: arm_pmu: implement CPU_PM
> notifier"), it resets all the counters even when the pmcr_el0.E and
> pmcntenset_
I didn't see this merged for 4.15, is it too late to include this?
All other changes needed to get CEC to work on rk3288 and rk3399 are all merged.
Regards,
Hans
On 10/26/2017 08:19 PM, Pierre-Hugues Husson wrote:
> The documentation already mentions "cec" optional clock, but
> currently
On Mon, Nov 20, 2017 at 08:15:56PM +0800, Jin, Yao wrote:
>
>
> On 11/20/2017 5:26 PM, Jiri Olsa wrote:
> > On Mon, Nov 20, 2017 at 10:43:35PM +0800, Jin Yao wrote:
> > > perf stat --per-thread is useful to break down data per thread.
> > > But it currently requires specifying --pid/--tid to limi
On 18 November 2017 at 15:31, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
> instruct the PM core and middle-layer (bus type, PM domain, etc.)
> code that it is desirable to leave the device in runtime suspend
> after s
On Mon, Nov 20, 2017 at 8:31 AM, Chris Chiu wrote:
> On Fri, Nov 17, 2017 at 10:25 PM, Andy Shevchenko
> wrote:
>> On Thu, Nov 16, 2017 at 3:44 PM, Chris Chiu wrote:
>>> +
>>> +struct acer_wireless_data {
>>> + struct input_dev *idev;
>>
>>> + struct acpi_device *adev;
>>
>> Do you
On 2017-11-20 12:24, Thomas Gleixner wrote:
> On Sat, 18 Nov 2017, Jan Kiszka wrote:
>> On 2017-11-17 23:49, Thomas Gleixner wrote:
>>> On Thu, 16 Nov 2017, Jan Kiszka wrote:
Calibrate the TSC and, where necessary, the APIC timer against the
TMTIMER. We need our own implementation as neit
On Thu, Nov 16, 2017 at 03:28:19PM +, Will Deacon wrote:
> On Thu, Oct 26, 2017 at 10:09:41AM +0100, Mark Rutland wrote:
> > +static bool __range_ok_c(unsigned long addr, unsigned long size)
> > +{
> > + unsigned long result;
> > +
> > + if (__builtin_uaddl_overflow(addr, size, &result))
>
On Fri, 10 Nov 2017, Dave Hansen wrote:
> From: Dave Hansen
>
> This is largely code from Andy Lutomirski. I fixed a few bugs
> in it, and added a few SWITCH_TO_* spots.
>
> KAISER needs to switch to a different CR3 value when it enters
> the kernel and switch back when it exits. This essentia
On Mon, Nov 20, 2017 at 11:20:13AM +0100, Michael Kerrisk (man-pages) wrote:
> On 08/16/2017 07:14 PM, Eric W. Biederman wrote:
> > Aleksa Sarai writes:
> >
> >>> A couple of things to note on the bigger picture.
> >>>
> >>> The glibc library on all distributions has been changed to not have a
>
2017-11-20 20:04 GMT+08:00 Michal Hocko :
> On Fri 17-11-17 09:49:54, Shakeel Butt wrote:
>> On Fri, Nov 17, 2017 at 9:41 AM, Yafang Shao wrote:
> [...]
>> > Of couse that is the best way.
>> > But we can not ensue all applications will do it.
>> > That's why I introduce a proper defalut value for
On 11/20/2017 5:26 PM, Jiri Olsa wrote:
On Mon, Nov 20, 2017 at 10:43:35PM +0800, Jin Yao wrote:
perf stat --per-thread is useful to break down data per thread.
But it currently requires specifying --pid/--tid to limit it to a process.
For analysis it would be useful to do it globally for the
2017-11-20 20:06 GMT+08:00 Dmitry Vyukov :
> On Mon, Nov 20, 2017 at 10:23 AM, Dmitry Vyukov wrote:
>> On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li wrote:
>>> Hi Dmitry,
>>> 2017-11-20 12:09 GMT+08:00 Wanpeng Li :
2017-11-18 4:22 GMT+08:00 syzbot
:
> Hello,
>
> syzbot has te
On Mon, Nov 20, 2017 at 10:23 AM, Dmitry Vyukov wrote:
> On Mon, Nov 20, 2017 at 10:19 AM, Wanpeng Li wrote:
>> Hi Dmitry,
>> 2017-11-20 12:09 GMT+08:00 Wanpeng Li :
>>> 2017-11-18 4:22 GMT+08:00 syzbot
>>> :
Hello,
syzbot has tested the proposed patch but the reproducer still trig
On Fri 17-11-17 09:49:54, Shakeel Butt wrote:
> On Fri, Nov 17, 2017 at 9:41 AM, Yafang Shao wrote:
[...]
> > Of couse that is the best way.
> > But we can not ensue all applications will do it.
> > That's why I introduce a proper defalut value for them.
> >
>
> I think we disagree on the how to
On Fri, Nov 17, 2017 at 05:54:05PM -0800, Megha Dey wrote:
> + mutex_lock(&bm_counter_mutex);
> + for (i = 0; i < BM_MAX_COUNTERS; i++) {
> + if (bm_counter_owner[i] == NULL) {
> + counter_to_use = i;
> + bm_counter_owner[i] = event;
> +
On 11/18/2017 07:23 PM, Cao jin wrote:
> Drop unnecessary "__subdir-Y" and `cat /dev/null`
>
> Signed-off-by: Cao jin
> ---
> Don't know why they exist, but a simple build is fine without them
> in my test
>
> scripts/Makefile.modbuiltin | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletio
On Mon, Nov 20, 2017 at 11:34:07AM +, Daniel Thompson wrote:
>
>
> On 20/11/17 10:45, Johan Hovold wrote:
> > Fix child-node lookup during probe, which ended up searching the whole
> > device tree depth-first starting at the parent rather than just matching
> > on its children.
> >
> > This
On Sun, Nov 19, 2017 at 11:23:42PM -0500, Frank Rowand wrote:
> adding devicetree list, devicetree maintainers
>
> On 11/18/17 12:59, Ulf Samuelsson wrote:
> > I noticed when checking out the OpenWRT support for the board that they
> > have a method to avoid having to pass the device tree address
On 11/09/2017 06:52 PM, Joel Fernandes wrote:
[...]
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 56f343b8e749..ba9609407cb9 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -5724,7 +5724,7 @@ static int cpu_util_wake(int cpu, struct task_struct *p);
static unsi
On 2017-11-18 02:00, Rob Herring wrote:
On Thu, Nov 16, 2017 at 05:48:35PM +0530, Kiran Gunda wrote:
Handle the short circuit(SC) interrupt and check if the SC interrupt
is valid. Re-enable the module to check if it goes away. Disable the
module altogether if the SC event persists.
Signed-off-b
On 20/11/17 10:45, Johan Hovold wrote:
Two framebuffer device-node names were looked up during probe, but were
only used as flags to indicate the presence of two framebuffer device.
Drop the unused framebuffer name along with a likewise unused device
pointer from the driver data, and update the
On 11/14/2017 01:32 AM, Michael S. Tsirkin wrote:
You should Cc Nitesh who is working on a related feature.
OK, I'll do. We have two more issues which haven't been discussed yet,
please have a check below.
On Mon, Nov 13, 2017 at 06:34:48PM +0800, Wei Wang wrote:
Ping for comments, thanks
On Fri, Nov 17, 2017 at 11:19:05AM -0200, Mauro Carvalho Chehab wrote:
Em Fri, 17 Nov 2017 11:08:01 -0200
Gustavo Padovan escreveu:
2017-11-17 Mauro Carvalho Chehab :
> Em Fri, 17 Nov 2017 15:49:23 +0900
> Alexandre Courbot escreveu:
>
> > > @@ -178,6 +179,12 @@ static int vb2_queue_or_prepa
On 20/11/17 10:45, Johan Hovold wrote:
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
This would only cause trouble if the child node is missing while there
is an unrelated node na
On 20/11/17 10:45, Johan Hovold wrote:
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
To make things worse, the parent mfd node was also prematurely freed,
while the child backligh
On 20/11/17 10:45, Johan Hovold wrote:
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
To make things worse, the parent mfd node was also prematurely freed.
Fixes: 59eb2b5e57ea ("d
On Mon, Nov 20, 2017 at 9:22 AM, Michal Hocko wrote:
> On Fri 17-11-17 11:15:45, Arnd Bergmann wrote:
>> The cleanup caused build warnings for constant mask pointers:
>>
>> mm/mempolicy.c: In function ‘mpol_to_str’:
>> ./include/linux/nodemask.h:108:11: warning: the comparison will always
>> eval
On Sun, Nov 19, 2017 at 11:29:35AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 14, 2017 at 04:18:23PM +, Mark Rutland wrote:
> > I agree that we need both patches. On its own (in the absence of PAN/UAO),
> > 57f4959bad0a154a wouldn't have any effect, but it is critical to ensure
> > that we
On Sat, 18 Nov 2017, Jan Kiszka wrote:
> On 2017-11-17 23:49, Thomas Gleixner wrote:
> > On Thu, 16 Nov 2017, Jan Kiszka wrote:
> >> Calibrate the TSC and, where necessary, the APIC timer against the
> >> TMTIMER. We need our own implementation as neither the PIC nor the HPET
> >> are available, an
On Sat, 18 Nov 2017, Jan Kiszka wrote:
> On 2017-11-17 22:54, Thomas Gleixner wrote:
> > Shouldn't this structure and SETUP_JAILHOUSE be defined in a header file
> > which can be exported to boot loaders?
>
> Something like arch/x86/include/uapi/asm/jailhouse_setup.h?
Something like that.
Thanks
Hi all,
Since I'm going slightly off-topic, I've tweaked the subject line and
trimmed some of the conversation.
I believe everyone in the CC list might be interested in the
following, yet feel free to adjust.
Above all, I'd kindly ask everyone to skim through and draw their conclusions.
If the id
On 20/11/17 11:49, Wei Liu wrote:
> CC netfront maintainers.
>
> On Mon, Nov 20, 2017 at 11:41:09AM +0100, Eduardo Otubo wrote:
>> When unloading module xen_netfront from guest, dmesg would output
>> warning messages like below:
>>
>> [ 105.236836] xen:grant_table: WARNING: g.e. 0x903 still in
On Sun, Nov 19, 2017 at 01:44:40PM +0100, Pali Rohár wrote:
> On Thursday 09 November 2017 22:21:31 Pali Rohár wrote:
> > So from all tests and discussion I would propose new unification:
> >
> > 1. Read label only from the root directory. If label in root directory
> >is missing then disk wou
On 18/11/17 17:46, Fabian Baumanis wrote:
Removed uneccessary parantheses which were sorrounding two
if-statements.
There is only one 'if' statement changed by the patch. Apart from that
(and the typos in the patch description), the patch is fine as far as it
goes. However, the checkpatch s
> -Original Message-
> From: Eduardo Otubo [mailto:ot...@redhat.com]
> Sent: 20 November 2017 10:41
> To: xen-de...@lists.xenproject.org
> Cc: net...@vger.kernel.org; Paul Durrant ; Wei
> Liu ; linux-kernel@vger.kernel.org;
> vkuzn...@redhat.com; cav...@redhat.com; che...@redhat.com;
> mga.
+Jarkko
On Sun, Nov 19, 2017 at 04:35:51PM +, Jonathan Cameron wrote:
> On Thu, 2 Nov 2017 16:04:07 +0100
> Wolfram Sang wrote:
>
> > On Thu, Nov 02, 2017 at 02:35:50PM +, Jonathan Cameron wrote:
> > > On Fri, 27 Oct 2017 18:27:02 +0200
> > > Marc CAPDEVILLE wrote:
> > >
> > > > On a
Christoph Hellwig wrote:
> On Mon, Nov 20, 2017 at 10:42:37AM +0100, Michal Hocko wrote:
> > The patch has been dropped because allnoconfig failed to compile back
> > then
> > http://lkml.kernel.org/r/CAP=VYLr0rPWi1aeuk4w1On9CYRNmnEWwJgGtaX=wevgabur...@mail.gmail.com
> > I have problem to find the
On 2017-11-18 19:37:10 [+0100], Mike Galbraith wrote:
> Below is my 2012 3.0-rt version of that for reference; at that time we
> were using slab, and slab_lock referenced below was a local_lock. The
> comment came from crash analysis of a deadlock I met before adding the
> (yeah, hacky) __migrate_
It is better to centralize the information of special devices in one
single file. Instead of manually parsing the list of devices that
have a special driver or those that need to be ignored, introduce
HID_QUIRK_HAVE_SPECIAL_DRIVER and set the correct quirks while fetching
those quirks.
Signed-off-
On Wed, Nov 15, 2017 at 03:39:09PM +0100, Johan Hovold wrote:
> On Wed, Nov 15, 2017 at 02:32:11PM +, Lee Jones wrote:
> > On Wed, 15 Nov 2017, Johan Hovold wrote:
> >
> > > On Tue, Nov 14, 2017 at 07:48:09PM +, Daniel Thompson wrote:
> > > > On 14/11/17 18:05, Johan Hovold wrote:
> > > >
On Nov 20 2017 or thereabouts, Jiri Kosina wrote:
> On Thu, 16 Nov 2017, Benjamin Tissoires wrote:
>
> > > I am planning to queue this for 4.16; do you happen to have any followups
> > > since you posted v2 in october?
> >
> > Cool. I did not updated it since, but if you want I can send a v3
> >
Most HID devices behave properly when they are used with hid-generic.
Since kernel v4.12, we do not poll for input reports at plug in, so
hid-generic should behave properly with all HID devices.
There has been a long standing list of HID devices that have a special
driver. It used to be just a few
Better having all the devices quirks in one place.
Note that this change introduces an initial lookup for the device in
hid_gets_squirk(), which should not theoretically be required, but which
actually allows to not have to reparse the list of ignored devices
if we call hid_lookup_quirks twice.
S
Hi,
this is v3 rebased on top of for-next.
There are no other changes.
Cheers,
Benjamin
Benjamin Tissoires (4):
HID: core: move the dynamic quirks handling in core
HID: quirks: move the list of special devices into a quirk
HID: core: move the list of ignored devices in hid-quirks.c
HID:
usbhid has a list of dynamic quirks in addition to a list of static quirks.
There is not much USB specific in that, so move this part of the module
in core so we can have one central place for quirks.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- rebased on top of for-next (MCS_GAMEPADB
CC netfront maintainers.
On Mon, Nov 20, 2017 at 11:41:09AM +0100, Eduardo Otubo wrote:
> When unloading module xen_netfront from guest, dmesg would output
> warning messages like below:
>
> [ 105.236836] xen:grant_table: WARNING: g.e. 0x903 still in use!
> [ 105.236839] deferring g.e. 0x90
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
This would only cause trouble if the child node is missing while there
is an unrelated node named "backlight" elsewhere in the tree.
Fix
On 20/11/17 10:29, Ian Abbott wrote:
On 20/11/17 07:50, Jesse Chan wrote:
This change resolves a new compile-time warning
when built as a loadable module:
WARNING: modpost: missing MODULE_LICENSE() in
drivers/staging/comedi/drivers/ni_atmio.o
see include/linux/module.h for more information
T
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
To make things worse, the parent mfd node was also prematurely freed,
while the child backlight node was leaked.
Fixes: 47ec340cb8e2 ("m
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting at the parent rather than just matching
on its children.
To make things worse, the parent mfd node was also prematurely freed.
Fixes: 59eb2b5e57ea ("drivers/video/backlight/as3711_bl.c: add OF
A number of drivers have been using the wrong OF helper when doing child-node
lookups during probe. This meant that they were doing tree-wide searches rather
than matching on child nodes and that the parent node could end up being
prematurely freed.
Johan
v2
- add patch 4/4 which fixes two node
Two framebuffer device-node names were looked up during probe, but were
only used as flags to indicate the presence of two framebuffer device.
Drop the unused framebuffer name along with a likewise unused device
pointer from the driver data, and update the platform data to pass in
booleans instead
On 18/11/17 16:26, Matthew Giassa wrote:
Resolving license check warning for drivers/staging/comedi. Added the
license definitions present in the rest of the module and made sure it's
aligned with the license (GPL) in the comments for the affected file
(ni_atmio.c). Original warning:
WARNING: mo
Am Freitag, den 17.11.2017, 13:21 -0500 schrieb Alan Stern:
>
> The real fix would be to change the interface drivers by adding proper
> support for reset-resume. Otherwise there will always be a time window
> following resume during which the interface is non-functional.
Very hard to do with
On Mon, Nov 20, 2017 at 10:42:37AM +0100, Michal Hocko wrote:
> The patch has been dropped because allnoconfig failed to compile back
> then
> http://lkml.kernel.org/r/CAP=VYLr0rPWi1aeuk4w1On9CYRNmnEWwJgGtaX=wevgabur...@mail.gmail.com
> I have problem to find the follow up discussion though. The m
701 - 800 of 892 matches
Mail list logo
