On Wed, Jan 23, 2019 at 3:37 PM Greg Kroah-Hartman
wrote:
>
> On Wed, Jan 23, 2019 at 02:58:22PM +0200, Gilad Ben-Yossef wrote:
> > Hi,
> >
> > On Tue, Jan 22, 2019 at 5:14 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > When calling debugfs functions, there is no need to ever check the
> > > return
On Thu, 24 Jan 2019 at 07:58, Vivek Gautam wrote:
>
> On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
> wrote:
> >
> > On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> > >
> > > On 21/01/2019 13:36, Ard Biesheuvel wrote:
> > > > On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
> > > >>
> > >
From: Jan Kiszka
Somewhere along recent changes to power control of the wl1835, power-on
became very unreliable on the hikey, failing like this:
wl1271_sdio: probe of mmc2:0001:1 failed with error -16
wl1271_sdio: probe of mmc2:0001:2 failed with error -16
After playing with some dt parameters
On 1/22/19 3:28 PM, Greg Kroah-Hartman wrote:
There's no need to export fcoe_ctlr_destroy_store as a symbol, so remove
the EXPORT_SYMBOL() line for it.
Cc: Johannes Thumshirn
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Signed-off-by: Greg Kroah-Hartman
---
drivers/scsi/fcoe/fcoe_tr
From: Jan Kiszka
Somewhere along recent changes to power control of the wl1835, power-on
became very unreliable on the hikey, failing like this:
wl1271_sdio: probe of mmc2:0001:1 failed with error -16
wl1271_sdio: probe of mmc2:0001:2 failed with error -16
After playing with some dt parameters
On Thu, Jan 24, 2019 at 03:11:53PM +0800, xinwu wrote:
> Hi Sakari,
>
> Thanks for your response.
>
>
> On 2019年01月22日 18:03, Sakari Ailus wrote:
> > Hi Xinwu,
> >
> > On Tue, Jan 22, 2019 at 04:34:44PM +0800, Liu, Xinwu wrote:
> > > device_register exposes the device to userspace.
> > >
> > >
Add a reset controller driver for Xilinx Zynq UltraScale+ MPSoC.
The zynqmp reset-controller has the ability to reset lines
connected to different blocks and peripheral in the Soc.
Signed-off-by: Nava kishore Manne
---
Changes for v3:
-Fixed some minor coding issues as suggested
śr., 23 sty 2019 o 20:18 Uwe Kleine-König
napisał(a):
>
> Hello Bartosz,
>
> On Wed, Jan 23, 2019 at 03:15:32PM +0100, Bartosz Golaszewski wrote:
> > Provide a helper that allows users to retrieve the configured flow type
> > of dummy interrupts. That allows certain users to decide whether an irq
Add documentation to describe Xilinx ZynqMP reset driver
bindings.
Signed-off-by: Nava kishore Manne
Signed-off-by: Jolly Shah
Reviewed-by: Rob Herring
---
.../bindings/reset/xlnx,zynqmp-reset.txt | 52 +++
.../dt-bindings/reset/xlnx-zynqmp-resets.h| 130 ++
2 fil
Nava kishore Manne (3):
firmware: xilinx: Add reset API's
dt-bindings: reset: Add bindings for ZynqMP reset driver
reset: reset-zynqmp: Adding support for Xilinx zynqmp reset
controller.
.../bindings/reset/xlnx,zynqmp-reset.txt | 52 +++
drivers/firmware/xilinx/zynqmp.c
This Patch Adds reset API's to support release, assert
and status functionalities by using firmware interface.
Signed-off-by: Nava kishore Manne
---
Changes for v3:
-Modified the reset start and end macro
values as suggested by Vesa.
Changes for v2:
Hi Rob, Mark,
Ping, can you please provide your feedback?
Even if you have no comments, please say so.
Thanks again!
On Mon, Jan 7, 2019 at 6:51 PM Geert Uytterhoeven
wrote:
> Best Wishes for 2019!
>
> Can you please provide your opinion on parsing the whole device tree for
> "resets" phandle p
Hi all,
Top post, because new argument.
There's lots of really good technical arguments for having the
userspace component of a driver stack that spans both kernel and
userspace open too. For me, that's not really the important argument.
I care about open source, I'm not interested in blobs (bey
On 1/24/19 2:35 AM, shuah wrote:
> On 1/21/19 7:46 AM, Hans Verkuil wrote:
>> Hi Shuah,
>>
>> On 12/18/2018 06:59 PM, sh...@kernel.org wrote:
>>> From: Shuah Khan
>>>
>>> Media Device Allocator API to allows multiple drivers share a media device.
>>> This API solves a very common use-case for medi
On Thu, Jan 24, 2019 at 12:56:15PM +0800, Peter Xu wrote:
> On Mon, Jan 21, 2019 at 12:42:33PM +0200, Mike Rapoport wrote:
>
> [...]
>
> > > @@ -1343,7 +1344,7 @@ static int userfaultfd_register(struct
> > > userfaultfd_ctx *ctx,
> > >
> > > /* check not compatible vmas */
> > >
Hi Laurent,
On Tue, Jan 22, 2019 at 11:10:28PM +0200, Laurent Pinchart wrote:
>
> Thank you for the patch.
>
> On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote:
> > commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge:
>
> Commits are usually quoted using the short 12
On Thu, Jan 24, 2019 at 12:22:00AM +0200, Laurent Pinchart wrote:
>
> On Wed, Jan 23, 2019 at 02:21:05PM -0800, Dmitry Torokhov wrote:
> > On Thu, Jan 24, 2019 at 12:17:35AM +0200, Laurent Pinchart wrote:
> > > On Wed, Jan 23, 2019 at 02:03:42PM -0800, Dmitry Torokhov wrote:
> > >> On Wed, Jan 2
We use below condition to check inline_xattr_size boundary:
if (!F2FS_OPTION(sbi).inline_xattr_size ||
F2FS_OPTION(sbi).inline_xattr_size >=
DEF_ADDRS_PER_INODE -
F2FS_TOTAL_EXTRA_ATTR_SIZE -
Hello Mark,
Thanks again for looking through my changes =)
On Wed, Jan 23, 2019 at 03:51:21PM +, Mark Brown wrote:
> On Tue, Jan 22, 2019 at 11:43:28AM +0200, Matti Vaittinen wrote:
> > Header rohm-bd718x7.h was split to generic and component specific
> > parts. This changed the struct bd718x
This patchset introduces support for MediaTek Command-Queue DMA controller.
MediaTek Command-Queue DMA controller (CQDMA) on MT6765 SoC is dedicated to
memory-to-memory transfer through queue-based descriptor management.
There are only 3 physical channels inside CQDMA, while the driver is extend
From: Shun-Chih Yu
MediaTek Command-Queue DMA controller (CQDMA) on MT6765 SoC is dedicated
to memory-to-memory transfer through queue based descriptor management.
There are only 3 physical channels inside CQDMA, while the driver is
extended to support 32 virtual channels for multiple dma users
From: Shun-Chih Yu
Document the devicetree bindings for MediaTek Command-Queue DMA controller
which could be found on MT6765 SoC or other similar Mediatek SoCs.
Signed-off-by: Shun-Chih Yu
Reviewed-by: Rob Herring
---
.../devicetree/bindings/dma/mtk-cqdma.txt | 31 +
end_pfn is never used after commit ('iommu/iova: Make dma
32bit pfn implicit'), cleanup it.
Cc: Joerg Roedel
Cc: Robin Murphy
Cc: Zhen Lei
Signed-off-by: Shaokun Zhang
---
drivers/iommu/dma-iommu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/iommu/dma-iommu.
> On Wed, Jan 23, 2019 at 5:18 PM Andy Shevchenko
> wrote:
> >
> > On Mon, Jan 14, 2019 at 4:13 PM Guan Yung Tseng
> > wrote:
> > >
> > > Modified NI devices class to PCI_CLASS_COMMUNICATION_MULTISERIAL.
> > > The reason of doing this is because all NI multi port serial cards
> > > use PCI_CLA
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 change that allows the VM_FAULT_RETRY
> > to happen for more than once.
> >
> > Signed-off-by: Peter Xu
>
> So it would be nice to add
Adapt to the new ICB framework for bus bandwidth voting.
This requires the source/destination port ids.
Also this requires a tuple of values.
The tuple is for two different paths - from UFS master
to BIMC slave. The other is from CPU master to UFS slave.
This tuple consists of the average and pea
Hi Catalin,
On 01/23/2019 11:45 PM, Catalin Marinas wrote:
> On Tue, Jan 22, 2019 at 05:44:02AM +, Will Deacon wrote:
>> On Mon, Jan 21, 2019 at 02:21:28PM +, Catalin Marinas wrote:
>>> arm64: Do not issue IPIs for user executable ptes
>>>
>>> From: Catalin Marinas
>>>
>>> Commit 3b8c9f1c
From: Miles Chen
When debugging slab errors in slub.c, sometimes we have to trigger
a panic in order to get the coredump file. Add a debug option
SLAB_WARN_ON_ERROR to toggle WARN_ON() when the option is set.
Change since v1:
1. Add a special debug option SLAB_WARN_ON_ERROR and toggle WARN_ON()
Hi Sakari,
Thanks for your response.
On 2019年01月22日 18:03, Sakari Ailus wrote:
Hi Xinwu,
On Tue, Jan 22, 2019 at 04:34:44PM +0800, Liu, Xinwu wrote:
device_register exposes the device to userspace.
Therefore, while the register process is ongoing, the userspace program
will fail to open the
On Mon, Jan 21, 2019 at 7:55 PM Ard Biesheuvel
wrote:
>
> On Mon, 21 Jan 2019 at 14:56, Robin Murphy wrote:
> >
> > On 21/01/2019 13:36, Ard Biesheuvel wrote:
> > > On Mon, 21 Jan 2019 at 14:25, Robin Murphy wrote:
> > >>
> > >> On 21/01/2019 10:50, Ard Biesheuvel wrote:
> > >>> On Mon, 21 Jan 2
+George/Prashanth.
Guys please see if you have any objections to this patch. I am not
very familiar with this stuff and it would be good to get some
feedback from you guys.
@Rafael: Do you have any comments on this ?
On 17-01-19, 19:00, Xiongfeng Wang wrote:
> Hisilicon chips do not support deli
Hi Joerg,
On 1/11/19 7:16 PM, Joerg Roedel wrote:
+
+static bool
+intel_iommu_dev_has_feat(struct device *dev, enum iommu_dev_features feat)
+{
+ struct device_domain_info *info = dev->archdata.iommu;
+
+ if (feat == IOMMU_DEV_FEAT_AUX)
+ return scalable_mode_support()
On 1/23/19 11:22 AM, Paul E. McKenney wrote:
On Tue, Jan 22, 2019 at 04:42:19PM +0800, Su Yue wrote:
Thanks for your quick reply! Paul
On 1/22/19 12:01 PM, Paul E. McKenney wrote:
On Tue, Jan 22, 2019 at 11:40:53AM +0800, Su Yue wrote:
Hi, guys
While running rcutorture tests with "onoff
Hi stefano,
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2019年1月24日 7:44
> To: h...@infradead.org
> Cc: Stefano Stabellini ; Peng Fan
> ; m...@redhat.com; jasow...@redhat.com;
> xen-de...@lists.xenproject.org; linux-remotep...@vger.kernel.org;
> l
On 23-01-19, 06:22, Guenter Roeck wrote:
> See Documentation/kobject.txt.
>
> "One important point cannot be overstated: every kobject must have a
> release() method, and the kobject must persist (in a consistent state)
> until that method is called. If these constraints are not met, the code is
>
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2019年1月23日 4:00
> To: Peng Fan
> Cc: m...@redhat.com; jasow...@redhat.com; sstabell...@kernel.org;
> h...@infradead.org; xen-de...@lists.xenproject.org;
> linux-remotep...@vger.kernel.org; linux-kerne
Hi Ted,
Commits
f5e55e777cc9 ("fscrypt: return -EXDEV for incompatible rename or link into
encrypted dir")
643fa9612bf1 ("fscrypt: remove filesystem specific build config option")
62230e0d702f ("f2fs: use IS_ENCRYPTED() to check encryption status")
592ddec7578a ("ext4: use IS_ENCRYPTED()
Here is another chapter of the story to get gta04 gnss power
management into the mainline kernel.
There is a w2sg0004 without wakeup line in there, so power state
can only be determined indirectly by looking at the serial data lines.
Then there as also an lna which needs to be powered for real gps
The api forbids writing data there otherwise. Prepare for the
serdev_open()/close() being a part of sirf_set_active.
Signed-off-by: Andreas Kemnade
---
No changes in v4
Changes in v3:
- add more locking
- style cleanup
- mutex *not* renamed since we need a second one
Changes in v2:
- add lo
Devices might have a separate lna between antenna input of the gps
chip and the antenna which might have a separate supply.
Signed-off-by: Andreas Kemnade
---
Changes in v4:
- cleaned up error checking
- was 5/6 earlier
Changes in v3:
- improved error checking
- style cleanup
Changes in v2:
Some Wi2Wi devices do not have a wakeup output, so device state can
only be indirectly detected by looking whether there is communication
over the serial lines.
This approach requires a report cycle set to a value less than 2 seconds
to be reliable.
Signed-off-by: Andreas Kemnade
---
Changes in v
Add lna-supply property.
Signed-off-by: Andreas Kemnade
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/gnss/gnss.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/gnss/gnss.txt
b/Documentation/devicetree/bindings/gnss/gnss.txt
index f1e4a
Add w2sg0004 compatible string since devices without wakeup
pins are now supported.
Signed-off-by: Andreas Kemnade
Reviewed-by: Rob Herring
Reviewed-by: Johan Hovold
---
Documentation/devicetree/bindings/gnss/sirfstar.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/device
This is a leftover of commit 997cde2a2220 ("mtd: nand: denali: skip
driver internal bounce buffer when possible").
Signed-off-by: Masahiro Yamada
---
drivers/mtd/nand/raw/denali.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mtd/nand/raw/denali.h b/drivers/mtd/nand/raw/denali.h
in
Hi all,
Changes since 20190123:
New tree: kspp-gustavo
The vfs tree still had its build failure for which I applied a patch.
The spi tree gained a conflict against the mips tree.
The scsi tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree):
Hi Darren,
> On Dec 12, 2018, at 22:06, Pali Rohár wrote:
>
> On Wednesday 12 December 2018 14:41:25 Kai-Heng Feng wrote:
>> There's a new wmi event generated by dell-wmi when pressing keyboard
>> backlight hotkey:
>> [ 3285.474172] dell_wmi: Unknown key with type 0x0010 and code 0x003f pressed
Quoting Doug Anderson (2019-01-23 15:24:36)
> Hi,
>
> On Tue, Jan 22, 2019 at 5:09 PM Bjorn Andersson
> wrote:
> >
> > On Tue 22 Jan 16:40 PST 2019, Doug Anderson wrote:
> >
> > > Hi,
> > >
> > > On Tue, Jan 22, 2019 at 4:26 PM Bjorn Andersson
> > > wrote:
> > > > > > + clocks = <&
On Fri, 2019-01-18 at 20:59 +0800, Wangyan Wang wrote:
> From: chunhui dai
Describe something here.
>
> Fixes: 0fc721b2968e ("drm/mediatek: add hdmi driver for MT2701 and MT7623")
> Signed-off-by: chunhui dai
Any one who pass a patch should sign off it.
Regards,
CK
> ---
> drivers/gpu/drm/
memcg has a significant number of files exposed to kernfs where their
value is either exposed directly or is "max" in the case of
PAGE_COUNTER_MAX.
There's a fair amount of duplicated code here, since each file involves
turning a seq_file to a css, getting the memcg from the css, safely
reading t
The QCA Rome USB Bluetooth controller has several issues once LPM gets
enabled:
- Fails to get enumerated in coldboot. [1]
- Drains more power (~ 0.2W) when the system is in S5. [2]
- Disappears after a warmboot. [2]
The issue happens because the device lingers at LPM L1 in S5, so device
can't get
From: Vijai Kumar K
PTN5150 is a small thin low power CC (Configurationn Channel)
Logic chip supporting the USB Type-C connector application with
CC control logic detection and indication functions.
Signed-off-by: Vijai Kumar K
[cw00.choi: fix indentation of binding document and change patch su
This series introduces a generic TEE bus driver concept for TEE based
kernel drivers which would like to communicate with TEE based devices/
services.
Patch #1 adds TEE bus concept where devices/services are identified via
Universally Unique Identifier (UUID) and drivers register a table of
device
OP-TEE provides a pseudo TA to enumerate TAs which can act as devices/
services for TEE bus. So implement device enumeration using invoke
function: PTA_CMD_GET_DEVICES provided by pseudo TA to fetch array of
device UUIDs. Also register these enumerated devices with TEE bus as
"optee-clntX" device.
Introduce a generic TEE bus driver concept for TEE based kernel drivers
which would like to communicate with TEE based devices/services. Also
add support in module device table for these new TEE based devices.
In this TEE bus concept, devices/services are identified via Universally
Unique Identifi
This flag indicates that requests in this context should not wait for
tee-supplicant daemon to be started if not present and just return
with an error code. It is needed for requests which should be
non-blocking in nature like ones arising from TEE based kernel drivers
or any in kernel api that use
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 (OP-TEE in this case) only. So this driver
aims to provides a generic interface to OP-TEE based random number
generator service.
Hi Stephen,
Thanks for the test and report. I'll fix it.
On 19. 1. 24. 오후 12:47, Stephen Rothwell wrote:
> Hi Chanwoo,
>
> After merging the extcon tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/extcon/extc
The ax88772_bind() should return error code immediately when the PHY
was not reset properly through ax88772a_hw_reset().
Otherwise, The asix_get_phyid() will block when get the PHY
Identifier from the PHYSID1 MII registers through asix_mdio_read()
due to the PHY isn't ready. Furthermore, it will
On Tue, Jan 22, 2019 at 09:43:38PM -0500, Jerome Glisse wrote:
> On Wed, Jan 23, 2019 at 10:17:45AM +0800, Peter Xu wrote:
> > On Tue, Jan 22, 2019 at 12:02:24PM -0500, Jerome Glisse wrote:
> > > On Tue, Jan 22, 2019 at 05:39:35PM +0800, Peter Xu wrote:
> > > > On Mon, Jan 21, 2019 at 09:05:35AM -0
On Tue, Jan 22, 2019 at 09:39:47PM -0500, Jerome Glisse wrote:
> On Wed, Jan 23, 2019 at 10:12:41AM +0800, Peter Xu wrote:
> > On Tue, Jan 22, 2019 at 11:53:10AM -0500, Jerome Glisse wrote:
> > > On Tue, Jan 22, 2019 at 04:22:38PM +0800, Peter Xu wrote:
> > > > On Mon, Jan 21, 2019 at 10:55:36AM -0
On 2019/1/24 12:18, Stephen Rothwell wrote:
> Hi Bartosz,
>
> After merging the gpio-brgl tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/gpio-davinci.c: In function 'davinci_gpio_get_irq_chip':
> drivers/gpio/gpio-davinci.c:472:9: warning: functi
> > Looks ok for me
>
> With Shah’s blessing, is it possible to merge this patch to your -next tree?
I am currently reviewing it, but the driver is large so it takes time.
signature.asc
Description: PGP signature
On Mon, Jan 21, 2019 at 01:10:39PM +0200, Mike Rapoport wrote:
> On Mon, Jan 21, 2019 at 03:57:18PM +0800, Peter Xu wrote:
> > It does not make sense to try to wake up any waiting thread when we're
> > write-protecting a memory region. Only wake up when resolving a write
> > protected page fault.
Hi Bjorn,
Thank you for the review. I will address your comments in the next patchset.
Regards,
Srinath.
On Fri, Jan 18, 2019 at 8:11 PM Bjorn Helgaas wrote:
>
> On Fri, Jan 18, 2019 at 09:53:20AM +0530, Srinath Mannam wrote:
> > Add changes related to IPROC PCIe RC IP new features.
> >
> > Thi
On Wed, Jan 23, 2019 at 2:52 AM Philipp Zabel wrote:
>
> On Thu, 2019-01-17 at 14:38 -0800, Andrey Smirnov wrote:
> [...]
> > > To be honest, I don't like these two, I'm not convinced anymore that
> > > they actually qualify as reset signals. To me it looks like this is
> > > something that the PC
On Mon, Jan 21, 2019 at 08:54:46AM -0500, Jerome Glisse wrote:
> On Mon, Jan 21, 2019 at 03:57:11PM +0800, Peter Xu wrote:
> > change_protection() was used by either the NUMA or mprotect() code,
> > there's one parameter for each of the callers (dirty_accountable and
> > prot_numa). Further, these
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
> >
> > Accurate userfaultfd WP tracking is possible by tracking exactly which
> > virtual memory ranges were writeprotected by userland. We can't
The interconnect framework is designed to provide a
standard kernel interface to control the settings of
the interconnects on a SoC.
The interconnect API uses a consumer/provider-based model,
where the providers are the interconnect buses and the
consumers could be various drivers.
MDSS is one of
Add interconnect properties such as interconnect provider specifier
, the edge source and destination ports which are required by the
interconnect API to configure interconnect path for MDSS.
Changes in v2:
- None
Changes in v3:
- Remove common property definitions (Rob Herring)
Since the upstream interconnect bus framework has landed
upstream, the existing references of custom bus scaling
needs to be cleaned up.
Changes in v2:
- Fixed build error due to partial clean up
Changes in v3:
- Condense multiple lines into a single line (Sean Paul)
Changes in v
The interconnect API provides an interface for consumer drivers to express
their bandwidth needs in the SoC. This data is aggregated and the on-chip
interconnect hardware is configured to the appropriate power/performance
profile.
MDSS is one of the interconnect consumers which uses the interconne
On Thu, Jan 10, 2019 at 05:01:17PM -0800, Eric Biggers wrote:
>
> Indeed, Chandan Rajendra sent out a new version of the patch which fixes the
> problem (by removing the 'select BLOCK' from fs/ubifs/Kconfig), but it never
> made it into the fscrypt tree and hence never made it into linux-next.
>
On Mon, Jan 21, 2019 at 12:42:33PM +0200, Mike Rapoport wrote:
[...]
> > @@ -1343,7 +1344,7 @@ static int userfaultfd_register(struct
> > userfaultfd_ctx *ctx,
> >
> > /* check not compatible vmas */
> > ret = -EINVAL;
> > - if (!vma_can_userfault(cur))
> > +
Looks good.
Reviewed-by: Chaitanya Kulkarni
From: linux-block-ow...@vger.kernel.org on
behalf of Gustavo A. R. Silva
Sent: Tuesday, January 22, 2019 10:45 PM
To: Philipp Reisner; Lars Ellenberg; Jens Axboe; Joshua Morris; Philip Kelleher
Cc: drbd-...@lists.linbit.com; linux-bl...@vger.ke
On Thu, Jan 24, 2019 at 12:11:28PM +0800, Jason Wang wrote:
>
> On 2019/1/24 下午12:07, Jason Wang wrote:
> >
> > On 2019/1/23 下午10:08, Michael S. Tsirkin wrote:
> > > 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 ac
On Thu, Jan 24, 2019 at 12:07:54PM +0800, Jason Wang wrote:
>
> On 2019/1/23 下午10:08, Michael S. Tsirkin wrote:
> > 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 expensi
On Wed, Jan 23, 2019 at 4:57 AM Vinod Koul wrote:
> On 22-01-19, 15:48, John Stultz wrote:
> > Do let me know if there's an example you'd rather I follow.
>
> To elaborate I was thinking of alternate scheme with:
>
> compatible = "hisilicon,k3-dma-1.0", NULL
> compatible = "hisilic
+ DT ML
On Tue, Jan 22, 2019 at 7:08 PM Jagan Teki wrote:
>
> On Mon, Jan 21, 2019 at 9:46 PM Rob Herring wrote:
> >
> > On Fri, Jan 18, 2019 at 10:01 AM Jagan Teki
> > wrote:
> > >
> > > On Wed, Jan 9, 2019 at 7:08 PM Rob Herring wrote:
> > > >
> > > > Please CC DT list if you want bindings
On Thu, Jan 17, 2019 at 1:18 AM Masahiro Yamada
wrote:
>
> When building an external module, $(obj) is the absolute path to it.
>
> The header search paths from ccflags-y etc. should not be tweaked.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild.
(2/2 was discarded.)
> scri
On Thu, Jan 17, 2019 at 7:03 PM Masahiro Yamada
wrote:
>
> All the callers of size_append pass $(filter-out FORCE,$^).
> Move $(filter-out FORCE,$^) to the definition of size_append.
>
> This makes the callers cleaner because $(call ...) is unneeded
> for a macro with no argument.
>
> Signed-off-b
On Thu, Jan 17, 2019 at 10:23 AM Masahiro Yamada
wrote:
>
> The symbol table in the final archive is unneeded; the linker does not
> require the symbol table after the --whole-archive option. Every object
> file in the archive is included in the link anyway.
>
> Pass thin archives from subdirector
Hi Wolfram,
> On Dec 31, 2018, at 22:36, Shah, Nehal-bakulchandra
> wrote:
>
> Hi Elie,
>
>
> On 12/27/2018 4:52 AM, Elie Morisse wrote:
[snipped]
>
> Looks ok for me
With Shah’s blessing, is it possible to merge this patch to your -next tree?
Kai-Heng
>
> Thanks
> Nehal Shah
On Fri, Jan 18, 2019 at 5:17 PM Masahiro Yamada
wrote:
>
> The recursion of the top Makefile is inefficient.
> Just descend to scripts/kconfig/.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild.
>
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --gi
This code was added by commit 26d266e10e5e ("mtd: nand: denali: fix
raw and oob accessors for syndrome page layout"), but I do not see
sensible reason.
The IRQ flags are correctly reset by denali_cmd_ctrl(), so this code
is unneeded.
Signed-off-by: Masahiro Yamada
---
drivers/mtd/nand/raw/dena
Masahiro Yamada (2):
mtd: rawnand: denali: remove unneeded denali_reset_irq() call
mtd: rawnand: denali: remove unused function argument 'raw'
drivers/mtd/nand/raw/denali.c | 21 +
1 file changed, 9 insertions(+), 12 deletions(-)
--
2.7.4
This argument is not used at all.
Signed-off-by: Masahiro Yamada
---
drivers/mtd/nand/raw/denali.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/mtd/nand/raw/denali.c b/drivers/mtd/nand/raw/denali.c
index 6775644..24aeafc 100644
--- a/drivers/mtd
Hi Bartosz,
After merging the gpio-brgl tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/gpio/gpio-davinci.c: In function 'davinci_gpio_get_irq_chip':
drivers/gpio/gpio-davinci.c:472:9: warning: function returns address of local
variable [-Wreturn-local-addr
From: Suravee Suthikulpanit
When a VM is terminated, the VFIO driver detaches all pass-through
devices from VFIO domain by clearing domain id and page table root
pointer from each device table entry (DTE), and then invalidates
the DTE. Then, the VFIO driver unmap pages and invalidate IOMMU pages.
On 2019/1/24 下午12:07, Jason Wang wrote:
On 2019/1/23 下午10:08, Michael S. Tsirkin wrote:
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 li
On 2019/1/23 下午10:08, Michael S. Tsirkin wrote:
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 softwar
-- Forwarded message -
From: Diego Viola
Date: Thu, Jan 24, 2019 at 1:57 AM
Subject: Nested KVM is broken on a AMD Ryzen 5 2400G
To: , ,
,
Hello,
I am trying to do nested KVM on a Ryzen 5 2400G, my use case is the following:
- Arch Linux as the host OS.
- Ubuntu 18.04.1 as the
On Wed, Jan 23, 2019 at 05:22:03PM -0700, Mathieu Poirier wrote:
> On Fri, 18 Jan 2019 at 18:44, Leo Yan wrote:
[...]
> > After applying this patch series, we can verify sample flags with below
> > command:
> >
> > # perf script -F,-time,+flags,+ip,+sym,+dso,+addr,+symoff -k vmlinux
>
> Since
Hi James,
Today's linux-next merge of the scsi tree got a conflict in:
drivers/scsi/arcmsr/arcmsr_hba.c
between commit:
750afb08ca71 ("cross-tree: phase out dma_zalloc_coherent()")
from Linus' tree and commit:
3e3153b050fc ("scsi: arcmsr: Use dma_alloc_coherent to replace
dma_zalloc_co
Hi Chanwoo,
After merging the extcon tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
WARNING: modpost: missing MODULE_LICENSE() in drivers/extcon/extcon-ptn5150.o
see include/linux/module.h for more information
Introduced by commit
58963276749e ("extcon: Add suppor
On Sat, 2019-01-12 at 16:21:23 UTC, =?utf-8?q?Jonathan_Neusch=C3=A4fer?= wrote:
> The Hollywood GPIO controller is connected to the Hollywood PIC (&PIC1)
> at IRQs 10 and 11; IRQ 10 for GPIO lines that are configured for access
> by the PPC, 11 for GPIO lines that are configured for access by the
>
On Fri, 2019-01-11 at 03:22:31 UTC, Masahiro Yamada wrote:
> The header search path -I. in kernel Makefiles is very suspicious;
> it allows the compiler to search for headers in the top of $(srctree),
> where obviously no header file exists.
>
> Commit 46f43c6ee022 ("KVM: powerpc: convert marker p
On Tue, 2019-01-08 at 15:08:00 UTC, Christophe Leroy wrote:
> ipic_set_highest_priority(), ipic_enable_mcp() and ipic_disable_mcp()
> are unused. This patch drops them.
>
> Signed-off-by: Christophe Leroy
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/8acb88682cc00a41a677c245
On Fri, 2018-09-07 at 15:35:26 UTC, Igor Stoppa wrote:
> WARN_ON() already contains an unlikely(), so it's not necessary to
> wrap it into another.
>
> Signed-off-by: Igor Stoppa
> Cc: Arseny Solokha
> Cc: Benjamin Herrenschmidt
> Cc: Paul Mackerras
> Cc: Michael Ellerman
> Cc: linuxppc-...@l
On Tue, 2019-01-08 at 21:00:10 UTC, "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 elements for that array. For example:
>
> struct foo {
On Mon, 2019-01-14 at 20:13:04 UTC, Mathieu Malaterre wrote:
> GCC supports -mcpu=G4
>
> This patch gives the opportunity to select ALTIVEC for this variant.
>
> Signed-off-by: Mathieu Malaterre
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/9bd10b649826774bb5e1e7fb67544e65
1 - 100 of 980 matches
Mail list logo
