(adding proper linux-c6x-dev list, sorry about the noise)
On Wed, Jun 27, 2018 at 03:09:20PM +0300, Mike Rapoport wrote:
> The c6x is already using memblock and does most of early memory
> reservations with it, so it was only a matter of removing the bootmem
> initialization and handover of the
On Mon, 25 Jun 2018 09:21:02 -0700
Joel Fernandes wrote:
>
> From: "Joel Fernandes (Google)"
> Subject: [PATCH v9.1 7/7] kselftests: Add tests for the preemptoff and irqsoff
> tracers
>
> Here we add unit tests for the preemptoff and irqsoff tracer by using a
> kernel module introduced
On Wed, Apr 11, 2018 at 09:07:30PM +0200, Sebastian Andrzej Siewior wrote:
>
> This already happens:
> - vmstat_shepherd() does get_online_cpus() and within this block it does
> queue_delayed_work_on(). So this has to wait until cpuhotplug
> completed before it can schedule something and then
Make workaround for errata i870 applicable in Host mode as
well(previously it was enabled only for EP mode) as per errata
documentation: http://www.ti.com/lit/er/sprz450/sprz450.pdf
Tested on DRA72 EVM
Changes since v1:
Drop IRQ handling rework (will be sent out separately)
v1:
Add disk name to tracepoints so we can better distinguish between
individual disks in the trace output and admin commands which
are represented without a disk name.
Signed-off-by: Johannes Thumshirn
---
drivers/nvme/host/core.c | 4 ++--
drivers/nvme/host/trace.h | 39
It does look similar to what Naoya was seeing. Herton, have you tried applying:
http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thank you,
Pavel
On Wed, Jun 27, 2018 at 3:35 AM Michal Hocko wrote:
>
> This smells like an issue Naoya was
Hello,
Atmel SAMA5D2 is equipped with two QSPI interfaces. These interfaces can
work as in SPI-compatible mode or use two / four lines to improve
communication speed. At the moment there is QSPI driver strongly tied to
NOR-flash memory and MTD subsystem.
Intention of this change is to provide new
On Wed, Jun 27, 2018 at 5:27 AM Mike Rapoport wrote:
>
> Hi,
>
> On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > >
> > > Hi,
> > > I am wondering why do we still keep mm/bootmem.c when most architectures
> > > already moved
Hi Will,
On 2018/6/27 14:28, Will Deacon wrote:
> On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
>> On 2018/6/26 18:47, Will Deacon wrote:
>>> If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
>>> replacing:
>>>
>>> dc civac, cur_\()\type\()p
>>>
>>>
On Wed, Jun 27, 2018 at 07:52:23PM +0900, Tetsuo Handa wrote:
> On 2018/06/27 8:50, Paul E. McKenney wrote:
> > On Wed, Jun 27, 2018 at 05:10:48AM +0900, Tetsuo Handa wrote:
> >> As far as I can see,
> >>
> >> - atomic_set(_callback_count, 1);
> >> + atomic_inc(_callback_count);
> >>
> >> should
This clock is especially used by the RTC driver, so export it so that
devicetree users can use it.
Signed-off-by: Robert Jarzmik
---
Since v2: fix missing parenthesis in clk-pxa25x.c and clk-pxa3xx.c
---
drivers/clk/pxa/clk-pxa25x.c | 6 --
drivers/clk/pxa/clk-pxa27x.c | 7
On Tue, Jun 26, 2018 at 11:15:14AM -0700, Doug Anderson wrote:
> I think he's still planning on re-shuffling his tree a bit. When he
> does this, do you need him to put the RPMh patches somewhere you can
> merge into your tree?
Well, I *think* there's no actual dependency here since it's a new
The RTC controller is fed by an external fixed 32kHz clock. Yet the
driver wants to acquire this clock, even though it doesn't make any use
of it, ie. doesn't get the rate to make calculation.
Therefore, use the exported 32.768kHz clock in the PXA clock tree to
make the driver happy and working.
Hi Paul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc2 next-20180627]
[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
On Wed, Jun 27, 2018 at 03:57:13PM +0100, Daniel Thompson wrote:
> On Tue, Jun 26, 2018 at 10:11:17PM +0530, Manivannan Sadhasivam wrote:
> > > > diff --git a/include/dt-bindings/power/owl-s900-powergate.h
> > > > b/include/dt-bindings/power/owl-s900-powergate.h
> > > > new file mode 100644
> > >
Mark Brown writes:
> On Mon, Jun 18, 2018 at 09:56:20PM +0200, Robert Jarzmik wrote:
>
>> I must insist on "Wednesday", as I need to have one last pass from 0-day
>> kernel
>> checker to be fully covered, and I'd like as well to know which tree the ASoC
>> patch will take, ie. if Mark commits
Hi Naga,
This is not an issue at all but I think [PATCH vX Y/Z] is a preferred
and shorter suffix, you can create it automatically by using
git format-patch -v X ^.. --cover-letter
On Thu, 21 Jun 2018 12:12:31 +0530, Naga Sureshkumar Relli
wrote:
> Add driver for arm pl353 static
2018-06-26 20:59+0800, LiuYang:
> GCC 5.4.0 enables raw strings by default and they have higher priority
> than macros, thus R is interpreted incorrectly.
> Fix it by putting a space between macro R and a string literal.
>
> Signed-off-by: LiuYang
> ---
This got fixed in 2012 by b188c81f2e1a
Bit positions of PCIE_SS1_AXI2OCP_LEGACY_MODE_ENABLE and
PCIE_SS1_AXI2OCP_LEGACY_MODE_ENABLE in CTRL_CORE_SMA_SW_7 are
incorrectly documented in the TRM. In fact, the bit positions are
swapped. Update the DT bindings for PCIe EP to reflect the same.
Signed-off-by: Vignesh R
---
Add ti,syscon-unaligned-access property to PCIe RC nodes to set
appropriate bits in CTRL_CORE_SMA_SW_7 register to enable workaround for
errata i870.
Signed-off-by: Vignesh R
---
arch/arm/boot/dts/dra7.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi
Update device tree binding documentation of TI's dra7xx PCI controller
for enabling unaligned mem access as applicable not just in EP mode but
in host mode as well.
Signed-off-by: Vignesh R
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/pci/ti-pci.txt | 5 +
1 file changed,
On Wed, Jun 27, 2018 at 10:35:03AM +0100, Allan Xavier wrote:
> Looks good overall, just one comment.
>
> On 26/06/18 19:44, Josh Poimboeuf wrote:
> > + /*
> > +* Unfortunately, -fnoreorder-functions puts the child
> > +* inside the
Hello,
On Wed, 27 Jun 2018 17:01:50 +0200, Robert Jarzmik wrote:
> The RTC controller is fed by an external fixed 32kHz clock. Yet the
> driver wants to acquire this clock, even though it doesn't make any use
> of it, ie. doesn't get the rate to make calculation.
>
> Therefore, use the exported
Am 27.06.2018 um 10:33 schrieb Dan Carpenter:
On Tue, Jun 26, 2018 at 10:32:09PM +0200, Michael Straube wrote:
On 06/26/18 22:17, Joe Perches wrote:
On Tue, 2018-06-26 at 21:44 +0200, Michael Straube wrote:
On 06/26/18 19:32, Andy Shevchenko wrote:
On Tue, Jun 26, 2018 at 11:14 AM, Michael
On Mon 2018-06-25 23:16:04, Tony Lindgren wrote:
> * Pavel Machek [180625 09:52]:
> > Hi!
> >
> > > > > V4.18 is slower than it should be.
> > > > >
> > > > > user@devuan:~$ time cat /dev/urandom | head -c 1000 | bzip2 -9 -
> > > > > | wc -c
> > > > > 10044291
> > > > > 52.73user
Hi James,
On 2018/6/27 9:39, James Morse wrote:
> Hi Wei,
>
> On 26/06/18 18:47, Will Deacon wrote:
>> On Wed, Jun 27, 2018 at 01:16:44AM +0800, Wei Xu wrote:
>>> [0.00] Booting Linux on physical CPU 0x00 [0x480fd010]
>>> [0.00] Linux version
On Tue, Jun 26, 2018 at 07:54:06PM +0800, GaoMing wrote:
> for example, 1708 inodes every group,3 block groups, bitmap bytes are
> 1708/8=213.5 when the inode bitmap has some errors, e2fsprogs cannot fix it
>
> Signed-off-by: GaoMing
File systems like this should not exist. Can you please
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index
Hi Linus,
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
Hi Gregory.
On Tue, Jun 26, 2018 at 11:20 PM, Gregory CLEMENT
wrote:
> Hi Ethan,
>
> On mar., juin 19 2018, Ethan Tuttle wrote:
>
>> With CONFIG_FORTIFY_SOURCE, memcpy uses the declared size of operands to
>> detect buffer overflows. If src or dest is declared as a char, attempts to
>> copy
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
Changes to v4:
- Move caching from nvme_setup_cmd to .init_request (Keith)
---
drivers/nvme/host/core.c |
Patch one is a preparation patch from Sagi and caches the nvme_ctrl in
the nvme_request. This is not only useful for the tracepoints but for
further development as well.
The second patch adds the controller IDs and if applicable the disk
name to the tracepoints so we can distinguish between the
On Wednesday 27 June 2018 03:56 PM, Lorenzo Pieralisi wrote:
> On Tue, Jun 26, 2018 at 04:15:01PM -0500, Bjorn Helgaas wrote:
>> On Tue, Jun 26, 2018 at 09:10:07AM +0800, kernel test robot wrote:
>>>
>>> Greetings,
>>>
>>> 0day kernel testing robot got the below dmesg and the first bad commit
On Wed 27-06-18 13:29:05, Richard Weinberger wrote:
> On Wed, Jun 27, 2018 at 11:34 AM, Jefferson Carpenter
> wrote:
> > Is there a way for a user process to mark memory as 'sensitive' or
> > 'non-sensitive' when it is allocated? That could allow it not to have to be
> > zeroed before being
On Wed, Jun 27, 2018 at 02:56:00PM +0200, Michael Straube wrote:
> Should I add a thanks line to the commit message:
>
> Thanks to Dan Carpenter, Joe Perches and Andy Shevchenko.
>
> Or would that be considered as too much?
You can write whatever the heck you want... :P No one cares.
Atmel SAMA5D2 QuadSPI driver was moved from mtd to spi subsystem,
this change is just moving DT-binding documentation.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
Documentation/devicetree/bindings/{mtd => spi}/atmel-quadspi.txt | 0
1 file changed, 0 insertions(+), 0
This patch adds new interface to existing driver. New code is not used yet,
it will be enabled later.
Changes are prepared in small steps to keep patches readable.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 205
Code used for previous interface is no longer needed.
This change just removes obsolete code.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 389
1 file changed, 389 deletions(-)
diff --git
Kernel contains QSPI driver strongly tied to MTD and nor-flash memory.
New spi-mem interface allows usage also other memory types, especially
much larger NAND with SPI interface. This driver works as SPI controller
and is not related to MTD, however can work with NAND-flash or other
peripherals
Previously added spi-mem interface is now used instead of older approach.
Suggested-by: Boris Brezillon
Signed-off-by: Piotr Bugalski
---
drivers/mtd/spi-nor/atmel-quadspi.c | 91 -
1 file changed, 18 insertions(+), 73 deletions(-)
diff --git
On Wed, Jun 27, 2018 at 02:22:03PM +0100, Wei Xu wrote:
> On 2018/6/26 18:47, Will Deacon wrote:
> > If you look at the __idmap_kpti_put_pgtable_ent_ng asm macro, can you try
> > replacing:
> >
> > dc civac, cur_\()\type\()p
> >
> > with:
> >
> > dc ivac, cur_\()\type\()p
> >
Errata i870 is applicable in both EP and RC mode. Therefore rename
function dra7xx_pcie_ep_unaligned_memaccess(), that implements errata
workaround, to dra7xx_pcie_unaligned_memaccess() and call it from a
common place. So, that errata workaround is applied for both modes of
operation.
On 2018-06-27 00:15, Sebastian Andrzej Siewior wrote:
On 2018-06-26 14:28:26 [-0700], Isaac J. Manjarres wrote:
Remove CPU ID swapping in stop_two_cpus() so that the
source CPU's stopper thread is added to the wake queue last,
so that the source CPU's stopper thread is woken up last,
ensuring
Hi Paul,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc2 next-20180627]
[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
On Tue, Jun 26, 2018 at 9:33 PM, Jason Gunthorpe wrote:
> On Tue, Jun 26, 2018 at 05:05:40PM +0200, Miguel Ojeda wrote:
>> Hi,
>>
>> On Tue, Jun 26, 2018 at 12:44 AM, Jason Gunthorpe wrote:
>> > The true option causes this indenting for functions:
>> >
>> > static struct something_very_very_long
The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
when logbuf_lock is available") brought back the possible deadlocks
in printk() and NMI.
This is rework of the proposed fix, see
https://lkml.kernel.org/r/20180606111557.xzs6l3lkvg7lq...@pathway.suse.cz
I realized that we could
It is just a preparation step. The patch does not change
the existing behavior.
Signed-off-by: Petr Mladek
---
kernel/printk/printk.c | 43 ++-
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
On Wed, Jun 27, 2018 at 12:40:15PM +0200, Frederic Weisbecker wrote:
> On Tue, Jun 26, 2018 at 10:48:26AM -0700, Paul E. McKenney wrote:
> > On Tue, Jun 26, 2018 at 06:32:55PM +0200, Peter Zijlstra wrote:
> > > On Tue, Jun 26, 2018 at 06:16:04PM +0200, Anna-Maria Gleixner wrote:
> > > > Hi,
> > >
On (06/27/18 23:16), Sergey Senozhatsky wrote:
> > Petr Mladek (3):
> > printk: Split the code for storing a message into the log buffer
> > printk: Create helper function to queue deferred console handling
> > printk/nmi: Prevent deadlock when accessing the main log buffer in NMI
>
> Patch
On Tue, Jun 26, 2018 at 04:06:45PM +0200, Jann Horn wrote:
> On Tue, Jun 26, 2018 at 3:08 PM Christian Brauner
> wrote:
> >
> > On Mon, Jun 25, 2018 at 06:34:19PM +0200, Jann Horn wrote:
> > > The old code would hold the userns_state_mutex indefinitely if
> > > memdup_user_nul stalled due to e.g.
The patch
regulator: bd71837: Staticize ldo_2_volts
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: bd71837: Simplify bd71837_set_voltage_sel_restricted
implementation
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree
On Tue 2018-06-26 10:39:59, Steven Rostedt wrote:
> On Tue, 26 Jun 2018 14:43:32 +0200
> Petr Mladek wrote:
>
> > On Mon 2018-06-25 23:44:07, Sergey Senozhatsky wrote:
> > > On (06/25/18 10:37), Steven Rostedt wrote:
> > > >
> > > > Is IMHO rather ugly.
> > >
> > > Either way works for me.
On Wed, Jun 27, 2018 at 10:15 AM Herton R. Krzesinski wrote:
> Thanks, I'll try it. It'll probably work since I tried memory_reserve
> but "hacking" it at e820__register_nosave_regions, anyway I'll confirm
> it here.
If it works, please send the new "Reserved but unavailable" value from dmesg:
[
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 403b45de1262..f57f42ed7160 100644
---
Signed-off-by: Axel Lin
---
drivers/regulator/bd71837-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/bd71837-regulator.c
b/drivers/regulator/bd71837-regulator.c
index 6eae4d0432a2..403b45de1262 100644
--- a/drivers/regulator/bd71837-regulator.c
On Wed 27-06-18 13:59:27, Michal Hocko wrote:
> On Wed 27-06-18 13:53:49, Jan Kara wrote:
> > On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> [...]
> > > Appart from that, do we really care about 32b here? Big DIO, IB users
> > > seem to be 64b only AFAIU.
> >
> > IMO it is a bad habit to leave
On Wed, Jun 27, 2018 at 12:51:43PM +0900, Masahiro Yamada wrote:
> Hi Olof,
>
> 2018-06-27 2:42 GMT+09:00 Olof Johansson :
> > Hi,
> >
> > On Mon, Jun 25, 2018 at 11:13:04PM +0900, Masahiro Yamada wrote:
> >> Hi Arnd, Olof,
> >>
> >> Please pull some fixes of ARM UniPhier platform.
> >>
> >>
> >>
From: Chintan Pandya
The following kernel panic was observed on ARM64 platform due to a stale
TLB entry.
1. ioremap with 4K size, a valid pte page table is set.
2. iounmap it, its pte entry is set to 0.
3. ioremap the same address with 2M size, update its pmd entry with
a new value.
4.
ioremap() supports pmd mappings on x86-PAE. However, kernel's pmd
tables are not shared among processes on x86-PAE. Therefore, any
update to sync'd pmd entries need re-syncing. Freeing a pte page
also leads to a vmalloc fault and hits the BUG_ON in vmalloc_sync_one().
Disable free page
On (06/27/18 16:08), Petr Mladek wrote:
> The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
> when logbuf_lock is available") brought back the possible deadlocks
> in printk() and NMI.
>
> This is rework of the proposed fix, see
>
ioremap() calls pud_free_pmd_page() / pmd_free_pte_page() when it creates
a pud / pmd map. The following preconditions are met at their entry.
- All pte entries for a target pud/pmd address range have been cleared.
- System-wide TLB purges have been peformed for a target pud/pmd address
On Wed, Jun 27, 2018 at 09:22:07AM +0200, Michal Hocko wrote:
> On Tue 26-06-18 10:03:45, Paul E. McKenney wrote:
> [...]
> > 3. Something else?
>
> How hard it would be to use a different API than oom notifiers? E.g. a
> shrinker which just kicks all the pending callbacks if the reclaim
>
Hi Masahiro,
On 06/26/2018 09:52 PM, Masahiro Yamada wrote:
> 2018-06-27 3:09 GMT+09:00 Miquel Raynal :
>> Hi Masahiro,
>>
>> On Tue, 26 Jun 2018 11:38:21 +0900, Masahiro Yamada
>> wrote:
>>
>>> 2018-06-25 23:55 GMT+09:00 Boris Brezillon :
On Mon, 25 Jun 2018 09:50:18 -0500
Dinh Nguyen
On Tue, Jun 26, 2018 at 10:11:17PM +0530, Manivannan Sadhasivam wrote:
> > > diff --git a/include/dt-bindings/power/owl-s900-powergate.h
> > > b/include/dt-bindings/power/owl-s900-powergate.h
> > > new file mode 100644
> > > index ..f1aaf761112b
> > > --- /dev/null
> > > +++
On Wed, Jun 27, 2018 at 02:42:55PM +0200, Jan Kara wrote:
> On Wed 27-06-18 13:59:27, Michal Hocko wrote:
> > On Wed 27-06-18 13:53:49, Jan Kara wrote:
> > > On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> > [...]
> > > > Appart from that, do we really care about 32b here? Big DIO, IB users
> > >
Am 27.06.2018 um 16:57 schrieb Daniel Thompson:
> On Tue, Jun 26, 2018 at 10:11:17PM +0530, Manivannan Sadhasivam wrote:
>>> Question: Should it still be GPL-2.0+ or the new GPL-2.0-or-later?
>>
>> I think GPL-2.0+ is fine.
>
> So... when I saw this I did wonder why one would knowly choose to use
On Friday 01 June 2018 01:55 AM, David Lechner wrote:
> This adds nodes for describing the Bluetooth chip and connections on
> LEGO MINDSTORMS EV3 to da850-lego-ev3.dts.
>
> Signed-off-by: David Lechner
Applied for v4.19.
Thanks,
Sekhar
On 06/25/2018 09:38 PM, Wolfram Sang wrote:
On Wed, Jun 13, 2018 at 02:36:19PM -0500, Eddie James wrote:
Bus recovery should reset the engine and force clock the bus 9 times
to recover most situations.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 19 +++
On Wed, Jun 27, 2018 at 09:14:21AM -0400, Pavel Tatashin wrote:
> It does look similar to what Naoya was seeing. Herton, have you tried
> applying:
>
> http://ozlabs.org/~akpm/mmots/broken-out/x86-e820-put-e820_type_ram-regions-into-memblockreserved.patch
Thanks, I'll try it. It'll probably
This series fixes two issues in the x86 ioremap free page handlings
for pud/pmd mappings.
Patch 01 fixes BUG_ON on x86-PAE reported by Joerg. It disables
the free page handling on x86-PAE.
Patch 02-03 fixes a possible issue with speculation which can cause
stale page-directory cache.
- Patch
On Wed 2018-06-27 23:16:12, Sergey Senozhatsky wrote:
> On (06/27/18 16:08), Petr Mladek wrote:
> > The commit 719f6a7040f1bdaf96 ("printk: Use the main logbuf in NMI
> > when logbuf_lock is available") brought back the possible deadlocks
> > in printk() and NMI.
> >
> > This is rework of the
On Tue, Jun 26, 2018 at 8:40 AM Linus Torvalds
wrote:
>
> The problem on x86-64 cross-building to i386 is that the *compiler* is
> the same, but the flags are not, and the games the Makefile plays
> aren't sufficient. It plays with changing HOSTCC to CC in order to get
> he right target compiler,
Hi Alexandre,
On Tue, Jun 26, 2018 at 04:07:43PM +0200, Alexandre Belloni wrote:
> > diff --git a/arch/mips/generic/vmlinux.its.S
> > b/arch/mips/generic/vmlinux.its.S
> > index 1a08438fd893..9c954f2ae561 100644
> > --- a/arch/mips/generic/vmlinux.its.S
> > +++ b/arch/mips/generic/vmlinux.its.S
On Wed, Jun 27, 2018 at 07:33:55AM -0600, Rob Herring wrote:
> On Wed, Jun 27, 2018 at 5:27 AM Mike Rapoport wrote:
> >
> > Hi,
> >
> > On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote:
> > > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote:
> > > >
> > > > Hi,
> > > > I am
On Wed, Jun 27, 2018 at 4:11 PM, Dan Carpenter wrote:
> On Wed, Jun 27, 2018 at 02:56:00PM +0200, Michael Straube wrote:
>> Should I add a thanks line to the commit message:
>>
>> Thanks to Dan Carpenter, Joe Perches and Andy Shevchenko.
>>
>> Or would that be considered as too much?
>
> You
Prevent a config where KVM_AMD=y and CRYPTO_DEV_CCP_DD=m thereby ensuring
that AMD Secure Processor device driver will be built-in when KVM_AMD is
also built-in.
v1->v2:
* Removed usage of 'imply' Kconfig option.
* Change patch commit message.
Fixes: 505c9e94d832 ("KVM: x86: prefer "depends on"
On 6/27/2018 5:53 AM, Johannes Thumshirn wrote:
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
Changes to v4:
- Move caching from nvme_setup_cmd to
Nikita:
Since you are mostly arguing against the suggestions I made to Andrey
Gusakov in off-list review, I'll respond.
On Wed, Jun 27, 2018 at 12:11 AM Nikita Yushchenko
wrote:
>
> > + i2c_gpio: i2c-gpio {
> > + compatible = "i2c-gpio";
> > + pinctrl-names =
On Wed, Jun 27, 2018 at 8:43 AM, wrote:
> From: Sean Wang
>
> +config BT_HCIBTUART_MTK
> + tristate "MediaTek HCI UART driver"
> + depends on BT_HCIBTUART
> + default y
Perhaps it's an overkill for users which would like to have less
amount on stuff in kernel.
> +#include
On Wed, Jun 27, 2018 at 1:46 PM, Andrey Smirnov
wrote:
> We are now starting to give Andrey Gusakov conflicting
> recommendations. For the sake of moving forward, can we agree that
> this and similar comments are relatively minor and defer to the
> maintainers to make a call which way to go?
>
The open coded access is now replaced, that might prevent
from using the enhanced FSGSBASE mechanism.
Based-on-code-from: Andy Lutomirski
Signed-off-by: Chang S. Bae
Reviewed-by: Andi Kleen
Reviewed-by: Andy Lutomirski
Reviewed-by: Thomas Gleixner
Cc: H. Peter Anvin
Cc: Ingo Molnar
Cc:
Instead of open coding the calls to load_seg_legacy(), add a
load_fsgs() helper to handle fs and gs. When FSGSBASE is enabled,
load_fsgs() will be updated.
Signed-off-by: Chang S. Bae
Reviewed-by: Andi Kleen
Reviewed-by: Andy Lutomirski
Reviewed-by: Thomas Gleixner
Cc: H. Peter Anvin
Cc:
Given feedbacks from [1], it was suggested to separate two parts
and to (re-)submit this patchset first.
To facilitate FSGSBASE, Andy's FS/GS base read fix is first
ordered, then some helper functions and refactoring work
are included. Cleanup for the vDSO initialization is
for preparing per-CPU
On Wed 27-06-18 08:57:18, Jason Gunthorpe wrote:
> On Wed, Jun 27, 2018 at 02:42:55PM +0200, Jan Kara wrote:
> > On Wed 27-06-18 13:59:27, Michal Hocko wrote:
> > > On Wed 27-06-18 13:53:49, Jan Kara wrote:
> > > > On Wed 27-06-18 13:32:21, Michal Hocko wrote:
> > > [...]
> > > > > Appart from
From: Jonathan Bakker
This DTS file have initial support Samsung SGH-T959P phone,
also known as Samsung Galaxy S 4G or fascinate4g.
It belongs to Samsung Aries devices family.
Initial version have support for:
- sdcard
- max8998 pmic and rtc
- max17040 fuel gauge
- gpio keys
- fimd (no panel
There are Samsung devices, which are not Exynos-based boards,
like it's in case of S5PV210. Document this information at beginning
of file.
Signed-off-by: Paweł Chmiel
---
Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This DTS file have initial support Samsung Aries based phones.
Initial version have support for:
- sdcard
- internal memory (present only on non 4g variant)
- max8998 pmic and rtc
- max17040 fuel gauge
- gpio keys
- fimd (no panel driver yet)
- usb (peripherial mode)
- wifi
Signed-off-by: Paweł
Document the binding for Samsung Galaxy S (i9000) phone.
Also add binding for whole Samsung Aries devices family (based on S5PV210).
Signed-off-by: Paweł Chmiel
--
Changes from v1:
- Added missing commit msg.
--
---
Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 2 ++
1
From: Jonathan Bakker
Document the binding for Samsung Galaxy S Fascinate 4G (SGH-T959P).
Signed-off-by: Jonathan Bakker
Signed-off-by: Paweł Chmiel
--
Changes from v1:
- Added missing commit msg.
--
---
Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 1 +
1 file
On Wed, Jun 27, 2018 at 2:48 PM, Paul Cercueil wrote:
> Hi Linus,
>
> Here's a set of (rather RFC) patches, to implement
> pinctrl_gpio_get_direction(). I did that, because my gpio-ingenic driver
> calls pinctrl_gpio_set_direction() within its gpio_chip's .set_direction
> callback, but there was
+Cc: Erik
On Tue, Jun 26, 2018 at 8:57 PM, Toralf Förster wrote:
> The attached dmesg contains non printable chars 0x01 33 around "ACPI BIOS
> Error (bug): Could not resolve" which is a new issue compared to the dmesg of
> 4.17.2
>
> System is a stable hardened Gentoo Linux at a ThinkPad
On Tue, 2018-06-26 at 11:01 -0400, Nathaniel McCallum wrote:
> On Tue, Jun 26, 2018 at 4:44 AM Jarkko Sakkinen
> wrote:
> >
> > On Mon, 2018-06-25 at 08:45 -0700, Andy Lutomirski wrote:
> > > I'm personally rather strongly in favor of the vastly simpler model in
> > > which we first merge SGX
When merging codec formats, dpcm_runtime_base_format() should skip
the codecs which are not supporting the current stream direction.
At the moment, if a BE link has more than one codec, and only one
of these codecs has no capture DAI, it becomes impossible to start
a capture stream because the
Hi Toshi,
On Wed, Jun 27, 2018 at 08:13:47AM -0600, Toshi Kani wrote:
> From: Chintan Pandya
>
> The following kernel panic was observed on ARM64 platform due to a stale
> TLB entry.
>
> 1. ioremap with 4K size, a valid pte page table is set.
> 2. iounmap it, its pte entry is set to 0.
> 3.
On Wed, Jun 27, 2018 at 10:42:01AM +0800, Boqun Feng wrote:
> On Tue, Jun 26, 2018 at 12:27:47PM -0700, Paul E. McKenney wrote:
> > On Tue, Jun 26, 2018 at 07:46:52PM +0800, Boqun Feng wrote:
> > > On Tue, Jun 26, 2018 at 06:44:47PM +0800, Boqun Feng wrote:
> > > > On Tue, Jun 26, 2018 at
On Tue, Jun 26, 2018 at 7:13 AM Petr Mladek wrote:
>
> please pull one revert from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pmladek/printk
> tags/printk-for-4.18
That tag doesn't actually contain any revert.
Linus
On Wed, 2018-06-27 at 16:56 +0100, Will Deacon wrote:
> Hi Toshi,
>
> On Wed, Jun 27, 2018 at 08:13:47AM -0600, Toshi Kani wrote:
> > From: Chintan Pandya
> >
> > The following kernel panic was observed on ARM64 platform due to a stale
> > TLB entry.
> >
> > 1. ioremap with 4K size, a valid
On Wed, Jun 27, 2018 at 02:53:24PM +0200, Johannes Thumshirn wrote:
> TP_fast_assign(
> - __entry->qid = qid;
> + __assign_str(name, disk_name);
> + __entry->ctrl_id = nvme_req(req)->ctrl->cntlid;
> + __entry->qid =
On Wed, Jun 27, 2018 at 12:21 PM, wrote:
> From: Honghui Zhang
>
> Mediatek's host controller have two slots, each have it's own control
> registers. The host driver need to identify which slot was connected
> in order to access the device's configuration space. There's problem
> for current
1 - 100 of 1028 matches
Mail list logo
