Hi Rob,
On 08/03/2019 00:13, Rob Herring wrote:
> On Fri, Feb 1, 2019 at 6:08 AM Neil Armstrong wrote:
>>
>> Add support for SCDC Setup for TMDS Clock > 3.4GHz and enable TMDS
>> Scrambling when supported or mandatory.
>>
>> This patch also adds an helper to setup the control bit to support
>>
On Fri, 2019-03-08 at 08:54 +0100, Paolo Bonzini wrote:
> On 08/03/19 07:10, Xiaoyao Li wrote:
> > > so that non-virtualizable features are hidden and
> > >
> > > if (boot_cpu_has(X86_FEATURE_SPLIT_LOCK_DETECT))
> > > data |= CORE_CAP_SPLIT_LOCK_DETECT;
> > >
> > > so that userspace
On 08/03/2019 08.01, Leon Romanovsky wrote:
>
> Mathematical therm for discrete numbers greater or equal to zero is
> "normal numbers".
Sorry, WHAT? "Normal" is used and abused for a lot of things in
mathematics, but I have never heard it used that way. When attached to
the word "number", it
Probably more a lockdep than XFS thing..
On Fri, Mar 01, 2019 at 11:06:04PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:c63e9e91a254 Add linux-next specific files for 20190301
> git tree: linux-next
> console output:
Marc Zyngier writes:
> For quite some time, I wondered why the PCI mwifiex device built in my
> Chromebook was unable to use the good old legacy interrupts. But as MSIs
> were working fine, I never really bothered investigating. I finally had a
> look, and the result isn't very pretty.
>
> On
Quoting Nathan Chancellor (2019-03-08 01:20:24)
> When building with -Wsometimes-uninitialized, Clang warns:
>
> drivers/gpu/drm/i915/i915_request.c:1032:6: warning: variable 'this_cpu'
> is used uninitialized whenever '&&' condition is false
> [-Wsometimes-uninitialized]
>
> time_after expands
On Fri, Mar 8, 2019 at 2:51 PM Jay Vosburgh wrote:
>
> Bo YU wrote:
>
> >There are some warning when:
> >
> >sudo make C=1 CF=-D__CHECK_ENDIAN__ drivers/net/bonding/
> >
> >drivers/net/bonding/bond_main.c:2438:40: warning: incorrect type in
> >assignment (different base types)
>
On Sun, Mar 3, 2019 at 8:47 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
On 2019/3/7 下午11:34, Michael S. Tsirkin wrote:
On Thu, Mar 07, 2019 at 10:45:57AM +0800, Jason Wang wrote:
On 2019/3/7 上午12:31, Michael S. Tsirkin wrote:
+static void vhost_set_vmap_dirty(struct vhost_vmap *used)
+{
+ int i;
+
+ for (i = 0; i < used->npages; i++)
+
runtime pm calls as part of ufshcd_init() can trigger a
ufshcd_runtime_suspend() which always fails until the point
we do a platform_set_drvdata(), setting the devices 'power.runtime_error'
Use pm_runtime_get_noresume()/pm_runtime_put_noidle() to prevent
this from happening.
Signed-off-by:
Add an error check for pm_runtime_get_sync(), ignoring this can
hide issues with the runtime pm handling in the driver.
Signed-off-by: Rajendra Nayak
---
drivers/scsi/ufs/ufshcd.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/scsi/ufs/ufshcd.c
These are some runtime pm fixes I stumbled upon while
working on adding support for controlling multiple
power domains (needed on qualcomm sdm845 platforms)
in the ufshcd-pltfrm driver.
Rajendra Nayak (3):
scsi: ufs: Fix runtime pm handling in ufshcd-pltfrm
scsi: ufs: Add error checks for
Doing a runtime pm get/put as part of ufs_qcom_testbus_config()
seems completely unnecessary, since this is called only early
during ufs_qcom_init() when the runtime operations are not
completely setup for ufs runtime suspend/resume to even work.
Signed-off-by: Rajendra Nayak
---
On Thu, Mar 07, 2019 at 05:35:46PM -0800, Vineet Gupta wrote:
> - ARCv2 LLSC based spinlocks smp_mb() both before and after the LLSC
>instructions, which is not required per lkmm ACQ/REL semantics.
>smp_mb() is only needed _after_ lock and _before_ unlock.
>So remove the extra
Am 08.03.19 um 04:51 schrieb Randy Dunlap:
On 3/7/19 1:11 PM, Tobin C. Harding wrote:
Current RST file contains an unknown directive causing Sphinx to emit
ERROR: Unexpected indentation.
Use normal language construct instead.
Signed-off-by: Tobin C. Harding
This is a good idea.
On Wed, Mar 06, 2019 at 03:50:16PM +, Steven Price wrote:
> walk_page_range() is going to be allowed to walk page tables other than
> those of user space. For this it needs to know when it has reached a
> 'leaf' entry in the page tables. This information is provided by the
> p?d_large()
On Thu, Mar 07, 2019 at 05:35:46PM -0800, Vineet Gupta wrote:
> @@ -68,8 +72,6 @@ static inline void arch_spin_unlock(arch_spinlock_t *lock)
> smp_mb();
>
> lock->slock = __ARCH_SPIN_LOCK_UNLOCKED__;
> -
> - smp_mb();
> }
>
> /*
> @@ -226,8 +218,6 @@ static inline void
Здравейте,
Ваучерите за храна се нареждат сред любимите социални придобивки на работещите
хора и сред най-предпочитаните начини за стимулиране от работодателите. Те
подобряват ефективността и производителността на Вашите служители.
Благодарение на ваучерите за храна реализирате спестявания –
On Thu, Mar 07, 2019 at 05:35:46PM -0800, Vineet Gupta wrote:
> - ARCv2 LLSC based spinlocks smp_mb() both before and after the LLSC
>instructions, which is not required per lkmm ACQ/REL semantics.
>smp_mb() is only needed _after_ lock and _before_ unlock.
>So remove the extra
Am 07.03.19 um 22:11 schrieb Tobin C. Harding:
Hi,
I had a few hours to spare so I thought I'd clear some Sphinx build
warnings/errors. There isn't anything too controversial here. The only
interesting thing I hit was in patch 7 (docs: Remove unknown 'hint'
directive), I couldn't work out
On Thu, Mar 07, 2019 at 05:45:26PM -0700, Nathan Chancellor wrote:
> Hi all,
>
> We are trying to get Clang's -Wsometimes-uninitialized turned on for the
> kernel as it can catch some bugs that GCC can't. This warning came up:
>
> drivers/tty/serial/qcom_geni_serial.c:1079:6: warning: variable
Hi Linus,
plese pull the dma-mapping updates below.
There are various conflicts this time. Most of them are Kconfig conflicts
that just have changes right next to each other, where you should take both.
Additionally the powerpc tree that is now merged switched the powerpc code
to use the
hi Russell, Ulf
On 3/7/19 5:46 PM, Russell King - ARM Linux admin wrote:
On Thu, Mar 07, 2019 at 05:39:02PM +0100, Ludovic Barre wrote:
- if (data->flags & MMC_DATA_READ)
- datactrl |= MCI_DPSM_DIRECTION;
Given that this is currently an invariant between all, it doesn't
Hi, Bibby:
On Wed, 2019-03-06 at 17:50 +0800, Bibby Hsieh wrote:
> cmdq driver provide a function that get event number
> from device node for client.
I think device tree is based on the view of hardware design, so you need
not to mention how the driver design.
Client hardware would send event
On 2019/3/8 上午3:16, Andrea Arcangeli wrote:
On Thu, Mar 07, 2019 at 12:56:45PM -0500, Michael S. Tsirkin wrote:
On Thu, Mar 07, 2019 at 10:47:22AM -0500, Michael S. Tsirkin wrote:
On Wed, Mar 06, 2019 at 02:18:12AM -0500, Jason Wang wrote:
+static const struct mmu_notifier_ops
Hi Joel,
On Thu, Mar 7, 2019 at 4:03 PM Joel Fernandes wrote:
> On Thu, Mar 07, 2019 at 09:58:24AM +0100, Geert Uytterhoeven wrote:
> > On Fri, Mar 1, 2019 at 5:10 PM Joel Fernandes (Google)
> > wrote:
> > > Introduce in-kernel headers and other artifacts which are made available
> > > as an
On Thu, Mar 07, 2019 at 03:36:28PM -0700, Nathan Chancellor wrote:
> When building with -Wsometimes-uninitialized, Clang warns:
>
> drivers/pwm/pwm-img.c:126:13: error: variable 'timebase' is used
> uninitialized whenever 'if' condition is false
> [-Werror,-Wsometimes-uninitialized]
>
> The
When ep_busy_loop() is called, timed_out is always zero,
otherwise ep_poll() would return first.
Signed-off-by: Peng Wang
---
fs/eventpoll.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/eventpoll.c b/fs/eventpoll.c
index a5d219d920e7..0b3981ffc7ae 100644
---
On Fri, Mar 08, 2019 at 09:31:00AM +0100, Linus Walleij wrote:
> On Sun, Mar 3, 2019 at 8:47 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
On Fri, 8 Mar 2019 at 00:49, Russell King - ARM Linux admin
wrote:
>
> On Thu, Mar 07, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote:
> > On Thu, Mar 7, 2019 at 1:15 AM Arnd Bergmann wrote:
> > >
> > > Passing registers containing zero as both the address (NULL pointer)
> > > and data into
Hi,
On 08-03-19 01:04, Srinivas Pandruvada wrote:
On Thu, 2019-03-07 at 15:07 -0800, Rajat Jain wrote:
Hello,
On Thu, Mar 7, 2019 at 12:37 PM Hans de Goede
wrote:
Hi,
On 07-03-19 21:27, Gwendal Grignou wrote:
Srinivas,
I am looking at problem on a laptop machine that suspends to
S01x,
Hello Nathan,
the copy of my mail sent to clang-built-li...@googlegroups.com was not
accepted. (So I dropped this address from the recipients for this
reply.) Probably this list isn't open for non-members to post to. This
is a bit annoying, so I ask you to either fix that or don't add this
On 2019/3/8 上午3:17, Jerome Glisse wrote:
On Thu, Mar 07, 2019 at 12:56:45PM -0500, Michael S. Tsirkin wrote:
On Thu, Mar 07, 2019 at 10:47:22AM -0500, Michael S. Tsirkin wrote:
On Wed, Mar 06, 2019 at 02:18:12AM -0500, Jason Wang wrote:
+static const struct mmu_notifier_ops
On 08/03/2019 08:26, Kalle Valo wrote:
> Marc Zyngier writes:
>
>> For quite some time, I wondered why the PCI mwifiex device built in my
>> Chromebook was unable to use the good old legacy interrupts. But as MSIs
>> were working fine, I never really bothered investigating. I finally had a
>>
On Tue, Mar 5, 2019 at 1:09 AM Randy Dunlap wrote:
> On 3/4/19 4:03 PM, Enrico Weigelt, metux IT consult wrote:
> > On 04.03.19 21:19, Arnd Bergmann wrote:
> >> LEDS_GPIO can only be selected when LEDS_CLASS is already enabled:
> >>
> >> WARNING: unmet direct dependencies detected for LEDS_GPIO
>
On Mon, Mar 4, 2019 at 9:09 PM Arnd Bergmann wrote:
> The driver was newly introduced but the version that got merged
> produces a harmless compiler warning:
>
> drivers/platform/x86/pcengines-apuv2.c: In function 'apu_board_init':
> drivers/platform/x86/pcengines-apuv2.c:211:6: error: unused
On 2019/3/8 上午5:27, Andrea Arcangeli wrote:
Hello Jerome,
On Thu, Mar 07, 2019 at 03:17:22PM -0500, Jerome Glisse wrote:
So for the above the easiest thing is to call set_page_dirty() from
the mmu notifier callback. It is always safe to use the non locking
variant from such callback. Well it
The issue happens with following steps:
Access usb3.0/3.1 device that uses uas driver.
Power off hub port connecting device by ioctl(USBDEVFS_CONTROL).
Wait longer than 30s(scsi layer timeout period is 30s).
Execute commands like lsusb, no response and usb subsytem hangs.
After scsi layer
Üdvözlöm!
2019-től a legtöbb kiegészítő juttatás jövedelemként fog adózni (kivételt képez
a SZÉP kártya).
Juttatási kártyáinknak köszönhetően könnyebben nyerhet meg új tehetségeket,
könnyebben tarthatja meg dolgozóit, és növelheti motivációjukat.
Kártyáink tetszőleges célokra használhatók
Hi Tom,
On Thu, Mar 7, 2019 at 10:38 PM Tom Li wrote:
> On Thu, Mar 07, 2019 at 10:39:23AM +0100, Geert Uytterhoeven wrote:
> > On Thu, Mar 7, 2019 at 10:00 AM Jani Nikula
> > wrote:
> > > It's possible to do this using a reboot notifier. I am not sure if there
> > > are better ways to achieve
Hi Sergei,
On Thu, Mar 7, 2019 at 6:50 PM Sergei Shtylyov
wrote:
> On 01/28/2019 09:49 AM, Mason Yang wrote:
> > Add a driver for Renesas R-Car Gen3 RPC-IF SPI controller.
> >
> > Signed-off-by: Mason Yang
> > Signed-off-by: Sergei Shtylyov
> [...]
> > diff --git
On 04/03/19 19:56, Sean Christopherson wrote:
> On Tue, Jan 29, 2019 at 04:19:34PM +0100, Paolo Bonzini wrote:
>> On 28/01/19 11:33, Yang Weijiang wrote:
There is no code in this series to pass these fields to and from
userspace, and also to save/restore U_CET, INT_SSP_TAB, PL0_SSP and
On 2019/3/8 上午11:45, Jerome Glisse wrote:
On Thu, Mar 07, 2019 at 10:43:12PM -0500, Michael S. Tsirkin wrote:
On Thu, Mar 07, 2019 at 10:40:53PM -0500, Jerome Glisse wrote:
On Thu, Mar 07, 2019 at 10:16:00PM -0500, Michael S. Tsirkin wrote:
On Thu, Mar 07, 2019 at 09:55:39PM -0500, Jerome
Since commit 3812b8c5c5d5 ("kbuild: make -r/-R effective in top
Makefile for old Make versions"), make-kpkg is not working.
make-kpkg directly includes the top Makefile of Linux kernel, and
appends some debian_* targets.
/usr/share/kernel-package/ruleset/kernel_version.mk:
# Include the
On Tue, Mar 5, 2019 at 4:19 PM Jan Kundrát wrote:
> This commit should probably go to 5.0-stable and 4.20-stable as well
I doubt that this commit is fixing a regression, but who knows...
> If I cherry-pick the following two commits to my 5.0, my board boots once
> again:
>
> 16f4372fd7a5
On Mon, Feb 25, 2019 at 02:54:13PM +0100, Ulf Hansson wrote:
> This looks good to me, however the lack of feedback/tests worries me a
> bit. So, unless you think it's a bad idea, I intend to apply this when
> v5.1 rc1 is out, which allows a lengthy test period in linux-next.
Please don't rush to
On Fri, Mar 8, 2019 at 10:56 AM William Breathitt Gray
wrote:
> On Fri, Mar 08, 2019 at 09:31:00AM +0100, Linus Walleij wrote:
> > On Sun, Mar 3, 2019 at 8:47 AM William Breathitt Gray
> > wrote:
> >
> > > This macro iterates for each 8-bit group of bits (clump) with set bits,
> > > within a
On 07.03.19 00:27, Dominique Martinet wrote:
> Enrico Weigelt, metux IT consult wrote on Wed, Mar 06, 2019:
>> Signed-off-by: Enrico Weigelt, metux IT consult
>
> I don't mind trivial patches but please resend with a description of
> what is done (change spaces to tabs) in the commit message.
On 08/03/2019 03:07, Andy Tang wrote:
>
>
>> -Original Message-
>> From: Daniel Lezcano
>> Sent: 2019年3月7日 17:15
>> To: Andy Tang ; Shawn Guo
>> Cc: Leo Li ; robh...@kernel.org; mark.rutl...@arm.com;
>> linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org;
>>
Formatting of Kconfig files doesn't look so pretty, so just
take a damp cloth and clean it up.
Signed-off-by: Enrico Weigelt, metux IT consult
---
fs/9p/Kconfig | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/fs/9p/Kconfig b/fs/9p/Kconfig
index
Hi Linus,
The following changes since commit 5908e6b738e3357af42c10e1183753c70a0117a9:
Linux 5.0-rc8 (2019-02-24 16:46:45 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-updates-v5.1
for you to fetch changes up to
Marc Zyngier writes:
> On 08/03/2019 08:26, Kalle Valo wrote:
>> Marc Zyngier writes:
>>
>>> dt-bindings/marvell-8xxx: Allow wake-up interrupt to be placed in a
>>> separate node
>>> mwifiex: Fetch wake-up interrupt from 'wake-up' subnode when it exists
>>> mwifiex: Flag wake-up
On Mon 2019-03-04 12:00:09, Andy Shevchenko wrote:
> Switch to bitmap_zalloc() to show clearly what we are allocating.
> Besides that it returns pointer of bitmap type instead of opaque void *.
>
> Signed-off-by: Andy Shevchenko
Reviewed-by: Petr Mladek
I have already sent pull request for
Hi Peter, Oleg,
NMI watchdog fires systematically on my machine with recent Kernels,
whereas the NMI watch is supposed to be disabled:
# cat /proc/sys/kernel/watchdog
0
# cat /proc/sys/kernel/nmi_watchdog
0
#
[ 53.765648] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7
[ 53.765648]
On 2019-03-08 00:07:41 [+], Liu, Yongxin wrote:
> The lane is critical resource which needs to be protected. One CPU can use
> only one
> lane. If CPU number is greater than the number of total lane, the lane can be
> shared
> among CPUs.
>
> In non-RT kernel, get_cpu() disable preemption
On Fri, 8 Mar 2019 at 10:18, Christoph Hellwig wrote:
>
> On Mon, Feb 25, 2019 at 02:54:13PM +0100, Ulf Hansson wrote:
> > This looks good to me, however the lack of feedback/tests worries me a
> > bit. So, unless you think it's a bad idea, I intend to apply this when
> > v5.1 rc1 is out, which
Update the code to match the comment that self wakeup of
grace period kthread is allowed from interrupt handler, and
softirq handler, running in the grace period kthread's
context. Present code allows self wakeups from all
interrupt contexts - nmi, softirq and hardirq contexts.
Signed-off-by:
On 7/03/19 8:51 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 06, 2019 at 08:32:42AM -0800, Tony Jones escreveu:
>> On 3/6/19 1:26 AM, Adrian Hunter wrote:
>>> On 2/03/19 3:19 AM, Tony Jones wrote:
Support both Python2 and Python3 in the exported-sql-viewer.py,
wakeup_source_activate() performs a check to see if the wakeup source is
registered or not. It works fine for a newly added wakeup source which
may not have been registered but fails to catch the case where a wakeup
source is unregistered as the timer.function is still valid.
Fix it by setting
wakeup_source_remove() is the counterpart of wakeup_source_add() helper
and must undo the initializations done by wakeup_source_add(). Currently
the timer is initialized by wakeup_source_add() but removed from
wakeup_source_drop(), which doesn't look logically correct. Also it
should be okay to
On Fri, Mar 08, 2019 at 09:57:45AM +0100, Ard Biesheuvel wrote:
> On Fri, 8 Mar 2019 at 00:49, Russell King - ARM Linux admin
> wrote:
> >
> > On Thu, Mar 07, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote:
> > > On Thu, Mar 7, 2019 at 1:15 AM Arnd Bergmann wrote:
> > > >
> > > > Passing
On Thu, Mar 07, 2019 at 04:04:23PM -0800, Nick Desaulniers wrote:
> On Thu, Mar 7, 2019 at 3:49 PM Russell King - ARM Linux admin
> wrote:
> >
> > On Thu, Mar 07, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote:
> > > Underspecification of constraints to extended inline assembly is a
> > >
I think is_enabled() and if_enable_echo() in scripts/package/mkdebian
are useful.
builddeb also has many repetitive greps over the kernel config, so I
borrowed the idea to clean it up.
Signed-off-by: Masahiro Yamada
---
scripts/package/builddeb | 32 +++-
1 file
This will be a little more efficient since unset CONFIG options are
stripped away from auto.conf, and we can hard-code the path to auto.conf
since it is never overridden.
include/config/kernel.release is generated before %pkg is run.
So, it is guaranteed auto.conf is up-to-date.
Signed-off-by:
This might be a kind of bike-shed, but I personally prefer grep'able
code.
I often do 'git grep CONFIG_FOO' instead of 'git grep FOO' when I
want to know where that CONFIG option is used.
This makes code longer, but I hope this is acceptable level.
Signed-off-by: Masahiro Yamada
---
> -Original Message-
> From: Daniel Lezcano
> Sent: 2019年3月8日 17:28
> To: Andy Tang ; Shawn Guo
> Cc: Leo Li ; robh...@kernel.org; mark.rutl...@arm.com;
> linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; linux...@vger.kernel.org;
On Thu 2019-03-07 10:53:48, John Ogness wrote:
> On 2019-03-04, Sergey Senozhatsky wrote:
> > If there are setups which can be fully !atomic (in terms of console
> > output) then we, essentially, have a fully preemptible kthread printk
> > implementation.
>
> Correct. I've mentioned in another
With the default iova and dma-iommu driver, the starting
address of a new buffer would be at lower address than
the previous one.
This patch can solve this problem simply, but I want
a way to control the address direction of the IOMMU/IOVA.
The reason why we(ayaka and I) need to do this is
On Fri 2019-03-08 10:31:34, Sergey Senozhatsky wrote:
> On (03/07/19 13:06), John Ogness wrote:
> > On 2019-03-04, Sergey Senozhatsky wrote:
> > > This, theoretically, creates a whole new world of possibilities for
> > > console drivers. Now they can do GFP_KERNEL allocations and stall
> > >
On Fri, 8 Mar 2019 at 10:53, Russell King - ARM Linux admin
wrote:
>
> On Fri, Mar 08, 2019 at 09:57:45AM +0100, Ard Biesheuvel wrote:
> > On Fri, 8 Mar 2019 at 00:49, Russell King - ARM Linux admin
> > wrote:
> > >
> > > On Thu, Mar 07, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote:
> > > >
Hallo Dan,
Am 05.03.19 um 16:52 schrieb Dan Murphy:
> Create a m_can platform framework that peripherial
> devices can register to and use common code and register sets.
> The peripherial devices may provide read/write and configuration
> support of the IP.
>
> Signed-off-by: Dan Murphy
> ---
>
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new
Web de correo electrónico de administración de notificaciones
Este mensaje es de nuestro centro de mensajería 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
On Fri, 8 Mar 2019 at 11:08, Ard Biesheuvel wrote:
>
> On Fri, 8 Mar 2019 at 10:53, Russell King - ARM Linux admin
> wrote:
> >
> > On Fri, Mar 08, 2019 at 09:57:45AM +0100, Ard Biesheuvel wrote:
> > > On Fri, 8 Mar 2019 at 00:49, Russell King - ARM Linux admin
> > > wrote:
> > > >
> > > > On
PING^1
On 2/13/19 12:19 PM, Martin Liška wrote:
> Hi.
>
> I'm sending updated version of the patch. I'm going to document particular
> changes
> in quotes below:
>
> On 8/23/18 6:16 PM, William Cohen wrote:
>> On 08/23/2018 10:31 AM, Arnaldo Carvalho de Melo wrote:
>>> Em Thu, Aug 23, 2018 at
--
jmichell...@gmail.com
Web de correo electrónico de administración de notificaciones
Este mensaje es de nuestro centro de mensajería 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
On Mon, Mar 04, 2019 at 07:13:05PM +0100, Paul Cercueil wrote:
> Hi Thierry,
>
> On Mon, Mar 4, 2019 at 1:22 PM, Thierry Reding
> wrote:
> > On Sat, Mar 02, 2019 at 08:33:50PM -0300, Paul Cercueil wrote:
> > [...]
> > > diff --git a/drivers/clocksource/ingenic-timer.c
> > >
Hi Steve,
On Thu, 2019-03-07 at 15:33 -0800, Steve Longerbeam wrote:
> The ycbcr2rgb and inverse rgb2ycbcr tables define the BT.601 Y'CbCr
> encoding coefficients.
>
> The rgb2ycbcr table specifically describes the BT.601 encoding from
> full range RGB to full range YUV. Add table comments to
On Thu, 2019-03-07 at 15:33 -0800, Steve Longerbeam wrote:
> The saturation bit was being set at bit 9 in the second 32-bit word
> of the TPMEM CSC. This isn't correct, the saturation bit is bit 42,
> which is bit 10 of the second word.
>
> Fixes: 1aa8ea0d2bd5d ("gpu: ipu-v3: Add Image Converter
Am 05.03.19 um 16:52 schrieb Dan Murphy:
> Rename the common m_can_priv class structure to
> m_can_classdev as this is more descriptive.
>
> Signed-off-by: Dan Murphy
> ---
>
> v7 - Fixed remaining checkpatch issues, renamed priv to cdev -
> https://lore.kernel.org/patchwork/patch/1047219/
On Thu, Feb 21, 2019 at 01:25:23PM +0100, Borislav Petkov wrote:
> On Thu, Feb 21, 2019 at 12:52:30PM +0100, Greg KH wrote:
> > I would, but I do not see this patch in Linus's tree yet :)
>
> You will soon :)
I see it now, so it's now queued up, thanks.
greg k-h
On Thu, Mar 7, 2019 at 10:02 PM Adam Ford wrote:
>
> The imx6q Technical reference manual shows the interrupt is
> available to wake from sleep using the power button. The driver
> has been available for quite some time, and other variants of the
> i.MX6 have it enabled, so this implements it
On Fri 2019-03-08 05:05:12, John Ogness wrote:
> On 2019-02-27, Petr Mladek wrote:
> Implement a non-sleeping NMI-safe write_atomic console function in
> order to support emergency printk messages.
> >>>
> >>> OK, it would be safe when prb_lock() is the only lock taken
> >>> in the NMI
From: Colin Ian King
Don't populate the array addr_list on the stack but instead make it
static. Makes the object code smaller by 20 bytes
Before:
textdata bss dec hex filename^M
169293626 384 2093951cb ../usb/em28xx/em28xx-input.o
After:
textdata
On Thu 2019-03-07 16:30:29, Sergey Senozhatsky wrote:
> On (02/12/19 15:29), John Ogness wrote:
> [..]
> > +static bool console_can_emergency(int level)
> > +{
> > + struct console *con;
> > +
> > + for_each_console(con) {
> > + if (!(con->flags & CON_ENABLED))
> > +
Commit b30b61ff6b1dc37f in linux-next.git did not get in time for closing
previous report. I assume that a pull request will be sent shortly from
Daniel Vetter.
#syz fix: drm/vkms: Fix flush_work() without INIT_WORK().
Hi Daniel,
On Fri, Mar 1, 2019 at 12:53 PM Daniel Baluta wrote:
> They are used by simple-card.c machine driver.
>
> asoc_simple_card_parse_clk
> -> /* Parse dai->sysclk come from "clocks = <>" */
> clk = devm_get_clk_from_child(dev, node, NULL);
The simple-card looks for the "clocks"
On Fri, Mar 08, 2019 at 11:08:40AM +0100, Ard Biesheuvel wrote:
> On Fri, 8 Mar 2019 at 10:53, Russell King - ARM Linux admin
> wrote:
> >
> > On Fri, Mar 08, 2019 at 09:57:45AM +0100, Ard Biesheuvel wrote:
> > > On Fri, 8 Mar 2019 at 00:49, Russell King - ARM Linux admin
> > > wrote:
> > > >
>
On Fri, Mar 08, 2019 at 10:13:58AM +0100, Geert Uytterhoeven wrote:
> Hi Tom,
>
> If the kernel just crashes, of course all of that doesn't happen.
> Is your graphics card reset when the reset button is pressed, or only on
> cold power on?
It's a laptop, so it doesn't have a reset button. I've
Lorenzo, Mark,
On Wed, 6 Mar 2019 at 19:15, Lorenzo Pieralisi
wrote:
>
> On Mon, Mar 04, 2019 at 11:14:18AM +0100, Ulf Hansson wrote:
> > On Fri, 1 Mar 2019 at 18:28, Mark Rutland wrote:
> > >
> > > On Thu, Feb 28, 2019 at 02:59:17PM +0100, Ulf Hansson wrote:
> > > > Instead of iterating
On 08.03.19 10:11, Linus Walleij wrote:
> As Torvalds did not yet pull the GPIO tree (maybe because of this
> and other bugs, who knows) I applied this to my GPIO tree for
> now.
Great. I actually like it better this way, so his pull will be clean
and consistent.
Did you also apply the kconfig
On Fri, 8 Mar 2019 at 11:34, Russell King - ARM Linux admin
wrote:
>
> On Fri, Mar 08, 2019 at 11:08:40AM +0100, Ard Biesheuvel wrote:
> > On Fri, 8 Mar 2019 at 10:53, Russell King - ARM Linux admin
> > wrote:
> > >
> > > On Fri, Mar 08, 2019 at 09:57:45AM +0100, Ard Biesheuvel wrote:
> > > > On
On Thu, Mar 07, 2019 at 06:26:47PM +0300, Alexey Budankov wrote:
>
> On 07.03.2019 15:14, Jiri Olsa wrote:
> > On Thu, Mar 07, 2019 at 11:39:46AM +0300, Alexey Budankov wrote:
> >>
> >> On 05.03.2019 15:25, Jiri Olsa wrote:
> >>> On Fri, Mar 01, 2019 at 06:58:32PM +0300, Alexey Budankov wrote:
>
On 25/02/19 14:27, Yang Weijiang wrote:
> For Guest XSS, right now, only bit 11(user states) and bit 12
> (supervisor states) are supported, if other bits are being set,
> need to modify KVM_SUPPORTED_XSS macro to have support.
>
> Signed-off-by: Zhang Yi Z
> Signed-off-by: Yang Weijiang
> ---
Dmitrii Tcvetkov wrote:
> After upgrade to 5.0 on XPS 13 9360 I get NULL pointer dereference in
> dmesg (attached). Distro is Arch Linux, kernel is built with custom
> config (attached), but distro kernel[1] reproduces the issue on the
> laptop as well.
>
> Bisect led me to commit f6ac858589768
On 08/03/2019 08:37, Mike Rapoport wrote:
> On Wed, Mar 06, 2019 at 03:50:16PM +, Steven Price wrote:
>> walk_page_range() is going to be allowed to walk page tables other than
>> those of user space. For this it needs to know when it has reached a
>> 'leaf' entry in the page tables. This
resize_hpt_for_hotplug() reports a warning when it cannot
resize the hash page table ("Unable to resize hash page
table to target order") but in some cases it's not a problem
and can make user thinks something has not worked properly.
This patch moves the warning to arch_remove_memory() to
only
I forgot the version change note:
v2: add warning messages for H_PARAMETER and H_RESOURCE
Thanks,
Laurent
On 08/03/2019 11:54, Laurent Vivier wrote:
> resize_hpt_for_hotplug() reports a warning when it cannot
> resize the hash page table ("Unable to resize hash page
> table to target order")
On Fri, Mar 08, 2019 at 11:16:47AM +0100, Ard Biesheuvel wrote:
> Compiling the following code
>
> """
> #include
>
> static void foo(void *a, int b)
> {
> asm("str %0, [%1]" :: "r"(a), "r"(b));
> }
>
> int main(void)
> {
> foo(NULL, 0);
> }
> """
>
> with GCC 6.3 (at -O2) gives me
>
1 - 100 of 902 matches
Mail list logo
