On Wed, Oct 04, 2017 at 10:46:56PM +0530, Srishti Sharma wrote:
> drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
> b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
> index
On 10/05/2017 01:00 PM, David Howells wrote:
Lockdown is typically enabled during boot and may be terminated, if configured,
by typing a special key combination on a directly attached physical keyboard.
Does this include a Bluetooth keyboard (which might not actually exist
and might in reality
On Wed, Oct 04, 2017 at 03:34:55PM +0200, Arnd Bergmann wrote:
> Replaces upstream commit 0b2e9e7947e7 ("media: staging/imx: remove
> confusing IS_ERR_OR_NULL usage")
>
> We get a harmless warning about a potential uninitialized variable
> use in the driver:
>
> drivers/staging/media/imx/imx-medi
On Thu, Oct 05, 2017 at 02:06:49PM +0200, Michal Hocko wrote:
> On Wed 04-10-17 16:46:36, Roman Gushchin wrote:
> > The cgroup-aware OOM killer treats leaf memory cgroups as memory
> > consumption entities and performs the victim selection by comparing
> > them based on their memory footprint. Then
Commit-ID: 262e681183ddcdb24d64a2f993e41a226adcec29
Gitweb: https://git.kernel.org/tip/262e681183ddcdb24d64a2f993e41a226adcec29
Author: Borislav Petkov
AuthorDate: Mon, 2 Oct 2017 11:28:36 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 14:23:06 +0200
x86/mce: Hide mca_cfg
Commit-ID: 69a330007091ea8a801dd9fcd897ec52f9529586
Gitweb: https://git.kernel.org/tip/69a330007091ea8a801dd9fcd897ec52f9529586
Author: Nicolas Iooss
AuthorDate: Mon, 2 Oct 2017 11:28:35 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 14:23:06 +0200
RAS/CEC: Use the right
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> > diff --git a/arch/powerpc/kernel/membarrier.c
> > b/arch/powerpc/kernel/membarrier.c
> > new file mode 100644
> > index ..b0d79a5f5981
> > --- /dev/nu
Hi Arnd,
On Thu, Oct 5, 2017 at 2:09 PM, Arnd Bergmann wrote:
> A bugfix for the SMP case broke the build for the UP case:
>
> arch/arm/mach-shmobile/headsmp-apmu.o: In function `shmobile_boot_apmu':
> (.text+0x34): undefined reference to `secondary_startup'
>
> The assembler file mixes code that
Use vma_pages function on vma object instead of explicit computation.
This is a clean up patch.
A version of this is already queued for -next here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/core&id=b4f4a2755665bf847231050b569f587ce0945482
Ah.
On Thu, Oct 05, 2017 at 02:11:17PM +0200, Arnd Bergmann wrote:
> This adds a hard Kconfig dependency on HWSPINLOCK, which is the
> simplest solution since we don't care about building for the case
> without HWSPINLOCK.
Given that there are stubs for HWSPINLOCK it'd be good to also have an
|| COMP
On 10/05/2017 07:23 AM, Nicholas Piggin wrote:
On Wed, 4 Oct 2017 14:37:53 -0700
"Paul E. McKenney" wrote:
From: Mathieu Desnoyers
Provide a new command allowing processes to register their intent to use
the private expedited command.
This allows PowerPC to skip the full memory barrier i
On 05/10/17 13:16, Allen Pais wrote:
> Use vma_pages function on vma object instead of explicit computation.
> This is a clean up patch.
A version of this is already queued for -next here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/core&id=b4f4a2755665b
On Thu, 2017-10-05 at 14:05 +0200, Arnd Bergmann wrote:
> gcc produces a harmless warning about a recently introduced
> signed integer overflow:
>
> drivers/net/wireless/rsi/rsi_91x_hal.c: In function 'rsi_prepare_mgmt_desc':
> include/uapi/linux/swab.h:13:15: error: integer overflow in expression
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG N
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG
Quoting Arnd Bergmann (2017-10-05 13:07:22)
> An earlier bugfix tried to work around this build failure:
>
> drivers/gpu/drm/i915/selftests/mock_gem_device.c: In function
> 'mock_gem_device':
> drivers/gpu/drm/i915/selftests/mock_gem_device.c:151:20: error: 'struct
> dev_archdata' has no member
Use vma_pages function on vma object instead of explicit computation.
This is a clean up patch.
Signed-off-by: Allen Pais
---
arch/arm64/mm/dma-mapping.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c
index 614a
On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> diff --git a/arch/powerpc/kernel/membarrier.c
> b/arch/powerpc/kernel/membarrier.c
> new file mode 100644
> index ..b0d79a5f5981
> --- /dev/null
> +++ b/arch/powerpc/kernel/membarrier.c
> @@ -0,0 +1,45 @@
> +void memb
The ARM allmodconfig build fails in linux-next, since one
clk interface was accidentally never exported but is now
used by an mmc driver:
ERROR: "clk_bulk_prepare" [drivers/mmc/host/sdhci-msm.ko] undefined!
This exports it as well.
Fixes: d8034e3379a8 ("mmc: sdhci-msm: Utilize bulk clock API")
F
With CONFIG_HWSPINLOCK=m, the new driver fails to link as a built-in driver:
drivers/spi/spi-sprd-adi.o: In function `sprd_adi_remove':
spi-sprd-adi.c:(.text+0x18): undefined reference to `hwspin_lock_free'
drivers/spi/spi-sprd-adi.o: In function `sprd_adi_probe':
spi-sprd-adi.c:(.text+0xfc): unde
The new driver fails to build when CONFIG_PINCTRL is disabled:
drivers/gpu/drm/rockchip/rockchip_lvds.c: In function
'rockchip_lvds_grf_config':
drivers/gpu/drm/rockchip/rockchip_lvds.c:229:39: error: dereferencing pointer
to incomplete type 'struct dev_pin_info'
if (lvds->pins && !IS_ERR(lvd
A bugfix for the SMP case broke the build for the UP case:
arch/arm/mach-shmobile/headsmp-apmu.o: In function `shmobile_boot_apmu':
(.text+0x34): undefined reference to `secondary_startup'
The assembler file mixes code that is used for SMP with code
that we also need on a single-CPU build, so I'm
One of the recent changes introduced a warning about
undefined behavior in the sanity checking:
drivers/gpu/drm/i915/intel_ddi.c: In function 'intel_ddi_hdmi_level':
drivers/gpu/drm/i915/intel_ddi.c:654:6: error: 'n_hdmi_entries' may be used
uninitialized in this function [-Werror=maybe-uninitial
An earlier bugfix tried to work around this build failure:
drivers/gpu/drm/i915/selftests/mock_gem_device.c: In function 'mock_gem_device':
drivers/gpu/drm/i915/selftests/mock_gem_device.c:151:20: error: 'struct
dev_archdata' has no member named 'iommu'
Checking for CONFIG_IOMMU_API is not suffi
> Anything with bytes 1-31,127 will get -EACCES.
You're making a mistake of catering to Unix shells which are pure garbage
as programming languages instead of fixing them or switching to saner
alternatives and then "fixing" kernel to sort-of workaround Unix shells
deficiencies.
Formally, you patc
The new backlight code causes a link failure when backlight
support itself is disabled:
drivers/gpu/drm/omapdrm/displays/panel-dpi.o: In function `panel_dpi_probe_of':
panel-dpi.c:(.text+0x35c): undefined reference to `of_find_backlight_by_node'
This adds a Kconfig dependency like we have for the
On Wed 04-10-17 16:46:36, Roman Gushchin wrote:
> The cgroup-aware OOM killer treats leaf memory cgroups as memory
> consumption entities and performs the victim selection by comparing
> them based on their memory footprint. Then it kills the biggest task
> inside the selected memory cgroup.
>
> B
gcc produces a harmless warning about a recently introduced
signed integer overflow:
drivers/net/wireless/rsi/rsi_91x_hal.c: In function 'rsi_prepare_mgmt_desc':
include/uapi/linux/swab.h:13:15: error: integer overflow in expression
[-Werror=overflow]
(((__u16)(x) & (__u16)0x00ffU) << 8) | \
Kconfig currently doesn't handle 'm' appearing in a Kconfig file before
the modules symbol is defined (the symbol with 'option modules'). The
problem is the following code, which runs during parsing:
/* change 'm' into 'm' && MODULES */
if (e->left.sym == &symbol_mod)
menu_finalize() is one of the more opaque parts of Kconfig, and I need
to make some changes to it to fix an issue related to modules. Add some
comments related to expression rewriting and dependency propagation as a
review aid. They will also help other people trying to understand the
code.
Signed
More directly describes the only thing it does.
Signed-off-by: Ulf Magnusson
---
scripts/kconfig/menu.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index e935793..8354dfa 100644
--- a/scripts/kconfig/menu.c
Hello,
This patchset fixes a segfault that occurs if 'm' appears in certain
expressions before the modules symbol is defined. The problem is that m is
rewritten to m && already during parsing. Doing it in
menu_finalize(), which runs after parsing, fixes the problem.
To aid the review and people
From: Colin Ian King
Functions ahc_devlimited_syncrate and ahc_linux_initialize_scsi_bus
are declared static in their prototypes but are missing in their
definitions, so add the missing static.
Cleans up sparse warnings:
symbol 'ahc_devlimited_syncrate' was not declared. Should it be static?
sym
...instead of keeping pointer to struct pci_dev.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 51
1 file changed, 25 insertions(+), 26 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
Hi,
On Wednesday, October 04, 2017 07:23:07 PM Hunter, Adrian wrote:
> > -Original Message-
> > From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> > Sent: Wednesday, October 4, 2017 12:40 PM
> > To: Linus Walleij
> > Cc: Hunter, Adrian ; Ulf Hansson
> > ; linux-mmc ; lin
There are fields in the struct ips_mcp_limits which are not used
anywhere and a label which we may get rid of.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers
On Wed, Oct 4, 2017 at 4:47 PM, Sudeep Holla wrote:
> On 04/10/17 15:17, Arnd Bergmann wrote:
>> On Wed, Oct 4, 2017 at 3:53 PM, Sudeep Holla wrote:
>>> On 04/10/17 13:35, Arnd Bergmann wrote:
On Wed, Oct 4, 2017 at 1:07 PM, Sudeep Holla wrote:
>> There are probably several ways of doing t
The routine is named incorrectly since the first attempt as there is
nothing like a put_opp() helper. We wanted to unregister the set_opp()
helper here and so it should rather be named as
dev_pm_opp_unregister_set_opp_helper().
Signed-off-by: Viresh Kumar
---
drivers/opp/core.c | 6 +++---
i
This patch removes the FSF address from the GPL notice to fix a
checkpatch.pl CHECK message.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 4
drivers/platform/x86/intel_ips.h | 4
2 files changed, 8 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/d
Use devm_ and pcim_ functions to make error handling
simpler and code smaller and tidier.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 62 ++--
1 file changed, 15 insertions(+), 47 deletions(-)
diff --git a/drivers/platform/x86/intel_
This makes code cleaner.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
index 063d9a1624b4..6f6900065bc2 100644
--- a/d
Intel vendor ID is defined globally, thus we may use PCI_VDEVICE().
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
index 6f6900065bc2..48
On Thu, 2017-10-05 at 13:22 +0200, Linus Walleij wrote:
> On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
>
> > Offset on meson pinctrl and gpios is something that was carried from the
> > vendor driver, where there is a weird link between the 2
> > controllers. Since these 2 controllers ar
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> GPIOX_22 is declared as a gpio but the id is no present in the pin
> table. This hole trigger an error while reading the pingroup debugfs entry
>
> GPIOX_22 is no routed externally. For all we know, it could an internal
> pin of SoC
>
> Sign
find_idlest_group returns NULL when the local group is idlest. The
caller then continues the find_idlest_group search at a lower level
of the current CPU's sched_domain hierarchy. find_idlest_group_cpu is
not consulted and, crucially, @new_cpu is not updated. This means the
search is pointless and
On Thu, Oct 05, 2017 at 01:12:30PM +0200, Michal Hocko wrote:
> On Thu 05-10-17 11:27:07, Roman Gushchin wrote:
> > On Wed, Oct 04, 2017 at 02:24:26PM -0700, Shakeel Butt wrote:
> [...]
> > > Sorry about the confusion. There are two things. First, should we do a
> > > css_get on the newly selected
When p is allowed on none of the CPUs in the sched_domain, we
currently return NULL from find_idlest_group, and pointlessly
continue the search on lower sched_domain levels (where p is also not
allowed) before returning prev_cpu regardless (as we have not updated
new_cpu).
Add an explicit check fo
This patchset optimises away an unused comparison, and fixes some corner cases
in
the find_idlest_group path of select_task_rq_fair.
Changes v2 -> v3:
- 1/5 through 4/5 unchanged.
- 5/5: Essentially undid [1]. Vincent pointed out that this isn't really a
bugfix but more of a change in poli
In preparation for changes that would otherwise require adding a new
level of indentation to the while(sd) loop, create a new function
find_idlest_cpu which contains this loop, and rename the existing
find_idlest_cpu to find_idlest_group_cpu.
Code inside the while(sd) loop is unchanged. @new_cpu i
Since commit 83a0a96a5f26 ("sched/fair: Leverage the idle state info
when choosing the "idlest" cpu") find_idlest_grou_cpu (formerly
find_idlest_cpu) no longer returns -1.
Signed-off-by: Brendan Jackman
Cc: Dietmar Eggemann
Cc: Vincent Guittot
Cc: Josef Bacik
Cc: Ingo Molnar
Cc: Morten Rasmus
When the local group is not allowed we do not modify this_*_load from
their initial value of 0. That means that the load checks at the end
of find_idlest_group cause us to incorrectly return NULL. Fixing the
initial values to ULONG_MAX means we will instead return the idlest
remote group in that ca
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> On meson-gx platforms, TEST_N has been incorrectly declared in the EE
> controller while it belongs to AO controller.
>
> Move the pin to the appropriate controller
>
> Signed-off-by: Jerome Brunet
Patch applied.
Yours,
Linus Walleij
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> pin_base was used with the manually set pin offset in meson pinctrl. This
> is no longer the case, pin_base is 0 on every meson pinctrl controllers
> and should go away.
>
> Tested-by: Martin Blumenstingl
> Signed-off-by: Jerome Brunet
Pa
On Thu, 2017-10-05 at 12:21 +0530, Viresh Kumar wrote:
> Hi Joe,
Hi Viresh.
> Recently I was Cc'd for some of the patches from Manu, as
> get_maintainers incorrectly mentioned me.
>
> Apart from the fact that I never contributed to the mentioned
> file (drivers/phy/qualcomm/phy-qcom-qmp.c), the
On Wed 04-10-17 16:46:35, Roman Gushchin wrote:
> Traditionally, the OOM killer is operating on a process level.
> Under oom conditions, it finds a process with the highest oom score
> and kills it.
>
> This behavior doesn't suit well the system with many running
> containers:
>
> 1) There is no
hv_do_hypercall() does virt_to_phys() translation and with some configs
(CONFIG_SLAB) this doesn't work for percpu areas, we pass wrong memory to
hypervisor and get #GP. We could use working slow_virt_to_phys() instead
but doing so kills the performance.
Move pcpu_flush/pcpu_flush_ex structures ou
Hi Steve,
On Wed, 2017-10-04 at 13:14 -0400, Steven Rostedt wrote:
> On Fri, 22 Sep 2017 14:59:43 -0500
> Tom Zanussi wrote:
>
> > + /*
> > +* New timestamps may not be consistent with the previous setting.
> > +* Reset the buffer so that it doesn't have incomparable timestamps.
>
> I
From: Miles Chen
Current flow guarantees a valid pointer when handling
the __GFP_ZERO case. So remove the unnecessary NULL pointer
check.
Signed-off-by: Miles Chen
---
mm/slob.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/slob.c b/mm/slob.c
index a8bd6fa..a72649c 100
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> Tested-by: Martin Blumenstingl
> Signed-off-by: Jerome Brunet
Patch applied.
Linus Walleij
I get these warnings:
../arch/powerpc/boot/mpsc.c: In function 'mpsc_get_virtreg_of_phandle':
../arch/powerpc/boot/mpsc.c:113:35: warning: cast from pointer to
integer of different size [-Wpointer-to-int-cast]
../arch/powerpc/boot/mpsc.c: In function 'mpsc_console_init':
../arch/powerpc/boot/mpsc
Fix checkpatch issues: "CHECK: Alignment should match open parenthesis"
Signed-off-by: Srinivasan Shanmugam
---
drivers/staging/rtl8723bs/core/rtw_recv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c
b/drivers/staging/rtl8723bs/cor
Commit-ID: 3916a4135c696fa226a1abe6d6a0ff7f5edd9a7c
Gitweb: https://git.kernel.org/tip/3916a4135c696fa226a1abe6d6a0ff7f5edd9a7c
Author: Jithu Joseph
AuthorDate: Wed, 4 Oct 2017 15:48:57 -0700
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 13:20:32 +0200
x86/intel_rdt: Remove re
Commit-ID: 5fd88b60e11b7d81b2c944c1b45834c4a6aa0157
Gitweb: https://git.kernel.org/tip/5fd88b60e11b7d81b2c944c1b45834c4a6aa0157
Author: Colin Ian King
AuthorDate: Mon, 2 Oct 2017 15:59:31 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 13:20:32 +0200
x86/intel_rdt/cqm: Mak
On 05/10/17 12:20, Arnd Bergmann wrote:
> On Wed, Oct 4, 2017 at 5:01 PM, Sudeep Holla wrote:
+
+static struct platform_driver scmi_cpufreq_platdrv = {
+ .driver = {
+ .name = "scmi-cpufreq",
+ },
+ .probe = scmi_cpufreq_pr
On Thu, Sep 21, 2017 at 08:24:27AM +0200, Thomas Meyer wrote:
> Make sure (of/i2c/platform)_device_id tables are NULL terminated.
> Found by coccinelle spatch "misc/of_table.cocci"
>
> Signed-off-by: Thomas Meyer
Applied to for-current, thanks! But please use descriptive subjects, I
cahanged it
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> Tested-by: Martin Blumenstingl
> Signed-off-by: Jerome Brunet
Patch applied.
Yours,
Linus Walleij
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> Signed-off-by: Jerome Brunet
Patch applied.
Yours,
Linus Walleij
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> Signed-off-by: Jerome Brunet
Patch applied.
Yours,
Linus Walleij
From: Markus Elfring
Date: Thu, 5 Oct 2017 13:16:51 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
arch/powerpc/kvm/book3s_64_mmu_hv.c | 1 -
1 file changed, 1 deletion(-
On Thu, Sep 21, 2017 at 09:37:43AM +0200, Ricardo Ribalda Delgado wrote:
> SMBUS_BLOCK_DATA transactions might fail due to a race condition with
> the IMC, even when the IMC semaphore is used.
>
> This bug has been reported and confirmed by AMD, who suggested as a
> solution an IMC firmware upgrad
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> Offset on meson pinctrl and gpios is something that was carried from the
> vendor driver, where there is a weird link between the 2
> controllers. Since these 2 controllers are independent, this offset adds
> an unnecessary complexity.
>
> T
On Wed, Oct 4, 2017 at 5:01 PM, Sudeep Holla wrote:
>>> +
>>> +static struct platform_driver scmi_cpufreq_platdrv = {
>>> + .driver = {
>>> + .name = "scmi-cpufreq",
>>> + },
>>> + .probe = scmi_cpufreq_probe,
>>> + .remove = scmi_cpufreq_re
On Tue, Oct 3, 2017 at 8:26 PM, Grygorii Strashko
wrote:
> On 10/02/2017 02:55 AM, Linus Walleij wrote:
>> On Thu, Sep 28, 2017 at 4:22 PM, Grygorii Strashko
>> wrote:
>>
>>> Sry, but I do not agree with this series.
>>> - no prof that it can be re-used by other drivers than tegra
>>> (at least
On Thu, Sep 21, 2017 at 03:30:09PM +0200, Pierre-Yves MORDRET wrote:
> I2C drive setup structure is not properly allocated.
> Make it static instead of pointer to store driver data.
>
> Signed-off-by: Pierre-Yves MORDRET
Ouch! How did it work before?
Applied to for-current, thanks! Please provi
On Mon, Oct 2, 2017 at 9:55 AM, Linus Walleij wrote:
> This is not necessarily a blocker if it can be shown that others than
> TI/OMAP can reuse it.
>
> I've looked at things like the imagination pistachio:
>
> pinctrl@18101C00 {
> compatible = "img,pistachio-system-pinctrl";
> re
On Wed 04-10-17 16:31:38, Johannes Weiner wrote:
> On Wed, Oct 04, 2017 at 01:17:14PM -0700, David Rientjes wrote:
> > On Wed, 4 Oct 2017, Roman Gushchin wrote:
> >
> > > > > @@ -828,6 +828,12 @@ static void __oom_kill_process(struct
> > > > > task_struct *victim)
> > > > > struct mm_struct
On Thu 05-10-17 11:27:07, Roman Gushchin wrote:
> On Wed, Oct 04, 2017 at 02:24:26PM -0700, Shakeel Butt wrote:
[...]
> > Sorry about the confusion. There are two things. First, should we do a
> > css_get on the newly selected memcg within the for loop when we still
> > have a reference to it?
>
>
On 5 October 2017 at 12:55, Bartlomiej Zolnierkiewicz
wrote:
> On Wednesday, October 04, 2017 11:48:27 AM Ulf Hansson wrote:
>> [...]
>>
>> >> MQ code that doesn't perform and therefore we cannot switch seamlessly
>> >> to MQ.
>> >
>> > I think that switching seamlessly to blk-mq in short/medium-t
On 22.09.2017 21:37, Hans de Goede wrote:
The Intel cherrytrail xhci controller has an extended cap mmio-range
which contains registers to control the muxing to the xhci (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a mux driver included in the xhci code (o
On Fri, Sep 22, 2017 at 11:33 PM, Hoan Tran wrote:
> This patch adds maintainer for Synopsys DesignWare APB GPIO driver.
>
> Signed-off-by: Hoan Tran
Patch applied.
I added an F: entry for the DT bindings as well.
Thank you for taking on this driver!
Yours,
Linus Walleij
On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote:
> Hi Wolfram,
>
> On ven., sept. 29 2017, Kalyan Kinthada
> wrote:
>
> > This commit modifies the documentation for
> > "marvell,mv78230-a0-i2c" compatible string.
> >
> > The "marvell,mv78230-a0-i2c" compatible string enables t
On Wed, Oct 04, 2017 at 05:16:31PM -0700, John Stultz wrote:
> On Wed, Oct 4, 2017 at 9:11 AM, Gabriel Beddingfield
> wrote:
> > We found that the problem is an interaction between the NTP code and
> > what I call the "delta_delta hack." (see [1] and [2]) This code
> > allocates a static variable
On Thu, 2017-10-05 at 12:00 +0100, David Howells wrote:
>
> Only validly signed wifi databases may be use.
We don't even have this yet, and when we do, we want this to be the
case for typical configurations regardless of lockdown.
johannes
On Thu, 05 Oct 2017, Jan Kara wrote:
OK, this makes sense but do you have any particular user in mind? In
particular I'm not sure how big advantage this API brings over an existing
one in include/linux/list_bl.h. Sure it's a tradeoff between bitlock /
spinlock but is there a user where it matter
On Wed, 4 Oct 2017, John Stultz wrote:
> On Wed, Oct 4, 2017 at 9:11 AM, Gabriel Beddingfield
> wrote:
> > TL;DR: the "delta_delta" hack[1 and 2] in kernel/time/timekeeping.c
> > and drivers/rtc/class.c undermines the NTP system. It's not
> > appropriate to use if sub-second precision is availabl
Josh Poimboeuf wrote:
> On Wed, Oct 04, 2017 at 06:44:50AM +0900, Tetsuo Handa wrote:
> > Josh Poimboeuf wrote:
> > > On Tue, Oct 03, 2017 at 11:28:15AM -0500, Josh Poimboeuf wrote:
> > > > There are two bugs:
> > > >
> > > > 1) Somebody -- presumably lockdep -- is corrupting the stack. Need the
On Tue, Sep 26, 2017 at 06:56:30PM -0700, Palmer Dabbelt wrote:
> +/*
> + * This is particularly ugly: it appears we can't actually get the definition
> + * of task_struct here, but we need access to the CPU this task is running
> on.
> + * Instead of using C we're using asm-offsets.h to get the c
On Wed, 4 Oct 2017, Gabriel Beddingfield wrote:
> On Wed, Oct 4, 2017 at 11:22 AM, Thomas Gleixner wrote:
> Long story short: you can't always have your low-power clock be your
> monotonic/sched clock.
sched_clock and the clocksource for timekeeping, which feeds monotonic are
not required to be t
Hi Ard, Michael,
Attached is a draft for a manual page (kernel_lockdown.7) that I intend to
point at from messages emitted when the kernel prohibits something because the
kernel is in 'lockdown' mode, typically triggered by EFI secure boot.
Let me know what you think.
David
---
.\"
.\" Copyright
On 21/09/17 12:41, Linus Walleij wrote:
> On Fri, Sep 15, 2017 at 10:26 AM, Jerome Brunet wrote:
>
>> I initially planned to do some refcounting in the gpio layer but that would
>> make
>> no sense, as you pointed out, the irq could be shared. This refcounting would
>> only make sense at the irq
The "goto force_balance" here is intended to mitigate the fact that
avg_load calculations can result in bad placement decisions when
priority is asymmetrical. From the original commit (fab476228ba3
"sched: Force balancing on newidle balance if local group has
capacity") that adds it:
Under cer
2017-09-29 9:04 GMT+08:00 Wanpeng Li :
> The issue is reported in xen community.
>
> Anthony PERARD pointed out:
>
> https://www.mail-archive.com/xen-devel@lists.xen.org/msg117283.html#
>
> | When developing PVH for OVMF, I've used the lapic timer. It turns out that
> the
> | way it is used by O
The simple-framebuffer nodes have a unit address, but no reg property which
generates a warning when compiling it with DTC.
Change the simple-framebuffer node names so that there is no warnings on
this anymore.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi | 8
1 fi
We use task_util in find_idlest_group via capacity_spare_wake. This
task_util is updated in wake_cap. However wake_cap is not the only
reason for ending up in find_idlest_group - we could have been sent
there by wake_wide. So explicitly sync the task util with prev_cpu
when we are about to head to
The USB power supply node in the AXP209 DTSI is using underscores in its
node name, which is generating a warning. Change those underscores for
hyphens.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/axp209.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boo
Our oscillators clock names have a unit address, but no reg property, which
generates a warning in DTC. Change these names to remove those unit
addresses.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arc
On Wednesday, October 04, 2017 11:48:27 AM Ulf Hansson wrote:
> [...]
>
> >> MQ code that doesn't perform and therefore we cannot switch seamlessly
> >> to MQ.
> >
> > I think that switching seamlessly to blk-mq in short/medium-term
> > is not possible (SCSI tried and failed to do so). The changes
Some controllers have only one muxing option in the SoC. In such a case, we
can just move the muxing into the DTSI, and remove it from the DTS.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/sun4i-a10-a1000.dts| 6 --
arch/arm/boot/dts/sun4i-a10-ba10-tvbox.dts | 6 ---
From: Wanpeng Li
The description in the Intel SDM of how the divide configuration
register is used: "The APIC timer frequency will be the processor's bus
clock or core crystal clock frequency divided by the value specified in
the divide configuration register."
Observation of baremetal shown tha
701 - 800 of 958 matches
Mail list logo
