>>> On 21.02.18 at 22:39, wrote:
> On Mon, Feb 19, 2018 at 6:49 AM, Jan Beulich wrote:
>> Commit df3405245a ("x86/asm: Add suffix macro for GEN_*_RMWcc()")
>> introduced "suffix" RMWcc operations, adding bogus clobber specifiers:
>> For one, on x86 there's no point explicitly clobbering "cc". In
At 02/22/2018 04:50 AM, Samuel Neves wrote:
Without this fix, /proc/cpuinfo will display an incorrect amount
of CPU cores, after bringing them offline and online again, as
exemplified below:
$ cat /proc/cpuinfo | grep cores
cpu cores : 4
cpu cores : 8
cpu cores : 8
cpu cores
On Wed, Feb 21, 2018 at 11:38:25PM +, James Hogan wrote:
> Now that arch/metag/ has been removed, remove the METAG dependency from
> the IMG SCB I2C device driver. The hardware is also present on MIPS SoCs
> so the driver still has value.
>
> Signed-off-by: James Hogan
I'd think it should go
On Wed, Feb 21, 2018 at 02:25:18PM -0600, Dan Rue wrote:
> On Wed, Feb 21, 2018 at 01:47:09PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.15.5 release.
> > There are 163 patches in this series, all will be posted as a response
> > to this one. If any
On Fri, Feb 16, 2018 at 9:13 AM, Tomasz Figa wrote:
> On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
>> On 15/02/18 04:17, Tomasz Figa wrote:
>> [...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the normally happening fast path
On 22/02/2018 04:01, Julia Lawall wrote:
On Wed, 21 Feb 2018, Rodrigo Siqueira wrote:
This patch fixes the checkpatch.pl warning:
drivers/iio/dummy/iio_dummy_evgen.c:151: WARNING: Symbolic permissions
'S_IWUSR' are not preferred. Consider using octal permissions '0200'.
I haven't studied up
This patch fix the following build warnings:
CC [M] drivers/staging/media/atomisp/pci/atomisp2/atomisp_drvfs.o
cc1: warning:
drivers/staging/media/atomisp/pci/atomisp2/css2400/isp/kernels/bayer_ls/bayer_ls_1.0/:
No such file or directory [-Wmissing-include-dirs]
cc1: warning:
drivers/staging/
On 21/02/18 17:00, Manish Narani wrote:
> Hi Adrian,
>
>> -Original Message-
>> From: Manish Narani
>> Sent: Wednesday, February 21, 2018 11:39 AM
>> To: Adrian Hunter ; michal.si...@xilinx.com;
>> ulf.hans...@linaro.org; linux-arm-ker...@lists.infradead.org; linux-
>> m...@vger.kernel.org
Hi Alexandre,
On Wed, Feb 21, 2018 at 10:37 PM, Alexandre Belloni
wrote:
> The RTC core is always calling rtc_valid_tm after the read_time callback.
> It is not necessary to call it just before returning from the callback.
>
> Signed-off-by: Alexandre Belloni
Thank you, will apply and queue for
The scheduler directory was removed via commit 1b1f42d8fde4 ("drm: move
amd_gpu_scheduler into common location")
Remove it from include path.
Signed-off-by: Corentin Labbe
---
drivers/gpu/drm/amd/amdgpu/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/Makef
This patch fix the following build warnings:
CC [M] drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o
cc1: warning: ../display/: No such file or directory [-Wmissing-include-dirs]
cc1: warning: ../display/include: No such file or directory
[-Wmissing-include-dirs]
CC [M] drivers/gpu/drm/amd/amdgpu/amd
> > Also who cares? The commit message is perfectly clear.
>
> I do care about newcomers really learning on how to write a proper
> commit message.
>
> The commit messsage should really say why the patch is needed, no what the
> patch does.
>
It fixes a checkpatch warning. The warning was ri
Am 22.02.2018 um 09:21 schrieb Corentin Labbe:
The scheduler directory was removed via commit 1b1f42d8fde4 ("drm: move
amd_gpu_scheduler into common location")
Remove it from include path.
Signed-off-by: Corentin Labbe
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/Makefile
Am 22.02.2018 um 09:21 schrieb Corentin Labbe:
This patch fix the following build warnings:
CC [M] drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o
cc1: warning: ../display/: No such file or directory [-Wmissing-include-dirs]
cc1: warning: ../display/include: No such file or directory
[-Wmissing-incl
On 2/22/2018 9:08 AM, Christophe Leroy wrote:
> Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721
>
> Performing the hash of an empty file leads to a kernel Oops
>
> [ 44.504600] Unable to handle kernel paging request for data at address
> 0x000c
> [ 44.512819] Faulting instruction addre
On Thu, 22 Feb 2018 00:00:31 +0900
Masami Hiramatsu wrote:
> Add $argN special fetch variable for accessing function
> arguments. This allows user to trace the Nth argument easily
> at the function entry.
>
> Note that this returns most probably assignment of registers
> and stacks. In some case
On 2018-02-22, Al Viro wrote:
>> @@ -2378,22 +2420,36 @@ void d_delete(struct dentry * dentry)
>> /*
>> * Are we the only user?
>> */
>> -again:
>> spin_lock(&dentry->d_lock);
>> +again:
>> inode = dentry->d_inode;
>> isdir = S_ISDIR(inode->i_mode);
>> if (dent
On Wed, Feb 21, 2018 at 05:20:40PM -0600, Bjorn Helgaas wrote:
> On Wed, Feb 21, 2018 at 04:25:08PM +0530, George Cherian wrote:
> > I have found another configuration where this fails.
> > Following is the configuration
> > 1) Connected a PCIe Intel i40 card under the root port.
> > 2) unbind the
On Thu, Feb 22, 2018 at 09:10:18AM +0100, Wolfram Sang wrote:
> On Wed, Feb 21, 2018 at 11:38:25PM +, James Hogan wrote:
> > Now that arch/metag/ has been removed, remove the METAG dependency from
> > the IMG SCB I2C device driver. The hardware is also present on MIPS SoCs
> > so the driver sti
On 21 February 2018 at 14:13, Valentin Schneider
wrote:
> On 02/16/2018 01:44 PM, Vincent Guittot wrote:
>> On 16 February 2018 at 13:13, Valentin Schneider
>> wrote:
>>> On 02/14/2018 03:26 PM, Vincent Guittot wrote:
Stopped the periodic update of blocked load when all idle CPUs have fully
On Thu, 22 Feb 2018, at 15:33, Joel Stanley wrote:
> I am interested in all ASPEED drivers, and the previous match wasn't
> grabbing files in nested directories. Use N instead.
>
> Add the arm kernel mailing list so that patches get reviewed there, and
> the linux-aspeed list which exists only s
Hi Shanker,
On Mon, Feb 19, 2018 at 09:38:07AM -0600, Shanker Donthineni wrote:
> In AArch64/AArch32, the virtual counter uses a fixed virtual offset
> of zero in the following situations as per ARMv8 specifications:
>
> 1) HCR_EL2.E2H is 1, and CNTVCT_EL0/CNTVCT are read from EL2.
> 2) HCR_EL2.{
topology_sibling_cpumask() is the correct thread-related topology
information in the kernel.
S/topology_sibling_mask/topology_sibling_cpumask
Signed-off-by: Dou Liyang
---
Documentation/x86/topology.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/x86/topolo
On Thu, Feb 22, 2018 at 12:05:11AM +0800, Palmer Dabbelt wrote:
> On Mon, 12 Feb 2018 21:13:15 PST (-0800), alan...@andestech.com wrote:
> > This patch set includes the building blocks of dynamic ftrace features
> > for RISC-V machines.
> >
> > Changes in v4:
> > - Organize code structure accordin
Hi Philipp,
On Wed, Feb 21, 2018 at 5:51 PM, Philipp Zabel wrote:
> I have a suggestion to avoid having to use the IS_ERR_OR_NULL macro, see
> below:
>
> On Tue, 2018-02-13 at 17:36 +0100, Geert Uytterhoeven wrote:
>> Vfio-platform requires reset support, provided either by ACPI, or, on DT
>> pla
Dear Andrew & Joel,
Since you are ASPEED BMC experts, any time and interest in eSPI code
review ? I've sent
it before, but no more response. Intel recommends eSPI bus than LPC as I
know. I just kept
the minimal eSPI code which is approved to work well in our real server
boards for two more
On Thu, 22 Feb 2018 08:42:31 +,
Christoffer Dall wrote:
>
> Hi Shanker,
>
> On Mon, Feb 19, 2018 at 09:38:07AM -0600, Shanker Donthineni wrote:
> > In AArch64/AArch32, the virtual counter uses a fixed virtual offset
> > of zero in the following situations as per ARMv8 specifications:
> >
> >
On 21/02/18 23:36, Dave Chinner wrote:
> On Wed, Feb 21, 2018 at 11:56:22AM +0200, Igor Stoppa wrote:
[...]
> It seems lots of people get confused when discussing concepts vs
> implementation... :)
IMHO, if possible, it's better to use unambiguous terms at every point.
__ro_after_init is alrea
Hi Greg,
Sorry for late responds for I was on vacation.
On 2018/2/17 0:27, Greg KH wrote:
> On Mon, Feb 12, 2018 at 06:43:09PM +0800, Yisheng Xie wrote:
>> If we failed to create debugfs for ion at ion_device_create, the
>> debug_root of ion_device will be NULL, and then when try to create debug
On 22/02/18 00:24, Kees Cook wrote:
> On Tue, Feb 20, 2018 at 8:40 AM, Igor Stoppa wrote:
[...]
>> sorry for being dense ... are you proposing that I do something to
>> lkdtm_rodata.c ? An example would probably help me understand.
>
> It would likely live in lkdtm_perms.c (or maybe lkdtm_hea
Hi Sudeep,
On Monday 12 Feb 2018 at 18:45:23 (+), Sudeep Holla wrote:
[...]
> +/*
> + * perf_ops->freq_set is not a synchronous, the actual OPP change will
> + * happen asynchronously and can get notified if the events are
> + * subscribed for by the SCMI firmware
> + */
> +static int
> +scmi_
2018-02-22 1:13 GMT+01:00 Pierre-Loup A. Griffais :
>
> On 02/21/2018 12:21 PM, Rodrigo Rivas Costa wrote:
>>
>> Related to that, Benjamin Tissoires replied to 1/3:
--- a/drivers/hid/hid-quirks.c
+++ b/drivers/hid/hid-quirks.c
@@ -629,6 +629,10 @@ static const struct hid_device_
On Thu, Feb 22, 2018 at 1:13 AM, Pierre-Loup A. Griffais
wrote:
>
>
> On 02/21/2018 12:21 PM, Rodrigo Rivas Costa wrote:
>>
>> On Tue, Feb 20, 2018 at 04:09:39PM -0800, Pierre-Loup A. Griffais wrote:
>>>
>>> On 02/20/2018 03:20 PM, Rodrigo Rivas Costa wrote:
On Tue, Feb 20, 2018 at 02:29
It's used to record how many memory sections are marked as present
during system boot up, and will be used in the later patch.
Signed-off-by: Baoquan He
---
mm/sparse.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/sparse.c b/mm/sparse.c
index 7af5e7a92528..433d3c9b4b56 100644
--- a/m
In sparse_init(), two temporary pointer arrays, usemap_map and map_map
are allocated with the size of NR_MEM_SECTIONS. They are used to store
each memory section's usemap and mem map if marked as present. With
the help of these two arrays, continuous memory chunk is allocated for
usemap and memmap
In sparse_init(), if CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y, system
will allocate one continuous memory chunk for mem maps on one node and
populate the relevant page tables to map memory section one by one. If
fail to populate for a certain mem section, print warning and its
->section_mem_map wi
This is v2 post. V1 can be found here:
https://www.spinics.net/lists/linux-mm/msg144486.html
In sparse_init(), two temporary pointer arrays, usemap_map and map_map
are allocated with the size of NR_MEM_SECTIONS. They are used to store
each memory section's usemap and mem map if marked as present.
On Thu, Feb 22, 2018 at 04:59:27PM +0800, Yisheng Xie wrote:
> Hi Greg,
>
> Sorry for late responds for I was on vacation.
>
> On 2018/2/17 0:27, Greg KH wrote:
> > On Mon, Feb 12, 2018 at 06:43:09PM +0800, Yisheng Xie wrote:
> >> If we failed to create debugfs for ion at ion_device_create, the
>
On 22/02/18 00:28, Kees Cook wrote:
> On Tue, Feb 20, 2018 at 8:59 AM, Igor Stoppa wrote:
>>
>>
>> On 13/02/18 01:50, Kees Cook wrote:
>>> On Mon, Feb 12, 2018 at 8:52 AM, Igor Stoppa wrote:
[...]
+ genalloc_selftest();
>>>
>>> I wonder if it's possible to make this module-loadable
On 02/22/18 at 05:11pm, Baoquan He wrote:
> This is v2 post. V1 can be found here:
> https://www.spinics.net/lists/linux-mm/msg144486.html
>
> In sparse_init(), two temporary pointer arrays, usemap_map and map_map
> are allocated with the size of NR_MEM_SECTIONS. They are used to store
> each memo
On Wed, Feb 21, 2018 at 01:39:52PM -0800, Linus Torvalds wrote:
> showing with a hung kernel. And most of the above is actually
> completely useless. Those are the *usermode* registers it shows, not
> the kernel registers at the time of the crash (the final rip/rsp/code
> lines are for the actual k
Hi,
A couple of two more fixes, on top of tip:locking/urgent, to Alpha's
implementations of xchg() and cmpxchg():
- The first, suggested by Will, removing the macro '__ASM__MB'
in favour of smp_mb();
- The second, reported by Will, adding a leading smp_mb().
Compile tested only.
Cheers
On 02/21/2018 10:26 AM, Javier González wrote:
Add support for 2.0 address format. Also, align address bits for 1.2 and
2.0 to be able to operate on channel and luns without requiring a format
conversion. Use a generic address format for this purpose.
Signed-off-by: Javier González
---
driver
Replace each occurrence of __ASM__MB with a (trailing) smp_mb() in
xchg(), cmpxchg(), and remove the now unused __ASM__MB definitions;
this improves readability, with no additional synchronization cost.
Suggested-by: Will Deacon
Signed-off-by: Andrea Parri
Cc: Peter Zijlstra
Cc: Paul E. McKenne
Successful RMW operations are supposed to be fully ordered, but
Alpha's xchg() and cmpxchg() do not align to this requirement.
Will reported that:
> So MP using xchg:
>
> WRITE_ONCE(x, 1)
> xchg(y, 1)
>
> smp_load_acquire(y) == 1
> READ_ONCE(x) == 0
>
> would be allowed.
(thus violating the abov
Hi Laurent,
On Thu, Feb 22, 2018 at 1:05 AM, Laurent Pinchart
wrote:
> From: Pantelis Antoniou
>
> The changeset helpers are easier to use, use them instead of
> using the static property.
>
> Signed-off-by: Pantelis Antoniou
> Acked-by: Wolfram Sang
> ["okay" -> "ok"]
Why? ePAPR says "okay",
On Wed, Feb 21, 2018 at 11:38:12PM +, James Hogan wrote:
> So lets call it a day and drop the Meta architecture port from the
> kernel. RIP Meta.
So long, and thanks for all the fish!
Nice cleanup though, most welcome :-)
Acked-by: Peter Zijlstra (Intel)
Hi Marc,
Thank you for the review!
On Tue, 20 Feb 2018 18:07:54 +
Marc Zyngier wrote:
> Hi Mylène,
>
> On 19/02/18 08:18, Mylène Josserand wrote:
> > The ARM architected timers use an offset between their physical and
> > virtual counters. That offset should be configured by the bootloader
On Wed, Feb 21, 2018 at 4:29 PM, Hans Verkuil wrote:
> On 02/21/2018 07:01 AM, Alexandre Courbot wrote:
>> Hi Hans,
>>
>> On Tue, Feb 20, 2018 at 7:36 PM, Hans Verkuil wrote:
>>> On 02/20/18 05:44, Alexandre Courbot wrote:
>
>
>
+#define MEDIA_REQUEST_IOC(__cmd, func)
On Thu, 2018-02-22 at 12:01 +1100, Michael Ellerman wrote:
> So I guess this patch is OK for now, but we do need a full back port of
> 222f20f to 4.9.
Hi,
in the light of this, do you know the full status of protections against
Meltdown on powerpc/ppc64el architecures on 4.9?
Regards,
--
Yves-A
On 2018年02月22日 15:54, Sergei Shtylyov wrote:
Hello!
On 2/22/2018 9:24 AM, Jason Wang wrote:
Commit 762c330d670e ("tuntap: add missing xdp flush") tries to fix the
devmap stall caused by missed xdp flush by counting the pending xdp
redirected packets and flush when it exceeds NAPI_POLL_WEIGHT
Hi Geert,
On Thu, 2018-02-22 at 09:50 +0100, Geert Uytterhoeven wrote:
[...]
> > > @@ -127,8 +134,15 @@ static int vfio_platform_get_reset(struct
> > > vfio_platform_device *vdev)
> > > vdev->of_reset = vfio_platform_lookup_reset(vdev->compat,
> > >
This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The
reason is we try to batch packets for devmap which causes calling
xdp_do_flush() in the process context. Simply disabling preemption
may not work since process may move among processors which lead
xdp_do_flush() to miss some flushes
Commit 762c330d670e ("tuntap: add missing xdp flush") tries to fix the
devmap stall caused by missed xdp flush by counting the pending xdp
redirected packets and flush when it exceeds NAPI_POLL_WEIGHT or
MSG_MORE is clear. This may lead to BUG() since xdp_do_flush() was
called in the process contex
On 22/02/2018 01:07, Jim Mattson wrote:
> On Wed, Feb 21, 2018 at 1:41 PM, Paolo Bonzini wrote:
>> We need to change the default all-1s bitmap if the MSRs are _not_
>> intercepted. However, the code was disabling the intercept when it was
>> _enabled_ in the VMCS01. This is not causing bigger tr
On 02/22/2018 08:47 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 08.28, Matias Bjørling wrote:
On 02/21/2018 10:26 AM, Javier González wrote:
Both 1.2 and 2.0 specs define a field for media and controller
capabilities. Also, 1.2 defines a separate field dedicated to device
capabilities.
In 2.
On 02/22/2018 08:49 AM, Javier González wrote:
On 22 Feb 2018, at 08.47, Matias Bjørling wrote:
On 02/21/2018 10:26 AM, Javier González wrote:
Create a generic identify structure to collect the identify information
before knowing the spec. version. This forces different version paths to
cast t
Hi Gwendal,
On 22/02/18 03:20, Gwendal Grignou wrote:
> On Mon, Feb 19, 2018 at 2:41 PM, Enric Balletbo i Serra
> wrote:
>> From: Gwendal Grignou
> This patch is not needed anymore. It was added to
>>
>> Send dummy command to EC at resume time, wait for status.
>> If EC loses that command and re
On 02/22/2018 08:55 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 08.45, Matias Bjørling wrote:
On 02/21/2018 10:26 AM, Javier González wrote:
Complete the generic geometry structure with the maxoc and maxocpu
felds, present in the 2.0 spec.
Signed-off-by: Javier González
---
drivers/nvme/h
On 02/22/18 10:30, Alexandre Courbot wrote:
> On Wed, Feb 21, 2018 at 4:29 PM, Hans Verkuil wrote:
>> On 02/21/2018 07:01 AM, Alexandre Courbot wrote:
>>> Hi Hans,
>>>
>>> On Tue, Feb 20, 2018 at 7:36 PM, Hans Verkuil wrote:
On 02/20/18 05:44, Alexandre Courbot wrote:
>>
>>
>>
> +#defin
On 22/02/18 09:04, Quentin Perret wrote:
> Hi Sudeep,
>
> On Monday 12 Feb 2018 at 18:45:23 (+), Sudeep Holla wrote:
> [...]
>> +/*
>> + * perf_ops->freq_set is not a synchronous, the actual OPP change will
>> + * happen asynchronously and can get notified if the events are
>> + * subscribed
On Wed, Feb 21, 2018 at 01:56:33AM +, Andrew Lutomirski wrote:
> > It would be much nicer to be able to control this at runtime rather
> > than compile-time. Why not a /proc tunable? We could always use more
> > of those ;)
>
> /proc/sys/kernel/hardening_features_that_cost_essentially_nothin
On Thu, Feb 22, 2018 at 10:26:54AM +0100, Peter Zijlstra wrote:
> On Wed, Feb 21, 2018 at 11:38:12PM +, James Hogan wrote:
> > So lets call it a day and drop the Meta architecture port from the
> > kernel. RIP Meta.
>
> So long, and thanks for all the fish!
>
> Nice cleanup though, most welco
On Wed, Feb 21, 2018 at 9:59 PM, syzbot
wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> 79c0ef3e85c015b0921a8fd5dd539d1480e9cd6c (Mon Feb 19 19:58:19 2018 +)
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
>
> So far this crash happened 2 times on
> http
Do not stop/restart dma on overrun or errors.
Dma will be restarted on current frame transfer
completion. Frame transfer completion is ensured
even if overrun or error occurs by DCMI continuous
capture mode which restarts data transfer at next
frame sync.
Do no warn on overrun while in irq thread,
Fix lock scheme leading to spurious freeze.
Signed-off-by: Hugues Fruchet
---
version 2:
- dcmi_buf_queue() refactor to avoid to have "else" after "return"
(warning detected by checkpatch.pl --strict -f stm32-dcmi.c)
drivers/media/platform/stm32/stm32-dcmi.c | 57 +
> On 22 Feb 2018, at 10.45, Matias Bjørling wrote:
>
> On 02/22/2018 08:55 AM, Javier Gonzalez wrote:
>>> On 22 Feb 2018, at 08.45, Matias Bjørling wrote:
>>>
>>> On 02/21/2018 10:26 AM, Javier González wrote:
Complete the generic geometry structure with the maxoc and maxocpu
felds, p
Add DCMI JPEG support.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/stm32/stm32-dcmi.c | 195 +++---
1 file changed, 148 insertions(+), 47 deletions(-)
diff --git a/drivers/media/platform/stm32/stm32-dcmi.c
b/drivers/media/platform/stm32/stm32-dcmi.c
index 2
Fix unnecessary parentheses in if conditions.
Detected by checkpatch.pl --strict.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/stm32/stm32-dcmi.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/media/platform/stm32/stm32-dcmi.c
b/drivers/medi
On Wed, Feb 21, 2018 at 12:59:14PM -0800, Andrew Morton wrote:
> On Wed, 21 Feb 2018 11:29:33 +0100 Michal Hocko wrote:
>
> > On Tue 20-02-18 18:16:59, Kees Cook wrote:
> > > One of the classes of kernel stack content leaks[1] is exposing the
> > > contents of prior heap or stack contents when a
The Rockchip PMIC driver can automatically detect connected component
versions by reading the ID_MSB and ID_LSB registers. The probe function
will always fail with RK818 PMICs because the ID_MSK is 0xFFF0 and the
RK818 template ID is 0x8181.
This patch changes this value to 0x8180.
Signed-off-by:
There are two clusters (2 + 4 CPUs) on this platform and a separate
cpufreq policy is available for each of the CPUs. The loop in
tegra186_cpufreq_init() tries to find the structure for the right CPU
and finish initialization. But it is missing a `break` statement at the
end, which forces it to res
The RAS SError Syndrome can be Implementation-Defined,
arm64_is_ras_serror() is used to judge whether it is RAS SError,
but arm64_is_ras_serror() does not include this judgement. In order
to avoid function name confusion, we rename the arm64_is_ras_serror()
to arm64_is_categorized_ras_serror(), thi
On 02/22/2018 10:52 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 10.45, Matias Bjørling wrote:
On 02/22/2018 08:55 AM, Javier Gonzalez wrote:
On 22 Feb 2018, at 08.45, Matias Bjørling wrote:
On 02/21/2018 10:26 AM, Javier González wrote:
Complete the generic geometry structure with the max
From: Colin Ian King
Trivial fix to spelling mistake in hid_err error message text.
Signed-off-by: Colin Ian King
---
drivers/hid/hid-elan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/hid-elan.c b/drivers/hid/hid-elan.c
index 803a725785cf..52381d1beba3 1006
Javier
> On 22 Feb 2018, at 11.00, Matias Bjørling wrote:
>
> On 02/22/2018 10:52 AM, Javier Gonzalez wrote:
>>> On 22 Feb 2018, at 10.45, Matias Bjørling wrote:
>>>
>>> On 02/22/2018 08:55 AM, Javier Gonzalez wrote:
> On 22 Feb 2018, at 08.45, Matias Bjørling wrote:
>
> On 02/2
On 22/02/18 00:14, Rob Herring wrote:
On Tue, Feb 20, 2018 at 3:33 AM, Srinivas Kandagatla
wrote:
Thanks for your review comments,
On 18/02/18 23:04, Rob Herring wrote:
On Wed, Feb 14, 2018 at 09:13:23AM +, Srinivas Kandagatla wrote:
Thanks for the review,
On 13/02/18 23:12, Rob He
On 02/22/2018 08:37 AM, Vincent Guittot wrote:
> On 21 February 2018 at 14:13, Valentin Schneider
> wrote:
>> On 02/16/2018 01:44 PM, Vincent Guittot wrote:
>>> On 16 February 2018 at 13:13, Valentin Schneider
>>> wrote:
On 02/14/2018 03:26 PM, Vincent Guittot wrote:
> Stopped the period
On 02/21/18 18:47, Jacopo Mondi wrote:
> Add driver for Renesas Capture Engine Unit (CEU).
>
> The CEU interface supports capturing 'data' (YUV422) and 'images'
> (NV[12|21|16|61]).
>
> This driver aims to replace the soc_camera-based sh_mobile_ceu one.
>
> Tested with ov7670 camera sensor, prov
On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote:
> And yes, if we go with a purely RCpc interpretation of acquire and
> release, then I don't believe the writes in the previous critical
> section would be ordered with the writes in the subsequent critical
> section.
Excuse my ignoran
Hi Baoquan,
>
> In sparse_init(), two temporary pointer arrays, usemap_map and map_map
> are allocated with the size of NR_MEM_SECTIONS. They are used to store
> each memory section's usemap and mem map if marked as present. With
> the help of these two arrays, continuous memory chunk is allocat
On 21/02/2018 23:15, dann frazier wrote:
On Tue, Feb 20, 2018 at 01:48:31AM +0800, John Garry wrote:
This patchset supports the IPMI-bt device attached to the Low-Pin-Count
interface implemented on Hisilicon Hip06/Hip07 SoC.
---
| LPC host|
On 22/02/2018 00:38, James Hogan wrote:
> Now that arch/metag/ has been removed, remove the metag generic
> per-thread timer driver. It is of no value without the architecture
> code.
>
> Signed-off-by: James Hogan
> Cc: Daniel Lezcano
> Cc: Thomas Gleixner
> Cc: linux-me...@vger.kernel.org
Ac
On Wed, Feb 21, 2018 at 9:29 PM, Eric W. Biederman
wrote:
> At the point of fuse_dev_do_read the user space process that initiated the
> action on the fuse filesystem may no longer exist. The process have been
> killed or may have fired an asynchronous request and exited.
>
> If the initial proce
>>> On 21.02.18 at 17:53, wrote:
> * Jan Beulich wrote:
>
>> Using just the leaf page table entry flags would cause a false warning
>> in case _PAGE_RW is clear or _PAGE_NX is set in a higher level entry.
>> Hand through both the current entry's flags as well as the accumulated
>> effective val
On Thu, Feb 22, 2018 at 02:58:47PM +0800, Boqun Feng wrote:
> > And yes, if we go with a purely RCpc interpretation of acquire and
> > release, then I don't believe the writes in the previous critical
> > section would be ordered with the writes in the subsequent critical
> > section. That's reall
Hi,
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of ShuFanLee
> Sent: 2018年2月21日 23:02
> To: heikki.kroge...@linux.intel.com; li...@roeck-us.net; g...@kroah.com
> Cc: shufan_...@richtek.com; cy_hu...@richtek.com;
> linux-
Le 22/02/2018 à 09:30, Horia Geantă a écrit :
On 2/22/2018 9:08 AM, Christophe Leroy wrote:
Upstream 87a81dce53b1ea61acaeefa5191a0376a2d1d721
Performing the hash of an empty file leads to a kernel Oops
[ 44.504600] Unable to handle kernel paging request for data at address
0x000c
[
On Thursday, February 22, 2018 9:35:43 AM CET Lukas Wunner wrote:
> On Wed, Feb 21, 2018 at 05:20:40PM -0600, Bjorn Helgaas wrote:
> > On Wed, Feb 21, 2018 at 04:25:08PM +0530, George Cherian wrote:
> > > I have found another configuration where this fails.
> > > Following is the configuration
> >
Hi Geert,
On Thursday, 22 February 2018 11:26:44 EET Geert Uytterhoeven wrote:
> On Thu, Feb 22, 2018 at 1:05 AM, Laurent Pinchart wrote:
> > From: Pantelis Antoniou
> >
> > The changeset helpers are easier to use, use them instead of
> > using the static property.
> >
> > Signed-off-by: Pantel
The I.T.Works TW701 7" tablet is a differently branded version of the
same generic 7" Windows tablet as the Trekstor ST70416-6. Add a DMI
match-table entry for it pointing to the Trekstor's touchscreen info.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/silead_dmi.c | 9 +
1 file
Hi,
On 02/20/2018 07:10 PM, Alan Stern wrote:
> On Tue, 20 Feb 2018, Roger Quadros wrote:
>
>> On 20/02/18 16:46, Amelie DELAUNAY wrote:
>>> Hi,
>>>
>>> On 02/20/2018 03:00 PM, Roger Quadros wrote:
Hi,
On 20/02/18 14:58, Amelie Delaunay wrote:
> On some boards, especially when
On Thu, Feb 22, 2018 at 11:06:36AM +0100, Peter Zijlstra wrote:
> On Wed, Feb 21, 2018 at 09:42:08PM -0800, Daniel Lustig wrote:
> > And yes, if we go with a purely RCpc interpretation of acquire and
> > release, then I don't believe the writes in the previous critical
> > section would be ordered
On giovedì 22 febbraio 2018 06:14:07 CET Jeremy Cline wrote:
> Hey folks,
>
> Commit 30323fb6d552c41997baca5292bf7001366cab57 (Support tablet mode
> switch) causes the keyboard on my XPS 13 to stop working. This
> particular model has a touch screen (which I've disabled in the BIOS),
> but isn't a
Add driver and bindings for the OV2680 2 megapixel CMOS 1/5" sensor, which has
a single MIPI lane interface and output format of 10-bit Raw RGB.
Features supported are described in PATCH 2/2.
Cheers,
Rui
Rui Miguel Silva (2):
media: ov2680: dt: Add bindings for OV2680
media: ov2680: Add
Hi Frank,
On Thursday, 22 February 2018 08:07:14 EET Frank Rowand wrote:
> On 02/20/18 15:10, Laurent Pinchart wrote:
> > Hello,
> >
> > This patch series addresses a design mistake that dates back from the
> > initial DU support. Support for the LVDS encoders, which are IP cores
> > separate fro
Add device tree binding documentation for the OV5640 camera sensor.
CC: devicet...@vger.kernel.org
Signed-off-by: Rui Miguel Silva
---
.../devicetree/bindings/media/i2c/ov2680.txt | 34 ++
1 file changed, 34 insertions(+)
create mode 100644 Documentation/devicetree/bin
This patch adds V4L2 sub-device driver for OV2680 image sensor.
The OV2680 is a 1/5" CMOS color sensor from Omnivision.
Supports output format: 10-bit Raw RGB.
The OV2680 has a single lane MIPI interface.
The driver exposes following V4L2 controls:
- auto/manual exposure,
- exposure,
- auto/manual
> On 22 Feb 2018, at 10.39, Matias Bjørling wrote:
>
> On 02/22/2018 08:47 AM, Javier Gonzalez wrote:
>>> On 22 Feb 2018, at 08.28, Matias Bjørling wrote:
>>>
On 02/21/2018 10:26 AM, Javier González wrote:
Both 1.2 and 2.0 specs define a field for media and controller
capabilit
On Wed, Feb 21, 2018 at 9:29 PM, Eric W. Biederman
wrote:
> Upon a cursory examinination the uid and gid of a fuse request are
> necessary for correct operation. Failing a fuse request where those
> values are not reliable seems a straight forward and reliable means of
> ensuring that fuse reques
1 - 100 of 952 matches
Mail list logo
