My main motivation is to get rid of crappy header search path manipulation
from Kbuild core.
Before that, I want to do as many treewide cleanups as possible.
If you are interested in the big picture of this work,
the full patch set is available at:
The included headers are located in include/target/. I was able to
build these drivers without the extra header search paths.
Signed-off-by: Masahiro Yamada
---
drivers/infiniband/ulp/isert/Makefile | 1 -
drivers/infiniband/ulp/srpt/Makefile | 1 -
2 files changed, 2 deletions(-)
diff --git
Hi all,
Changes since 20190124:
The vfs tree still had its build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 3454
3915 files changed, 114384 insertions(+), 72024 deletions(-)
I
Hi Justin,
On 1/24/19 5:56 PM, justinpo...@gmail.com wrote:
> From: Justin Chen
>
> To read a channel we require 3 cycles to send, process, and receive
> the data. The transfer buffer for the third transaction is left blank.
> This leaves it up to the SPI driver to decide what to do.
>
> In
On Fri, Jan 18, 2019 at 11:32 AM Mathieu Malaterre wrote:
>
> In the past an attempt was made to remove a set of warnings triggered by
> gcc 8.x and W=1 by changing calls to strncpy() into strlcpy(). This was
> rejected as one of the desired behavior is to keep initializing the rest
> of the
On Thu, Jan 24, 2019 at 2:46 AM wrote:
>
> From: Shun-Chih Yu
>
> This patch introduces active_vdec to indicate the virtual descriptor
> under processing by the CQDMA dmaengine, and simplify the control logic
> by removing redundant queue structure, tasklets, and completion
> management.
>
>
On 1/24/19 7:09 PM, Jon Hunter wrote:
On 07/01/2019 03:28, Joseph Lo wrote:
Add support for the Tegra210 timer that runs at oscillator clock
(TMR10-TMR13). We need these timers to work as clock event device and to
replace the ARMv8 architected timer due to it can't survive across the
power
On Fri, Jan 25, 2019 at 5:14 AM Nicolas Dufresne wrote:
>
> Le mercredi 23 janvier 2019 à 14:04 +0100, Hans Verkuil a écrit :
> > > > Does this return the same set of formats as in the 'Querying
> > > > Capabilities' phase?
> > > >
> > >
> > > It's actually an interesting question. At this point
tty_set_termios() should be called with slave side of pty driver. So, If
tty driver is pty master, it needs to be switched to ->link. Also,
tiocmget() and tiocmset() operations are optional so we need NULL check
for some drivers missing the operations like pty.
Reported-by:
+John
HI John,
On Mon, 2019-01-21 at 16:49 +0800, Uwe Kleine-König wrote:
> On Sat, Jan 19, 2019 at 10:54:47AM +0800, Ryder Lee wrote:
> > On Fri, 2019-01-18 at 09:43 +0100, Matthias Brugger wrote:
> > >
> > > On 18/01/2019 04:24, Ryder Lee wrote:
> > > > This adds a property "mediatek,num-pwms"
You dropped the version tag that doesn't reflect that is a newer one
and that would be easily ignored by other people
On Thu, Jan 24, 2019 at 2:46 AM wrote:
>
> From: Shun-Chih Yu
>
> Document the devicetree bindings for MediaTek Command-Queue DMA controller
> which could be found on MT6765 SoC
On 1/17/19 8:17 AM, Ilya Dryomov wrote:
> On Tue, Jan 15, 2019 at 8:41 PM Gustavo A. R. Silva
> wrote:
>>
>> One of the more common cases of allocation size calculations is finding
>> the size of a structure that has a zero-sized array at the end, along
>> with memory for some number of
On Fri, Jan 25, 2019 at 12:13:13AM +0530, Jagan Teki wrote:
> Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
>
> Add panel driver for it.
>
> Signed-off-by: Jagan Teki
Tested-by: Bhushan Shah
--
Bhushan Shah
http://blog.bshah.in
IRC Nick : bshah on Freenode
GPG key
Currently, the Kbuild core manipulates header search paths in a crazy
way [1].
To fix this mess, I want all Makefiles to add explicit $(srctree)/ to
the search paths in the srctree. Some Makefiles are already written in
that way, but not all. The goal of this work is to make the notation
On 1/24/19 6:01 PM, Marcos Paulo de Souza wrote:
Since 4cf6324b17e9, a portion of function blk_cleanup_queue was moved to
a newly created function called blk_exit_queue, including the call of
blkcg_exit_queue. So, adjust the documenation according.
Signed-off-by: Marcos Paulo de Souza
---
+John
HI John,
On Mon, 2019-01-21 at 16:49 +0800, Uwe Kleine-König wrote:
> On Sat, Jan 19, 2019 at 10:54:47AM +0800, Ryder Lee wrote:
> > On Fri, 2019-01-18 at 09:43 +0100, Matthias Brugger wrote:
> > >
> > > On 18/01/2019 04:24, Ryder Lee wrote:
> > > > This adds a property "mediatek,num-pwms"
On 1/24/19 9:29 PM, Gustavo A. R. Silva wrote:
>
>
> On 1/24/19 9:13 PM, Casey Schaufler wrote:
>> On 1/24/2019 6:56 PM, 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
Currently, the Kbuild core manipulates header search paths in a crazy
way [1].
To fix this mess, I want all Makefiles to add explicit $(srctree)/ to
the search paths in the srctree. Some Makefiles are already written in
that way, but not all. The goal of this work is to make the notation
Add lxx2160a compatible to bindings documentation.
Signed-off-by: Peng Ma
---
changed for V4:
- add lx2160a compatible to bindings doc
.../devicetree/bindings/ata/ahci-fsl-qoriq.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
Add SATA device nodes for fsl-lx2160a and enable support
for QDS and RDB boards.
Signed-off-by: Peng Ma
---
changed for V4:
- no change
arch/arm64/boot/dts/freescale/fsl-lx2160a-qds.dts | 16 +++
arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts | 16 +++
On Thu, Jan 24, 2019 at 10:40:50AM -0500, Jerome Glisse wrote:
> On Thu, Jan 24, 2019 at 01:16:16PM +0800, Peter Xu wrote:
> > On Mon, Jan 21, 2019 at 10:09:38AM -0500, Jerome Glisse wrote:
> > > On Mon, Jan 21, 2019 at 03:57:08PM +0800, Peter Xu wrote:
> > > > From: Andrea Arcangeli
> > > >
> >
On Fri, Jan 25, 2019 at 5:04 AM Nicolas Dufresne wrote:
>
> Le mercredi 23 janvier 2019 à 12:28 +0100, Hans Verkuil a écrit :
> > On 01/23/19 11:00, Tomasz Figa wrote:
> > > On Sat, Nov 17, 2018 at 8:37 PM Hans Verkuil wrote:
> > > > On 11/17/2018 05:18 AM, Nicolas Dufresne wrote:
> > > > > Le
On 1/24/19 9:13 PM, Casey Schaufler wrote:
> On 1/24/2019 6:56 PM, 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 warnings:
>>
>>
On Fri, Jan 25, 2019 at 4:55 AM Nicolas Dufresne wrote:
>
> Le jeudi 24 janvier 2019 à 18:06 +0900, Tomasz Figa a écrit :
> > > Actually I just realized the last point might not even be achievable
> > > for some of the decoders (s5p-mfc, mtk-vcodec), as they don't report
> > > which frame
Now that the compatible strings for the display pipeline on the A23 have
been added to the bindings, add the corresponding compatibles to the
device nodes already in the A23/A33 shared dtsi.
While the A23 has the TCON ch1 clock defined in the CCU, and the channel
1 registers are available, it
Hi Jon,
Thanks for reviewing.
On 1/24/19 6:30 PM, Jon Hunter wrote:
On 07/01/2019 03:28, Joseph Lo wrote:
The Tegra210 timer provides fourteen 29-bit timer counters and one 32-bit
timestamp counter. The TMRs run at either a fixed 1 MHz clock rate derived
from the oscillator clock (TMR0-TMR9)
Hi everyone,
This series enables the display pipeline on the Allwinner A23 SoC.
A few fixes are included for corner cases when the frontend isn't
enabled.
The A23 display pipeline is very much the same as the A33, except
that the A23 does not have the SAT IP block embedded within the
display
The A23's display pipeline is similar to the A33. Differences include:
- Display backend supports larger layers, 8192x8192 instead of 2048x2048
- TCON has DMA input
- There is no SAT module packed in the display backend
Add compatible strings for the display pipeline and its components.
The PLL-MIPI clock is somewhat special as it has its own LDOs which
need to be turned on for this PLL to actually work and output a clock
signal.
Add the 2 LDO enable bits to the gate bits.
Fixes: 5690879d93e8 ("clk: sunxi-ng: Add A23 CCU")
Signed-off-by: Chen-Yu Tsai
---
The display backend does not support BGRX. There is also no trace
of this in the original list of supported formats before the commit
b636d3f97d04 ("drm/sun4i: frontend: Add support for the BGRX input
format"). Nor do the backend configuration helpers handle this format.
Remove BGRX
In some cases, such as running a new kernel with an old device tree that
has the frontend disabled, the backend's matching frontend might be
unavailable.
When this happens, the layers should only declare support for formats
that the backend support. This partially reverts commit 1c29d263f624
The A23's display pipeline is similar to the A33. Differences include:
- Display backend supports larger layers, 8192x8192 instead of 2048x2048
- TCON has DMA input
- There is no SAT module packed in the display backend
Add support for the display pipeline and its components.
As the
The Q8 design for A23/A33 tablets have an 18-bit RGB LCD panel connected
to the LCD interface on the SoC, the DC1SW output on the PMIC providing
power for the LCD, and PH7 toggling the reset pin for the panel.
This patch adds a device node for the panel, describing the above, and
enables the
The Q8 tablets follow the A23/A33 tablet reference design, and normally
use a "generic" 800x480 LCD panel. The actual panel may vary between
production runs, and there are no visible markings denoting its model.
This patch uses a panel that has the same dimensions and timings that
are close to
The display pipeline has the same structure, resources and connections
on both the A23 and A33. The differences include:
- compatible strings
- extra clock, reset control, and IO region for SAT in the backend
only found on the A33
- missing ch1 clock for the TCON
However, while the A23
We might want to use the backend pointer from DRM callbacks that get
called within drm_universal_plane_init(), such as the
.format_mod_supported callback.
Move the assignment of the layer's backend pointer to right after the
structure is allocated.
Signed-off-by: Chen-Yu Tsai
---
The NAND controller device node was inserted into the wrong position,
probably due to a rebase or merge, as the file's structure does not
provide enough context for git to accurately match the previous device
node block.
Fixes: d7b843df13ea ("ARM: dts: sun8i: add NAND controller node for
On Wed, Jan 23, 2019 at 09:36:25PM -0500, Richard Guy Briggs wrote:
> V3 namespaced file capabilities were introduced in
> commit 8db6c34f1dbc ("Introduce v3 namespaced file capabilities")
>
> Add support for these by adding the "frootid" field to the existing
> fcaps fields in the NAME and
On 1/24/19 8:14 PM, He Zhe wrote:
>
>
> On 1/25/19 10:26 AM, Jens Axboe wrote:
>> On 1/24/19 7:22 PM, He Zhe wrote:
>>>
>>> On 1/25/19 10:05 AM, Jens Axboe wrote:
On 1/24/19 6:40 PM, He Zhe wrote:
> On 1/24/19 11:40 PM, Jens Axboe wrote:
>> On 1/24/19 1:23 AM, He Zhe wrote:
>>>
On 1/25/19 10:26 AM, Jens Axboe wrote:
> On 1/24/19 7:22 PM, He Zhe wrote:
>>
>> On 1/25/19 10:05 AM, Jens Axboe wrote:
>>> On 1/24/19 6:40 PM, He Zhe wrote:
On 1/24/19 11:40 PM, Jens Axboe wrote:
> On 1/24/19 1:23 AM, He Zhe wrote:
>> On 1/24/19 12:05 AM, Jens Axboe wrote:
>>>
On 1/24/2019 6:56 PM, 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 warnings:
>
> security/integrity/ima/ima_appraise.c:116:26: warning: this statement may
> fall
hclge_mac_update_stats_complete doesn't check for NULL
returns of kcalloc, it may result in an Oops.
Fixes: d174ea75c96a ("net: hns3: add statistics for PFC frames and MAC control
frames")
Signed-off-by: YueHaibing
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 3 +++
1 file
On 2019/1/23 下午5:46, ufo19890...@gmail.com wrote:
From: yuzhoujian
We can monitor the sum wait time of a task group since 'commit 3d6c50c27bd6
("sched/debug: Show the sum wait time of a task group")'. However this
wait_sum just represents the confilct between different task groups, since
it
On Wed, Jan 23, 2019 at 05:55:57PM +0800, Jason Wang wrote:
> It was noticed that the copy_user() friends that was used to access
> virtqueue metdata tends to be very expensive for dataplane
> implementation like vhost since it involves lots of software checks,
> speculation barrier, hardware
On Thu, Jan 24, 2019 at 12:07:54PM +0800, Jason Wang wrote:
> > Meanwhile, could you pls post data comparing this last patch with the
> > below? This removes the speculation barrier replacing it with a
> > (useless but at least more lightweight) data dependency.
>
>
> SMAP off
>
> Your patch:
Remove duplicated include.
Signed-off-by: YueHaibing
---
net/bridge/br_multicast.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/bridge/br_multicast.c b/net/bridge/br_multicast.c
index 2c46c7a..780757b 100644
--- a/net/bridge/br_multicast.c
+++ b/net/bridge/br_multicast.c
@@ -35,7
CONFIG_HAVE_FUTEX_CMPXCHG is currently used to determine if
atomic_inatomic is always working or must be probed. For most
architectures it is either selected, or it is known that they always
have futex_atomic_cmpxchg_inatomic working.
Drop HAVE_FUTEX_CMPXCHG from the Kconfig and let architectures
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
security/integrity/ima/ima_appraise.c:116:26: warning: this statement may fall
through [-Wimplicit-fallthrough=]
Add sdma support for the imx8mq
Changes since V3
Builds against 5.0-rc3.
Dropped sdma device index matching in favour of phandles.
Corrected subsytem name to dmaengine
Devicetree fixes.
Fixed SDMA_H_CONFIG register bug.
Changes since V2
Dropped device tree bindings and added clock ratio check.
The imx8mq is a slightly different variant on the imx7d
Signed-off-by: Angus Ainslie (Purism)
---
Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt
On i.mx8mq, there are two sdma instances, and the common dma framework
will get a channel dynamically from any available sdma instance whether
it's the first sdma device or the second sdma device. Some IPs like
SAI only work with sdma2 not sdma1. To make sure the sdma channel is from
the correct
Add the sdma nodes to the base devicetree for the imx8mq
Signed-off-by: Angus Ainslie (Purism)
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 28 +++
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
This is identical to the imx7d data structures but we need to
be able to differentiate that the imx8mq has 2 sdma controllers.
Signed-off-by: Angus Ainslie (Purism)
---
drivers/dma/imx-sdma.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/dma/imx-sdma.c
On i.mx8 mscale B0 chip, AHB/SDMA clock ratio 2:1 can't be supportted,
since SDMA clock ratio has to be increased to 250Mhz, AHB can't reach
to 500Mhz, so use 1:1 instead.
Based on NXP commit MLK-16841-1 by Robin Gong
Signed-off-by: Angus Ainslie (Purism)
---
drivers/dma/imx-sdma.c | 21
On 01/18/19 at 07:13pm, Kairui Song wrote:
> Currently with "efi=noruntime" in kernel command line, calling
> kexec_file_load will raise below problem:
>
> [ 97.967067] BUG: unable to handle kernel NULL pointer dereference at
>
> [ 97.967894] #PF error: [normal kernel read
On Thu, Jan 24, 2019 at 10:34:32AM -0500, Jerome Glisse wrote:
> On Thu, Jan 24, 2019 at 03:05:03PM +0800, Peter Xu wrote:
> > On Mon, Jan 21, 2019 at 11:24:55AM -0500, Jerome Glisse wrote:
> > > On Mon, Jan 21, 2019 at 03:57:02PM +0800, Peter Xu wrote:
> > > > This is the gup counterpart of the
On Fri, Jan 25, 2019 at 2:57 AM Jernej Škrabec wrote:
>
> Dne ponedeljek, 21. januar 2019 ob 10:57:57 CET je Chen-Yu Tsai napisal(a):
> > On Mon, Jan 21, 2019 at 5:50 PM Maxime Ripard
> wrote:
> > > Hi,
> > >
> > > I'm a bit late to the party, sorry for that.
> > >
> > > On Sat, Jan 12, 2019 at
Remove duplicated include.
Signed-off-by: YueHaibing
---
tools/testing/selftests/bpf/test_flow_dissector.c | 2 --
tools/testing/selftests/bpf/test_maps.c | 1 -
tools/testing/selftests/bpf/test_sockmap.c| 1 -
3 files changed, 4 deletions(-)
diff --git
On 2019/1/24 下午12:53, Michael S. Tsirkin wrote:
- How hard is it to figure out which mode uses which code.
It's as simple as tracing __get_user() usage in vhost process?
Thanks
Well there are now mtu notifiers etc etc. It's hardly as well
contained as that.
We can setup filter out
When we excute the following commands, we got oops
rmmod ipmi_si
cat /proc/ioports
[ 1623.482380] Unable to handle kernel paging request at virtual address
0901d478
[ 1623.482382] Mem abort info:
[ 1623.482383] ESR = 0x9607
[ 1623.482385] Exception class = DABT (current EL), IL =
On 11/14/18 3:15 PM, anthony.yzn...@oracle.com wrote:
>
>
> On 11/10/2018 08:44 AM, Andrea Arcangeli wrote:
>> On Sat, Nov 10, 2018 at 01:22:49PM +, Mel Gorman wrote:
>>> On Fri, Nov 09, 2018 at 02:51:50PM -0500, Andrea Arcangeli wrote:
And if you're in the camp that is concerned
Restrict kdump to only reserve crashkernel below 64TB. Since the kdump
jumping may be from 5-level to 4-level, and the kdump kernel is put
above 64TB in 5-level kernel, then the jumping will fail. And the
crashkernel reservation is done during the 1st kernel bootup, there's
no way to detect the
On Tue, Jan 22, 2019 at 9:38 PM Rob Herring wrote:
>
> On Mon, Jan 21, 2019 at 8:16 PM Chen-Yu Tsai wrote:
> >
> > On Tue, Jan 22, 2019 at 8:19 AM Rob Herring wrote:
> > >
> > > On Mon, Jan 21, 2019 at 05:57:57PM +0800, Chen-Yu Tsai wrote:
> > > > On Mon, Jan 21, 2019 at 5:50 PM Maxime Ripard
In relocate_kernel() CR4.LA57 flag is set before kexec jumping if
the kernel has 5-level paging enabled. Then in boot/compressed/head_64.S,
it will check if the booting kernel is in 4-level or 5-level paging
mode, and handle accordingly. However, the old kernel which doesn't
contain the 5-level
Dear CK,
OK,I will modify according your comments in V3.
Best Regards
Wangyan Wang
On Thu, 2019-01-24 at 14:17 +0800, CK Hu wrote:
> On Fri, 2019-01-18 at 20:59 +0800, Wangyan Wang wrote:
> > From: chunhui dai
>
> Describe something here.
>
> >
> > Fixes: 0fc721b2968e ("drm/mediatek:
This is a RESEND post.
The original v1 post can be found here:
http://lkml.kernel.org/r/20180829141624.13985-1-...@redhat.com
It's trying to fix several corner case issues for kexec/kdump when
dynamic switching of paging mode is enabled in x86_64. Please click
above link to check the details.
Add two bit fields XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
Bit XLF_5LEVEL indicates if 5-level related code is contained
in this kernel.
Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_5LEVEL=y is set.
They are being used in later patch to check if kexec/kdump kernel
is loaded in
Hi,
On Fri, 25 Jan 2019 01:21:26 + "Li, Weinan Z" wrote:
>
> I am not sure about the problem. The commit id "0cce2823ed37" is just
> for the patch of "drm/i915/gvt: Refine error handling for
> prepare_execlist_workload". Is there any other problems I missed?
Its just that the subject line
On 1/24/19 7:22 PM, He Zhe wrote:
>
>
> On 1/25/19 10:05 AM, Jens Axboe wrote:
>> On 1/24/19 6:40 PM, He Zhe wrote:
>>>
>>> On 1/24/19 11:40 PM, Jens Axboe wrote:
On 1/24/19 1:23 AM, He Zhe wrote:
> On 1/24/19 12:05 AM, Jens Axboe wrote:
>> On 1/22/19 8:39 PM, Jens Axboe wrote:
From: Xin Long
Date: Tue, 22 Jan 2019 02:42:41 +0800
> Now sctp_transport_pmtu() passes transport->saddr into .get_dst() to set
> flow sport from 'saddr'. However, transport->saddr is set only when
> transport->dst exists in sctp_transport_route().
>
> If sctp_transport_pmtu() is called without
From: Xin Long
Date: Tue, 22 Jan 2019 02:42:09 +0800
> In the paths:
>
> sctp_sf_do_unexpected_init() ->
> sctp_make_init_ack()
> sctp_sf_do_dupcook_a/b()() ->
> sctp_sf_do_5_1D_ce()
>
> The new chunk 'retval' transport is set from the incoming chunk 'chunk'
> transport. However,
From: Xin Long
Date: Tue, 22 Jan 2019 02:40:12 +0800
> This patch is to improve sctp stream adding events in 2 places:
>
> 1. In sctp_process_strreset_addstrm_out(), move up SCTP_MAX_STREAM
> and in stream allocation failure checks, as the adding has to
> succeed after reconf_timer
From: Xin Long
Date: Tue, 22 Jan 2019 02:39:34 +0800
> This patch is to improve sctp stream reset events in 4 places:
>
> 1. In sctp_process_strreset_outreq(), the flag should always be set with
> SCTP_STREAM_RESET_INCOMING_SSN instead of OUTGOING, as receiver's in
> stream is reset
On 1/25/19 10:05 AM, Jens Axboe wrote:
> On 1/24/19 6:40 PM, He Zhe wrote:
>>
>> On 1/24/19 11:40 PM, Jens Axboe wrote:
>>> On 1/24/19 1:23 AM, He Zhe wrote:
On 1/24/19 12:05 AM, Jens Axboe wrote:
> On 1/22/19 8:39 PM, Jens Axboe wrote:
>> On Jan 22, 2019, at 8:13 PM, He Zhe
From: Frank Rowand
Fix compile warning in create_dyn_event(): 'ret' may be used uninitialized
in this function [-Wuninitialized].
Fixes: 5448d44c3855 ("tracing: Add unified dynamic event framework")
Signed-off-by: Frank Rowand
---
Compile and boot tested only. Please verify the
On 2019/1/25 2:31, Jason Gunthorpe wrote:
> On Thu, Jan 24, 2019 at 11:13:29AM +0800, Wei Hu (Xavier) wrote:
>>
>> On 2019/1/24 6:40, Jason Gunthorpe wrote:
>>> On Sat, Jan 19, 2019 at 11:36:06AM +0800, Wei Hu (Xavier) wrote:
>>>
+static int hns_roce_v2_cmd_hw_resetting(struct hns_roce_dev
In case DOC_CHIPID_G3, mtd->name is not freed in err handling path,
which is alloced by kasprintf(). Fix this by using devm_kasprintf().
Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
Signed-off-by: YueHaibing
---
v4: remove 'kfree' in remove patch
v3: use devm_kasprintf
---
Hi Bin,
Thanks for your help.
Hi Rob,
I find that Samsung describes the usb-connector attribute in DTS, and
uses a private driver.
And try to write DTS as following:
usb-connector node:
musb_con: musb_connector{
compatible = "linux,extcon-usb-gpio","usb-b-connector";
lable =
On 1/24/19 5:20 PM, Florian Fainelli wrote:
>
>
> On 1/24/19 3:45 PM, Frank Rowand wrote:
>> On 1/24/19 12:08 PM, Florian Fainelli wrote:
>>> Since c32569e358ad ("regulator: Use of_node_name_eq for node name
>>> comparisons") Vivien reported the mc13892-regulator complaining about
>>> not being
Hi Joerg,
On 1/24/19 9:22 PM, Joerg Roedel wrote:
On Thu, Jan 24, 2019 at 10:31:32AM +0800, Lu Baolu wrote:
Commit 765b6a98c1de3 ("iommu/vt-d: Enumerate the scalable
mode capability") enables VT-d scalable mode if hardware
advertises the capability. As we will bring up different
features and
From: Justin Chen
To read a channel we require 3 cycles to send, process, and receive
the data. The transfer buffer for the third transaction is left blank.
This leaves it up to the SPI driver to decide what to do.
In one particular case, if the tx buffer is not set the spi driver
sets it to
On 1/24/19 6:40 PM, He Zhe wrote:
>
>
> On 1/24/19 11:40 PM, Jens Axboe wrote:
>> On 1/24/19 1:23 AM, He Zhe wrote:
>>>
>>> On 1/24/19 12:05 AM, Jens Axboe wrote:
On 1/22/19 8:39 PM, Jens Axboe wrote:
> On Jan 22, 2019, at 8:13 PM, He Zhe wrote:
>> LTP case read_all_proc(read_all
Since 4cf6324b17e9, a portion of function blk_cleanup_queue was moved to
a newly created function called blk_exit_queue, including the call of
blkcg_exit_queue. So, adjust the documenation according.
Signed-off-by: Marcos Paulo de Souza
---
block/blk-cgroup.c | 2 +-
1 file changed, 1
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/scsi/fnic/vnic_wq.c: In function 'vnic_wq_alloc_bufs':
drivers/scsi/fnic/vnic_wq.c:50:19: warning:
variable 'vdev' set but not used [-Wunused-but-set-variable]
drivers/scsi/fnic/vnic_rq.c: In function 'vnic_rq_alloc_bufs':
In case of error, the function devm_gpiod_get() returns ERR_PTR() and
never returns NULL. The NULL test in the return value check should be
replaced with IS_ERR().
Fixes: 58963276749e ("extcon: Add support for ptn5150 extcon driver")
Signed-off-by: Wei Yongjun
---
On 2019/1/24 23:00, Boris Brezillon wrote:
> On Wed, 23 Jan 2019 17:28:19 +0800
> YueHaibing wrote:
>
>> In case DOC_CHIPID_G3, mtd->name is not freed in err handling path,
>> which is alloced by kasprintf(). Fix this by using devm_kasprintf().
>>
>> Fixes: ae9d4934b2d7 ("mtd: docg3: add
On 2019/1/25 8:52, Jaegeuk Kim wrote:
> On 01/24, Chao Yu wrote:
>> On 2019/1/23 8:02, Jaegeuk Kim wrote:
>>> Some works after roll-forward recovery can get an error which will release
>>> all the data structures. Let's flush them in order to make it clean.
>>>
>>> One possible corruption came
commit d6abe6df706c (drm/bridge: sil_sii8620: do not have a dependency
of RC_CORE) changed the driver to select both RC_CORE and INPUT.
However, this causes problems with other drivers, in particular an input
driver that depends on MFD_INTEL_LPSS_PCI (to be added in a separate
commit):
I have a patch to fix the memory leak but I haven't been able to test
it yet because I am remote right now and I accidentally bootlooped the
AMD device I am working on. I will have this tested early next week.
Here is the patch for anyone interested.
Curtis Malainey | Software Engineer |
On 2019/1/25 8:56, Jaegeuk Kim wrote:
> On 01/23, Chao Yu wrote:
>> On 2019/1/23 8:02, Jaegeuk Kim wrote:
>>> When we umount f2fs, we need to avoid long delay due to discard commands,
>>> which
>>> is actually taking tens of seconds, if storage is very slow on UNMAP. So,
>>> this
>>> patch
The pull request you sent on Fri, 25 Jan 2019 07:54:37 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-01-25-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d73aba1115cf40630cc8b4b7aed049ed8117b458
Thank you!
--
Deet-doot-dot, I am a bot.
On Thu, Jan 24, 2019 at 04:52:59PM -0800, ndesaulni...@google.com wrote:
> arch/x86/Makefile disables SSE and SSE2 for the whole kernel. The
> AMDGPU drivers modified in this patch re-enable SSE but not SSE2. Turn
> on SSE2 to support emitting double precision floating point instructions
>
Thank Stephen.
I am not sure about the problem. The commit id "0cce2823ed37" is just for the
patch of "drm/i915/gvt: Refine error handling for prepare_execlist_workload".
Is there any other problems I missed?
Regards.
-Weinan
> -Original Message-
> From: Jani Nikula
On 1/24/19 3:45 PM, Frank Rowand wrote:
> On 1/24/19 12:08 PM, Florian Fainelli wrote:
>> Since c32569e358ad ("regulator: Use of_node_name_eq for node name
>> comparisons") Vivien reported the mc13892-regulator complaining about
>> not being able to find regulators.
>>
>> This is because prior
On Thu, Jan 24, 2019 at 05:38:06PM +0530, Balakrishna Godavarthi wrote:
> wcn3990 requires a power pulse to turn ON/OFF along with
> regulators. Sometimes we are observing the power pulses are sent
> out with some time delay, due to queuing these commands. This is
> causing synchronization issues
On Thu, Jan 24, 2019 at 04:52:59PM -0800, ndesaulni...@google.com wrote:
> arch/x86/Makefile disables SSE and SSE2 for the whole kernel. The
> AMDGPU drivers modified in this patch re-enable SSE but not SSE2. Turn
> on SSE2 to support emitting double precision floating point instructions
>
+cc Jens + linux-block
在 2019/1/24 21:43, chenxiang 写道:
In function blk_mq_make_request(), though data->cmd_flags will be
initialized with bio->opf, later bio->opf may be set as REQ_INTEGRITY
if enabled DIX. So need to use bio->opf instead of data->cmd_flags in
function blk_mq_rq_ctx_init(), or
When we umount f2fs, we need to avoid long delay due to discard commands, which
is actually taking tens of seconds, if storage is very slow on UNMAP. So, this
patch introduces timeout-based work on it.
By default, let me give 5 seconds for discard.
Signed-off-by: Jaegeuk Kim
---
Change log from
On 01/23, Chao Yu wrote:
> On 2019/1/23 8:02, Jaegeuk Kim wrote:
> > When we umount f2fs, we need to avoid long delay due to discard commands,
> > which
> > is actually taking tens of seconds, if storage is very slow on UNMAP. So,
> > this
> > patch introduces timeout-based work on it.
> >
> >
On Thu, Jan 24, 2019 at 11:23 PM Kai-Heng Feng
wrote:
> Realtek bluetooth may not work after reboot:
> [ 12.446130] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e,
> hci rev 826c, hci ver 0008
>
> The power is not cut during system reboot, so the firmware is kept in
> Bluetooth
101 - 200 of 1508 matches
Mail list logo
