On Thu, 10 Jan 2019 at 21:53, Paweł Chmiel
wrote:
>
> This commit adds dmc nodes, which are needed by s5pv210 cpufreq driver
> to work.
>
> Signed-off-by: Paweł Chmiel
> ---
> arch/arm/boot/dts/s5pv210.dtsi | 12
> 1 file changed, 12 insertions(+)
>
Thanks, applied (actually I appl
On Tue, 8 Jan 2019 at 17:56, Paweł Chmiel
wrote:
>
> From: Jonathan Bakker
>
> This commit enables following devices present on Aries based phones:
> - pwm-vibrator attached to PWM 1
> - poweroff support
> - Atmel maXTouch touchscreen, connected to i2c2
> - Broadcom BCM4329 bluetooth over uart0
>
On Thu, Jan 10, 2019 at 11:29:20PM +0100, Florian Westphal wrote:
> Peter Zijlstra wrote:
> > Would using synchronize_rcu() not also mean you can get rid of that
> > xt_write_recseq*() stuff entirely?
>
> No, because those are used to synchronize with cpus that read
> the ruleset counters, see
>
On Tue, 8 Jan 2019 at 17:56, Paweł Chmiel
wrote:
>
> THis commit adds memory reservation required by MFC to run.
> On S5PV210 both regions needs to be on separate memory banks.
> Size of both regions is taken from stock sources.
>
> Signed-off-by: Paweł Chmiel
> ---
> Changes from v1:
>- Fixe
On Thu, Jan 10, 2019 at 01:56:41PM -0800, Bart Van Assche wrote:
> Hi Peter,
>
> Now that I had a closer look at your patch I think the approach of your patch
> is fine. Sorry for the confusion.
No problem; I'll try and write a coherent explanation in the Changelog
to help future readers.
On 2019-01-11 08:30:13 [+], Tang, Haoyu wrote:
> It doesn't consistent with document:
> https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
> I met an init which didn't accept unknown arguments.
Why are those a problem and nokaslr / nospectre_v2 / … are not?
> Haoyu
S
On Thu, Jan 10, 2019 at 11:24:28PM +0530, Nishad Kamdar wrote:
> Convert the GPIO driver to use the GPIO irqchip library
> GPIOLIB_IRQCHIP instead of reimplementing the same.
>
> Signed-off-by: Nishad Kamdar
> ---
> Changes in v5:
> - Restore "struct irq_chip irqc" in "struct gb_gpio_controller"
On Mon, Dec 17, 2018 at 10:34 PM Gustavo A. R. Silva
wrote:
> offset and lineinfo.line_offset are indirectly controlled by user-space,
> hence leading to a potential exploitation of the Spectre variant 1
> vulnerability.
>
> This issue was detected with the help of Smatch:
>
> drivers/gpio/gpioli
On Thu, 10 Jan 2019 at 19:57, Daniel Thompson
wrote:
>
> On Thu, Jan 10, 2019 at 05:54:57PM +0530, Sumit Garg wrote:
> > On ARM SoC's with TrustZone enabled, peripherals like entropy sources
> > might not be accessible to normal world (linux in this case) and rather
> > accessible to secure world
On Tue, Dec 18, 2018 at 04:51:58AM +, Nipun Gupta wrote:
> This patch also adds the iommu-map property in fsl-mc node, so
> that fsl-mc can use iommu.
>
> Signed-off-by: Nipun Gupta
> ---
> These patches are based over:
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git,
> as
Some multiport serial cards, such as the NI PXI-8430/2, NI PXI-8430/8,
and NI PXI-8432/4 use PCI_CLASS_COMMUNICATION_OTHER and this fail the
serial_pci_is_class_communication test added in the commit 7d8905d06405
("serial: 8250_pci: Enable device after we check black list").
Since these devices ar
On Thu, Jan 10, 2019 at 11:21:04PM +0530, Nishad Kamdar wrote:
> Use the gpiod interface instead of the deprecated old non-descriptor
> interface while continuing to ignore gpio flags from device tree in
> functions "deassert_reset()" and "assert_reset()" for now.
>
> Signed-off-by: Nishad Kamdar
On 11/01/2019 00:52, Kuninori Morimoto wrote:
...
>> It is still fragile. Again the machine driver could have incorrectly set
>> these 'allocated_platform/codecs' members as they are exposed to the
>> machine driver. You have no way to determine if the machine driver is
>> doing the correct thi
On Wed, Dec 19, 2018 at 7:00 AM William Breathitt Gray
wrote:
> This macro iterates for each 8-bit group of bits (clump) with set bits,
> within a bitmap memory region. For each iteration, "start" is set to the
> bit offset of the found clump, while the respective clump value is
> stored to the l
On 10/01/2019 16:48, Mark Brown wrote:
> On Thu, Jan 10, 2019 at 12:13:36PM +, Jon Hunter wrote:
>> On 09/01/2019 18:36, Mark Brown wrote:
>>> On Tue, Jan 08, 2019 at 05:28:14PM +, Jon Hunter wrote:
>
- struct snd_soc_dai_link_component *platform;
+ struct snd_soc_dai_link_co
On Thu, Jan 10, 2019 at 03:39:25PM -0500, Alan Stern wrote:
> On Wed, 9 Jan 2019, Paul Elder wrote:
>
> > This patch series adds a mechanism to allow asynchronously validating
> > the data stage of a control OUT request, and for stalling or suceeding
> > the request accordingly.
>
> One thing we
> -Original Message-
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: Friday, January 11, 2019 2:10 PM
> To: Nipun Gupta
> Cc: Leo Li ; robh...@kernel.org;
> mark.rutl...@arm.com; robin.mur...@arm.com; will.dea...@arm.com;
> linux-arm-ker...@lists.infradead.org; devicet...@vger.ke
On Thu, Jan 10, 2019 at 11:23:07PM +0530, Nishad Kamdar wrote:
> Use the gpiod interface instead of the deprecated old non-descriptor
> interface while continuing to ignore gpio flags from device tree in
> "svc_reset_onoff()" for now.
>
> Signed-off-by: Nishad Kamdar
> ---
> Changes in v5:
> -
We require gcc >= 4.6, so these can be removed.
Signed-off-by: Rasmus Villemoes
---
arch/x86/include/asm/bitops.h| 6 --
arch/x86/include/asm/string_32.h | 20
arch/x86/include/asm/string_64.h | 15 ---
3 files changed, 41 deletions(-)
diff --git a/arch
Nothing refers to the __constant_c_x_memset macro anymore, and when we
remove that, the two referenced static inline functions become orphan.
Signed-off-by: Rasmus Villemoes
---
arch/x86/include/asm/string_32.h | 84
1 file changed, 84 deletions(-)
diff --git a/
On Fri, Dec 21, 2018 at 6:33 PM Gregory CLEMENT
wrote:
> this small series fixes wrong pins configuration we currently have on
> Armada 37xx.
>
> For now it is especially annoying it we want to enable suspend to
> RAM for PCie.
All three patches applied for next (v5.1) with Miquel's
test tag.
Y
Hi Jon
> > Indeed there is such case so far, but my understanding is that current
> > driver should select "legacy style" or "modern style".
> > If driver setup it as "legacy", but access to "modern" member,
> > it is driver side bug, right ?
>
> Yes absolutely it is a driver bug, but looking a
On 2019/1/8 下午6:12, Jason Wang wrote:
On 2019/1/7 下午10:47, Michael S. Tsirkin wrote:
On Mon, Jan 07, 2019 at 02:58:08PM +0800, Jason Wang wrote:
On 2019/1/5 上午5:41, Michael S. Tsirkin wrote:
On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
This series tries to access virtqueue m
The user reported this problem, the upper application IO was
timeout when fstrim was running on this ocfs2 partition. the
application monitoring resource agent considered that this
application did not work, then this node was fenced by the cluster
brain (e.g. pacemaker).
The root cause is that fstr
It is unable to read the entry when it is the only one in
binary_bios_measurements:
00 00 00 00 08 00 00 00 c4 2f ed ad 26 82 00 cb
0010 1d 15 f9 78 41 c3 44 e7 9d ae 33 20 00 00 00 00
0020
This is obviously a firmware problem on my linux machine:
Manufacturer: Inspu
Change since V1:
- Add test results with LTP.
- Rewrite patch 1's commit header.
Here is the test result with LTP testcase ima_tpm.sh which is used
to verify binary_bios_measurements.
ima_tpm 1 TINFO: timeout per run is 0h 5m 0s
ima_tpm 1 TINFO: /proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc1+
The responsibility of tpm1_bios_measurements_start() is to walk
over the first *pos measurements, ensuring the skipped and
to-be-read measurements are not out-of-boundary.
Current logic is complicated a bit. Just employ a do-while loop
with necessary sanity check, and then get the goal.
Signed-of
On Thu, Jan 10, 2019 at 10:49:09AM -0500, Kyle Williams wrote:
> On Wed, Dec 12, 2018 at 12:37:09PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 07, 2018 at 08:47:21PM -0500, Kyle Williams wrote:
> > > From: Kyle Williams
> > >
> > > Description: enable the ability to disable LPM for all devi
On 19/12/2018 07.00, William Breathitt Gray wrote:
> +/**
> + * bitmap_set_value8 - set an 8-bit value within a memory region
> + * @bitmap: address to the bitmap memory region
> + * @value: the 8-bit value
> + * @start: bit offset of the 8-bit value
> + */
> +void bitmap_set_value8(unsigned long *
On 11/01/2019 03:53, Ganapatrao Kulkarni wrote:
> Hi Shameer,
>
> Patch looks OK to me, please feel free to add,
> Reviewed-by: Ganapatrao Kulkarni
>
> On Thu, Dec 13, 2018 at 5:25 PM Marc Zyngier wrote:
>>
>> On 13/12/2018 10:59, Shameer Kolothum wrote:
>>> From: Shanker Donthineni
>>>
>>> Th
On 1/11/19 10:17 AM, Marcos Paulo de Souza wrote:
ping?
On Sat, Dec 22, 2018 at 08:08:45AM -0200, Marcos Paulo de Souza wrote:
bio_alloc_bioset return a bio pointer or NULL, so we can avoid storing
the returned data into a new variable.
Signed-off-by: Marcos Paulo de Souza
Add Jens to cc
Hi Mark,
On 10/01/2019 14:27, Mark Rutland wrote:
> The perf tool uses /proc/sys/kernel/perf_event_mlock_kb to determine how
> large its ringbuffer mmap should be. This can be configured to arbitrary
> values, which can be larger than the maximum possible allocation from
> kmalloc.
>
> When this
On Thu, Jan 10, 2019 at 01:10:25PM +0530, Sabyasachi Gupta wrote:
> Remove unusual_sddr55.h which is included more than once
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/sddr55.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/usb/storage/sddr55.c b/drivers/us
Hi Alan,
On Thursday, January 10, 2019, Alan wrote:
>
> On Thu, 10 Jan 2019, Ran Wang wrote:
>
> > Hi Alan,
> >
> > > -Original Message-
> > > From: Alan Stern
> > > Sent: Wednesday, January 09, 2019 23:14
> > > To: Ran Wang
> > > Cc: Greg Kroah-Hartman ; linux-
> > > u...@vger.kernel.
On Thu, Jan 10, 2019 at 12:40:07PM +0530, Sabyasachi Gupta wrote:
> Remove duplicate headers which are included more than once.
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/datafab.c| 1 -
> drivers/usb/storage/ene_ub6250.c | 1 -
> 2 files changed, 2 deletions(-)
>
> dif
On Thu, Jan 10, 2019 at 12:19:36PM +0530, Sabyasachi Gupta wrote:
> Remove unusual_cypress.h which is included more than once.
>
> Signed-off-by: Sabyasachi Gupta
> ---
> drivers/usb/storage/cypress_atacb.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/usb/storage/cypress_atac
On Tue, Jan 08, 2019 at 12:34:17PM -0500, Alan Stern wrote:
> On Wed, 9 Jan 2019, Kai Heng Feng wrote:
>
> > > On Jan 8, 2019, at 11:41 PM, Greg KH wrote:
> > >
> > > On Mon, Dec 03, 2018 at 06:26:43PM +0800, Kai-Heng Feng wrote:
> > >> USB Bluetooth controller QCA ROME (0cf3:e007) sometimes sto
On Thu, Jan 10, 2019 at 12:02:05PM -0500, Konrad Rzeszutek Wilk wrote:
> Why not use swiotlb_nr_tbl ? That is how drivers/gpu/drm use to figure if they
> need to limit the size of pages.
That function just exports the overall size of the swiotlb aperture, no?
What I need here is the maximum size f
On Tue, Dec 18, 2018 at 05:07:46PM +0100, Alexandre Belloni wrote:
> Use a generic node name for the m25p80 flashes on ls1043 and ls1046 boards.
>
> Signed-off-by: Alexandre Belloni
Applied all (not MAINTAINERS patch), thanks.
On 11/01/2019 08:51, Kuninori Morimoto wrote:
>>> Indeed there is such case so far, but my understanding is that current
>>> driver should select "legacy style" or "modern style".
>>> If driver setup it as "legacy", but access to "modern" member,
>>> it is driver side bug, right ?
>>
>> Yes absol
On Fri, Jan 11, 2019 at 11:29:31AM +0800, Jason Wang wrote:
> Just wonder if my understanding is correct IOMMU_PLATFORM must be set for
> all virtio devices under AMD-SEV guests?
Yes, that is correct. Emulated DMA can only happen on the SWIOTLB
aperture, because that memory is not encrypted. The g
On Thu, Jan 10, 2019 at 10:24:31AM -0500, Sasha Levin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>
> Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>
> are available in the Git repository at:
>
> git
On Fri, Jan 11, 2019 at 04:06:52PM +0800, Zhenzhong Duan wrote:
>
> On 2019/1/10 22:43, Waiman Long wrote:
> > On 01/10/2019 03:02 AM, Zhenzhong Duan wrote:
> > > Hi Maintainer,
> > >
> > >
> > > There is a question confused me for days. Appreciate an answer.
> > >
> > > In below code, the comm
On Thu, Jan 10, 2019 at 10:21:00AM -0800, Todd Kjos wrote:
> To allow servers to verify client identity, allow a node
> flag to be set that causes the sender's security context
> to be delivered with the transaction. The BR_TRANSACTION
> command is extended in BR_TRANSACTION_SEC_CTX to
> contain a
On 2019-01-10 21:16, Sam Ravnborg wrote:
> Hi Peter.
>
> (Hijacking this thread as I lost the orginal mails)
Assuming you wanted to reply to this patch?
https://patchwork.kernel.org/patch/10753571/
>>> I found an unfortunate issue while recoding plane handling to use
>>> drm_atomic_helper_check_
On Fri, Jan 11, 2019 at 9:19 AM Ivan Mironov wrote:
>
> On Wed, 2019-01-09 at 15:52 +, Sasha Levin wrote:
> > Hi,
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a "Fixes:" tag,
> > fixing commit: 79e539453b34 DRM: i915: add mode setting support.
Hi,
This commit introduces the frequency constraint infrastructure, which
provides a generic interface for parts of the kernel to constraint the
working frequency range of a device.
The primary users of this are the cpufreq and devfreq frameworks. The
cpufreq framework already implements such con
This commit introduces the frequency constraint infrastructure, which
provides a generic interface for parts of the kernel to constraint the
working frequency range of a device.
The primary users of this are the cpufreq and devfreq frameworks. The
cpufreq framework already implements such constrai
This implements the frequency constraint callback and registers it with
the freq-constraint framework whenever a policy is created. On policy
removal the callback is unregistered.
The constraints are also taken into consideration in
cpufreq_set_policy().
No constraints are added until now though.
This implements the FREQ_CONSTRAINT_USER constraint and removes the old
style of doing the same. We just need to update the constraint on any
modifications to scaling_{min|max}_frequency and the freq-constraint
core will call cpufreq's callback which will call cpufreq_set_policy()
eventually.
Sign
On Wed, Jan 02, 2019 at 12:32:19PM +0100, Christian Brauner wrote:
> The binderfs instance in the initial ipc namespace will always have a
> reserve of 4 binder devices unless explicitly capped by specifying a lower
> value via the "max" mount option.
> This ensures when binder devices are removed
Add hostld_flags and hostld_libs shorthands. No function change.
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.host | 23 +--
1 file changed, 13 insertions(+), 10 deletions(-)
diff --git a/scripts/Makefile.host b/scripts/Makefile.host
index 0393f75..f2e15de 100644
---
GCC-plugin is the only user of the shared library build rules in
scripts/Makefile.host. Hence, those rules do not need to be treewide
available.
The build rules in scripts/Makefile.host are written in a too generic
way. I guess the main reason is because commit 24403874316a ("Shared
library suppor
On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK Hu wrote:
> Hi, Daniel:
>
> On Thu, 2019-01-10 at 21:02 +0100, Daniel Vetter wrote:
> > On Thu, Jan 10, 2019 at 08:01:37PM +0100, Frank Wunderlich wrote:
> > > Hi Daniel,
> > >
> > > > > Would be good to use the new generic fbdev emulation code here, f
Hi,
Manu Gautam writes:
>> Manu Gautam writes:
>>> If a function driver tries to re-submit an already queued request,
>>> it can results in corruption of pending/started request lists.
>>> Catch such conditions and fail the request submission to DCD.
>>>
>>> Signed-off-by: Manu Gautam
>>> ---
Add missing vin-supply 5V regulator node on usb_phy nodes needed
to power usb bus ports. Override the dr_mode from "host" to "peripheral"
for initialization of dwc2 usb0 phy node,changes fix the below
warning for usb initialization.
[1.203900] phy phy-c000.phy.0: USB ID detect failed!
[
On Fri 11-01-19 11:12:45, Pingfan Liu wrote:
[...]
> Hi, this patch works! Feel free to use tested-by me
Thanks a lot for your testing! Now it is time to seriously think whether
this is the right thing to do and sync all other arches that might have
the same problem. I will take care of it. Thanks
On Thu, Jan 10, 2019 at 04:26:27PM -0800, Vineet Gupta wrote:
> @@ -246,7 +246,7 @@ static __always_inline void __assign_bit(long nr,
> volatile unsigned long *addr,
> new__ = (old__ & ~mask__) | bits__; \
> } while (cmpxchg(ptr, old__, new__) != old__); \
Make header files alphabetical order.
Signed-off-by: Loic Pallardy
---
drivers/rpmsg/virtio_rpmsg_bus.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
index 664f957012cd..e1d563fbfe65 1006
On Thu, Jan 10, 2019 at 12:55 AM Paolo Abeni wrote:
>
> On Thu, 2019-01-10 at 09:25 +0100, Ian Kumlien wrote:
> > This works, and so does:
> > https://marc.info/?l=linux-netdev&m=154696956604748&w=2
> >
> > Pointed out by Paolo (tested both separately)
>
> Note: I cleared the tstamp in br_forwa
On Wed, Jan 2, 2019 at 10:00 AM wrote:
> From: "chuanjia.liu"
>
> Virtual gpio only used inside SOC and not being exported to outside SOC.
> Some modules use virtual gpio as eint and doesn't need SMT.
> So this patch add EINT support to virtual GPIOs.
>
> Signed-off-by: chuanjia.liu
> ---
> cha
On Thu, Jan 3, 2019 at 4:11 PM Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
> automatic base selection") the gpiochip label no longer has an ID
> suffix. Update the GPIO lookup entries.
>
> Fixes: 587f7a694f01 ("
On Fri, Jan 11, 2019 at 12:52:19PM +0530, Sumit Garg wrote:
> On Thu, 10 Jan 2019 at 19:49, Daniel Thompson
> wrote:
> > > +static int get_devices(struct tee_context *ctx, u32 session,
> > > +struct tee_shm *device_uuid, u32 *shm_size)
> >
> > Missing const on device_uuid?
> >
On 11-01-19, 09:32, Krzysztof Kozlowski wrote:
> On Thu, 10 Jan 2019 at 21:53, Paweł Chmiel
> wrote:
> >
> > This commit adds dmc nodes, which are needed by s5pv210 cpufreq driver
> > to work.
> >
> > Signed-off-by: Paweł Chmiel
> > ---
> > arch/arm/boot/dts/s5pv210.dtsi | 12
> > 1
On Fri, Dec 21, 2018 at 5:23 PM Jerome Brunet wrote:
>
> On platforms making a fair use of regulators, the dev_info() messages
> coming from the device link function are a bit too verbose. The amount
> of message will increase further with the clock framework joining the
> device link party.
>
> T
On Thu, Jan 10, 2019 at 06:13:47AM +, Sidong Yang wrote:
> Removed unnecessary local variable in have_hgsmi_mode_hints.
> The result of hgsmi_query_conf should be directly compared without
> assigning to local variable.
>
> Signed-off-by: Sidong Yang
> ---
> drivers/staging/vboxvideo/vbox_ma
Hi Shameer,
On 13/12/2018 10:59, Shameer Kolothum wrote:
From: Shanker Donthineni
The NUMA node information is visible to ITS driver but not being used
other than handling hardware errata. ITS/GICR hardware accesses to the
local NUMA node is usually quicker than the remote NUMA node. How slow
Hello,
syzbot found the following crash on:
HEAD commit:b808822a75a3 Add linux-next specific files for 20190111
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=179c22f740
kernel config: https://syzkaller.appspot.com/x/.config?x=c052ead0aed5001b
Hello,
syzbot found the following crash on:
HEAD commit:1bdbe2274920 Merge tag 'vfio-v5.0-rc2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=113a7310c0
kernel config: https://syzkaller.appspot.com/x/.config?x=edf1c3031097c304
da
The AM65 SoC has 2MB MSMC RAM. Add this as a mmio-sram
node so drivers can use it via genpool API.
Following areas are marked reserved:
- Lower 128KB for ATF
- 64KB@0xf for SYSFW
- Upper 1MB for cache
The reserved locations are subject to change at runtime by
the bootloader.
Cc: Nishanth Men
On Thu, 10 Jan 2019 at 21:53, Paweł Chmiel
wrote:
>
> There is possibility, that when probing driver, regulators are not yet
> initialized. In this case we should return EPROBE_DEFER and wait till
> they're initialized, since they're required currently for cpufreq driver
> to work. Also move regul
On Fri, 11 Jan 2019 at 10:41, Viresh Kumar wrote:
>
> On 11-01-19, 09:32, Krzysztof Kozlowski wrote:
> > On Thu, 10 Jan 2019 at 21:53, Paweł Chmiel
> > wrote:
> > >
> > > This commit adds dmc nodes, which are needed by s5pv210 cpufreq driver
> > > to work.
> > >
> > > Signed-off-by: Paweł Chmiel
On Fri, Jan 11, 2019 at 10:18 AM Viresh Kumar wrote:
>
> Hi,
>
> This commit introduces the frequency constraint infrastructure, which
> provides a generic interface for parts of the kernel to constraint the
> working frequency range of a device.
>
> The primary users of this are the cpufreq and d
Hi, Daniel:
On Fri, 2019-01-11 at 10:20 +0100, Daniel Vetter wrote:
> On Fri, Jan 11, 2019 at 11:20:09AM +0800, CK Hu wrote:
> > Hi, Daniel:
> >
> > On Thu, 2019-01-10 at 21:02 +0100, Daniel Vetter wrote:
> > > On Thu, Jan 10, 2019 at 08:01:37PM +0100, Frank Wunderlich wrote:
> > > > Hi Daniel,
>
On 11.01.2019 10:11, Luis de Oliveira wrote:
>
>
> On 11-Jan-19 7:25, eugen.hris...@microchip.com wrote:
>>
>>
>> On 10.01.2019 18:18, Luis de Oliveira wrote:
>>>
>>>
>>> On 09-Jan-19 13:07, eugen.hris...@microchip.com wrote:
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add th
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el
acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico
se actualizará
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
nuestros propietarios de cuentas de correo electrónico. Estamos eliminando el
acceso a todos nuestros clientes de correo web. Su cuenta de correo electrónico
se actualizará
On Fri, Jan 11, 2019 at 10:35 AM Eric Dumazet wrote:
> On Thu, Jan 10, 2019 at 12:55 AM Paolo Abeni wrote:
> > On Thu, 2019-01-10 at 09:25 +0100, Ian Kumlien wrote:
>
>
> > > This works, and so does:
> > > https://marc.info/?l=linux-netdev&m=154696956604748&w=2
> > >
> > > Pointed out by Paolo (
On Fri, 11 Jan 2019 at 15:09, Daniel Thompson
wrote:
>
> On Fri, Jan 11, 2019 at 12:52:19PM +0530, Sumit Garg wrote:
> > On Thu, 10 Jan 2019 at 19:49, Daniel Thompson
> > wrote:
> > > > +static int get_devices(struct tee_context *ctx, u32 session,
> > > > +struct tee_shm *devi
Currently, the 'firmware' directory only contains a single Makefile
to embed extra firmware into the kernel.
Move it to the more relevant place.
Signed-off-by: Masahiro Yamada
---
Makefile | 2 +-
drivers/base/firmware_loader/Makefile
The whole code of fallback_table.c is surrounded by #ifdef of
CONFIG_FW_LOADER_USER_HELPER.
Move the CONFIG_FW_LOADER_USER_HELPER switch to Makefile so that
it is not compiled at all when this CONFIG option is disabled.
I also removed the confusing comment, "Module or buit-in [sic]".
CONFIG_FW_LO
Hi PeterA,
The Cover leter has this:
> 5.Update memory-barriers.txt on enforcing heavy ordering for
> port-I/O accesses, courtesy of Will Deacon. This one needs
> an ack, preferably by someone from Intel. Matthew Wilcox
> posted some feedback from an Intel manual here, w
Hi,
On 19/12/2018 18:23, Valentin Schneider wrote:
> In [1] Peter had a suggestion to broadly mute hotplug lockdep warnings during
> init instead of going after every single warning and wrapping them with
> cpus_read_{lock, unlock}(). This is implemented in [PATCH 1/2].
>
> [PATCH 2/2] is a logic
pt., 11 sty 2019 o 10:46 Krzysztof Kozlowski napisał(a):
>
> On Thu, 10 Jan 2019 at 21:53, Paweł Chmiel
> wrote:
> >
> > There is possibility, that when probing driver, regulators are not yet
> > initialized. In this case we should return EPROBE_DEFER and wait till
> > they're initialized, since
On Mon, Jan 7, 2019 at 4:42 PM Thomas Petazzoni
wrote:
> This patch almost solves the problem. It doesn't work as-is, because it
> assumes that runtime PM is used by all GPIO controllers, which is not
> the case. When runtime PM is not enabled, pm_runtime_get_sync() fails
> with -EACCES, and the
On Fri, Jan 11, 2019 at 01:00:49PM +0530, Sumit Garg wrote:
> On Thu, 10 Jan 2019 at 19:53, Daniel Thompson
> wrote:
> > > diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> > > index 9ddb89e..5d6c317 100644
> > > --- a/drivers/tee/tee_core.c
> > > +++ b/drivers/tee/tee_core.c
> > > @@
Hi Gang,
On 2019/1/11 17:01, Gang He wrote:
> The user reported this problem, the upper application IO was
> timeout when fstrim was running on this ocfs2 partition. the
> application monitoring resource agent considered that this
> application did not work, then this node was fenced by the cluste
On Fri, 11 Jan 2019 at 15:24, Daniel Thompson
wrote:
>
> On Fri, Jan 11, 2019 at 01:00:49PM +0530, Sumit Garg wrote:
> > On Thu, 10 Jan 2019 at 19:53, Daniel Thompson
> > wrote:
> > > > diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> > > > index 9ddb89e..5d6c317 100644
> > > > ---
On Fri, Jan 11, 2019 at 06:52:00PM +0900, Masahiro Yamada wrote:
> Currently, the 'firmware' directory only contains a single Makefile
> to embed extra firmware into the kernel.
>
> Move it to the more relevant place.
So this moves any "build in" firmware to need to be placed in
drivers/base/firm
On Thu, Jan 10, 2019 at 03:40:04PM -0800, Dave Hansen wrote:
> Anything else you do will have *some* reduced mitigation value, which
> isn't a deal-breaker (to me at least). Some ideas:
>
> Take a look at the SWITCH_TO_KERNEL_CR3 in head_64.S. Every time that
> gets called, we've (potentially) j
Hi,
The AM654 SoC supports 2 DWC3 USB controller instances. The
AM654 base board supports the 2nd (USB1) instance in high-speed.
This series enables support for USB1 instance on the AM654-base-board.
To test, you need to first apply the below 2 series.
AM654 USB2 PHY support https://lkml.org/lk
From: Jyri Sarha
Main System control module support is added to the device tree to allow
driver to access to their control module registers.
Signed-off-by: Jyri Sarha
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 8
1 file changed, 8 insertions(+)
diff
Adds support for USB0 and USB1 instances on the AM6 SoC.
USB0 is limited to high-speed for now.
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 80
1 file changed, 80 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
Add pinmux for USB1 and enable it as a dual role port.
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
b/arch/arm64/boot/dts/ti/k3-am654-base-
On Thu, Jan 10, 2019 at 11:21:16PM +, Esme wrote:
> Attached is a fairly small C repro I did not see any references to
> this possible flaw (unchecked MSR access) in relation to
> __NR_perf_event_open
>
> Attached is the config directly extracted from proc. This is the call
> stack in relatio
On Thu, Dec 20, 2018 at 03:47:28PM +, Tom Murphy wrote:
> Ah shoot, it looks like I forgot to change flush_tlb_all -> flush_iotlb_all
>
> Should I submit another patch?
Yes, please.
Hello,
On 09/01/2019 10:59:40+, oliver.r...@wago.com wrote:
> The Ricoh chips have slightly different register layouts
> and the r2221 chip uses bit 5 as the oscillator halt sensor bit.
>
> Signed-off-by: Olive Rohe
> ---
> drivers/rtc/rtc-rs5c372.c | 32 +---
>
On Fri, Jan 11, 2019 at 10:18:18AM +0100, Greg KH wrote:
> On Wed, Jan 02, 2019 at 12:32:19PM +0100, Christian Brauner wrote:
> > The binderfs instance in the initial ipc namespace will always have a
> > reserve of 4 binder devices unless explicitly capped by specifying a lower
> > value via the "m
On Fri, Jan 11, 2019 at 2:13 PM Chao Fan wrote:
>
> On Fri, Jan 11, 2019 at 01:12:51PM +0800, Pingfan Liu wrote:
> >This patch identifies the point where memblock alloc start. It has no
> >functional.
> [...]
> >+#ifdef CONFIG_MEMORY_HOTPLUG
> >+ /*
> >+ * Memory used by the kernel cann
On Fri, Jan 11, 2019 at 1:31 PM Chao Fan wrote:
>
> On Fri, Jan 11, 2019 at 01:12:52PM +0800, Pingfan Liu wrote:
> >The current acpi_table_upgrade() relies on initrd_start, but this var is
> >only valid after relocate_initrd(). There is requirement to extract the
> >acpi info from initrd before me
101 - 200 of 1414 matches
Mail list logo
