This board has an AXP813 PMIC so let's include its dtsi.
Signed-off-by: Quentin Schulz
---
arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts
b/arch/arm/boot/dts/sun8i-a83t-tbs-a711.dts
index
The AXP813 has only two GPIOs. GPIO0 can either be used as a GPIO, an
LDO regulator or an ADC. GPIO1 can be used either as a GPIO or an LDO
regulator.
Moreover, the status bit of the GPIOs when in input mode is not offset
by 4 unlike the AXP209.
Signed-off-by: Quentin Schulz
---
.../devicetree/
As GPIO/pinctrl driver now supports AXP813, add a cell for it.
Signed-off-by: Quentin Schulz
---
drivers/mfd/axp20x.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c
index 2468b431bb22..d8c92fbbd170 100644
--- a/drivers/mfd/axp20x.c
+++ b/driver
This driver used to do only GPIO features of the GPIOs in X-Powers
AXP20X. Now that we have migrated everything to the pinctrl subsystem
and added pinctrl features, rename everything related to pinctrl from
gpio to pctl to ease the understanding of differences between GPIO
and pinctrl features.
Si
To prepare for patches that will add support for a new PMIC that has a
different GPIO input status register, add a gpio_status_offset within
axp20x_pctl structure and use it.
Signed-off-by: Quentin Schulz
---
drivers/pinctrl/pinctrl-axp209.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(
On Fri, 22 Sep 2017 11:35:49 +0200,
Takashi Iwai wrote:
>
> On Thu, 21 Sep 2017 17:38:53 +0200,
> Andrey Konovalov wrote:
> >
> > Hi!
> >
> > I've got the following report while fuzzing the kernel with syzkaller.
> >
> > On commit ebb2c2437d8008d46796902ff390653822af6cc4 (Sep 18).
> >
> >
Am 30.09.2017 um 20:31 schrieb Al Viro:
> On Mon, Sep 18, 2017 at 08:32:19PM +0200, Stefan Mätje wrote:
>> Hi,
>>
>> there is a change in Linus' mainline kernel
>> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/x86/include/asm/uaccess.h?id=6c51e67b64d169419fb1331803
On 02/10/2017 12:36, George Dunlap wrote:
>>> Although I'm not business man, I don't think the top cloud provider[s]
>>> would allow nested virtualization, however mature nested virtualization
>>> is. Even xen-pv is unable to be nested in the aws and azure.
>>
>> Check the contributors to KVM neste
On Sun 01-10-17 16:29:48, Shakeel Butt wrote:
> >
> > Going back to Michal's example, say the user configured the following:
> >
> >root
> > /\
> > A D
> > / \
> >B C
> >
> > A global OOM event happens and we find this:
> > - A > D
> > - B, C, D are oomgroups
>
On Mon, Oct 02, 2017 at 02:09:35PM +0200, Javier González wrote:
> > On 1 Oct 2017, at 15.25, Rakesh Pandit wrote:
> >
> > While separating read and erase mempools in 22da65a1b pblk_g_rq_cache
> > was used two times to set aside memory both for erase and read
> > requests. Because same kmem cach
On Sun, 2017-10-01 at 22:25 -0500, Eric W. Biederman wrote:
> Mimi Zohar writes:
> > There should be no open writers in ima_check_last_writer(), so the
> > file shouldn't be changing.
>
> This is slightly tangential but I think important to consider.
> What do you do about distributed filesystem
It has been reported that some platforms (odroid-c2) may require
a different tx phase setting to operate at high speed (hs200 and hs400)
To improve the situation, this patch includes tx phase in the tuning
process.
Fixes: d341ca88eead ("mmc: meson-gx: rework tuning function")
Reported-by: Heiner
Hi Marco,
On Fri, 2017-09-22 at 15:05 -0300, Marco Franchi wrote:
> Improve the binding example by removing the '@di0' notation, which
> fixes the following build warning:
>
> Warning (unit_address_vs_reg): Node /display@di0 has a unit name, but
> no reg property
>
> Signed-off-by: Marco Franch
This patchset fixes the issues reported by Heiner [0] with the odroid-c2.
In a nutshell, this series does the following:
* Make sure the mmc clock rate is not set higher than what is requested
* Reset the tuning values on mmc power cycle instead of POWER_ON
* Add tuning of the tx phase to the tuni
Using CLK_DIVIDER_ROUND_CLOSEST is unsafe as the mmc clock could be
rounded to a rate higher the specified rate. Removing this flag ensure
that, if the rate needs to be rounded, it will be rounded down.
Fixes: 51c5d8447bd7 ("MMC: meson: initial support for GX platforms")
Signed-off-by: Jerome Brun
Resetting the phase when POWER_ON is set the set_ios() call means that the
phase is reset almost every time the set_ios() is called, while the
expected behavior was to reset the phase on a power cycle.
This had gone unnoticed until now because in all mode (except hs400) the
tuning is done after th
Hi,
On 9/28/2017 8:31 PM, matthew.gerl...@linux.intel.com wrote:
>
> Hi Vignesh,
>
> I tried this patch on an Arria10 SOCFPGA devkit against the 4.1.33-ltsi
> kernel, and it did not go well. Commands to the flash chip timedout
> resulting in the probe function failing. I ran into other probl
On 29/09/2017 22:17, Marcelo Tosatti wrote:
> On Fri, Sep 29, 2017 at 07:05:41PM +0200, Paolo Bonzini wrote:
>> On 29/09/2017 18:40, Marcelo Tosatti wrote:
>>> Thats not the state of things (userspace in vcpu-0 is not specially tailored
>>> to not violate latencies in vcpu-1): that is not all user
On Wed, 27 Sep 2017 08:19:27 +0200,
Bhumika Goyal wrote:
>
> Make these const as they are only passed to a const argument of the
> function snd_pcm_set_ops in the file referencing them. Also, add const
> to the declaration in the headers.
>
> Structures found using Coccinelle and changes done by
On Tue, 22 Aug 2017, Nicolas Boichat wrote:
> Computes and forwards the device timestamp according to the
> specification.
>
> Many devices use a 16-bit timestamp field, with a resolution
> of 100us, therefore rolling around very frequently (every
> 6.5 seconds). To make sure there is no ambiguit
On Thu, 2017-09-28 at 12:56 -0400, Don Dutile wrote:
> Well, my point is more like: why put it in uio?
> why not make it available via pcie, setup while/if no driver attached?
> i.e., other non-uio users can use the mechanism like libvirt? ...
> if a PF driver isn't required.
This would allow
Hi Andy,
From by git archaeology, looks like last use of GET_CR0_INTO_EAX
was removed long ago, in 2008 (see commit below).
Right now, I only grep it here in a comment in entry_32.S:
/*
* We use macros for low-level operations which need to be overridden
* for paravirtualization. The followin
On Sunday, October 1, 2017 9:30:53 PM CEST Jérémy Lefaure wrote:
> Using the ARRAY_SIZE macro improves the readability of the code. It is
> useless to re-invent the ARRAY_SIZE macro so let's use it.
>
> It is useless to re-invent the ARRAY_SIZE macro so let's use it.
ACPICA is soewhat special cod
On Monday, October 2, 2017 12:30 PM, Michael S. Tsirkin wrote:
> On Sat, Sep 30, 2017 at 12:05:52PM +0800, Wei Wang wrote:
> > +static int send_balloon_page_sg(struct virtio_balloon *vb,
> > +struct virtqueue *vq,
> > +void *addr,
> > +
On Monday, October 2, 2017 11:12:42 AM CEST Jiri Slaby wrote:
> These are all functions which are invoked from elsewhere, so we annotate
> them as global using the new SYM_FUNC_START. And their ENDPROC's by
> SYM_FUNC_END.
>
> And make sure ENTRY/ENDPROC is not defined on X86_64, given these were
On Mon, Oct 02, 2017 at 06:32:18AM -0500, Brijesh Singh wrote:
> Because sev_enabled will always be 'false' when we are booting on bare
> metal. Whereas when we are running under hypervisor then this variable
> will be true for the SEV guest, please see [1].
Ok, then. This needs absolutely to be d
On Mon, 2017-10-02 at 08:09 -0400, Mimi Zohar wrote:
> On Mon, 2017-10-02 at 15:35 +1100, Dave Chinner wrote:
> > On Sun, Oct 01, 2017 at 07:42:42PM -0400, Mimi Zohar wrote:
> > > On Mon, 2017-10-02 at 09:34 +1100, Dave Chinner wrote:
> > > > On Sun, Oct 01, 2017 at 11:41:48AM -0700, Linus Torvalds
Sorry, lost track of this thing..
On Mon, Aug 14, 2017 at 02:44:59PM +0700, Suravee Suthikulpanit wrote:
> > Why does the degenerate code fail to remove things?
> >
>
> Sorry for confusion. Actually, the degenerate code does remove the duplicate
> NODE sched-domain.
>
> The difference is, wit
> On 1 Oct 2017, at 15.26, Rakesh Pandit wrote:
>
> If pblk_core_init fails lets destroy all global caches.
>
> Signed-off-by: Rakesh Pandit
> ---
> drivers/lightnvm/pblk-init.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/lightnvm/pblk-init.c b/driver
Commit b6c159a9cb69 ("i2c: ismt: Don't duplicate the receive length for
block reads") broke I2C block reads. It aimed to fix normal SMBus block
read, but changed the correct behavior of I2C block read in the process.
According to Documentation/i2c/smbus-protocol, one vital difference
between norma
On 30/09/2017 19:15, Paul E. McKenney wrote:
> On Sat, Sep 30, 2017 at 07:41:56AM +0800, Boqun Feng wrote:
>> On Fri, Sep 29, 2017 at 04:43:39PM +, Paul E. McKenney wrote:
>>> Not to be repetitive, but if the schedule() is on the guest, this change
>>> really does silently break up an RCU read-
On 9/24/2017 6:43 PM, Marek Vasut wrote:
> On 09/24/2017 02:33 PM, Vignesh R wrote:
>>
>>
>> On 9/24/2017 5:29 PM, Marek Vasut wrote:
>>> On 09/24/2017 12:59 PM, Vignesh R wrote:
As per 66AK2G02 TRM[1] SPRUHY8F section 11.15.5.3 Indirect Access
Controller programming sequence, a delay e
On Mon, Oct 02, 2017 at 02:24:34PM +0200, Michal Hocko wrote:
> On Sun 01-10-17 16:29:48, Shakeel Butt wrote:
> > >
> > > Going back to Michal's example, say the user configured the following:
> > >
> > >root
> > > /\
> > > A D
> > > / \
> > >B C
> > >
> > > A
On 2 October 2017 at 10:12, Jiri Slaby wrote:
> There is a couple of assembly functions, which are invoked only locally
> in the file they are defined. In C, we mark them "static". In assembly,
> annotate them using SYM_{FUNC,CODE}_START_LOCAL (and switch their
> ENDPROC to SYM_{FUNC,CODE}_END too
On Mon, Oct 02, 2017 at 02:30:33PM +0200, Paolo Bonzini wrote:
> I don't understand why is it correct to delay interrupt injection just
> because VCPU0 is running in a spinlock-protected region? I just cannot
> see the reason why it's safe and not a recipe for priority inversions.
It is indeed no
On Thu 2017-09-28 15:15:00, Joe Lawrence wrote:
> When an incoming module is considered for livepatching by
> klp_module_coming(), it iterates over multiple patches and multiple
> kernel objects in this order:
>
> list_for_each_entry(patch, &klp_patches, list) {
> klp_for_each_
On 10/2/2017 7:50 PM, Jiri Olsa wrote:
> On Thu, Sep 28, 2017 at 08:45:16PM +0800, Jin Yao wrote:
>
> SNIP
>
>> +return ret;
>> +
>> +return do_write(ff, &evlist->last_sample_time,
>> +sizeof(evlist->last_sample_time));
>> +}
>> +
>> static void print_hostna
On Mon 02-10-17 00:51:11, Alexandru Moise wrote:
> This attempts to bring more flexibility to how hugepages are allocated
> by making it possible to decide whether we want the hugepages to be
> allocated from ZONE_MOVABLE or to the zone allocated by the "kernelcore="
> boot parameter for non-movabl
On 10/2/2017 7:52 PM, Jiri Olsa wrote:
> On Thu, Sep 28, 2017 at 08:45:20PM +0800, Jin Yao wrote:
>> perf report has a --time option to limit the time range of output.
>> It only supports absolute time.
>>
>> Now this option is extended to support multiple time ranges and
>> support the percent o
Currently while search/inserting in RB tree,
memcmp used for comparing out of tree pages with in tree pages.
But on each compare step memcmp for pages start at
zero offset, i.e. that just ignore forward progress.
That make some overhead for search in deep RB tree and/or with
bit pages (4KiB+), so
Hi,
I am fuzzing linux 4.13-rc7 and I got a report about a memory leak.
Here is the alloc stack:
2017/10/01 02:08:59 BUG: memory leak:
unreferenced object 0x880069cf0300 (size 312):
comm "syz-executor0", pid 3032, jiffies 4294722144 (age 10.773s)
hex dump (first 32 bytes):
01 00 00 00
On Mon, Oct 02, 2017 at 08:52:59PM +0800, Jin, Yao wrote:
>
>
> On 10/2/2017 7:50 PM, Jiri Olsa wrote:
> > On Thu, Sep 28, 2017 at 08:45:16PM +0800, Jin Yao wrote:
> >
> > SNIP
> >
> >> + return ret;
> >> +
> >> + return do_write(ff, &evlist->last_sample_time,
> >> +
On Oct 02 2017 or thereabouts, Jiri Kosina wrote:
> On Tue, 22 Aug 2017, Nicolas Boichat wrote:
>
> > Computes and forwards the device timestamp according to the
> > specification.
> >
> > Many devices use a 16-bit timestamp field, with a resolution
> > of 100us, therefore rolling around very fre
For example on arm64 board, this add info to "user" entries in vmallocinfo
Before :
[...]
0xff8008997000 0xff80089d8000 266240 user
[...]
Afer :
[...]
0xff8008997000 0xff80089d8000 266240 atomic_pool_init+0x0/0x1d8 user
[...]
This help to debug mapping issues, and is consistent w
On Mon 2017-10-02 14:06:03, Linus Walleij wrote:
> On Mon, Oct 2, 2017 at 10:41 AM, Pavel Machek wrote:
>
> >> Bounce buffers are being removed from v4.15
>
> As Adrian states, this would make any last bugs go away. I would
> even consider putting this patch this into fixes if it solves the prob
On Fri, Sep 29, 2017 at 6:19 PM, Maxime Ripard
wrote:
> On Fri, Sep 29, 2017 at 08:22:55AM +, Chen-Yu Tsai wrote:
>> static const struct sun4i_tcon_quirks sun5i_a13_quirks = {
>> - .has_unknown_mux = true,
>> - .has_channel_1 = true,
>> + .has_unknown_mux= true,
>> +
On 08/30/2017 12:32 PM, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Mon, Aug 21, 2017 at 10:40:44AM +0800, Wei Ni wrote:
>>
>>
>> On Friday, August 11, 2017 10:57 AM, Zhang Rui wrote:
>>> On Mon, 2017-07-24 at 19:29 +0300, Mikko Perttunen wrote:
On Tegra186, the BPMP (Boot
On Sun, 2017-10-01 at 02:15 -0700, Christoph Hellwig wrote:
> > - task_active_pid_ns(current)->last_pid);
> > + task_active_pid_ns(current)->idr.idr_next-1);
>
> I think we want a well documented helper for this pattern instead
> of poking into the internals.
>
> Also is last
> -Original Message-
> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> Sent: Monday, October 2, 2017 6:53 AM
> To: Andy Shevchenko
> Cc: Gabriel M. Elder ; Gabriele Mazzotta
> ; Limonciello, Mario ;
> Darren Hart ; Andy Shevchenko ;
> platform-driver-...@vger.kernel.org; linux-kernel@vger
On Sun, Oct 1, 2017 at 10:30 PM, Jérémy Lefaure
wrote:
> Using the ARRAY_SIZE macro improves the readability of the code. Also,
> it is not always useful to use a variable to store this constant
> calculated at compile time.
>
> + {&gainctrl_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev
On Sun, 2017-10-01 at 16:05 +0530, Gargi Sharma wrote:
> On Sun, Oct 1, 2017 at 2:45 PM, Christoph Hellwig
> wrote:
> > > - task_active_pid_ns(current)->last_pid);
> > > + task_active_pid_ns(current)->idr.idr_next-1);
> >
> > I think we want a well documented helper for th
On Thu, Sep 28, 2017 at 7:02 AM, Mario Limonciello
wrote:
> Some cases the wrong type was used for errors and checks can be
> done more cleanly.
Oops, I forgot about this patch, so, please, disregard my comment WRT
to strncmp() use to the other patch.
> Signed-off-by: Mario Limonciello
> Revie
On Monday 02 October 2017 13:06:46 mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Pali Rohár [mailto:pali.ro...@gmail.com]
> > Sent: Monday, October 2, 2017 6:53 AM
> > To: Andy Shevchenko
> > Cc: Gabriel M. Elder ; Gabriele Mazzotta
> > ; Limonciello, Mario ;
> > Darre
On Mon, Oct 2, 2017 at 4:15 PM, Pali Rohár wrote:
> On Monday 02 October 2017 13:06:46 mario.limoncie...@dell.com wrote:
> Ok! Gabriel, can you provide us your DMI information about your machine?
>
> They are included in following files:
> /sys/class/dmi/id/sys_vendor
> /sys/class/dmi/id/product_
On Mon, Oct 02, 2017 at 06:52:01AM -0500, Brijesh Singh wrote:
> Thank you for the patch. One of feedback in RFC patches was to put the
> command id and their definitions in amd-memory-encryption.txt hence I
> was trying to follow that recommendation. Most of ioctls I have seen in
> api.txt are eit
On 10/02/2017 03:52 AM, Lorenzo Pieralisi wrote:
Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now
possible to define IRQ mapping functions on a per PCI host bridge basis.
Actual IRQ allocation is carried out by the pci_assign_irq() function in
pci_device_probe() - to make sure a
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Monday, October 2, 2017 8:16 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; LKML ; Platform Driver
> ; Andy Lutomirski ;
> quasi...@google.com; Pali Rohár
> Subject: Re: [PATCH v3 8/8] platfor
Looks fine,
Reviewed-by: Christoph Hellwig
I think I already gate it to basically the same patch as queued
up by Bart, but here again:
Reviewed-by: Christoph Hellwig
On Wed, 2017-09-27 at 17:45 +0200, Oleg Nesterov wrote:
> On 09/27, Gargi Sharma wrote:
> >
> > -#define find_next_offset(map, off)
> > \
> > - find_next_zero_bit((map)->page, BITS_PER_PAGE,
> > off)
> > -
>
> this should go into the previous patch, but
userfaultfd syscall wasn't invoked, so I don't believe that should
> matter.
>
> Thanks,
> Mark.
>
> [1]
> https://www.kernel.org/pub/linux/kernel/people/mark/bugs/20171002-skbuff-bug/
> [2] https://lkml.kernel.org/r/20170920180413.26713-1-aarca...@redhat.com
>
As soon as the sensor is powered on, change the I2C address to the one
specified in DT. This allows to use multiple physical sensors connected
to the same I2C bus.
Signed-off-by: Todor Tomov
---
drivers/media/i2c/ov5645.c | 42 ++
1 file changed, 42 insert
On Sat, Sep 30, 2017 at 02:12:11PM +0800, Ming Lei wrote:
> We need to pass PREEMPT flags to blk_queue_enter()
> for allocating request with RQF_PREEMPT in the
> following patch.
I don't like having another name space for flags. It seems like
we should simply pass ops on, and then map the nowait
On 01/10/2017 03:31, Boqun Feng wrote:
> Sasha Levin reported a WARNING:
>
> | WARNING: CPU: 0 PID: 6974 at kernel/rcu/tree_plugin.h:329
> | rcu_preempt_note_context_switch kernel/rcu/tree_plugin.h:329 [inline]
> | WARNING: CPU: 0 PID: 6974 at kernel/rcu/tree_plugin.h:329
> | rcu_note_context_swit
Hi Gustavo,
On Thu, Sep 07, 2017 at 03:42:11PM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan
Hi,
Refer to the documentation on the first patch for the details. The previous
iteration is here:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg118077.html
The 2nd patch propose
On 10/2/2017 7:58 PM, Jiri Olsa wrote:
> On Thu, Sep 28, 2017 at 08:45:21PM +0800, Jin Yao wrote:
>
> SNIP
>
>> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
>> index 9092de0..7fd3063 100644
>> --- a/tools/perf/builtin-script.c
>> +++ b/tools/perf/builtin-script.c
>> @@
Hi,
On Thu, Sep 07, 2017 at 03:42:13PM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan
Turn the reserved2 field into fence_fd that we will use to send
an in-fence to the kernel and return an out-fence from the kernel to
userspace.
Two new flags were added, V4L2_BUF_FLAG_IN_FENCE, that sho
Hi,
On Thu, Sep 07, 2017 at 03:42:15PM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan
Receive in-fence from userspace and add support for waiting on them
before queueing the buffer to the driver. Buffers are only queued
to the driver once they are ready. A buffer is ready when its
in-fenc
Hi,
On Thu, Sep 07, 2017 at 03:42:21PM -0300, Gustavo Padovan wrote:
From: Gustavo Padovan
For explicit synchronization (and soon for HAL3/Request API) we need
the v4l2-driver to guarantee the ordering in which the buffers were queued
by userspace. This is already true for many drivers, but we
On 10/1/2017 12:16 PM, Borislav Petkov wrote:
On Sun, Oct 01, 2017 at 12:00:31PM -0500, Brijesh Singh wrote:
When SEV feature is disabled, KVM will not be able to launch any SEV
guests. When SEV support is available, KVM can enable it in a specific
VM by setting SEV bit before executing the VMR
t; applied to avoid a userfaultfd bug. The userfaultfd syscall appears in
> all of the Syzkaller logs, so there is the chance that this is related,
> but as I've not seen any other issues I suspect that's unlikely.
>
> Thanks,
> Mark.
>
> [1]
> https://www.kerne
On Mon, 2017-10-02 at 09:35 -0400, Rik van Riel wrote:
> On Wed, 2017-09-27 at 17:45 +0200, Oleg Nesterov wrote:
> > On 09/27, Gargi Sharma wrote:
> > >
> > > -#define find_next_offset(map, off)
> > >
> > > \
> > > - find_next_zero_bit((map)->page, BITS_PE
On Mon, Oct 02, 2017 at 12:39:30PM +, Wang, Wei W wrote:
> On Monday, October 2, 2017 12:30 PM, Michael S. Tsirkin wrote:
> > On Sat, Sep 30, 2017 at 12:05:52PM +0800, Wei Wang wrote:
> > > +static int send_balloon_page_sg(struct virtio_balloon *vb,
> > > + struct virtq
Improve the binding example by removing the '@di0' notation, which
fixes the following build warning:
Warning (unit_address_vs_reg): Node /display@di0 has a unit name, but
no reg property
Signed-off-by: Marco Franchi
---
Change since v1:
-change 'display-di0' to 'disp0'.
Documentation/devicetr
As mentioned in the reply to Bart, I'd much rather use BLK_MQ_REQ_*
for the sane blk_get_request version (which should have the same
prototype as blk_mq_alloc_request) instead of having another flags
namespace.
Jérémy Lefaure writes:
> Using the ARRAY_SIZE macro improves the readability of the code. Also,
> it is not always useful to use a variable to store this constant
> calculated at compile time.
>
> Found with Coccinelle with the following semantic patch:
> @r depends on (org || report)@
> type T;
On Mon, Oct 02, 2017 at 11:53:31AM +0100, Robin Murphy wrote:
> Anchor nodes are not reserved IOVAs in the way that copy_reserved_iova()
> cares about - while the failure from reserve_iova() is benign since the
> target domain will already have its own anchor, we still don't want to
> be triggering
On 10/2/2017 9:00 PM, Jiri Olsa wrote:
> On Mon, Oct 02, 2017 at 08:52:59PM +0800, Jin, Yao wrote:
>>
>>
>> On 10/2/2017 7:50 PM, Jiri Olsa wrote:
>>> On Thu, Sep 28, 2017 at 08:45:16PM +0800, Jin Yao wrote:
>>>
>>> SNIP
>>>
+ return ret;
+
+ return do_write(ff, &evlist->
> +void blk_set_preempt_only(struct request_queue *q, bool preempt_only)
> +{
> + blk_mq_freeze_queue(q);
> + if (preempt_only)
> + queue_flag_set_unlocked(QUEUE_FLAG_PREEMPT_ONLY, q);
> + else
> + queue_flag_clear_unlocked(QUEUE_FLAG_PREEMPT_ONLY, q);
> + bl
On Mon, Oct 02, 2017 at 08:44:21AM -0500, Tom Lendacky wrote:
> I think we're talking about the same thing. You want sev_enabled to
> indicate whether you can launch an SEV guest. We would still need an
> sev_active variable to distinguish between SME and SEV during kernel
> execution when the sm
> + /*
> + * Simply quiesing SCSI device isn't safe, it is easy
> + * to use up requests because all these allocated requests
> + * can't be dispatched when device is put in QIUESCE.
> + * Then no request can be allocated and we may hang
> + * somewhere, such as system
On Mon, Oct 02, 2017 at 02:45:34PM +0200, Paolo Bonzini wrote:
> On 30/09/2017 19:15, Paul E. McKenney wrote:
> > On Sat, Sep 30, 2017 at 07:41:56AM +0800, Boqun Feng wrote:
> >> On Fri, Sep 29, 2017 at 04:43:39PM +, Paul E. McKenney wrote:
> >>> Not to be repetitive, but if the schedule() is o
Arnd Bergmann wrote:
> With KASAN and a couple of other patches applied, this driver is one
> of the few remaining ones that actually use more than 2048 bytes of
> kernel stack:
>
> broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
> 'wlc_phy_workarounds_nphy_gainctrl':
> broadcom/brcm80211/
Arnd Bergmann wrote:
> The stack consumption in this driver is still relatively high, with one
> remaining warning if the warning level is lowered to 1536 bytes:
>
> drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_n.c:17135:1: error:
> the frame size of 1880 bytes is larger than 1536 b
On Mon, Oct 02, 2017 at 03:01:55PM +0200, Matthieu CASTET wrote:
> For example on arm64 board, this add info to "user" entries in vmallocinfo
>
> Before :
> [...]
> 0xff8008997000 0xff80089d8000 266240 user
> [...]
>
> Afer :
> [...]
> 0xff8008997000 0xff80089d8000 266240 atomic_p
On 10/02/2017 11:40 AM, Arnd Bergmann wrote:
> The hardened strlen() function causes rather large stack usage
> in at least one file in the kernel when CONFIG_KASAN is enabled:
>
> drivers/media/usb/em28xx/em28xx-dvb.c: In function 'em28xx_dvb_init':
> drivers/media/usb/em28xx/em28xx-dvb.c:2062:1:
On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko wrote:
> On Mon 02-10-17 00:51:11, Alexandru Moise wrote:
> > This attempts to bring more flexibility to how hugepages are allocated
> > by making it possible to decide whether we want the hugepages to be
> > allocated from ZONE_MOVABLE or to t
On Sun, Oct 1, 2017 at 12:57 PM, Tetsuo Handa
wrote:
>> > I inserted u-SD card, only to realize that it is not detected as it
>> > should be. And dmesg indeed reveals:
>>
>> Tetsuo asked me to report this to linux-mm.
>>
>> But 2^4 is 16 pages, IIRC that can't be expected to work reliably, and
>>
On Mon, Oct 02, 2017 at 11:49:33AM +0200, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.14-rc3[1] compared to v4.13[2].
Hi,
a question regarding the um-defconfig build:
http://kisskb.ellerman.id.au/kisskb/target/2974/
The error thrown looks
This patchset adds basic support for the Qualcomm Camera Control Interface
(CCI) controller found on Qualcomm MSM8916/APQ8016 and MSM8996/APQ8996 SoC.
CCI has one I2C bus on MSM8916/APQ8016 and two I2C busses on MSM8996/APQ8096.
The present driver supports the first I2C bus only.
The driver is im
This commit adds the CCI node for the CCI controller that resides on
the Qualcomm MSM8916 and MSM8996 platforms.
CC: Andy Gross
CC: Rob Herring
CC: Mark Rutland
CC: devicet...@vger.kernel.org
CC: linux-...@vger.kernel.org
CC: linux-arm-ker...@lists.infradead.org
Signed-off-by: Todor Tomov
---
Hi Qiao,
On Mon, Sep 25, 2017 at 07:02:03PM +0800, qiaozhou wrote:
> Will this bodging patch be merged? It can solve the livelock issue on arm64
> platforms(at least improve a lot).
Whilst it seemed to help in some cases, I'm not keen to merge it until
we've identified a sensible way to parameter
Add an entry for Qualcomm Camera Control Interface driver.
Signed-off-by: Todor Tomov
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6671f37..aa3484f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11158,6 +11158,13 @@ W:
http://wir
Add DT binding document for Qualcomm Camera Control Interface driver
CC: Rob Herring
CC: Mark Rutland
CC: devicet...@vger.kernel.org
Signed-off-by: Todor Tomov
---
.../devicetree/bindings/i2c/i2c-qcom-cci.txt | 55 ++
1 file changed, 55 insertions(+)
create mode 1006
This commit adds basic I2C bus support for the Camera Control Interface
(CCI) controller found on the Qualcomm SoC processors.
CCI versions supported:
- 1.0.8 - found on MSM8916/APQ8016 - support for the only CCI I2C bus;
- 1.4.0 - found on MSM8996/APQ8096 - support for first (out of two)
I2C bu
> -Original Message-
> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> Sent: Saturday, September 30, 2017 3:01 PM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; andy.shevche...@gmail.com; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org; l...@kernel.org;
> quasi.
Hi Kim,
On Fri, Sep 29, 2017 at 05:19:40PM -0500, Kim Phillips wrote:
> On Thu, 28 Sep 2017 15:09:50 +0100
> Will Deacon wrote:
>
> > +/* Perf callbacks */
> > +static int arm_spe_pmu_event_init(struct perf_event *event)
> > +{
> > + u64 reg;
> > + struct perf_event_attr *attr = &event->attr
On Mon, Oct 02, 2017 at 09:48:31PM +0800, Jin, Yao wrote:
>
>
> On 10/2/2017 9:00 PM, Jiri Olsa wrote:
> > On Mon, Oct 02, 2017 at 08:52:59PM +0800, Jin, Yao wrote:
> >>
> >>
> >> On 10/2/2017 7:50 PM, Jiri Olsa wrote:
> >>> On Thu, Sep 28, 2017 at 08:45:16PM +0800, Jin Yao wrote:
> >>>
> >>> SNI
Can you move this to the beginning of your series, just after
the other edits to blk_mq_sched_dispatch_requests?
> +static void blk_mq_do_dispatch_sched(struct request_queue *q,
> + struct elevator_queue *e,
> + struct blk_mq_hw_ctx
Looks fine,
Reviewed-by: Christoph Hellwig
201 - 300 of 713 matches
Mail list logo
