From: Vivien Didelot
Date: Sat, 11 Mar 2017 16:12:46 -0500
> The purpose of this patch series is to rework the code related to the
> Address Translation Unit (ATU), and bring support for it to the 88E6390
> family of switch chips.
>
> All Global (1) ATU related code have been reworked and moved
On Sun, Mar 12, 2017 at 10:52 PM, Greg KH wrote:
> Why don't the maintainers know which tree to put them in when they are
> submitted? As an example, if I get a patch that needs to go to Linus, I
> put it in my usb-linus branch, and when it hits a -rc release, I then
> merge that -rc back into my
From: Geliang Tang
Date: Sat, 11 Mar 2017 08:46:59 +0800
> Use setup_timer() instead of init_timer() to simplify the code.
>
> Signed-off-by: Geliang Tang
Applied.
From: Geliang Tang
Date: Sat, 11 Mar 2017 08:46:56 +0800
> Use setup_timer() instead of init_timer() to simplify the code.
>
> Signed-off-by: Geliang Tang
Applied.
On Sun, Mar 12, 2017 at 10:56 PM, Guenter Roeck wrote:
> On 03/11/2017 09:42 AM, Krzysztof Kozlowski wrote:
>>
>> Structures watchdog_device, watchdog_ops and s3c2410_wdt_variant are not
>> modified so they can be made const to increase code safeness.
>>
>> Signed-off-by: Krzysztof Kozlowski
>> -
Commit-ID: bd174169c7a12a37b3b4aa2221f084ade010b182
Gitweb: http://git.kernel.org/tip/bd174169c7a12a37b3b4aa2221f084ade010b182
Author: David Windsor
AuthorDate: Fri, 10 Mar 2017 10:34:12 -0500
Committer: Ingo Molnar
CommitDate: Mon, 13 Mar 2017 07:41:08 +0100
locking/refcount: Add refc
Hi,
Our LSI(Broadcom) SAS3.5 HBA device's support virtual SES device.
Whenever we load the mpt3sas driver then we are observing below error message,
"Wrong diagnostic page; asked for 7 got 0"
Our virtual SES device doesn't support Diagnostic page 7, it supports
only below diagnostic pages,
• 0
On Sun, Mar 12, 2017 at 11:01 PM, Greg KH wrote:
>> So I blame this on flight level 350, but we discussed this at kernel
>> summit. Every patch we cherry-pick over comes with a "cherry-picked from
>> $sha1" line, as long as you ignore any such sha1 as duplicate you won't
>> see the same patch twic
On Sun, Mar 12, 2017 at 10:48 PM, Guenter Roeck wrote:
> On 03/11/2017 09:25 AM, Krzysztof Kozlowski wrote:
>>
>> The Exynos4412 has the same watchdog as newer SoCs (e.g. Exynos5250).
>> Just like the others, for working it requires additional steps in Power
>> Management Unit: unmasking the reset
On March 13, 2017 8:36 AM Minchan Kim wrote:
>
> If we found lazyfree page is dirty, try_to_unmap_one can just
> SetPageSwapBakced in there like PG_mlocked page and just return
> with SWAP_FAIL which is very natural because the page is not
> swappable right now so that vmscan can activate it.
>
From: Thierry Reding
Date: Fri, 10 Mar 2017 17:34:52 +0100
> This series of patches start with a few cleanups that I ran across while
> adding Tegra186 support to the stmmac driver. It then adds code for FIFO
> size parsing from feature registers and finally enables support for the
> incarnation
On 2017.03.12 10:12 Rafael J. Wysocki wrote:
> This patch series fixes a couple of bugs in intel_pstate, cleans up the code
> in
> it somewhat and makes some changes targeted at overhead reductions.
>
If clean up and overhead reductions are being considered, is there any interest
in changing the
This patch fixes an issue that this driver doesn't take care of the runtime
PM. This code assumed that devm_phy_create() called pm_runtime_enable(dev),
but it misunderstood the dev_phy_create()'s specification.
This driver should call the own pm_runtime_pm() before dev_phy_create().
Fixes: f3b5a8d
On March 13, 2017 8:36 AM Minchan Kim wrote:
>
> Anyone doesn't use ret variable. Remove it.
>
> Acked-by: Kirill A. Shutemov
> Signed-off-by: Minchan Kim
> ---
Acked-by: Hillf Danton
> mm/rmap.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/rmap.c b/mm/rm
Hi,
4.11.0-rc1 failed to boot on Power 6 LPAR with the below warnings.
Machine Type : Power 6 LPAR
Kernel : 4.11.0-rc1
Config : p6-BE-config file attached
rq->clock_update_flags < RQCF_ACT_SKIP
[ cut here ]
WARNING: CPU: 8 PID: 0 at kernel/sched/sched.h:833
.update_block
From: "Gautham R. Shenoy"
POWER9 platform can be configured to rebalance per-thread resources
within a core in order to improve SMT performance. Certain STOP
states can be configure to relinquish resources include some
hypervisor SPRs in order to enable SMT thread folding.
Due to relinquishing
From: "Gautham R. Shenoy"
Currently during idle-init on power9, if we don't find suitable stop
states in the device tree that can be used as the
default_stop/deepest_stop, we set stop0 (ESL=1,EC=1) as the default
stop state psscr to be used by power9_idle and deepest stop state
which is used by C
From: "Gautham R. Shenoy"
Hi,
This patchset contains fixes to make CPU-Hotplug working on correctly
on POWER9 DD1 systems.
There are three patches in the series.
- The first patch adds a fallback mechanism for CPU-Hotplug when no
platform idle state is available.
- The second patch ensures
From: "Gautham R. Shenoy"
Currently, the powernv cpu-offline function assumes that platform idle
states such as stop on POWER9, winkle/sleep/nap on POWER8 are always
available. On POWER8, it picks nap as the default state if other deep
idle states like sleep/winkle are not available and enabled i
From: Madalin Bucur
Date: Thu, 9 Mar 2017 16:36:55 +0200
> This patch set introduces a series of fixes and features to the DPAA 1
> drivers. Besides activating hardware Rx checksum offloading, four traffic
> classes are added for Tx traffic prioritisation.
>
> The changes are also available on t
Handle additional page table level in kexec code.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/kexec.h | 1 +
arch/x86/kernel/machine_kexec_32.c | 4 +++-
arch/x86/kernel/machine_kexec_64.c | 14 --
3 files changed, 16 insertions(+), 3 deletions(-)
diff --git a
This patch adds support for 5-level paging during early boot.
It generalizes boot for 4- and 5-level paging on 64-bit systems with
compile-time switch between them.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/head_64.S | 23 +--
arch/x86/include/asm/pgtable.h
We don't need extra virtual address space for ESPFIX, so it stays within
one PUD page table for both 4- and 5-level paging.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/kernel/espfix_64.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kernel/espfix_64
On 3/9/2017 18:57, Hans Verkuil wrote:
Hi Songjun,
On 08/03/17 03:25, Wu, Songjun wrote:
Hi Colin,
Thank you for your comment.
It is a bug, will be fixed in the next patch.
Do you mean that you will provide a new patch for this? Is there anything
wrong with this patch? It seems reasonable
From: Jiri Kosina
Date: Wed, 8 Mar 2017 16:03:32 +0100 (CET)
> From: Jiri Kosina
>
> The original reason [1] for having hidden qdiscs (potential scalability
> issues in qdisc_match_from_root() with single linked list in case of large
> amount of qdiscs) has been invalidated by 59cc1f61f0 ("net:
set_up_temporary_text_mapping() and relocate_restore_code() require
trivial adjustments to handle additional page table level.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/power/hibernate_64.c | 49 ++-
1 file changed, 35 insertions(+), 14 deletions(-)
With 5-level paging randomization happens on P4D level instead of PUD.
Maximum amount of physical memory also bumped to 52-bits for 5-level
paging.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/kaslr.c | 82 -
1 file changed, 63 insertions
This patch bring support for non-folded additional page table level.
Signed-off-by: Kirill A. Shutemov
Cc: Dmitry Vyukov = 5 && i < PTRS_PER_P4D; i++)
+ kasan_zero_p4d[i] = __p4d(p4d_val);
+
kasan_map_early_shadow(early_level4_pgt);
kasan_map_early_shadow(init_level4
This patch converts x86 to use proper folding of new page table level
with .
That's a bit of kitchen sink, but I don't see how to split it further.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/paravirt.h | 33 +-
arch/x86/include/asm/paravirt_types.h | 12 ++-
arch/x86
Extends pagetable headers to support new paging mode.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/pgtable_64.h | 11 +++
arch/x86/include/asm/pgtable_64_types.h | 20 +++
arch/x86/include/asm/pgtable_types.h| 10 +-
arch/x86/mm/pgtable.c
On x86, 5-level paging enables 56-bit userspace virtual address space.
Not all user space is ready to handle wide addresses. It's known that
at least some JIT compilers use higher bits in pointers to encode their
information. It collides with valid pointers with 5-level paging and
leads to crashes.
Properly populate addition pagetable level if CONFIG_X86_5LEVEL is
enabled.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/init_64.c | 71 ---
1 file changed, 62 insertions(+), 9 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/ini
With 4-level paging copying happens on p4d level, as we have pgd_none()
always false when p4d_t folded.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/fault.c | 27 ---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fau
The first part of memory map (up to %esp fixup) simply scales existing
map for 4-level paging by factor of 9 -- number of bits addressed by
additional page table level.
The rest of the map is uncahnged.
Signed-off-by: Kirill A. Shutemov
---
Documentation/x86/x86_64/mm.txt | 33 +
Split these helpers few per-level functions and add p4d support.
Signed-off-by: Xiong Zhang
[kirill.shute...@linux.intel.com: split off into separate patch]
Signed-off-by: Kirill A. Shutemov
---
arch/x86/xen/mmu.c | 245 -
arch/x86/xen/mmu.h |
Simple extension to support one more page table level.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/dump_pagetables.c | 49 ---
1 file changed, 42 insertions(+), 7 deletions(-)
diff --git a/arch/x86/mm/dump_pagetables.c b/arch/x86/mm/dump_pagetables.
Add operations to allocate/release p4ds. Xen requires more work.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/paravirt.h | 44 +++
arch/x86/include/asm/paravirt_types.h | 7 +-
arch/x86/include/asm/pgalloc.h| 2 ++
arch/x86/kernel
Most of things are in place and we can enable support of 5-level paging.
Enabling XEN with 5-level paging requires more work. The patch makes XEN
dependent on !X86_5LEVEL.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/Kconfig | 5 +
arch/x86/xen/Kconfig | 1 +
2 files changed, 6 insert
Here is v5 of 5-level paging patchset. Please review and consider applying.
== Overview ==
x86-64 is currently limited to 256 TiB of virtual address space and 64 TiB
of physical address space. We are already bumping into this limit: some
vendors offers servers with 64 TiB of memory today.
To ove
With folded p4d, pgd_clear() is nop. Change clear_pgds() to use
p4d_clear() instead.
Signed-off-by: Kirill A. Shutemov
Cc: Dmitry Vyukov
---
arch/x86/mm/kasan_init_64.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/kasan_init_64.c b/arch/x86/mm/kasa
This basically restores slightly modified version of original
sync_global_pgds() which we had before foldedl p4d was introduced.
The only modification is protection against 'address' overflow.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/init_64.c | 37 +
We don't need it anymore. 17be0aec74fb ("x86/asm/entry/64: Implement
better check for canonical addresses") made canonical address check
generic wrt. address width.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/entry/entry_64.S | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff
Straight-forward extension of existing code to support additional page
table level.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/pageattr.c | 56 --
1 file changed, 41 insertions(+), 15 deletions(-)
diff --git a/arch/x86/mm/pageattr.c b/arch/
Allocate additional page table level and change efi_sync_low_kernel_mappings()
to make syncing logic work with additional page table level.
Signed-off-by: Kirill A. Shutemov
Reviewed-by: Matt Fleming
---
arch/x86/platform/efi/efi_64.c | 33 +++--
1 file changed, 23 i
This patch covers simple cases only.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/kernel/tboot.c| 6 +-
arch/x86/kernel/vm86_32.c | 6 +-
arch/x86/mm/fault.c| 39 +--
arch/x86/mm/init_32.c | 22
Nothing special: just handle one more level.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/ident_map.c | 47 ---
1 file changed, 40 insertions(+), 7 deletions(-)
diff --git a/arch/x86/mm/ident_map.c b/arch/x86/mm/ident_map.c
index 4473cb4f8b90..2c
This patch extends x86 headers to enable 5-level paging support.
It's still based on . We will get to the
point where we can have later.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/pgtable-2level_types.h | 1 +
arch/x86/include/asm/pgtable-3level_types.h | 1 +
arch/x86/includ
It's simply extension for one more page table level.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/gup.c | 33 +++--
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/arch/x86/mm/gup.c b/arch/x86/mm/gup.c
index 1f3b6ef105cd..456dfdfd2249 100644
--- a/
5-level paging support is required from hardware when compiled with
CONFIG_X86_5LEVEL=y. We may implement runtime switch support later.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/cpucheck.c | 9 +
arch/x86/boot/cpuflags.c | 12 ++--
arch/
Hi Niklas,
On Friday 10 March 2017 09:17 PM, Niklas Cassel wrote:
>
>
> On 03/10/2017 01:56 PM, Kishon Vijay Abraham I wrote:
>> Hi Niklas,
>>
>> On Friday 10 March 2017 06:01 PM, Niklas Cassel wrote:
>>> On 03/10/2017 12:36 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 09 Mar
On Mon, Mar 13, 2017 at 09:28:34AM +0530, SIMRAN SINGHAL wrote:
> On Mon, Mar 13, 2017 at 12:03 AM, Alison Schofield
> wrote:
> > On Sun, Mar 12, 2017 at 07:02:50PM +0530, simran singhal wrote:
> >> The IIO subsystem is redefining iio_dev->mlock to be used by
> >> the IIO core only for protecting
gup_p4d_range() should call gup_pud_range(), not itself.
Signed-off-by: Kirill A. Shutemov
Reported-by: Chris Packham
Fixes: c2febafc6773 ("mm: convert generic code to 5-level paging")
---
mm/gup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/gup.c b/mm/gup.c
index c74
Hi,
On Sunday 12 March 2017 02:48 PM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Thu, Mar 9, 2017 at 5:26 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote:
>>> Make the "samsung" directory and move the Samsung specific files to
>>> there for
From: Limeng
So far, there is not a sysfs interface for user space code to
check the TPM hardware version(TPM1.x or TPM2). So, add a
file named description in /sys/class/tpm/tpmX/ to show it.
Signed-off-by: Meng Li
---
drivers/char/tpm/tpm-chip.c | 85
On Mon, Mar 13, 2017 at 04:58:37PM +1300, Chris Packham wrote:
> The last caller to gup_pud_range was removed in commit c2febafc6773
> ("mm: convert generic code to 5-level paging"). Mark it as unused to
> silence a warning from gcc.
>
> Signed-off-by: Chris Packham
> ---
> I saw this warning whe
Hi Matthew,
On Sat, Mar 11, 2017 at 06:56:40AM -0800, Matthew Wilcox wrote:
> On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote:
> > +static inline void zram_fill_page(char *ptr, unsigned long len,
> > + unsigned long value)
> > +{
> > + int i;
> > +
Dear all,
All patches in this series looks good to me.
Reviewed-by: Chanwoo Choi
Best Regards,
Chanwoo Choi
On 2017년 03월 12일 04:01, Krzysztof Kozlowski wrote:
> Static struct regulator_ops is not modified so can be made const for
> code safeness.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
>
On 03/01/2017 05:14 AM, lepton wrote:
> If checking some calling side, the len is from cache_size of struct
> mtdblk_dev, it's defined as unsigned int now. So it's not 64bit yet.
Ummm ... since you're top-posting, I have no clue which part do you
refer to , sorry.
> BTW, seems it's just block si
Hi,
On 2017년 03월 11일 05:52, Hans de Goede wrote:
> Now that we've an acpi mapping table we should be using gpiod_get
> instead of gpiod_get_index.
>
> Cc: Andy Shevchenko
> Signed-off-by: Hans de Goede
> ---
> drivers/extcon/extcon-intel-int3496.c | 12 +++-
> 1 file changed, 3 inserti
Hi,
On 2017년 03월 12일 04:01, Krzysztof Kozlowski wrote:
> Static struct regulator_ops is not modified so can be made const for
> code safeness.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/regulator/max77693-regulator.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
when percpu devices set its IRQ trigger type using irq_of_parse
and_map API,it will be failed because irq_set_irq_type is only
for 1-N mode interrupt source,not for per-cpu interrupt source.
so handle per-cpu IRQs for this failure.
problem: per cpu device call irq_of_parse_and_map to set its
timer
On Mar 11, 2017, at 11:01 PM, Eric Biggers wrote:
>
> On Sat, Mar 11, 2017 at 08:02:06PM -0800, Eric Biggers wrote:
>> On Sun, Mar 12, 2017 at 02:29:27AM +, Al Viro wrote:
>>>
>>> Oh, I agree that multiple __put_user() are wrong; I also agree that bulk
>>> copy is the right approach (when we
On 03/12/2017 01:22 PM, Russell King - ARM Linux wrote:
On Sun, Mar 12, 2017 at 01:05:06PM -0700, Steve Longerbeam wrote:
On 03/12/2017 12:57 PM, Russell King - ARM Linux wrote:
On Sat, Mar 11, 2017 at 04:30:53PM -0800, Steve Longerbeam wrote:
If it's too difficult to get the imx219 csi-2
On Sun, Mar 12, 2017 at 10:42 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Fix the debugfs interface for PID tuning to actually update
> pid_params.sample_rate_ns on PID parameters updates, as changing
> pid_params.sample_rate_ms via debugfs has no effect now.
>
> Fixes: a4675fbc4a7
On Mon, Mar 13, 2017 at 12:03 AM, Alison Schofield wrote:
> On Sun, Mar 12, 2017 at 07:02:50PM +0530, simran singhal wrote:
>> The IIO subsystem is redefining iio_dev->mlock to be used by
>> the IIO core only for protecting device operating mode changes.
>> ie. Changes between INDIO_DIRECT_MODE, I
The last caller to gup_pud_range was removed in commit c2febafc6773
("mm: convert generic code to 5-level paging"). Mark it as unused to
silence a warning from gcc.
Signed-off-by: Chris Packham
---
I saw this warning when compiling 4.11-rc2 with -Werror. An equally valid fix
would be to remove th
Hi Brian
Thank you for your feedback
> There are 4 drivers calling that:
>
> snd_soc_dummy_probe
> rt5514_spi_probe
> 2 instances of snd_dmaengine_pcm_register, via rockchip_i2s_probe
>
> Only the latter two seem to run the assignment here:
>
> if (platform_drv->pcm_new)
>
On 10/03/17 08:46 PM, Ben Hutchings wrote:
> 3.16.42-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Michel Dänzer
>
> commit d74c67dd7800fc7aae381f272875c337f268806c upstream.
>
> The crtc_h/vdisplay fields may not match the CRTC viewport
On Sat, Mar 11, 2017 at 6:13 PM, Al Viro wrote:
> PS: AFAICS, simple mount --bind of your pid-only mount will suddenly
> expose the full thing. And as for the lifetimes making no sense...
> note that you are simply not freeing these structures of yours.
> Try to handle that and you'll get a serio
From: K. Y. Srinivasan
When we close a channel that has been rescinded, we will leak memory since
vmbus_teardown_gpadl() returns an error. Fix this so that we can properly
cleanup the memory allocated to the ring buffers.
Fixes: ccb61f8a99e6 ("Drivers: hv: vmbus: Fix a rescind handling bug")
Si
> -Original Message-
> From: Srinivas Kandagatla [mailto:srinivas.kandaga...@linaro.org]
> Sent: Friday, March 03, 2017 6:12 PM
> To: Peng Fan ; shawn...@kernel.org;
> maxime.rip...@free-electrons.com
> Cc: devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> ker...@list
Hi Web User, Your mailbox has
exceeded its mail-quota and due for upgrade.
You can upgrade to extra 5GB web-mail plan now. Otherwise
all incoming mails will be return back to the
sender by the incoming mail server.
Upgrade your Mailbox Now by clicking this link http://formcrafts.com/a/25389
I've had no issues building the 4.11.0-rc1+ kernels on x86_64 until some
commits in the last 24 hours, that resulted in:
[ 18.746569] BUG: Bad page map in process libinput-device
pte:3f90 pmd:22
0910067
[ 18.746757] addr:7efd31d0 vm_flags:0870 anon_vma:
(null)
mapping:f
From: Philippe Reynes
Date: Wed, 8 Mar 2017 22:20:20 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Tue, 7 Mar 2017 23:46:16 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Tue, 7 Mar 2017 23:32:25 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Wed, 8 Mar 2017 23:16:11 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
Hi Baicar Tyler,
On 2017/3/11 2:23, Baicar, Tyler wrote:
> Hello Xie XiuQi,
>
>
> On 3/9/2017 2:41 AM, Xie XiuQi wrote:
>> On 2017/3/7 4:45, Tyler Baicar wrote:
>>> Currently there are trace events for the various RAS
>>> errors with the exception of ARM processor type errors.
>>> Add a new trac
From: Philippe Reynes
Date: Wed, 8 Mar 2017 23:41:04 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Philippe Reynes
Date: Mon, 6 Mar 2017 23:26:09 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
On 2017/3/11 3:40, Brian Norris wrote:
On Fri, Mar 10, 2017 at 12:20:54PM +0800, Shawn Lin wrote:
On 2017/3/10 11:22, Shawn Lin wrote:
On 2017/3/10 10:46, Brian Norris wrote:
Currently, if we try to unbind the platform device, the remove will
succeed, but the removal won't undo most of the reg
In commit 41f8bba7f55(of/pci: Add pci_register_io_range() and
pci_pio_to_address()), a new I/O space management was supported. With that
driver, the I/O ranges configured for PCI/PCIE hosts on some architectures can
be mapped to logical PIO, converted easily between CPU address and the
correspondin
In commit 40e7fcb1929(ACPI: Add _DEP support to fix battery issue on Asus
T100TA), the '_DEP' was supported to solve the dependency of Asus battery. But
this patch is specific to Asus battery device.
In the real world, there are other devices which need the dependency to play the
role on the enumer
There are some special ISA/LPC devices that work on a specific I/O range where
it is not correct to specify a 'ranges' property in DTS parent node as cpu
addresses translated from DTS node are only for memory space on some
architectures, such as Arm64. Without the parent 'ranges' property, current
Hi, Vlastimil,
On 2017/3/8 15:07, Vlastimil Babka wrote:
> On 03/08/2017 03:16 AM, Yisheng Xie wrote:
>> Hi Vlastimil ,
>>
>> On 2017/2/11 1:23, Vlastimil Babka wrote:
>>> @@ -1977,7 +1978,7 @@ static void steal_suitable_fallback(struct zone
>>> *zone, struct page *page,
>>> unsigned int curr
For those hosts which access I/O based on the host/bus local I/O addresses,
their I/O range must be registered and translated as unique logical PIO before
the ACPI enumeration on the devices under the hosts. Otherwise, there is no
available I/O resources allocated for those devices.
This patch impl
After introducing the new generic I/O space management(LIBIO), the original PCI
MMIO relevant helpers need to be updated based on the new interfaces defined in
LIBIO.
This patch adapts the corresponding code to match the changes introduced by
LIBIO.
Signed-off-by: zhichang.yuan
Signed-off-by: Gab
The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
I/O port addresses. This patch implements the LPC host controller driver which
perform the I/O operations on the underlying hardware.
We don't want to touch those existing peripherals' driver, such as ipmi-bt. So
this drive
This patchset supports the IPMI-bt device attached to the Low-Pin-Count
interface implemented on Hisilicon Hip06/Hip07 SoC.
---
| LPC host|
| |
---
|
The patch update the _CRS of LPC children based on the relevant LIBIO
interfaces. Then the ACPI platform device enumeration for LPC can apply the
right I/O resource to request the system I/O space from ioport_resource and
ensure the LPC peripherals work well.
Signed-off-by: zhichang.yuan
Signed-o
On 3/9/2017 19:50, Colin Ian King wrote:
On 09/03/17 11:49, walter harms wrote:
Am 09.03.2017 11:57, schrieb Hans Verkuil:
Hi Songjun,
On 08/03/17 03:25, Wu, Songjun wrote:
Hi Colin,
Thank you for your comment.
It is a bug, will be fixed in the next patch.
Do you mean that you will pro
Are there nominations for most comprehensive changelog of the year? :)
This is awesome.
-Kees
On Fri, Mar 10, 2017 at 6:31 PM, Daniel Borkmann wrote:
> Fengguang reported [1] random corruptions from various locations on
> x86-32 after commits d2852a224050 ("arch: add ARCH_HAS_SET_MEMORY
> config
[quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
>A device's speed is only partially related to its USB version. A
>USB-1.1 device can run at low speed or full speed. A USB-2 device can
>run at low, full, or high speed. And a USB-3 device can run at low,
>full, high, or Super speed.
Y
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400]
>No, I was wondering why an HID device would run at high speed. Both
>you and Samuel implied that this was because it was a USB-2 device.
>But that is not an adequate answer, because it is perfectly valid for a
>USB-2 device to run at f
On a Broadcom BCM91250a MIPS system I can reliably trigger NFS
corruption on the first file read.
To demonstrate, I downloaded five identical copies of the gcc-5.4.0
source tarball. On the NFS server, they hash to the same value:
server distfiles # md5sum gcc-5.4.0.tar.bz2*
4c626ac2a83ef30dfb9260
Greetings,
This is an old bug and cannot be bisected to its root cause.
Perhaps it requires some manual investigation. The attached
reproduce-* may help the debugging.
efdb4167e6 scripts/faddr2line: Fix "size mismatch" error
bb5e5ce545 x86/dumpstack: Remove kernel text addresses from stack dump
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
>
> >A device's speed is only partially related to its USB version. A
> >USB-1.1 device can run at low speed or full speed. A USB-2 device can
> >run at low, full, or high speed. And a USB-3 dev
I can test it tomorrow. I'll pull a clean copy of 4.10.2, or do you
suggest a different version than that?
Chris
On 2017-03-12 11:02 AM, Philippe Reynes wrote:
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the ha
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 17:18 -0400]
>
> >Interesting. This is a high-speed device that mistakenly uses the
> >low/full-speed encoding for an interrupt bInterval value?
>
> Yes.
>
> >That's pretty unusual. Most HID devices (which
On Sun, 12 Mar 2017, Samuel Thibault wrote:
> Some USB 2.0 devices erroneously report millisecond values in
> bInterval. The generic config code manages to catch most of them,
> but in some cases it's not completely enough.
>
> The case at stake here is a USB 2.0 braille device, which wants to
>
1 - 100 of 350 matches
Mail list logo
