On Wed, Jul 12, 2017 at 1:29 PM, Leonard Crestez
wrote:
> This checks that the cpufreq driver actually sets the requested
> frequency.
This won't work on modern x86 with APERF/MPERF (see recent commits in
that area).
Thanks,
Rafael
On 07/11/2017 11:45 PM, Serge E. Hallyn wrote:
Quoting Stefan Berger (Stefan bergerstef...@linux.vnet.ibm.com):
+/*
+ * xattr_list_userns_rewrite - Rewrite list of xattr names for user namespaces
+ * or determine needed size for attribute list
+ *
On Wed, Jul 12, 2017 at 1:16 PM, James Hogan wrote:
> On Tue, Jul 11, 2017 at 06:31:17PM -0700, Palmer Dabbelt wrote:
>> From: Jonathan Neuschäfer
>>
>> RISC-V needs a MAINTAINERS entry. Let's add one.
>>
>> Signed-off-by: Jonathan Neuschäfer
>> Signed-off-by: Palmer Dabbelt
>> ---
>> MAINTAIN
This checks that the cpufreq driver actually sets the requested
frequency.
Signed-off-by: Leonard Crestez
---
I've been looking at using kselftests for imx. This patch exposes an
issue with the imx6 cpufreq driver on imx6sx where frequencies are set
incorrectly because of clk mishandling. This
Fix checkpatch issue: CHECK: usleep_range is preferred over udelay;
Signed-off-by: Jaya Durga
---
drivers/staging/speakup/speakup_keypc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/speakup/speakup_keypc.c
b/drivers/staging/speakup/speakup_keypc.c
ind
On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote:
> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote:
> >
> > Some display stuff did change for 4.13 for GM20x+ boards. If it's not
> > too much trouble, a bisect would be pretty useful.
>
> Bisection seemingly went fine, but the result i
When switching to regmap, the way to compute the irq cause was
reorganized. However while doing it, a typo was introduced: a 'xor'
replaced a 'and'.
This lead to wrong behavior in the interrupt handler ans one of the
symptom was wrong irq handler called on the Armada 388 GP:
"->handle_irq(): c016
On Tue, Jul 11, 2017 at 06:31:17PM -0700, Palmer Dabbelt wrote:
> From: Jonathan Neuschäfer
>
> RISC-V needs a MAINTAINERS entry. Let's add one.
>
> Signed-off-by: Jonathan Neuschäfer
> Signed-off-by: Palmer Dabbelt
> ---
> MAINTAINERS | 8
> 1 file changed, 8 insertions(+)
>
> diff
This Ployer Momo7w revision has the same hardware as the Trekstor
ST70416-6, so we re-use the surftab_wintron70_st70416_6_data.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/silead_dmi.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/platform/x86/silead_dmi.c
b/
On Wed, Jul 12, 2017 at 02:57:55PM +0530, Viresh Kumar wrote:
> On 12-07-17, 10:31, Peter Zijlstra wrote:
> > So the problem with the thread is two-fold; one the one hand we like the
> > scheduler to directly set frequency, but then we need to schedule a task
> > to change the frequency, which will
On Tue 2017-07-11 15:41:50, Matt Redfearn wrote:
> On 11/07/17 13:43, Petr Mladek wrote:
> >IMHO, the reasonable solution is to move early console code and data
> >out of the init sections. We should do this for the early consoles
> >where the corresponding real console is registered using a deferr
On Tue, Jul 11, 2017 at 06:31:29PM -0700, Palmer Dabbelt wrote:
> diff --git a/arch/riscv/include/asm/unistd.h b/arch/riscv/include/asm/unistd.h
> new file mode 100644
> index ..9f250ed007cd
> --- /dev/null
> +++ b/arch/riscv/include/asm/unistd.h
> @@ -0,0 +1,16 @@
> +/*
> + * Copyright
On 7/11/2017 5:13 AM, Bjorn Andersson wrote:
On Thu 22 Jun 05:08 PDT 2017, Avaneesh Kumar Dwivedi wrote:
Two different processors on a SOC need to switch memory ownership
during load/unload. To enable this, second level memory map table
need to be updated, which is done by secure layer.
This
Palmer Dabbelt writes:
> On Mon, 10 Jul 2017 23:21:07 PDT (-0700), m...@ellerman.id.au wrote:
>> Palmer Dabbelt writes:
>>>
>> ...
>>> +#ifdef CONFIG_EARLY_PRINTK
>>> +static void sbi_console_write(struct console *co, const char *buf,
>>> + unsigned int n)
>>> +{
>>> +
On 7/8/2017 4:19 AM, Stephen Boyd wrote:
On 06/22, Avaneesh Kumar Dwivedi wrote:
diff --git a/drivers/firmware/qcom_scm-64.c b/drivers/firmware/qcom_scm-64.c
index 6e6d561..cdfe986 100644
--- a/drivers/firmware/qcom_scm-64.c
+++ b/drivers/firmware/qcom_scm-64.c
@@ -292,6 +304,86 @@ int qcom_sc
Fixes: 847b8bf62eb4 ("rtc: sun6i: Expose the 32kHz oscillator")
Cc: Maxime Ripard
Cc: Rob Herring
Signed-off-by: Alexey Klimov
---
drivers/rtc/rtc-sun6i.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-sun6i.c b/drivers/rtc/rtc-sun6i.c
index 39cbc12..7e7da60
Signed-off-by: Alexey Klimov
---
drivers/rtc/rtc-sun6i.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-sun6i.c b/drivers/rtc/rtc-sun6i.c
index 77bc4d3..1886b85 100644
--- a/drivers/rtc/rtc-sun6i.c
+++ b/drivers/rtc/rtc-sun6i.c
@@ -362,7 +362,7 @@ static int s
The memory allocated for rtc and clk_data will never be freed in
sun6i_rtc_clk_init() in case of error and return. This patch adds
required error path with memory freeing.
Fixes: 847b8bf62eb4 ("rtc: sun6i: Expose the 32kHz oscillator")
Cc: Maxime Ripard
Cc: Rob Herring
Signed-off-by: Alexey Klim
Dear Linux crypto folks,
Building CRYPTO_RSA not as module, but into the Linux kernel,
`rsa_init()` takes 130 ms on an ASRock E350M1.
(Timings are shown by adding `initcall_debug` to Linux command line [1].
The times are visualized by `analyze_boot.py` from pm-graph [2] or
`systemd-bootchar
On Wednesday 12 July 2017 02:56 PM, Tony Lindgren wrote:
> * Kishon Vijay Abraham I [170711 03:17]:
>> The error handling code in omap_ocp2scp_probe fails to invoke
>> pm_runtime_disable and fails to initialize return value in
>> certain cases. Fix it here.
>
> Applying into omap-for-v4.13/fixe
On Fri, Jun 30, 2017 at 09:43:56PM +0200, Robert Jarzmik wrote:
> Hi Lars, Mark, Charles, Lee,
>
> This is a resend of the v2, with patch 1 added (forgotten in v2). Patch 12 was
> slightly modified after module unloading tests, and Dmitry acks were added.
This all looks good to me modulo the nami
On Tue, Jun 20, 2017 at 11:35:50AM +0100, Colin King wrote:
> From: Colin Ian King
>
> The functions cvm_encrypt, cvm_decrypt, cvm_xts_setkey and
> cvm_enc_dec_init does not need to be in global scope, so make
> them static.
>
> Signed-off-by: Colin Ian King
Patch applied. Thanks.
--
Email:
On Wed, Jun 28, 2017 at 03:27:10PM +0200, David Gstir wrote:
> Certain cipher modes like CTS expect the IV (req->info) of
> ablkcipher_request (or equivalently req->iv of skcipher_request) to
> contain the last ciphertext block when the {en,de}crypt operation is done.
> This is currently not the ca
On Wed, Jun 28, 2017 at 10:22:03AM +0300, Gilad Ben-Yossef wrote:
> The Atmel SHA driver was treating -EBUSY as indication of queueing
> to backlog without checking that backlog is enabled for the request.
>
> Fix it by checking request flags.
>
> Signed-off-by: Gilad Ben-Yossef
Patch applied.
On Mon, Jun 19, 2017 at 08:01:06PM +0530, Naveen N. Rao wrote:
> Currently, there is no way to ask for signals to be delivered when a
> certain number of sideband events have been logged into the ring buffer.
> This is problematic if we are only interested in, say, context switch
> events. Furtherm
On Mon, Jun 19, 2017 at 08:01:08PM +0530, Naveen N. Rao wrote:
SNIP
> - if (!event->attr.watermark) {
> + if (!event->attr.count_sb_events && !event->attr.watermark) {
> int wakeup_events = event->attr.wakeup_events;
>
> if (wakeup_events) {
> diff --git a/ke
Jin Yao writes:
> It is often useful to know the branch types while analyzing branch
> data. For example, a call is very different from a conditional branch.
>
> Currently we have to look it up in binary while the binary may later
> not be available and even the binary is available but user has t
Palmer Dabbelt writes:
> On Mon, 10 Jul 2017 23:31:18 PDT (-0700), m...@ellerman.id.au wrote:
...
>> So if you have a functional early console (which I think you do) then
>> you might be better off just making this def_bool y.
>
> I think that's best. The SBI's EARLY_PRINTK support is quite clean
Arnaldo Carvalho de Melo writes:
> Em Tue, Jul 11, 2017 at 04:38:28PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Tue, Jul 11, 2017 at 04:03:04PM -0300, Arnaldo Carvalho de Melo escreveu:
>> > Em Fri, Jul 07, 2017 at 02:17:25PM +0200, Thomas-Mich Richter escreveu:
>> > > On 07/06/2017 02:35 P
When hns port type is not debug mode, netif_tx_disable is called
when there is a tx timeout, which requires system reboot to return
to normal state. This patch fix this problem by resetting the net
dev.
Fixes: b5996f11ea54 ("net: add Hisilicon Network Subsystem basic ethernet
support")
Signed-off
Hi Chanwoo,
2017-05-24 0:24 GMT+02:00 Benson Leung :
> Hi Chanwoo,
>
>
> On Tue, May 23, 2017 at 2:58 AM, Chanwoo Choi wrote:
>
>> OK. This patch must need the immutable branch.
>>
>> I expect that some maintainer will make the immutable branch
>> and then send pull request to other maintainer re
The cros_ec_dev driver should be used only to expose the Chrome OS Embedded
Controller to user-space and should not be used to add MFD devices by
calling mfd_add_devices. This patch moves this logic to the MFD cros_ec
driver and removes the MFD bits from the character device driver. Also
makes inde
From: Stephen Barber
The EC can function as a simple RT, this patch adds the RTC related
definitions needed by the rtc-cros-ec driver.
Signed-off-by: Stephen Barber
Signed-off-by: Enric Balletbo i Serra
Acked-by: Lee Jones
---
include/linux/mfd/cros_ec_commands.h | 8
1 file changed
Dear all,
Basically this is a resend and rebase due that [2] and [3] are currently
merged so all dependecies are in mainline now.
To remmember:
* 1/4 mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev.
As pointed by Lee Jones in this thread [1] we should not use the MFD API
outsid
From: Stephen Barber
On platforms with a Chrome OS EC, the EC can function as a simple RTC.
Add a basic driver with this functionality.
Signed-off-by: Stephen Barber
Signed-off-by: Enric Balletbo i Serra
Acked-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 10 ++
drivers/rtc/Makefile
On 12/07/2017 09:47, wangyijing wrote:
在 2017/7/12 16:17, John Garry 写道:
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_PO
From: Stephen Barber
If the EC supports RTC host commands, expose an RTC device.
Signed-off-by: Stephen Barber
Signed-off-by: Enric Balletbo i Serra
---
drivers/mfd/cros_ec.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c
This serie makes the PINning of ITLBs optional in the 8xx
in order to allow STRICT_KERNEL_RWX to work properly
Christophe Leroy (7):
powerpc/8xx: Ensures RAM mapped with LTLB is seen as block mapped on
8xx.
powerpc/8xx: Remove macro that checks kernel address
powerpc/32: Avoid risk of un
On the 8xx, the RAM mapped with LTLBs must be seen as block mapped,
just like areas mapped with BATs on standard PPC32.
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/8xx_mmu.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/mm/8xx_mmu.c b/arc
By default, the 8xx pins an ITLB on the first 8M of memory in order
to avoid any ITLB miss on kernel code.
However, with some debug functions like DEBUG_PAGEALLOC and
DEBUG_RODATA, pinning TLBs is contradictory.
In order to avoid any ITLB miss in a critical section without pinning
TLBs, we have to
The macro to check if an address is a kernel address or not is
not used anymore in DTLBmiss handler. It is used in ITLB miss handler
and in DTLB error handler. DTLB error handler is not a hot path, it
doesn't need such optimisation.
In order to simplify a following patch which will rework ITLB mis
As stated in a comment in head_8xx.S, today we "Always pin the first
8 MB ITLB to prevent ITLB misses while mucking around with SRR0/SRR1
in asm".
This issue has just been cleared by the preceding patch, therefore
we can make this pinning optional (on by default) and independent
of DATA pinning.
This reduces the DTLB miss handler hot path (user address path)
by one instruction by preserving r10.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_8xx.S | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/powerpc/kernel/head_8xx.S b/arch/powerp
Pinning TLBs bypasses STRICT_KERNEL_RWX or DEBUG_PAGEALLOC protections
so it should only be allowed when those are not selected
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconf
setup_initial_memory_limit() is only called during init.
mmu_patch_cmp_limit() is only called from 8xx_mmu.c
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/8xx_mmu.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/mm/8xx_mmu.c b/arch/powerpc/mm/8xx_m
On Wed, Jul 12, 2017 at 02:59:47PM +0530, Tirupathi Reddy wrote:
> regulator_disable_deferred: regulator_disable_work:
>mutex_lock(&rdev->mutex); .
>rdev->deferred_disables++; mutex_lock(&rdev->mutex);
>mutex_unlock(&rdev->mutex);
On 10/07/2017 08:06, Yijing Wang wrote:
This patchset is based Johannes's patch
"scsi: sas: scsi_queue_work can fail, so make callers aware"
Now the libsas hotplug has some issues, Dan Williams report
a similar bug here before
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg39187.html
On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote:
>
> Some display stuff did change for 4.13 for GM20x+ boards. If it's not
> too much trouble, a bisect would be pretty useful.
Bisection seemingly went fine, but the result is odd.
e98c58e55f68f8785aebfab1f8c9a03d8de0afe1 is the first bad com
On 2017/7/11 8:01, Casey Leedom wrote:
>
> Hey Alexander,
>
> Okay, I understand your point regarding the "most likely scenario" being
> TLPs directed upstream to the Root Complex. But I'd still like to make sure
> that we have an agreed upon API/methodology for doing Peer-to-Peer with
> Rel
Hi,
On Wed, Jul 12, 2017 at 11:04:08AM +0200, linux-kernel-...@beckhoff.com wrote:
> +/dts-v1/;
> +#include "imx53.dtsi"
> +
> +#define MX53_PAD_EIM_D26__UART2_RXD_MUX0x144 0x48c 0x880 0x2 0x0
> +#define MX53_PAD_EIM_D27__UART2_TXD_MUX0x148 0x490 0x000 0x2 0x0
> +#define MX53_PAD_EIM_D28__
On 12-07-17, 11:36, Peter Zijlstra wrote:
> On Wed, Jul 12, 2017 at 10:30:35AM +0530, Viresh Kumar wrote:
> > On 11-07-17, 07:14, Joel Fernandes wrote:
>
> > > Another approach than setting min in sugov_set_iowait_boost, is, since
> > > we have already retrieved the current util, we can check if f
Hi,
On Wed, Jul 12, 2017 at 4:55 PM, Wim ten Have wrote:
> On Wed, 12 Jul 2017 00:04:14 -0400
> Sinan Kaya wrote:
>
>> All PCIe devices are expected to be able to handle 8-bit tags.
>> 'commit 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported")'
>> enabled extended tags for all devices
From: Alexey Brodkin
This initial port adds support of ARC HS Development Kit board with some
basic features such serial port, USB, SD/MMC and Ethernet.
Essentially we run Linux kernel on all 4 cores (i.e. utilize SMP) and
heavily use IO Coherency for speeding-up DMA-aware peripherals.
Note as
This series introduces some required preparations and initial
port of ARC HS Development Kit board with some basic features such
as serial port, USB, SD/MMC and Ethernet.
Essentially we run Linux kernel on all 4 cores (i.e. utilize SMP) and
heavily use IO Coherency for speeding-up DMA-aware periph
Most of the time we indeed use the one and only LINUX_LINK_BASE
set to 0x8000_. But there might be good reasons to move
the kernel to another location like 0x9z etc.
And we want IOC aperture to cover entire area used by the kernel,
so let's make its base matching link base and add required ass
We faced with problem when we tried to utilize 1G DRAM by linux on
HSDK.
We can't use our usual kernel memory address (0x8000) like on
AXS103 because of DCCM memory bank located at exactly same
address (0x8000)
But we can't simply move kernel memory address to another address (like
0x9
On Wed, Jul 12, 2017 at 10:30:35AM +0530, Viresh Kumar wrote:
> On 11-07-17, 07:14, Joel Fernandes wrote:
> > Another approach than setting min in sugov_set_iowait_boost, is, since
> > we have already retrieved the current util, we can check if flags ==
> > SCHED_CPUFREQ_IOWAIT, then set initial t
On 07/07/2017 04:00 PM, Andrew Lunn wrote:
>> Ok. I'm fine with moving the phy-reset-gpios binding into the PHY.
>> But one question still remains: Who should then trigger the "hard
>> reset" of the PHY?
>
> Hi Richard
>
> I think i see a few whys to do this, but first i need to check
> somethin
A race condition between queueing and processing the disable_work
instances results in having a work instance in the queue and the
deferred_disables variable of regulator device structure having a
value '0'. If no new regulator_disable_deferred() call later from
clients, the deferred_disables varia
Hi Fathi and Shuah,
On 29 June 2017 at 14:07, Fathi Boudra wrote:
> On 28 June 2017 at 17:21, Shuah Khan wrote:
>> On 06/28/2017 02:30 AM, Fathi Boudra wrote:
>>> On 23 June 2017 at 22:44, Shuah Khan wrote:
On 06/23/2017 04:37 AM, Marcin Nowakowski wrote:
> This patch series fixes buil
On 12-07-17, 10:31, Peter Zijlstra wrote:
> So the problem with the thread is two-fold; one the one hand we like the
> scheduler to directly set frequency, but then we need to schedule a task
> to change the frequency, which will change the frequency and around we
> go.
>
> On the other hand, ther
* Kishon Vijay Abraham I [170711 03:17]:
> The error handling code in omap_ocp2scp_probe fails to invoke
> pm_runtime_disable and fails to initialize return value in
> certain cases. Fix it here.
Applying into omap-for-v4.13/fixes thanks.
Tony
Hi Jaechul,
On 07/07/2017 10:31 AM, Jaechul Lee wrote:
This driver can support more frequencies over 96KHz. There are no reasons
to limit the frequency range below 96KHz. If codecs/amps or something else
can't support higher resolution rates, the constraints would be set rates
properly because e
On Wed, Jul 12, 2017 at 10:48:03AM +0200, Ingo Molnar wrote:
> Hm, I'd argue that the old code is much clearer: we need both the start and
> the
> end of a function and have the properly named symbols for that.
>
> That entry_SYSCALL_compat() happens to start just where
> __end_entry_SYSENTER_c
> "Reshetova, Elena" writes:
>
> >> "Reshetova, Elena" writes:
> >>
> >> >> "Reshetova, Elena" writes:
> >> >>
> >> >> 2>> Elena Reshetova writes:
> >> >> >>
> >> >> >> > refcount_t type and corresponding API should be
> >> >> >> > used instead of atomic_t when the variable is used as
> >>
From: Patrick Brünn
The CX9020 differs from i.MX53 Quick Start Board by:
- use uart2 instead of uart1
- DVI-D connector instead of VGA
- no audio
- CCAT FPGA connected to emi
- enable rtc
Signed-off-by: Patrick Brünn
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx53-cx902
在 2017年07月12日 15:19, Heiko Stuebner 写道:
Hi Caesar,
Am Mittwoch, 12. Juli 2017, 14:29:28 CEST schrieb Caesar Wang:
Add Mali GPU device tree node for the RK3399 SoCs, with devfreq
opp table.
RK3399 and RK3399-OP1 SoCs have a different recommendation table with
gpu opp. As the ARM's mali driver f
On 2017-07-10 23:36, sathyanarayanan kuppuswamy wrote:
> Hi,
>
>
> On 07/10/2017 12:40 AM, Peter Rosin wrote:
>> On 2017-07-09 09:35, Kuppuswamy, Sathyanarayanan wrote:
>>> Hi,
>>>
>>>
>>> On 7/9/2017 12:07 AM, Peter Rosin wrote:
On 2017-07-09 01:12, Kuppuswamy, Sathyanarayanan wrote:
>
Johan Hovold writes:
> On Tue, Jul 11, 2017 at 08:52:37AM +0200, Anatolij Gustschin wrote:
>
>> For devices with connected EEPROM some modes (including UART) are
>> configurable in the EEPROM. For devices without EEPROM the default
>> mode is always UART, but FIFO-, Bitbang- and MPSSE-mode can be
This fixes multiple block statements found not to match
style as per checkpatch
Signed-off-by: Craig Inches
---
drivers/staging/lustre/include/linux/lnet/lnetst.h | 129 +
1 file changed, 81 insertions(+), 48 deletions(-)
diff --git a/drivers/staging/lustre/include/linux/lne
On Tue 11-07-17 17:45:41, Johannes Weiner wrote:
[...]
> diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
> index a56c3989f773..efd3f48c667c 100644
> --- a/mm/sparse-vmemmap.c
> +++ b/mm/sparse-vmemmap.c
> @@ -52,18 +52,24 @@ void * __meminit vmemmap_alloc_block(unsigned long size,
> int nod
This patch fixes some multiline comment blocks which didnt conform
to the style guide, found by checkpatch.
Signed-off-by: Craig Inches
---
.../staging/lustre/include/linux/lnet/lib-types.h | 46 ++
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git a/drivers/stag
This fixes a block statement which didnt end with */
Signed-off-by: Craig Inches
---
drivers/staging/lustre/include/linux/lnet/socklnd.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/include/linux/lnet/socklnd.h
b/drivers/staging/lustre/include/lin
This patch fixes a warning generated by checkpatch for
a line over 80 characters.
Signed-off-by: Craig Inches
---
drivers/staging/lustre/include/linux/lnet/lib-lnet.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/include/linux/lnet/lib-lnet.h
b/dri
From: Qiuyang Sun
This patch implements Direct Access (DAX) in F2FS, including:
- a mount option to choose whether to enable DAX or not
- read/write and mmap of regular files in the DAX way
- zero-out of unaligned partial blocks in the DAX way
- garbage collection of DAX files, by mapping both ol
This series fixes a few style issues in lustre. All where picked up
by checkpatch.
v2 Changes:
- Fixed typo in patch subject s/luster/lustre/
Craig Inc
On Wed, 12 Jul 2017, Andrea Adami wrote:
> On Mon, Jul 3, 2017 at 2:03 PM, Andrea Adami wrote:
> > On Mon, Jul 3, 2017 at 1:26 PM, Lee Jones wrote:
> >> Please use the $SUBJECT line expected by the subsystem.
> >>
> >> `git log --oneline -- $SUBSYSTEM` can help with this.
> >>
> >> You also need
On Wed, 12 Jul 2017 00:04:14 -0400
Sinan Kaya wrote:
> All PCIe devices are expected to be able to handle 8-bit tags.
> 'commit 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported")'
> enabled extended tags for all devices based on the spec direction.
>
> The Broadcom HT2100 seems to be h
在 2017/7/12 16:17, John Garry 写道:
> On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
On Tue, Jul 11, 2017 at 08:52:37AM +0200, Anatolij Gustschin wrote:
> On Mon, 10 Jul 2017 14:34:27 +0200
> Johan Hovold jo...@kernel.org wrote:
>
> >On Fri, Jul 07, 2017 at 11:53:29AM +0200, Anatolij Gustschin wrote:
> >> On Fri, 07 Jul 2017 09:48:48 +0200
> >> Bjørn Mork bj...@mork.no wrote:
> >>
* Borislav Petkov wrote:
> Anyone think this is an OK-ish idea?
>
> It saves us the global symbol but requires the two functions to remained
> glued together. :-\
>
> ---
> diff --git a/arch/x86/entry/entry_64_compat.S
> b/arch/x86/entry/entry_64_compat.S
> index e1721dafbcb1..262519da8661 10
Hi Doug,
在 2017/7/12 1:03, Doug Anderson 写道:
Hi,
On Fri, Jul 7, 2017 at 9:03 PM, David Wu wrote:
@@ -6,7 +6,13 @@ Required properties:
"rockchip,rk3288-pwm": found on RK3288 SoC
"rockchip,vop-pwm": found integrated in VOP on RK3288 SoC
- reg: physical base address and length of
The gpio-mxc driver is able to use two interrupts per gpio bank. One for
the lower 16 and the other for the higher 16 gpios. The iMX27 has only one
interrupt per bank. An error in the driver leads to the problem that the
driver uses an invalid interrupt for the higher 16 gpios. Which in turn
preven
Errors from enable_irq_wake() in gpio_set_wake_irq() were silently ignored.
Thus led to the problem that gpio_set_wake_irq() always returned
successfully, even if enable_irq_wake() returned an error.
Signed-off-by: Philipp Rosenberger
---
drivers/gpio/gpio-mxc.c | 11 ++-
1 file changed,
In the function gpio_set_wake_irq(), port->irq_high is only checked for
zero. As platform_get_irq() returns a value less then zero if no interrupt
was found, any gpio >= 16 was handled like an irq_high interrupt was
available. On iMX27 for example no high interrupt is available. This lead
to the pr
Hi Andrzej,
Could you please check this patch?
Best regards,
Hoegeun
On 06/27/2017 11:11 AM, Hoegeun Kwon wrote:
This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver
which uses mipi_dsi bus to communicate with panel. The panel has
320×320 resolution in 1.63" physical panel. This
On Wed, Jul 12, 2017 at 12:15:08PM +0800, Li, Aubrey wrote:
> Okay, the difference is that Mike's patch uses a very simple algorithm to
> make the decision.
No, the difference is that we don't end up with duplication of a metric
ton of code.
It uses the normal idle path, it just makes the NOHZ e
On Wed, Jul 12, 2017 at 09:39:17AM +0530, Viresh Kumar wrote:
> Yeah, I saw your discussion with Peter on #linux-rt IRC and TBH I wasn't aware
> that we are going to do fast switching that way. Just trying to get
> understanding of that idea a bit..
>
> So we will do fast switching from scheduler'
On Fri, Jun 30, 2017 at 03:43:37PM +0200, Romain Perier wrote:
> From: Martyn Welch
>
> The IPU that drives HDMI must have its pre_sel set to pll2_pfd_396m
> to avoid stepping on the LVDS output's toes, as the PLL can't be clocked
> to the pixel clock and to the LVDS serial clock (3.5*pixel clock
Well, again, please don't.
I'll be randomly taking this one as an example.
That RTC will fail in 2100, 6 years before rtc_tm_to_time begins to be
an issue.
Once again, your patch hides the fact that there is an issue. There is
no other way than reading the datasheet and actually think about what
ext4_xattr_inode_read() currently reads each block sequentially while
waiting for io operation to complete before moving on to the next
block. This prevents request merging in block layer.
Fix this by starting reads for all blocks then wait for completions.
Signed-off-by: Tahsin Erdogan
---
fs/
On Fri, Jun 30, 2017 at 03:35:57PM +0200, Romain Perier wrote:
> From: Ian Ray
>
> Default boot medium must be internal eMMC, we don't want the SDIO to be
> used for these devices. This commit disables the SD card interface
> for GE Healthcare Bx50v3 devices.
>
> Signed-off-by: Ian Ray
> Signed
* Josh Poimboeuf wrote:
> The biggest change is that undwarf was renamed to ORC. Here's the
> relevant explanation from the docs:
>
> Etymology
> -
>
> Orcs, fearsome creatures of medieval folklore, are the Dwarves' natural
> enemies. Similarly, the ORC unwinder was created
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
This work from Amir introduces the inodes index feature, which provides:
- hardlinks are not broken on copy up;
- infrastructure for overlayfs NFS export.
This also fixes constant st_i
rtc_time_to_tm and rtc_tm_to_time are not deprecated and make perfect sense
for RTCs that are simple 32bit counters.
Signed-off-by: Alexandre Belloni
---
include/linux/rtc.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/rtc.h b/include/linux/rtc.h
index b693adac853b..deb
On 07/11/2017 09:48 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 11, 2017 at 04:38:28PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Tue, Jul 11, 2017 at 04:03:04PM -0300, Arnaldo Carvalho de Melo escreveu:
>>> Em Fri, Jul 07, 2017 at 02:17:25PM +0200, Thomas-Mich Richter escreveu:
.
>
On 12/07/2017 03:06, wangyijing wrote:
-unsigned long port_events_pending;
-unsigned long phy_events_pending;
+struct asd_sas_event port_events[PORT_POOL_SIZE];
+struct asd_sas_event phy_events[PHY_POOL_SIZE];
int error;
Hi Yijing,
So now we are creating a static pool
On Wed, Jul 12, 2017 at 09:43:07AM +0200, Benjamin Gaignard wrote:
> Even if CONFIG_FB_PROVIDE_GET_FB_UNMAPPED_AREA flag is selected
> do not compile and use get_fb_unmapped_area() if CONFIG_MMU is
> also set. This will avoid mmap errors when compiling multi
> architectures at same time.
>
> Signe
rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they
rely on 32bits variables and that will make rtc break in y2038/2016.
Stop using those two functions to safer 64bits ones.
Signed-off-by: Benjamin Gaignard
CC: Michael Chan
CC: net...@vger.kernel.org
CC: linux-kernel@vger.kernel.or
rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they
rely on 32bits variables and that will make rtc break in y2038/2016.
Stop using those two functions to safer 64bits ones.
Signed-off-by: Benjamin Gaignard
CC: Thomas Gleixner
CC: Ingo Molnar
CC: x...@kernel.org
CC: John Stultz
C
601 - 700 of 765 matches
Mail list logo
