On Wed, Feb 13, 2019 at 3:12 AM Greg KH wrote:
>
> On Wed, Feb 13, 2019 at 02:54:43AM +0800, Xiang Xiao wrote:
> > Here is the detailed description for memrchr:
> >
> > void *memrchr(const void *s, int c, size_t n);
> >
> > The memrchr() function is like the memchr() function, except
> > that it
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/tty/n_hdlc.c: In function ‘n_hdlc_tty_ioctl’:
drivers/tty/n_hdlc.c:775:3: warning: this statement may fall through
[adding Mark Brown]
On 11.02.2019 02:23, Shawn Guo wrote:
> On Thu, Feb 07, 2019 at 09:00:44PM +, Trent Piepho wrote:
>> On Mon, 2019-01-07 at 14:22 +0100, Stefan Agner wrote:
>> > Allow to use DMA for SPI by adding the appropriate DMA properites
>> > to the ecspi nodes.
>> >
>> >
On Wed, Feb 13, 2019 at 3:15 AM Greg KH wrote:
>
> On Wed, Feb 13, 2019 at 03:09:19AM +0800, xiang xiao wrote:
> > On Wed, Feb 13, 2019 at 2:34 AM Greg KH wrote:
> > >
> > > On Wed, Feb 13, 2019 at 02:06:49AM +0800, Xiang Xiao wrote:
> > > > Here is the detailed description for memrchr:
> > > >
Selam tatlım, ben Katie Higgins, Bugün profilini gördüm, çok güzel ve
harika görünüyorsun
Seninle ilgileniyorum, beni bilgine geri yazabilirsen çok mutlu ve
minnettar olacağım.
Sizden haber alır duymaz size güzel fotoğraflarımı göndereceğim.
Lütfen e-postamı yazmaya devam et
On Tue, Feb 12, 2019 at 06:43:54PM +, Will Deacon wrote:
> On Mon, Feb 11, 2019 at 12:22:18PM -0800, Paul E. McKenney wrote:
> > On Mon, Feb 11, 2019 at 05:29:48PM +, Will Deacon wrote:
> > > The "KERNEL I/O BARRIER EFFECTS" section of memory-barriers.txt is vague,
> > > x86-centric,
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/usb/musb/musb_host.c: In function ‘musb_advance_schedule’:
drivers/usb/musb/musb_host.c:374:7: warning: this statement may fall through
On 11.02.2019 19:17, Nick Desaulniers wrote:
> On Sat, Feb 9, 2019 at 9:28 AM Stefan Agner wrote:
>>
>> Thanks for the reviews so far.
>>
>> During some more testing I stumbled upon another issue:
>>
>> On 07.02.2019 10:48, Stefan Agner wrote:
>> > Use unified assembler syntax (UAL) in inline
Arnd, Olof,
Here is the only AT91 pull request for this cycle.
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://git.kernel.org/pub/scm/linux/kernel/git/at91/linux
On 10.02.2019 22:24, Nicolas Pitre wrote:
> On Sun, 10 Feb 2019, Stefan Agner wrote:
>
>> This patchset converts all assembly code to unified assembler
>> language (UAL) compatible assembly code. From what I can tell,
>> this mainly boils down to using conditional infixes instead of
>> postfixes.
Hi,
On Tue, Feb 12, 2019 at 02:46:24PM +0900, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 19. 2. 12. 오전 12:30, Lukasz Luba wrote:
> > This patch set changes workqueue related features in devfreq framework.
> > First patch switches to delayed work instead of deferred.
> > The second switches to
On 12 February 2019 at 4:25PM, Christoph Hellwig wrote:
On Tue, Feb 12, 2019 at 01:42:56PM +0100, Christian Zigotzky wrote:
On 11 February 2019 at 08:38AM, Christoph Hellwig wrote:
On Sun, Feb 10, 2019 at 01:00:20PM +0100, Christian Zigotzky wrote:
I tested the whole series today. The kernels
On 12.02.19 18:24, Nitesh Narayan Lal wrote:
>
> On 2/12/19 4:24 AM, David Hildenbrand wrote:
>> On 12.02.19 10:03, Wang, Wei W wrote:
>>> On Tuesday, February 5, 2019 4:19 AM, Nitesh Narayan Lal wrote:
The following patch-set proposes an efficient mechanism for handing freed
memory
On Mon, Feb 11, 2019 at 8:22 PM Trent Piepho wrote:
> > Just trying to understand if the SDMA firmware plays a role on this
> > behavior or not.
>
> The ROM firmware only.
Does the problem also happen if the external SDMA firmware is used?
Just trying to narrow it down.
Am 12.02.19 um 15:05 schrieb Colin King:
> From: Colin Ian King
>
> There are several statements that are incorrectly indented. Fix these.
>
> Signed-off-by: Colin Ian King
Reviewed-by: Christian König
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_kms.c | 2 +-
>
On Wed, Feb 06, 2019 at 04:17:26PM +0300, Mika Westerberg wrote:
> +static struct tb_port *tb_port_remote(struct tb_port *port)
> +{
> + struct tb_port *remote = port->remote;
> +
> + /*
> + * If we have a dual link, the remote is available through the
> + * primary link.
> +
Register rseq(2) TLS for each thread (including main), and unregister
for each thread (excluding main). "rseq" stands for Restartable
Sequences.
See the rseq(2) man page proposed here:
https://lkml.org/lkml/2018/9/19/647
This patch is based on glibc-2.29. The rseq(2) system call was merged
When available, use the cpu_id field from __rseq_abi on Linux to
implement sched_getcpu(). Fall-back on the vgetcpu vDSO if unavailable.
Benchmarks:
x86-64: Intel E5-2630 v3@2.40GHz, 16-core, hyperthreading
glibc sched_getcpu(): 13.7 ns (baseline)
glibc sched_getcpu() using
On Wed, 13 Feb 2019 02:11:05 +0800
Xiang Xiao wrote:
> Because log may already add the timestamp sometime
Can you be a bit more detailed on this. When and where does this
happen? If anything, I would probably prefer that we export whether
time is being printed, and have the caller not print
On Tue, 12 Feb 2019 09:58:25 -0800
Joe Perches wrote:
> On Tue, 2019-02-12 at 14:00 +0100, Petr Mladek wrote:
> > On Fri 2019-02-08 09:11:17, Joe Perches wrote:
> > > On Fri, 2019-02-08 at 16:23 +0100, Petr Mladek wrote:
> > > > Move the code from the long pointer() function. We are going to
Hi Greg,
On Tue, Feb 12, 2019 at 01:23:57PM -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/usb/musb/musb_host.c: In function
On Mon, Feb 11, 2019 at 10:36:30PM +0100, Jacek Anaszewski wrote:
> Hi Yauhen,
>
> Thank you for the patch.
>
> Please find few comments in the code.
>
> On 2/9/19 11:12 PM, Yauhen Kharuzhy wrote:
> > diff --git a/drivers/leds/leds-cht-wcove.c b/drivers/leds/leds-cht-wcove.c
> > new file mode
On 12 February 2019 at 8:31PM, Christian Zigotzky wrote:
On 12 February 2019 at 4:25PM, Christoph Hellwig wrote:
On Tue, Feb 12, 2019 at 01:42:56PM +0100, Christian Zigotzky wrote:
On 11 February 2019 at 08:38AM, Christoph Hellwig wrote:
On Sun, Feb 10, 2019 at 01:00:20PM +0100, Christian
On Tue, Feb 12, 2019 at 08:14:09AM +, Lee Jones wrote:
> On Sun, 10 Feb 2019, Yauhen Kharuzhy wrote:
>
> > Add MFD cell for LEDs driver to the Intel Cherry Trail Whiskey Cove PMIC
> > mfd device driver.
> >
> > Signed-off-by: Yauhen Kharuzhy
> > ---
> > drivers/mfd/intel_soc_pmic_chtwc.c |
Great! I owe you a night worth of beers at a conference or if
you come anywhere near Innsbruck!
On Tue, 2019-02-12 at 10:49 -0800, Tony Lindgren wrote:
> Hi,
>
> * Martyn Welch [190211 04:27]:
> > The Bosch Guardian is a TI am335x based device.
> >
> > It's hardware specifications are as follows:
> >
> > * 256 MB DDR3 memory
> > * 512 MB NAND Flash
> > * USB OTG
> > * RS232
> > *
On 2/12/19 3:25 AM, Johan Hovold wrote:
On Tue, Feb 12, 2019 at 03:10:12AM -0800, Atish Patra wrote:
Currently, we set hwcap based on first valid hart from DT. This may not
be correct always as that hart might not be current booting cpu or may
have a different capability.
Set hwcap as the
Le 11/02/2019 à 17:22, Dave Hansen a écrit :
> On 2/9/19 3:00 AM, Brice Goglin wrote:
>> I've used your patches on fake hardware (memmap=xx!yy) with an older
>> nvdimm-pending branch (without Keith's patches). It worked fine. This
>> time I am running on real Intel hardware. Any idea where to
Thanks for the fix James!
On Tue, Feb 12, 2019 at 8:59 AM Martin K. Petersen
wrote:
>
>
> Jens,
>
> >> The fix is to set the non-rotational and add-randomness flags
> >> unconditionally early on in the disk initialization path, so they can
> >> be reset only if the device actually reports being
On 2/12/19 7:52 AM, Khalid Aziz wrote:
On 1/23/19 7:24 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Jan 10, 2019 at 02:09:37PM -0700, Khalid Aziz wrote:
From: Juerg Haefliger
Enable support for eXclusive Page Frame Ownership (XPFO) for arm64 and
provide a hook for updating a single kernel page
Use unified assembler syntax (UAL) in macros. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
Changes in v2:
- Remove excessive null tokens
Use unified assembler syntax (UAL) in headers. Divided syntax is
considered deprecated. This will also allow to build the kernel
using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
Changes in v2:
- Remove excessive null tokens
- Move t token before
Use unified assembler syntax (UAL) in assembly files. Divided
syntax is considered deprecated. This will also allow to build
the kernel using LLVM's integrated assembler.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
---
arch/arm/boot/bootp/init.S| 2 +-
Remove the -mno-warn-deprecated assembler flag to make sure the GNU
assembler warns in case non-unified syntax is used.
Signed-off-by: Stefan Agner
Acked-by: Nicolas Pitre
Reviewed-by: Nick Desaulniers
---
Changes in v2:
- Remove AFLAGS_NOWARN from CFLAGS_ISA
arch/arm/Makefile | 7 ++-
1
This patchset converts all assembly code to unified assembler
language (UAL) compatible assembly code. From what I can tell,
this mainly boils down to using conditional infixes instead of
postfixes.
Most of the conversion has been done using the following regular
expression:
find ./arch/arm/
Use unified assembler syntax (UAL) in inline assembler. Divided
syntax is considered deprecated. This will also allow to build
the kernel using LLVM's integrated assembler.
When compiling non-Thumb2 GCC always emits a ".syntax divided"
at the beginning of the inline assembly which makes the
Thomas Spurden writes:
> On Thu, 7 Feb 2019 at 20:10, Eric Anholt wrote:
>>
>> Signed-off-by: Eric Anholt
>
> Reviewed-by: Thomas Spurden
Merged this one, will send out respins of the others.
signature.asc
Description: PGP signature
Daniel Vetter writes:
> On Thu, Feb 07, 2019 at 03:26:13PM -0800, Eric Anholt wrote:
>> We always decrement at GEM free, so make sure we increment at GEM
>> creation for dma-bufs.
>
> Indeed. Reviewed-by: Daniel Vetter
Merged to drm-misc-next. Thanks!
signature.asc
Description: PGP
Hi all,
In commit
d1f20798a119 ("ipv6: propagate genlmsg_reply return code")
Fixes tag
Fixes: 915d7e5e593 ("ipv6: sr: add code base for control plane support of
SR-IPv6")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or
On Mon, Feb 11, 2019 at 11:31 AM Waiman Long wrote:
>
> Modify __down_read_trylock() to make it generate slightly better code
> (smaller and maybe a tiny bit faster).
This looks good, but I would ask you to try one slightly different approach.
Instead of this:
>long tmp =
On Tue, Feb 12, 2019 at 04:21:21AM +0100, Andrea Parri wrote:
> > > + if (!si)
> > > + goto bad_nofile;
> > > +
> > > + preempt_disable();
> > > + if (!(si->flags & SWP_VALID))
> > > + goto unlock_out;
> >
> > After Hugh alluded to barriers, it seems the read of SWP_VALID could be
On Thu, Jan 31, 2019 at 6:26 PM Yue Hu wrote:
>
> From 57cb7141b227b7f75a6e4afb8319f803510cc07f Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Thu, 31 Jan 2019 18:12:46 +0800
> Subject: [PATCH] pstore: Avoid to write records with null size
>
> Sometimes pstore_console_write() will write record
On Mon, Feb 11, 2019 at 7:37 AM Christoph Hellwig wrote:
>
> The OF_RESERVED_MEM can be used if we have either CMA or the generic
> declare coherent code built and we support the early flattened DT.
>
> So don't bother making it a user visible options that is selected
> by most configs that fit
On Tue, Feb 12, 2019 at 12:20:42PM +0100, Lukasz Luba wrote:
> Hi Matthias,
>
> On 2/11/19 10:42 PM, Matthias Kaehlcke wrote:
> > Hi Lukasz,
> >
> > On Mon, Feb 11, 2019 at 04:30:04PM +0100, Lukasz Luba wrote:
> >> There is no need for creating another workqueue in the system,
> >> the existing
diff --git a/Makefile b/Makefile
index 1933ac9c3406..956923115f7e 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 155
+SUBLEVEL = 156
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/arm/boot/dts/mmp2.dtsi b/arch/arm/boot/dts/mmp2.dtsi
index
On Sun, Jan 27, 2019 at 6:11 PM Yue Hu wrote:
>
> From 4320c0fcb5d685c8099937abce88e0b7fbbfe8dc Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Wed, 23 Jan 2019 16:56:48 +0800
> Subject: [PATCH] pstore/ram: Make initialization check as first one
>
> Since only one single ramoops area allowed at
I'm announcing the release of the 4.9.156 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.99 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 4.19.21 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 4.20.8 kernel.
All users of the 4.20 kernel series must upgrade.
The updated 4.20.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.20.y
and can be browsed at the normal kernel.org git web browser:
On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> Commit 4080ab083000 ("PM-runtime: Take suppliers into account in
> __pm_runtime_set_status()") introduced a race condition that may
> trigger if __pm_runtime_set_status() is used incorrectly (that is,
> if it
On Mon, Jan 21, 2019 at 11:19 PM Yue Hu wrote:
>
> From 7c1f672a2d7b7c2cfef313060bd429afc4af995b Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Tue, 22 Jan 2019 14:47:00 +0800
> Subject: [PATCH] pstore/ram: Avoid possible failure of dummy device unregister
>
> In ramoops_register_dummy() if
I'm announcing the release of the 4.20.8 kernel.
All users of the 4.20 kernel series must upgrade.
The updated 4.20.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.20.y
and can be browsed at the normal kernel.org git web browser:
On Feb 12, 2019, at 7:54 AM, demioben...@gmail.com wrote:
>
> From: "Demi M. Obenour"
>
> This adds the file open flag O_PATHSTATIC, which ensures that symbolic
> links are *never* followed, even in path components other than the last.
> This is distinct from O_NOFOLLOW, which only prevents
On Tue, Feb 12, 2019 at 09:13:09PM +0100, Greg KH wrote:
> I'm announcing the release of the 4.20.8 kernel.
>
> All users of the 4.20 kernel series must upgrade.
>
> The updated 4.20.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
On Tue, Jan 22, 2019 at 3:10 AM Yue Hu wrote:
>
> From 7123b8bfaede56796fb21767cc8c13496d9c44e6 Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Tue, 22 Jan 2019 18:51:48 +0800
> Subject: [PATCH] pstore: Fix some style warnings and errors
>
> WARNING: line over 80 characters
> +#if
On 12/02/2019 18.58, Joe Perches wrote:
> On Tue, 2019-02-12 at 14:00 +0100, Petr Mladek wrote:
>> On Fri 2019-02-08 09:11:17, Joe Perches wrote:
>>> On Fri, 2019-02-08 at 16:23 +0100, Petr Mladek wrote:
Move the code from the long pointer() function. We are going to improve
error
On Mon, Feb 11, 2019 at 7:36 AM Christoph Hellwig wrote:
>
> This function is only used in of_reserved_mem.c, and never overridden
> despite the __weak marker.
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/of/of_reserved_mem.c| 2 +-
> include/linux/of_reserved_mem.h | 7 ---
> 2
On Mon, Feb 11, 2019 at 02:17:26PM +0100, Pavel Machek wrote:
> Hi!
>
> > +static struct cht_wc_led cht_wc_leds[] = {
> > + {
> > + .name = "pmic::charge",
> > + .ctrl_reg = CHT_WC_LED1_CTRL,
> > + .fsm_reg = CHT_WC_LED1_FSM,
> > + .pwm_reg =
The old field is gone and the register now has a different field,
QRMAXCNT for how many TMU requests get serviced before thread switch.
We were accidentally reducing it from its default of 0x3 (4 requests)
to 0x0 (1).
v2: Skip setting the reg at all on 4.x, instead of trying to update
only
You'll get garbage measurements if the registers always read back
0xdeadbeef
Signed-off-by: Eric Anholt
---
drivers/gpu/drm/v3d/v3d_debugfs.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/v3d/v3d_debugfs.c
b/drivers/gpu/drm/v3d/v3d_debugfs.c
index
No compatible string for it yet, just the version-dependent changes.
They've now tied the hub and the core interrupt lines into a single
interrupt line coming out of the block. It also turns out I made a
mistake in modeling the V3D v3.3 and v4.1 bridge as a part of V3D
itself -- the bridge is
On Thu, Jan 31, 2019 at 11:35 PM Yue Hu wrote:
>
> From 9385613f546a4d0b2497dc2ed22cb9475eb3621c Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Fri, 1 Feb 2019 11:27:32 +0800
> Subject: [PATCH] pstore/ram: Add kmsg hlen null check to ramoops_pstore_write
>
> If null hdr happened in
> > From: Bartosz Golaszewski
> >
> > Add support for the push- and slide-button events for max77650.
> >
> > Signed-off-by: Bartosz Golaszewski
> > ---
> > drivers/input/misc/Kconfig | 9 ++
> > drivers/input/misc/Makefile | 1 +
> > drivers/input/misc/max77650-onkey.c |
On Tue, 12 Feb 2019 13:47:24 -0500 Johannes Weiner wrote:
> On Tue, Feb 12, 2019 at 09:56:45AM -0800, Roman Gushchin wrote:
> > The patchset contains few changes to the vmalloc code, which are
> > leading to some performance gains and code simplification.
> >
> > Also, it exports a number of
Jens Axboe - 12.02.19, 17:16:
> On 2/11/19 11:27 PM, Ben Finney wrote:
> > Martin Steigerwald writes:
> >> Well the file has in its header:
> >>
> >> /* Fast hashing routine for a long.
> >>
> >>(C) 2002 William Lee Irwin III, IBM */
> >>
> >> /*
> >>
> >> * Knuth recommends primes in
On 2/12/19 1:01 PM, Laura Abbott wrote:
> On 2/12/19 7:52 AM, Khalid Aziz wrote:
>> On 1/23/19 7:24 AM, Konrad Rzeszutek Wilk wrote:
>>> On Thu, Jan 10, 2019 at 02:09:37PM -0700, Khalid Aziz wrote:
From: Juerg Haefliger
Enable support for eXclusive Page Frame Ownership (XPFO) for
On Mon, 11 Feb 2019 12:17:37 -0800
Justin Chen wrote:
> On Mon, Feb 11, 2019 at 12:06 PM Jonathan Cameron wrote:
> >
> > On Sat, 9 Feb 2019 12:56:11 -0600
> > David Lechner wrote:
> >
> > > On 2/9/19 11:00 AM, Jonathan Cameron wrote:
> > > > Nope. This is a state lock used to protect
On 2/11/19 11:27 PM, Ben Finney wrote:
> Martin Steigerwald writes:
>
>> Well the file has in its header:
>>
>> /* Fast hashing routine for a long.
>>(C) 2002 William Lee Irwin III, IBM */
>>
>> /*
>> * Knuth recommends primes in approximately golden ratio to the
maximum
>> * integer
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/xen/xen-pciback/xenbus.c: In function ‘xen_pcibk_frontend_changed’:
drivers/xen/xen-pciback/xenbus.c:545:6: warning: this statement may
On Tue, Feb 12, 2019 at 09:54:47AM -0500, demioben...@gmail.com wrote:
> From: "Demi M. Obenour"
>
> While testing the O_PATHSTATIC patch, I discovered that Linux does not
> return any error if an invalid flag is passed to open(2). This prevents
> adding new flags without a (minor) risk of
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/xen/xen-scsiback.c: In function ‘scsiback_frontend_changed’:
drivers/xen/xen-scsiback.c:1185:6: warning: this statement may fall through
On Mon, Feb 11, 2019 at 7:37 AM Christoph Hellwig wrote:
>
> This API is primarily used through DT entries, but two architectures
> and two drivers call it directly. So instead of selecting the config
> symbol for random architectures pull it in implicitly for the actual
> users. Also rename
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add panel driver for it.
Signed-off-by: Jagan Teki
Reviewed-by: Sam Ravnborg
Tested-by: Bhushan Shah
Tested-by: Merlijn Wajer
---
Changes for v7:
- rebase on master
- collect Merlijn Tested-by
- add tabs about drm timings
Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
Add dt-bingings for it.
Signed-off-by: Jagan Teki
Reviewed-by: Rob Herring
---
Changes for v7, v6, v5, v4, v3:
- none
Changes for v2:
- new patch, derived from another dsi series
.../display/panel/feiyang,fy07024di26a30d.txt |
Hello,
Re: Business proposition for you.
I have a client in Russia who will like to invest with your
company. My client is willing to invest $10 Million to $50
million. Can I have your company website to show to my client
your company so that they will check and decide if they will
invest
On Fri, Feb 1, 2019 at 12:30 AM Yue Hu wrote:
>
> From bac8bbcd6081b967422dc82074a41098a0cf5180 Mon Sep 17 00:00:00 2001
> From: Yue Hu
> Date: Tue, 29 Jan 2019 11:42:27 +0800
> Subject: [PATCH] pstore: Add boot loader log messages support
>
> Sometimes we hope to check boot loader log messages
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
kernel/auditfilter.c: In function ‘audit_krule_to_data’:
kernel/auditfilter.c:668:7: warning: this statement may fall through
On Wed, Feb 6, 2019 at 8:11 AM Jorge Ramirez
wrote:
>
> On 2/5/19 12:02, Jorge Ramirez wrote:
> > On 1/30/19 21:02, Rob Herring wrote:
> >> On Tue, Jan 29, 2019 at 12:35:14PM +0100, Jorge Ramirez-Ortiz wrote:
> >>> Binding description for Qualcomm's Synopsys 1.0.0 super-speed PHY
> >>> controller
On Mon, 11 Feb 2019 17:30:18 -0500
Sven Van Asbroeck wrote:
> On Mon, Feb 11, 2019 at 4:27 PM Jonathan Cameron wrote:
> >
> > Agreed. Or potentially just use regmap_bulk_read and rely on
> > the regmap internal locking to do it for you.
>
> Neat solution. But it may only work correctly iff
Hi Joyce,
On 2/12/19 10:24 AM, Ooi, Joyce wrote:
As there is restriction to access to EMAC System Manager registers in
the kernel for Intel Stratix10, the use of SMC calls are required and
added in dwmac-socfpga driver.
Signed-off-by: Ooi, Joyce
I have a pending patchset[1] that addresses
On 2019-02-08 3:51 a.m., Thomas Petazzoni wrote:
Those hooks implement the exact same behavior as the default hooks by
gpiolib, so there is no point in having a duplicated definition in
gpio-bcm-kona.
Signed-off-by: Thomas Petazzoni
Acked-by: Scott Branden
Cc: Ray Jui
Cc: Florian
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
kernel/events/core.c: In function ‘perf_event_parse_addr_filter’:
kernel/events/core.c:9154:11: warning: this statement may fall through
On Wed, Jan 23, 2019 at 4:06 AM liaoweixiong
wrote:
>
> Why should we need pstore_block?
> 1. Most embedded intelligent equipment have no persistent ram, which
> increases costs. We perfer to cheaper solutions, like block devices.
> In fast, there is already a sample for block device logger in
On Tue, Feb 12, 2019 at 11:22:33AM +, Colin King wrote:
> From: Colin Ian King
>
> The null check on an allocation failure on pd is currently checking
> if pd is non-null rather than null. Fix this by adding the missing !
> operator.
>
> Fixes: 21a428a019c9 ("RDMA: Handle PD allocations by
On Tue, 12 Feb 2019 11:21:29 +0100 Michal Hocko wrote:
> Tetsuo has reported that creating a thousands of processes sharing MM
> without SIGHAND (aka alien threads) and setting
> /proc//oom_score_adj will swamp the kernel log and takes ages [1]
> to finish. This is especially worrisome that all
On Tue, 12 Feb 2019 18:45:49 +0100
Krzysztof Kozlowski wrote:
> Exynos4212 and Exynos4412 have only four ADC channels so using
> "samsung,exynos-adc-v1" compatible (for eight channels ADCv1) on them is
> wrong. Add a new compatible for Exynos4x12.
>
> Signed-off-by: Krzysztof Kozlowski
I'll
Add MFD cell for LEDs driver to the Intel Cherry Trail Whiskey Cove PMIC
mfd device driver.
Signed-off-by: Yauhen Kharuzhy
---
drivers/mfd/intel_soc_pmic_chtwc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/intel_soc_pmic_chtwc.c
b/drivers/mfd/intel_soc_pmic_chtwc.c
index
Add support for LEDs connected to the Intel Cherry Trail Whiskey Cove
PMIC. Charger and general-purpose leds are supported. Hardware blinking
is implemented, breathing is not.
This driver was tested with Lenovo Yoga Book notebook.
Signed-off-by: Yauhen Kharuzhy
---
drivers/leds/Kconfig
This patch series introduces new driver for controlling LEDs connected
to Intel Cherry Trail Whiskey Cove PMIC (general-purpose LED and charger
status led). Only simple 'always on' and blinking modes are supported
for now, no breathing.
Driver was tested only with Lenovo Yoga Book notebook, and I
On 2019-02-12 20:06, Sowjanya Komatineni wrote:
> This patch sorts all the include headers alphabetically for the
> I2C Tegra driver.
>
> Acked-by: Thierry Reding
> Reviewed-by: Dmitry Osipenko
> Signed-off-by: Sowjanya Komatineni
> ---
> [V9/V10/V11/V12/V13/V14/V15/V16/V17/V18/V19] : Rebased
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
kernel/trace/blktrace.c: In function ‘blk_trace_ioctl’:
kernel/trace/blktrace.c:725:9: warning: this statement may fall through
On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> If a stateless device link to a certain supplier with
> DL_FLAG_PM_RUNTIME set in the flags is added and then removed by the
> consumer driver's probe callback, the supplier's PM-runtime usage
> counter will
On Thu, Dec 20, 2018 at 05:17:50PM +0100, Johan Hovold wrote:
> Fix "gpiio5" typo in the (currently unused) blsp2_uart1 4-pin sleep
> config.
>
> Fixes: 22e6789f9493 ("arm64: dts: msm8996: add blsp2_uart1 pinctrl")
> Cc: Srinivas Kandagatla
> Signed-off-by: Johan Hovold
> ---
>
On 2019/02/13 5:56, Andrew Morton wrote:
> On Tue, 12 Feb 2019 11:21:29 +0100 Michal Hocko wrote:
>
>> Tetsuo has reported that creating a thousands of processes sharing MM
>> without SIGHAND (aka alien threads) and setting
>> /proc//oom_score_adj will swamp the kernel log and takes ages [1]
>>
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
kernel/trace/trace_events_filter.c: In function ‘predicate_parse’:
kernel/trace/trace_events_filter.c:494:8: warning: this statement may fall
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
kernel/trace/trace_probe.c: In function ‘parse_probe_arg’:
kernel/trace/trace_probe.c:302:6: warning: this statement may fall through
On Mon, Feb 11, 2019 at 03:25:28PM +0100, Maxime Chevallier wrote:
> Marvell 10G PHY driver has a generic way of initializing the supported
> link modes by reading the PHY's C45 PMA abilities. This can be made
> generic, since these registers are part of the 802.3 specifications.
>
> This commit
On Mon, 11 Feb 2019 22:59:53 +0100 Andrey Konovalov
wrote:
> With tag based KASAN page_address() looks at the page flags to see
> whether the resulting pointer needs to have a tag set. Since we don't
> want to set a tag when page_address() is called on SLAB pages, we call
>
On Mon, Feb 11, 2019 at 03:25:29PM +0100, Maxime Chevallier wrote:
> The 802.3bz specification, based on previous by the NBASET alliance,
> defines the 2.5GBaseT and 5GBaseT link modes for ethernet traffic on
> cat5e, cat6 and cat7 cables.
>
> These mode integrate with the already defined C45
901 - 1000 of 1653 matches
Mail list logo
