Add support for MSI
Signed-off-by: Xiaowei Song
Signed-off-by: Yao Chen
---
drivers/pci/dwc/pcie-kirin.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/pci/dwc/pcie-kirin.c b/drivers/pci/dwc/pcie-kirin.c
index d2970a009eb5..369bf87d2fff 100644
--- a/dr
Before Version Patches
==
patch v5
https://patchwork.kernel.org/patch/10493797/
patch v4
https://patchwork.kernel.org/patch/10402399/
patch v3
https://www.spinics.net/lists/linux-pci/msg72322.html
patch v2
https://www.spinics.net/lists/kernel/msg2797610.html
patch v1
https://
> + * This is a MIPS specific ioremap variant. ioremap_cacheable_cow
> + * requests a cachable mapping with CWB attribute enabled.
> */
> #define ioremap_cacheable_cow(offset, size) \
> __ioremap_mode((offset), (size), _CACHE_CACHABLE_COW)
This isn't actually used
> -Original Message-
> From: Sascha Hauer [mailto:s.ha...@pengutronix.de]
> Sent: 2018年7月11日 14:25
> To: Robin Gong
> Cc: vk...@kernel.org; dan.j.willi...@intel.com; shawn...@kernel.org; Fabio
> Estevam ; li...@armlinux.org.uk;
> linux-arm-ker...@lists.infradead.org; ker...@pengutronix.de
On Wed, Jul 11, 2018 at 06:37:02AM +, Robin Gong wrote:
>
> > -Original Message-
> > From: Vinod [mailto:vk...@kernel.org]
> > Sent: 2018年7月10日 23:33
> > To: Robin Gong
> > Cc: dan.j.willi...@intel.com; shawn...@kernel.org;
> > s.ha...@pengutronix.de; Fabio Estevam ;
> > li...@armlinu
The "Beaglebone Enhanced" by Sancloud is based on the Beaglebone Black,
but with the following differences:
* Gigabit capable PHY
* Extra USB hub, optional i2c control
* lps3331ap barometer connected over i2c
* MPU6050 6 axis MEMS accelerometer/gyro connected over i2c
* 1GiB DDR3 RAM
* RTL87
The "Beaglebone Enhanced" by Sancloud is based on the Beaglebone Black,
but with the following differences:
* Gigabit capable PHY
* Extra USB hub, optional i2c control
* lps3331ap barometer connected over i2c
* MPU6050 6 axis MEMS accelerometer/gyro connected over i2c
* 1GiB DDR3 RAM
* RTL87
Add vendor prefix for Sancloud Ltd.
Signed-off-by: Koen Kooi
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 7cad066.
Hi Andy,
On Tue, 10 Jul 2018 19:19:21 +0300 Andy Shevchenko wrote:
> On Tue, 2018-07-10 at 11:15 +0800, Jisheng Zhang wrote:
> > For Synopsys DesignWare 8250 uart which version >= 4.00a, there's a
> > valid divisor latch fraction register. The fractional divisor width is
> > 4bits ~ 6bits.
> >
>
Hi all,
Changes since 20180710:
News: This release fails my simple PowerPC qemu boot without kvm ...
The driver-core tree gained conflicts against the iommu tree.
The scsi-mkp tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 5214
5338 fil
> -Original Message-
> From: Vinod [mailto:vk...@kernel.org]
> Sent: 2018年7月10日 23:33
> To: Robin Gong
> Cc: dan.j.willi...@intel.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; Fabio Estevam ;
> li...@armlinux.org.uk; linux-arm-ker...@lists.infradead.org;
> ker...@pengutronix.de; dma
From: "Joel Fernandes (Google)"
Here we introduce a test module for introducing a long preempt or irq
disable delay in the kernel which the preemptoff or irqsoff tracers can
detect. This module is to be used only for test purposes and is default
disabled.
Following is the expected output (only b
From: "Joel Fernandes (Google)"
Only resending the test module and kselftest patches with minor changes
as suggested by Steve.
Previous posting of the series is at: https://lkml.org/lkml/2018/6/7/1162
Joel Fernandes (Google) (2):
lib: Add module for testing preemptoff/irqsoff latency tracers
From: "Joel Fernandes (Google)"
Here we add unit tests for the preemptoff and irqsoff tracer by using a
kernel module introduced previously to trigger long preempt or irq
disabled sections in the kernel.
Reviewed-by: Masami Hiramatsu
Acked-by: Masami Hiramatsu
Signed-off-by: Joel Fernandes (Go
On Wed, Jul 11, 2018 at 12:23:11AM +0800, Robin Gong wrote:
> Add check_bd_buswidth() to minimize the code size.
>
> Signed-off-by: Robin Gong
> ---
> drivers/dma/imx-sdma.c | 64
> +++---
> 1 file changed, 29 insertions(+), 35 deletions(-)
>
> diff
On Wed, Jul 11, 2018 at 12:23:10AM +0800, Robin Gong wrote:
> Add MEMCPY support, meanwhile, add SDMA_BD_MAX_CNT instead
> of '0x'.
>
> Signed-off-by: Robin Gong
> ---
> +static struct dma_async_tx_descriptor *sdma_prep_memcpy(
> + struct dma_chan *chan, dma_addr_t dma_dst,
> +
]
>> [also build test ERROR on v4.18-rc4 next-20180709]
>> [if your patch is applied to the wrong git tree, please drop us a note to
>> help improve the system]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Denis-OSTERLAND/rtc-isl1208-fixes-documentation-
Hi Michael:
Thanks for your review.
On 7/11/2018 5:29 AM, Michael Kelley (EOSG) wrote:
> From: Tianyu Lan Monday, July 9, 2018 2:03 AM
>> Hyper-V supports a pv hypercall HvFlushGuestPhysicalAddressSpace to
>> flush nested VM address space mapping in l1 hypervisor and it's to
>> reduce ove
On Mon, Jul 09, 2018 at 06:42:29PM -0400, Boris Ostrovsky wrote:
> On 07/02/2018 12:02 PM, Mark Rutland wrote:
> > On Mon, Jul 02, 2018 at 05:46:55PM +0200, Peter Zijlstra wrote:
> >> On Mon, Jul 02, 2018 at 04:12:50PM +0100, Mark Rutland wrote:
> >>> +static struct pt_regs *perf_get_sample_regs(st
On Tue, Jul 10, 2018 at 09:44:57PM -0400, Steven Rostedt wrote:
> On Wed, 2 May 2018 10:12:14 +1000
> Nicholas Piggin wrote:
>
> > > I have mixed feelings about this patch, I am Ok with this patch but I
> > > suggest its sent with the follow-up patch that shows its use of this.
> > > And also app
To improve page allocator's performance for order-0 pages, each CPU has
a Per-CPU-Pageset(PCP) per zone. Whenever an order-0 page is needed,
PCP will be checked first before asking pages from Buddy. When PCP is
used up, a batch of pages will be fetched from Buddy to improve
performance and the size
On Wed, Jul 11, 2018 at 1:13 AM, Mike Marshall wrote:
> Hi...
>
> I applied this patch to 4.18.0-rc4. It applied cleanly and there's no xfstests
> regressions. Sorry if I held you up any...
>
> You can add: Tested-By: Mike Marshall
>
Thanks Mike. Can we get this patch in queue for 4.19 merge win
Hi Prakash,
On 07/10/2018 09:19 PM, Prakash, Prashanth wrote:
On 7/9/2018 11:42 PM, George Cherian wrote:
Hi Prakash,
On 07/09/2018 10:12 PM, Prakash, Prashanth wrote:
Hi George,
On 7/9/2018 4:10 AM, George Cherian wrote:
Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides perform
Hi Stephen,
On 7 July 2018 at 03:55, Stephen Boyd wrote:
> Quoting Joel Stanley (2018-06-28 16:15:40)
>> The HPLL can be configured through a register (SCU24), however some
>> platforms chose to configure it through the strapping settings and do
>> not use the register. This was not noticed as th
On Tue, Jul 10, 2018 at 07:06:07PM +0100, Mark Rutland wrote:
> It's possible for userspace to control event_id. Sanitize event_id when
> using it as an array index, to inhibit the potential spectre-v1 write
> gadget.
>
> This class of issue is also known as CVE-2018-3693, or "bounds check bypass
On Wed, Jul 04, 2018 at 10:46:41AM +0200, David Sterba wrote:
> On Tue, Jul 03, 2018 at 11:01:02AM +0100, Mark Rutland wrote:
> > In many cases, it would be useful to be able to use the full
> > sanity-checked refcount helpers regardless of CONFIG_REFCOUNT_FULL, as
> > this would help to avoid dupl
Andrew,
there seem to be some renew of interest in 9P lately, so if you'd like I
can take care of rounding these up and prepare a pull request for 4.19
(as we're already well into 4.18 release cycle, I believe most of the
patches can wait)
This patch however I consider important enough to take fo
On Mon, Jul 2, 2018 at 2:20 PM Jae Hyun Yoo
wrote:
>
> This patch changes the order of enum aspeed_i2c_master_state and
> enum aspeed_i2c_slave_state defines to make their initial value to
> ASPEED_I2C_MASTER_INACTIVE and ASPEED_I2C_SLAVE_STOP respectively.
> In case of multi-master use, if a slav
On Tue, Jul 03, 2018 at 11:30:38AM -0700, Kees Cook wrote:
> On Tue, Jul 3, 2018 at 3:01 AM, Mark Rutland wrote:
> > In many cases, it would be useful to be able to use the full
> > sanity-checked refcount helpers regardless of CONFIG_REFCOUNT_FULL, as
> > this would help to avoid duplicate warnin
On Wed, Jul 11, 2018 at 5:21 AM, Al Viro wrote:
[...]
> @@ -3407,8 +3407,6 @@ static int do_last(struct nameidata *nd,
> if (!error && will_truncate)
> error = handle_truncate(file);
> out:
> - if (unlikely(error) && (*opened & FILE_OPENED))
> - fput(fi
On Mon, Jul 2, 2018 at 2:14 PM Jae Hyun Yoo
wrote:
>
> There are some log printing without a newline character. This
> patch adds the missing newline characters.
>
> Signed-off-by: Jae Hyun Yoo
> ---
> drivers/i2c/busses/i2c-aspeed.c | 18 +-
> 1 file changed, 9 insertions(+), 9
> -Original Message-
> From: Vinod [mailto:vk...@kernel.org]
> Sent: 2018年7月10日 23:31
> To: Robin Gong
> Cc: dan.j.willi...@intel.com; shawn...@kernel.org;
> s.ha...@pengutronix.de; Fabio Estevam ;
> li...@armlinux.org.uk; linux-arm-ker...@lists.infradead.org;
> ker...@pengutronix.de; dmae
> Hi Robin,
>
> On 11-07-18, 00:23, Robin Gong wrote:
> > Add MEMCPY support, meanwhile, add SDMA_BD_MAX_CNT instead of
> > '0x'.
>
> latter part should be its own patch. Never mix things
Okay, I will split it even for this minor change.
>
> > +static struct dma_async_tx_descriptor *sdma_pre
The bmc-misc-ctrl platform driver stitches together the associated
devicetree bindings and the sysfs-devices-platform-field ABI to expose
fields described in the devicetree to userspace via sysfs.
While the userspace interface does not provide an abstraction over the
hardware, it does provide some
The AST2500 has VGA scratch registers that are read-only, SuperIO
scratch registers that are a mix of read-only and read-write, and a
graphics DAC mux that must be read or configured in the process of
booting e.g. an OpenPOWER system.
These capabilities do not really have a place in other drivers,
Baseboard Management Controllers (BMCs) are embedded SoCs that exist to
provide remote management of (primarily) server platforms. BMCs are
often tightly coupled to the platform in terms of behaviour and provide
many hardware features integral to booting and running the host system.
Some of these
Hello,
This series is a second stab at exposing hardware controls on Baseboard
Management Controllers that are hard to fit into any a coherent abstraction.
The patches introduce new devicetree bindings and sysfs attributes, along with
a platform driver to expose devicetree nodes of the former as
"Fields" expose control of hardware directly to userspace where
appropriate. Examples of expected use are single bit switches or other
small masks of registers where the range of values is entirely policy
driven and the field is not part of a larger, coherent design.
These fields can be from read-
On Tue, Jul 10, 2018 at 08:49:58PM -0400, Steven Rostedt wrote:
> On Thu, 28 Jun 2018 11:21:49 -0700
> Joel Fernandes wrote:
>
> > From: "Joel Fernandes (Google)"
> >
> > Here we add unit tests for the preemptoff and irqsoff tracer by using a
> > kernel module introduced previously to trigger a
On Tue, Jul 10, 2018 at 08:47:07PM -0400, Steven Rostedt wrote:
> On Thu, 28 Jun 2018 11:21:48 -0700
> Joel Fernandes wrote:
>
> > From: "Joel Fernandes (Google)"
> >
> > In this patch we introduce a test module for simulating a long atomic
> > section in the kernel which the preemptoff or irqs
Now that all producers of dev_pagemap instances in the kernel are
properly converted to EXPORT_SYMBOL_GPL, fix up implicit consumers that
interact with dev_pagemap owners via put_page(). To reiterate,
dev_pagemap producers are EXPORT_SYMBOL_GPL because they adopt and
modify core memory management i
The devm_memremap_pages() facility is tightly integrated with the
kernel's memory hotplug functionality. It injects an altmap argument
deep into the architecture specific vmemmap implementation to allow
allocating from specific reserved pages, and it has Linux specific
assumptions about page struct
devm semantics arrange for resources to be torn down when
device-driver-probe fails or when device-driver-release completes.
Similar to devm_memremap_pages() there is no need to support an explicit
remove operation when the users properly adhere to devm semantics.
Note that devm_kzalloc() automati
The routines hmm_devmem_add(), and hmm_devmem_add_resource() duplicated
devm_memremap_pages() and are now simple now wrappers around the core
facility to inject a dev_pagemap instance into the global pgmap_radix
and hook page-idle events. The devm_memremap_pages() interface is base
infrastructure f
Commit e8d513483300 "memremap: change devm_memremap_pages interface to
use struct dev_pagemap" refactored devm_memremap_pages() to allow a
dev_pagemap instance to be supplied. Passing in a dev_pagemap interface
simplifies the design of pgmap type drivers in that they can rely on
container_of() to l
The last step before devm_memremap_pages() returns success is to
allocate a release action, devm_memremap_pages_release(), to tear the
entire setup down. However, the result from devm_add_action() is not
checked.
Checking the error from devm_add_action() is not enough. The api
currently relies on
In preparation for consolidating all ZONE_DEVICE enabling via
devm_memremap_pages(), teach it how to handle the constraints of
MEMORY_DEVICE_PRIVATE ranges.
Cc: Christoph Hellwig
Cc: "Jérôme Glisse"
Reported-by: Logan Gunthorpe
Reviewed-by: Logan Gunthorpe
Signed-off-by: Dan Williams
---
ker
Given the fact that devm_memremap_pages() requires a percpu_ref that is
torn down by devm_memremap_pages_release() the current support for
mapping RAM is broken.
Support for remapping "System RAM" has been broken since the beginning
and there is no existing user of this this code path, so just kil
Changes since v3 [1]:
* Collect Logan's reviewed-by on patch 3
* Collect John's and Joe's tested-by on patch 8
* Update the changelog for patch 1 and 7 to better explain the
EXPORT_SYMBOL_GPL rationale.
* Update the changelog for patch 2 to clarify that it is a cleanup to
make the following pat
Add support for the Zodiac Inflight Innovations i.MX51-base SCU3 Ethernet
Switch Board (ESB)
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger.kernel.org
Cc
Add DT bindings for regulators implemented in UniPhier SoCs.
Signed-off-by: Kunihiko Hayashi
---
.../bindings/regulator/uniphier-regulator.txt | 57 ++
1 file changed, 57 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/uniphier-regulator.tx
Initial commit to add support for regulators implemented in UniPhier SoCs.
This supports USB VBUS only.
Signed-off-by: Kunihiko Hayashi
---
drivers/regulator/Kconfig | 8 ++
drivers/regulator/Makefile | 1 +
drivers/regulator/uniphier-regulator.c | 213 ++
This series add new regulator controller support for UniPhier SoCs.
Currently this supports USB3 VBUS controller only. This USB3 VBUS belongs to
USB3 glue layer.
Changes since v2:
- replace functions in regulator_ops with helper ones
Changes since v1:
- dt-bindings: add description of glue layer
On 11 July 2018 at 06:59, Eddie James wrote:
>
>
> On 07/10/2018 02:39 PM, Wolfram Sang wrote:
>>>
>>> Sorry, what do you mean "show up as"? Yes, we could first shift all our
>>> addresses in user-space before passing them to the driver, so that the
>>> msg->addr field is exactly what the hardware
Hi Alexei,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1e09177acae32a61586af26d83ca5ef591cdcaf5
commit: 819dd92b9c0bc7bce9097d8c1f14240f471bb386 bpfilter: switch to CC from
HOSTCC
date: 5 weeks ago
config: alp
Hi all,
After merging the scsi-mkp tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/spinlock_types.h:18:0,
from include/linux/spinlock.h:82,
from drivers/scsi/libfc/fc_rport.c:61:
drivers/scsi/libfc/f
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
MAINTAINERS
between commit:
54e45716a84a ("scsi: remove NCR_D700 driver")
from Linus' tree and commit:
01a21986f8ed ("MAINTAINERS: Add Sam as the maintainer for NCSI")
from the scsi-mkp tree.
I fixed it up (see b
Windows I/O, such as the real-time clock. The address register (port
0x70 in the RTC case) can use coalesced I/O, cutting the number of
userspace exits by half when reading or writing the RTC.
Guest access rtc like this: write register index to 0x70, then write or
read data from 0x71. writing 0x7
Hi Michal
Sorry , I l forget to update the changlog for the second patch, but
the cpuset information is not missing. Do I still need to make the
v14 or just update the changelog for v13?
Thanks
I am on vacation away from an actual keyboard until next week. Will look at it
then.
> Le 10 juill. 2018 à 20:52, Kees Cook a écrit :
>
>> On Tue, Jun 26, 2018 at 8:56 PM, Nicolas Pitre
>> wrote:
>> The vt code translates UTF-8 strings into glyph index values and stores
>> those glyph values
On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote:
OMAP5 sensors don't claim COUNTER feature support (they use
COUNTER_DELAY feature instead) so there is no need to set fields
of struct temp_sensor_registers which are only used for COUNTER
feature.
There should be no functional changes ca
Hi all,
Today's linux-next merge of the driver-core tree got a conflict in:
drivers/iommu/ipmmu-vmsa.c
between commits:
0b8ac1409641 ("iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code")
3701c123e1c1 ("iommu/ipmmu-vmsa: Hook up r8a779(70|95) DT matching code")
98dbffd39a65 ("iommu/ipmm
On Tue, Jul 10, 2018 at 7:59 PM Al Viro wrote:
>
> Umm... Something like [..]
Ack.
Linus
On Tue, 10 Jul 2018, Eric W. Biederman wrote:
>
> Use the information we already have to document which signals are sent
> to a group of processes and which signals are sent to a single process
> or a single thread.
Ahh.
This is much nicer than what I was playing with yesterday, trying to
sep
mmc_select_hs400es() calls mmc_select_bus_width() which will continue
to set 4bit transfer mode if fail to set 8bit mode. The bus width
should not be set to 4bit in HS400es.
When fail to set 8bit mode, need return error directly for HS400es.
Signed-off-by: Hongjie Fang
---
drivers/mmc/core/mmc.
On Tue, Jul 10, 2018 at 07:44:59PM -0700, Linus Torvalds wrote:
> I like the patch, I hate the commit message.
>
> It makes sense right now in this sequence, but I'd really like the
> commit message to say _why_ this sequence led up to this point.
>
> Right now I still remember you trying this, a
Hi Douglas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on agross/for-next]
[also build test ERROR on next-20180710]
[cannot apply to v4.18-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Ok, you didn't seem to have a coverletter email, so I'm just replying
to the first one.
Apart from the couple of totally trivial things I reacted to, this
looks very clean and nice. And now I sat in front of the computer
while reading it, so I could follow along better.
So apart from the small st
Wen Yang and majiang
report that a periodic signal received during fork can cause fork to
continually restart preventing an application from making progress.
The code was being overly pesimistic. Fork needs to guarantee that a
signal sent to multiple processes is logically delivered before the
When f_setown is called a pid and a pid type are stored. Replace the use
of PIDTYPE_PID with PIDTYPE_TGID as PIDTYPE_TGID goes to the entire thread
group. Replace the use of PIDTYPE_MAX with PIDTYPE_PID as PIDTYPE_PID now
is only for a thread.
Update the users of __f_setown to use PIDTYPE_TGID i
Use the information we already have to document which signals are sent
to a group of processes and which signals are sent to a single process
or a single thread. This information will be needed later to ensure
signals are atomic with respect to fork (always coming in before or
after the system cal
Now that we can make the distinction use PIDTYPE_TGID rather than
PIDTYPE_PID. There is no immediate effect as they point point at the
same task, but this allows using enum pid_type instead of bool group
in the signal sending functions.
Signed-off-by: "Eric W. Biederman"
---
kernel/signal.c
The function is general and inline so there is no need
to hide it inside of exit.c
Signed-off-by: "Eric W. Biederman"
---
include/linux/sched/signal.h | 8
kernel/exit.c| 8
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/include/linux/sched/signa
Everywhere except in the pid array we distinguish between a tasks pid and
a tasks tgid (thread group id). Even in the enumeration we want that
distinction sometimes so we have added __PIDTYPE_TGID. With leader_pid
we almost have an implementation of PIDTYPE_TGID in struct signal_struct.
Add PIDT
send_sig is thread only making it the wrong command for an action
directed at a process.
force_sig does not set SEND_SIG_FORCED (causing unnecessary work in
__send_signal) and jumps through unnecessary hoops to deal
with blocked and ignored signals which SIGKILL can neve
This is cheap and no cost so we might as well.
Signed-off-by: "Eric W. Biederman"
---
init/init_task.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/init/init_task.c b/init/init_task.c
index 74f60baa2799..7914ffb8dc73 100644
--- a/init/init_task.c
+++ b/init/init_task.c
@@ -33,6 +33,7 @@ s
To access these fields the code always has to go to group leader so
going to signal struct is no loss and is actually a fundamental simplification.
This saves a little bit of memory by only allocating the pid pointer array
once instead of once for every thread, and even better this removes a
few p
Signed-off-by: "Eric W. Biederman"
---
virt/kvm/kvm_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index ada21f47f22b..4c593acc4510 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -2560,7 +2560,7 @@ static long kv
The cost is the the same and this removes the need
to worry about complications that come from de_thread
and group_leader changing.
__task_pid_nr_ns has been updated to take advantage of this change.
Signed-off-by: "Eric W. Biederman"
---
arch/ia64/kernel/asm-offsets.c | 2 +-
arch/ia64/
On Sun, Jul 01, 2018 at 10:52:59PM +0530, Manivannan Sadhasivam wrote:
> This patchset adds I2C controller support for Actions Semiconductor S900 SoC.
> This driver has been structured in a way such that there will be only
> one controller driver for the whole Owl family series (S500, S700 and
> S9
On Mon, Jul 09, 2018 at 01:22:58PM +0800, Lu Baolu wrote:
> The obsolete per iommu pasid tables are no longer used. Hence,
> clean up them.
>
> Cc: Ashok Raj
> Cc: Jacob Pan
> Cc: Kevin Tian
> Cc: Liu Yi L
> Signed-off-by: Lu Baolu
> Reviewed-by: Liu Yi L
> ---
> drivers/iommu/intel-iommu.c
I like the patch, I hate the commit message.
It makes sense right now in this sequence, but I'd really like the
commit message to say _why_ this sequence led up to this point.
Right now I still remember you trying this, and having to revert it
because it didn't work before all the fput/put_filp i
On Tue, Jul 10, 2018 at 07:35:23PM -0700, Linus Torvalds wrote:
> This one looked odd to me.
>
> Then I saw 5/42, and it made more sense.
>
> I think the explanation is a bit misleading. Technically correct, but
> not *why* you did it.
Probably should fold these two together, now that reordering
The following patches should be close. I took some patches I haven't
taken the time to merge yet that make PIDTYPE_TGID not a hack.
Updated the code that deals with signals to handle PIDTYPE_TGID.
Pushed the pid type down from the signal senders all of the way
down into __send_signal. That wo
On Tue, Jul 10, 2018 at 07:39:07PM -0700, Linus Torvalds wrote:
> On Tue, Jul 10, 2018 at 7:23 PM Al Viro wrote:
> >
> >
> > cleanup_all:
> > + if (unlikely(error > 0)) {
> > + WARN_ON(1);
> > + error = -EINVAL;
> > + }
>
> Can we please do this as
>
>
On Tue, Jul 10, 2018 at 7:23 PM Al Viro wrote:
>
>
> cleanup_all:
> + if (unlikely(error > 0)) {
> + WARN_ON(1);
> + error = -EINVAL;
> + }
Can we please do this as
if (WARN_ON_ONCE(error > 0))
error = -EINVAL;
instead?
That alr
This one looked odd to me.
Then I saw 5/42, and it made more sense.
I think the explanation is a bit misleading. Technically correct, but
not *why* you did it.
Linus
Hi Mark,
On Tue, 10 Jul 2018 18:44:51 +0100 wrote:
> On Tue, Jul 10, 2018 at 10:27:17AM +0900, Kunihiko Hayashi wrote:
>
> > +static int uniphier_regulator_enable(struct regulator_dev *rdev)
> > +{
> > + struct uniphier_regulator_priv *priv = rdev_get_drvdata(rdev);
> > +
> > + return regma
On 5/14/2018 5:12 PM, Bartlomiej Zolnierkiewicz wrote:
The comments about ADC code values are incorrect. Fix them.
Acked-by: Keerthy
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/thermal/ti-soc-thermal/omap4-thermal-data.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
From: Al Viro
Signed-off-by: Al Viro
---
fs/file_table.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/fs/file_table.c b/fs/file_table.c
index 1f14b80a4e67..eee7cf629e52 100644
--- a/fs/file_table.c
+++ b/fs/file_table.c
@@ -51,6 +51,7 @@ static void file_free_rcu(st
From: Al Viro
always equal to ->f_cred
Signed-off-by: Al Viro
---
fs/internal.h | 2 +-
fs/namei.c| 4 ++--
fs/open.c | 15 ++-
3 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/fs/internal.h b/fs/internal.h
index 66473bf388e4..ab84a29f4874 100644
--- a/fs/i
From: Al Viro
Doing iput() after path_put() is wrong.
Cc: sta...@kernel.org
Signed-off-by: Al Viro
---
drivers/misc/cxl/api.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/misc/cxl/api.c b/drivers/misc/cxl/api.c
index 753b1a698fc4..6b16946f9b05 100644
---
From: Al Viro
Signed-off-by: Al Viro
---
fs/internal.h | 1 -
fs/namei.c| 7 +--
fs/open.c | 17 +
3 files changed, 6 insertions(+), 19 deletions(-)
diff --git a/fs/internal.h b/fs/internal.h
index ab84a29f4874..33a28438570e 100644
--- a/fs/internal.h
+++ b/fs/int
From: Al Viro
... just use put_pipe_info() to get the pipe->files down to 1 and let
fput()-called pipe_release() do freeing.
Signed-off-by: Al Viro
---
fs/pipe.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/fs/pipe.c b/fs/pipe.c
index bb0840e234f3..9405e455f5b1 10
From: Al Viro
Signed-off-by: Al Viro
---
fs/open.c| 2 +-
include/linux/security.h | 5 ++---
security/security.c | 4 ++--
3 files changed, 5 insertions(+), 6 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index c8fd5126c50e..008a65e82de5 100644
--- a/fs/open.c
+++ b/fs/
From: Al Viro
no point in rcu-delays here
Signed-off-by: Al Viro
---
fs/file_table.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/file_table.c b/fs/file_table.c
index 7ec0b3e5f05d..1f14b80a4e67 100644
--- a/fs/file_table.c
+++ b/fs/file_table.c
@@ -123,11 +123,10
From: Al Viro
Parallel to FILE_CREATED, goes into ->f_mode instead of *opened.
NFS is a bit of a wart here - it doesn't have file at the point
where FILE_CREATED used to be set, so we need to propagate it
there (for now). IMA is another one (here and everywhere)...
Note that this needs do_dentr
From: Al Viro
basically, "is that instance set up enough for regular fput(), or
do we want put_filp() for that one".
NOTE: the only alloc_file() caller that could be followed by put_filp()
is in arch/ia64/kernel/perfmon.c, which is (Kconfig-level) broken.
Signed-off-by: Al Viro
---
fs/file_ta
From: Al Viro
Just check FMODE_OPENED in __fput() and be done with that...
Signed-off-by: Al Viro
---
fs/file_table.c | 15 +--
fs/namei.c | 4 ++--
fs/open.c| 11 +++
include/linux/file.h | 1 -
4 files changed, 10 insertions(+), 21 deletions(-
From: Al Viro
Failure of ->open() should *not* be followed by fput(). Fixed by
using filp_clone_open(), which gets the cleanups right.
Signed-off-by: Al Viro
---
drivers/gpu/drm/drm_lease.c | 16 +---
fs/internal.h | 1 -
include/linux/fs.h | 1 +
3 files
1 - 100 of 932 matches
Mail list logo
