Commit-ID: 6dde6429c5ff5b38d6d40a14a6ee105117e6364d
Gitweb: https://git.kernel.org/tip/6dde6429c5ff5b38d6d40a14a6ee105117e6364d
Author: Thomas Richter
AuthorDate: Fri, 15 Jun 2018 12:11:05 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:37 -0300
perf stat:
Commit-ID: 0c24d6fb7bd3578e5b9e4972d01bbe3d087ded33
Gitweb: https://git.kernel.org/tip/0c24d6fb7bd3578e5b9e4972d01bbe3d087ded33
Author: Thomas Richter
AuthorDate: Fri, 15 Jun 2018 12:11:04 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:37 -0300
perf alias:
Commit-ID: c6555c14572aeadf4fe2819abd971c4e7608b926
Gitweb: https://git.kernel.org/tip/c6555c14572aeadf4fe2819abd971c4e7608b926
Author: Yonghong Song
AuthorDate: Sat, 16 Jun 2018 10:47:39 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:37 -0300
perf tools:
Commit-ID: ea23ac73085743a4f1682d6605fe019577c82e1e
Gitweb: https://git.kernel.org/tip/ea23ac73085743a4f1682d6605fe019577c82e1e
Author: Thomas Richter
AuthorDate: Fri, 15 Jun 2018 12:11:03 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:37 -0300
perf alias:
Commit-ID: f568b472815fd6c34fe4cc30dde4572ee300d6c4
Gitweb: https://git.kernel.org/tip/f568b472815fd6c34fe4cc30dde4572ee300d6c4
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Jun 2018 16:55:32 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
t
Commit-ID: bb9a33cb8a807e5ae9906563f5c1533904651b8b
Gitweb: https://git.kernel.org/tip/bb9a33cb8a807e5ae9906563f5c1533904651b8b
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Jun 2018 16:46:57 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
t
Commit-ID: 801f5e1ac783df9fafff8899ef2d5511bd4dbdcb
Gitweb: https://git.kernel.org/tip/801f5e1ac783df9fafff8899ef2d5511bd4dbdcb
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Jun 2018 12:04:32 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
t
Commit-ID: b1494ec029af6d6ea189cbc96ad66463f8df3579
Gitweb: https://git.kernel.org/tip/b1494ec029af6d6ea189cbc96ad66463f8df3579
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Jun 2018 11:48:43 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
p
Commit-ID: 7b818dc57230bf050bbc4218cd4df8ec59b9945d
Gitweb: https://git.kernel.org/tip/7b818dc57230bf050bbc4218cd4df8ec59b9945d
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 15 Jun 2018 11:33:35 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
t
Commit-ID: 621a5a327c1e36ffd7bb567f44a559f64f76358f
Gitweb: https://git.kernel.org/tip/621a5a327c1e36ffd7bb567f44a559f64f76358f
Author: Adrian Hunter
AuthorDate: Thu, 7 Jun 2018 14:30:02 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
perf intel-pt
Commit-ID: 16ddcfbf7f3d07aa781e26b39f2c28636a4ed2fd
Gitweb: https://git.kernel.org/tip/16ddcfbf7f3d07aa781e26b39f2c28636a4ed2fd
Author: Jiri Olsa
AuthorDate: Mon, 11 Jun 2018 11:34:22 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
perf tests: Add
Commit-ID: 933ccf2002aaef1037cb676622a694f5390c3d59
Gitweb: https://git.kernel.org/tip/933ccf2002aaef1037cb676622a694f5390c3d59
Author: Jiri Olsa
AuthorDate: Mon, 11 Jun 2018 11:34:21 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:36 -0300
perf tests: Add
Commit-ID: 143c99f6ac6812d23254e80844d6e34be897d3e1
Gitweb: https://git.kernel.org/tip/143c99f6ac6812d23254e80844d6e34be897d3e1
Author: Sandipan Das
AuthorDate: Mon, 11 Jun 2018 16:10:49 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:35 -0300
perf report p
Commit-ID: b930e62ecd362843002bdf84c2940439822af321
Gitweb: https://git.kernel.org/tip/b930e62ecd362843002bdf84c2940439822af321
Author: Thomas Richter
AuthorDate: Mon, 11 Jun 2018 09:31:53 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:35 -0300
perf test s
Commit-ID: 01766229533f9bdb1144a41b4345c8c7286da7b4
Gitweb: https://git.kernel.org/tip/01766229533f9bdb1144a41b4345c8c7286da7b4
Author: Thomas Richter
AuthorDate: Mon, 11 Jun 2018 09:31:52 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 25 Jun 2018 11:59:35 -0300
perf record
Hi Alan,
On Tue, Jun 26, 2018 at 02:22:07PM +0800, alanx.chi...@intel.com wrote:
> From: "alanx.chiang"
>
> The AT24 series chips use 8-bit address by default. If some
> chips would like to support more than 8 bits, should add the compatible
> field for specfic chips in the driver.
>
> Provide
Hi Lorenzo,
On 18-06-25 02:27 AM, Lorenzo Pieralisi wrote:
On Fri, Jun 22, 2018 at 11:59:08PM +0800, Ley Foon Tan wrote:
On Thu, 2018-06-21 at 22:08 -0700, Scott Branden wrote:
On 18-06-21 09:54 AM, Lorenzo Pieralisi wrote:
On Wed, Jun 20, 2018 at 10:07:33AM +0200, Jan Kiszka wrote:
On 2
Hi Alan,
On Tue, Jun 26, 2018 at 02:22:08PM +0800, alanx.chi...@intel.com wrote:
> From: "alanx.chiang"
>
> Provide a flexible way to determine the addressing bits of eeprom.
> Pass the addressing bits to driver through address-width property.
>
> Signed-off-by: Alan Chiang
> Signed-off-by: An
e inline keyword at the beginning of the function
> declaration (2018-06-22 11:07:47 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-for-mingo-4.18-20180625
>
> for you to fet
On Mon, 2018-06-25 at 23:53 +0200, Daniel Lezcano wrote:
> On 25/06/2018 09:10, Stanley Chu wrote:
> > Add binding documentation for the System Timer driver of
> > the Mediatek SoCs.
> >
> > Signed-off-by: Stanley Chu
> > ---
> > .../bindings/timer/mediatek,mtk-systimer.txt | 18
> > +++
On Mon 25-06-18 21:15:03, Kani Toshimitsu wrote:
> On Mon, 2018-06-25 at 19:53 +0200, Michal Hocko wrote:
> > On Mon 25-06-18 14:56:26, Kani Toshimitsu wrote:
> > > On Sun, 2018-06-24 at 15:19 +0200, Thomas Gleixner wrote:
> > > > On Wed, 16 May 2018, Toshi Kani wrote:
> > > >
> > > > > This serie
>>> On 25.06.18 at 18:33, wrote:
> On 06/25/2018 03:25 AM, Jan Beulich wrote:
>> Some Intel CPUs don't recognize 64-bit XORs as zeroing idioms - use
>> 32-bit ones instead.
>
> Hmph. Is that considered a bug (errata)?
No.
> URL/references?
Intel's Optimization Reference Manual says so (in rev
On 06/25/2018 08:21 AM, Jan Kara wrote:
> On Thu 21-06-18 18:30:36, Jan Kara wrote:
>> On Wed 20-06-18 15:55:41, John Hubbard wrote:
>>> On 06/20/2018 05:08 AM, Jan Kara wrote:
On Tue 19-06-18 11:11:48, John Hubbard wrote:
> On 06/19/2018 03:41 AM, Jan Kara wrote:
>> On Tue 19-06-18 02
From: "alanx.chiang"
The AT24 series chips use 8-bit address by default. If some
chips would like to support more than 8 bits, should add the compatible
field for specfic chips in the driver.
Provide a flexible way to determine the addressing bits through
address-width in this patch.
Signed-off
From: "alanx.chiang"
Provide a flexible way to determine the addressing bits of eeprom.
Pass the addressing bits to driver through address-width property.
Signed-off-by: Alan Chiang
Signed-off-by: Andy Yeh
---
since v1
-- Add a warn message for 8-bit addressing.
---
drivers/misc/eeprom/at24
From: "alanx.chiang"
In at24.c, it uses 8-bit addressing by default. In this patch,
add a property address-width that provides a flexible method to
pass the information to the driver.
alanx.chiang (2):
dt-bindings: at24: Add address-width property
eeprom: at24: Add support for address-width
* 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 2.40system 61.53 (1m1.534s) elapsed 89.60%CPU
> > > > user@devuan:~$ uname -a
On Mon, Jun 25, 2018 at 8:07 PM Michal Hocko wrote:
>
> On Mon 25-06-18 19:15:12, Mathieu Malaterre wrote:
> > Commit 26f09e9b3a06 ("mm/memblock: add memblock memory allocation apis")
> > introduced two new function definitions:
> >
> > memblock_virt_alloc_try_nid_nopanic()
> > memblock_virt_a
On Mon, Jun 18, 2018 at 08:34:50PM -0700, Andrei Vagin wrote:
> Hi David,
>
> We run CRIU tests for vfs/for-next, and today a few of these test failed. I
> found that the problem appears after this patch..
>
> > int pid_ns_prepare_proc(struct pid_namespace *ns)
> > {
> > + struct proc_fs_cont
commit (5fe156f regulator: pfuze100: add enable/disable
for switch) will cause those unreferenced switches being
turned off if "regulator-always-on" is NOT present, as
pfuze switches are normally used by critical modules which
must be always ON or shared by many peripherals which
do NOT implement p
Hi,
On 06/22, Christoph Hellwig wrote:
>Hi Xiaolong,
>
>can you retest this workload on the following branch:
>
>git://git.infradead.org/users/hch/vfs.git remove-get-poll-head
>
>Gitweb:
>
>
> http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/remove-get-poll-head
Here is the
On Tue, Jun 26, 2018 at 2:06 AM, Shakeel Butt wrote:
> A lot of memory can be consumed by the events generated for the huge or
> unlimited queues if there is either no or slow listener. This can cause
> system level memory pressure or OOMs. So, it's better to account the
> fsnotify kmem caches t
king about this for awhile and then determining I REALLY did not
want to think about it as my brain was getting tied into a gordian knot.
{^_^}
On 20180625 19:23, Michael Schmitz wrote:
Joanne,
Martin's boot log (including your patch) says:
Jun 19 21:19:09 merkaba kernel: [ 7891.843284]
Hi Matthias,
On 2018-06-26 05:35, Matthias Kaehlcke wrote:
On Mon, Jun 25, 2018 at 04:43:54PM -0700, Matthias Kaehlcke wrote:
This is a nice improvement, a few remaining questions inline.
On Mon, Jun 25, 2018 at 07:10:10PM +0530, Balakrishna Godavarthi
wrote:
> In function qca_setup, we set
Hi Pavel,
On 25 June 2018 at 20:18, Pavel Machek wrote:
> On Mon 2018-06-25 13:03:19, Baolin Wang wrote:
>> From: Bjorn Andersson
>>
>> Some LED controllers have support for autonomously controlling
>> brightness over time, according to some preprogrammed pattern or
>> function.
>>
>> This adds
On (06/26/18 07:03), Dmitry Vyukov wrote:
> > I don't think this is a printk() issue per se, so I think Option B is
> > the only option. You should not get stuck in an infinite loop if we run
> > short on memory. Perhaps we could have an Option C which would exit
> > this loop gracefully with some
> Subject: Re: [Patch v2 14/15] CIFS: Add support for direct I/O write
>
> On 5/30/2018 3:48 PM, Long Li wrote:
> > From: Long Li
> >
> > Implement the function for direct I/O write. It doesn't support AIO,
> > which will be implemented in a follow up patch.
> >
> > Signed-off-by: Long Li
> > --
> Subject: Re: [Patch v2 13/15] CIFS: Add support for direct I/O read
>
>
>
> On 5/30/2018 3:48 PM, Long Li wrote:
> > From: Long Li
> >
> > Implement the function for direct I/O read. It doesn't support AIO,
> > which will be implemented in a follow up patch.
> >
> > Signed-off-by: Long Li
>
Hi all,
Changes since 20180625:
The cifs tree lost its build failure.
The drm tree still had its build failure for which I disabled some
sample code.
The nvdimm tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 2240
2288 files changed, 72718 inser
> Subject: Re: [Patch v2 11/15] CIFS: Pass page offset for calculating signature
>
> On 5/30/2018 3:48 PM, Long Li wrote:
> > From: Long Li
> >
> > When calculating signature for the packet, it needs to read into the
> > correct page offset for the data.
> >
> > Signed-off-by: Long Li
> > ---
>
On Tue, Jun 26, 2018 at 11:46:35AM +0800, Wei Wang wrote:
> On 06/26/2018 09:37 AM, Michael S. Tsirkin wrote:
> > On Mon, Jun 25, 2018 at 08:05:10PM +0800, Wei Wang wrote:
> >
> > > @@ -326,17 +353,6 @@ static void stats_handle_request(struct
> > > virtio_balloon *vb)
> > > virtqueue_ki
On Mon, Jun 25, 2018 at 08:50:26PM +0100, John Whitmore wrote:
> On Mon, Jun 25, 2018 at 02:05:04PM +0100, Justin Skists wrote:
> >
> > > On 25 June 2018 at 13:36 John Whitmore wrote:
> > >
> > >
> > > On Mon, Jun 25, 2018 at 12:06:30PM +0300, Andy Shevchenko wrote:
> > > > On Sun, Jun 24, 2018
On Sun, Jun 24, 2018 at 04:34:51PM +0100, John Whitmore wrote:
> Changed a number of hard coded function names to use %s and __func__
>
> Mailing list response suggest that there is a better method for debugging
> using netdev_dbg(). I can't argue with that, but for the moment this change
> will c
We are taking a look at this - Ronnie had some ideas. Probably simply
not implemented - hopefully not too hard to fix.
On Mon, Jun 25, 2018 at 6:58 PM Laura Abbott wrote:
>
> Hi,
>
> A while back, someone reported a failure on Fedora when trying to boot
> a QEMU image off of a CIFS share. The iss
KVM is supposed to update some guest VM's CPUID bits (e.g. OSXSAVE) when
CR4 is changed. A bug was found in KVM recently and it was fixed by
Commit c4d2188206ba ("KVM: x86: Update cpuid properly when CR4.OSXAVE or
CR4.PKE is changed"). This patch adds a test to verify the synchronization
between gu
HI folks,
I've come across a strange problem recently when doing some MPI
based CPU+IO load test simulations recently. I've been running them
on the same machine I use to host all my filesystem test VMs
(16p/32t, 64GB RAM) which is currently running 4.16.12. Both the
MPI job context and the qemu
On 6/14/2018 12:26 PM, Andy Shevchenko wrote:
> On Thu, Jun 14, 2018 at 6:45 PM, Stuart Hayes
> wrote:
>>
>> If the WSMT ACPI table is present and indicates that a fixed communication
>> buffer should be used, use the firmware-specified buffer instead of
>> allocating a buffer in memory for co
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Acked-by: Michael Ellerman
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Tho
Remove the dance around old and new attributes. Just don't modify the
previous breakpoint at all until we have verified everything.
Reported-by: Linus Torvalds
Original-patch-by: Andy Lutomirski
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc:
This field seem to be unused, perhaps a leftover from old code...
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deacon
Cc: Mark Rutland
Cc: Max Filippov
Cc: Chris Zankel
Cc: Catal
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deaco
We soon won't be able to rely on bp->attr anymore to get the new
type of the modifying breakpoint because the new attributes are going
to be copied only once we successfully modified the breakpoint slot.
This will fix the current misdesigned layout where the new attr are
copied to the modifying br
All architectures have implemented it, we can now remove the poor weak
version.
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deacon
Cc: Mark Rutland
Cc: Max Filippov
Cc: Chris Zan
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Acked-by: Will Deacon
Acked-by: Mark Rutland
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc:
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Will Deaco
arch_validate_hwbkpt_settings() mixes up attribute check and commit into
a single code entity. Therefore the validation may return an error due to
incorrect atributes while still leaving halfway modified architecture
breakpoint data.
This is harmless when we deal with a new breakpoint but it becom
We can't pass the breakpoint directly on arch_check_bp_in_kernelspace()
anymore because its architecture internal datas (struct arch_hw_breakpoint)
are not yet filled by the time we call the function, and most
implementation need this backend to be up to date. So arrange the
function to take the pr
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Acked-by: Mark Rutland
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Cc: Thomas
Migrate to the new API in order to remove arch_validate_hwbkpt_settings()
that clumsily mixes up architecture validation and commit.
Original-patch-by: Andy Lutomirski
Signed-off-by: Frederic Weisbecker
Cc: Linus Torvalds
Cc: Andy Lutomirski
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Ingo Molnar
Ingo,
Please pull the perf/breakpoint-v4 branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
perf/breakpoint-v4
HEAD: ba25ee9c7b3ef1543c2a24a7ca6a621433803ee4
Only change since v3 is a rebase against latest tip:perf/core
---
When we mo
2018-06-25 23:55 GMT+09:00 Boris Brezillon :
> On Mon, 25 Jun 2018 09:50:18 -0500
> Dinh Nguyen wrote:
>
>> On 06/22/2018 10:58 AM, Richard Weinberger wrote:
>> > Masahiro,
>> >
>> > Am Freitag, 22. Juni 2018, 16:37:21 CEST schrieb Masahiro Yamada:
>> >> Hi Richard,
>> >>
>> >>
>> >> 2018-06-19 21
On Wed, Jun 13, 2018 at 02:36:12PM -0500, Eddie James wrote:
> This series adds an algorithm for an I2C master physically located on an FSI
> slave device. The I2C master has multiple ports, each of which may be
> connected
> to an I2C slave. Access to the I2C master registers is achieved over FSI
On Wed, Jun 13, 2018 at 02:36:13PM -0500, Eddie James wrote:
> Document the bindings.
>
> Signed-off-by: Eddie James >
Broken email address here. checkpatch warns about it.
On Wed, Jun 13, 2018 at 02:36:16PM -0500, Eddie James wrote:
> Add abort procedure for failed transfers. Add engine and bus reset
> procedures to recover from as many faults as possible.
I think this is a way too aggressive recovery. Your are doing the 9
pulse toggles basically on any error while
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 +++
> 1 file changed, 19 insertions(+)
>
>
On Wed, Jun 13, 2018 at 02:36:17PM -0500, Eddie James wrote:
> Execute I2C transfers from the FSI-attached I2C master. Use polling
> instead of interrupts as we have no hardware IRQ over FSI.
>
> Signed-off-by: Eddie James
> ---
> drivers/i2c/busses/i2c-fsi.c | 195
> +++
On Wed, Jun 20, 2018 at 07:17:53AM +0200, Peter Rosin wrote:
> Hi!
>
> With the introduction of mux-locked I2C muxes, the concept of
> locking only a segment of the I2C adapter tree was added. At the
> time, I did not want to cause a lot of extra churn, so left most
> users of i2c_lock_adapter alo
> This is not perfectly equivalent, since i2c_smbus_xfer was callable from
> atomic/irq context if you happened to end up emulating SMBus with an I2C
> transfer, and that is no longer the case with this patch. It is unknown
> (to me) if anything depends on that quirk, but it seems fragile enough
On Wed, Jun 20, 2018 at 11:43:23AM +0200, Peter Rosin wrote:
> If DMA safe memory was allocated, but the subsequent I2C transfer
> fails the memory is leaked. Plug this leak.
>
> Fixes: 8a77821e74d6 ("i2c: smbus: use DMA safe buffers for emulated SMBus
> transactions")
> Signed-off-by: Peter Rosi
Joanne,
Martin's boot log (including your patch) says:
Jun 19 21:19:09 merkaba kernel: [ 7891.843284] sdb: RDSK (512) sdb1
(LNX^@)(res 2 spb 1) sdb2 (JXF^D)(res 2 spb 1) sdb3 (DOS^C)(res 2 spb
4)
Jun 19 21:19:09 merkaba kernel: [ 7891.844055] sd 7:0:0:0: [sdb]
Attached SCSI disk
so it's indeed
On Mon 25 Jun 18:34 PDT 2018, Alex Elder wrote:
> From: Bjorn Andersson
>
> "start" and "stop" are more suitable names for how these two operations
> are used, and they fit better with the upcoming introduction of two
> additional operations in the struct.
>
> [el...@linaro.org: minor comment e
Hi all,
Today's linux-next merge of the nvdimm tree got a conflict in:
arch/x86/kernel/cpu/mcheck/mce.c
between commit:
d3d6923cd1ae ("x86/mce: Carve out the crashing_cpu check")
from the tip tree and commit:
f6785eac562b ("x86/memory_failure: Introduce {set,clear}_mce_nospec()")
from
On Mon 25 Jun 18:32 PDT 2018, Alex Elder wrote:
> On 05/29/2018 06:53 AM, Alex Elder wrote:
> > On 05/29/2018 04:12 AM, Arnaud Pouliquen wrote:
> >> Hello Alex
> >>
> >>
> >> We have the same needs (prepare unprepare steps) on our platform. We
> >> tested you core patches and they answers to our n
Hi John,
On 26 June 2018 at 01:23, John Stultz wrote:
> On Sat, Jun 23, 2018 at 5:14 PM, Thomas Gleixner wrote:
>> On Wed, 13 Jun 2018, Baolin Wang wrote:
>>> Moreover we can register the clocksource with CLOCK_SOURCE_SUSPEND_NONSTOP
>>> to be one persistent clock, then we can simplify the suspe
Hi Thomas,
On 24 June 2018 at 08:14, Thomas Gleixner wrote:
> On Wed, 13 Jun 2018, Baolin Wang wrote:
>> Moreover we can register the clocksource with CLOCK_SOURCE_SUSPEND_NONSTOP
>> to be one persistent clock, then we can simplify the suspend/resume
>> accounting by removing CLOCK_SOURCE_SUSPEND
This adds dt-binding documentation for Mediatek MT6765. Only
include very basic items, gic, uart timer and cpu.
Signed-off-by: Mars Cheng
---
Documentation/devicetree/bindings/arm/mediatek.txt |4
.../interrupt-controller/mediatek,sysirq.txt |1 +
.../devicetree/bindings/seria
This adds basic chip support for MT6765 SoC.
Signed-off-by: Mars Cheng
---
arch/arm64/boot/dts/mediatek/Makefile |1 +
arch/arm64/boot/dts/mediatek/mt6765-evb.dts | 33 ++
arch/arm64/boot/dts/mediatek/mt6765.dtsi| 158 +++
3 files changed, 192 inserti
This patch adds basic SoC support for Mediatek's new 8-core SoC,
MT6765, which is mainly for smartphone application.
Change in V2:
1. fix clk properties in uart dts node
2. fix typo in submit title
3. add simple-bus in mt6765.dtsi
4. use correct SPDX license format
Mars Cheng (2):
dt-bindings
> On Jun 25, 2018, at 6:32 PM, Tycho Andersen wrote:
>
>> On Sat, Jun 23, 2018 at 12:27:43AM +0200, Jann Horn wrote:
>>> On Fri, Jun 22, 2018 at 11:51 PM Kees Cook wrote:
>>>
On Fri, Jun 22, 2018 at 11:09 AM, Andy Lutomirski
wrote:
One possible extra issue: IIRC /proc/.../me
The SDCLK was named SDCLKCLK, and no one has used this yet.
Fix it.
Signed-off-by: Lei YU
---
drivers/clk/clk-aspeed.c | 2 +-
include/dt-bindings/clock/aspeed-clock.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/clk-aspeed.c b/drivers/clk/cl
From: Bjorn Andersson
"start" and "stop" are more suitable names for how these two operations
are used, and they fit better with the upcoming introduction of two
additional operations in the struct.
[el...@linaro.org: minor comment edits]
Signed-off-by: Bjorn Andersson
Acked-by: Alex Elder
Te
(This is just a rebase of https://lkml.org/lkml/2018/5/15/919)
This series changes the prototype for rproc_add_subdev(). The
caller is now responsible for populating the function pointers
recorded in the rproc_subdev structure, rather than having them be
passed as arguments. These two existing f
From: Bjorn Andersson
In preparation of adding the additional prepare and unprepare operations
make the client responsible for filling out the function pointers of the
rproc_subdev. This makes the arguments to rproc_add_subdev() more
manageable, in particular when some of the functions are left o
From: Bjorn Andersson
On rare occasions a subdevice might need to prepare some hardware
resources before a remote processor is booted, and clean up some
state after it has been shut down.
One such example is the IP Accelerator found in various Qualcomm
platforms, which is accessed directly from
Rename functions used when subdevices are started and stopped to
reflect the new naming scheme.
Signed-off-by: Alex Elder
Tested-by: Fabien Dessenne
---
drivers/remoteproc/qcom_common.c | 16
drivers/remoteproc/remoteproc_core.c | 8
2 files changed, 12 insertions
From: Bjorn Andersson
Some subdevices, such as glink ssr only care about the stop operation,
so make the operations optional to reduce client code.
Signed-off-by: Bjorn Andersson
Acked-by: Alex Elder
Tested-by: Fabien Dessenne
---
drivers/remoteproc/remoteproc_core.c | 20 +--
On Sat, Jun 23, 2018 at 12:27:43AM +0200, Jann Horn wrote:
> On Fri, Jun 22, 2018 at 11:51 PM Kees Cook wrote:
> >
> > On Fri, Jun 22, 2018 at 11:09 AM, Andy Lutomirski
> > wrote:
> > > One possible extra issue: IIRC /proc/.../mem uses FOLL_FORCE, which is
> > > not what we want here.
>
> Uuug
On 05/29/2018 06:53 AM, Alex Elder wrote:
> On 05/29/2018 04:12 AM, Arnaud Pouliquen wrote:
>> Hello Alex
>>
>>
>> We have the same needs (prepare unprepare steps) on our platform. We
>> tested you core patches and they answers to our need.
>
> I'm very glad to hear that. Would you offer your "Te
Hi Matthias,
On 2018-06-26 05:13, Matthias Kaehlcke wrote:
This is a nice improvement, a few remaining questions inline.
On Mon, Jun 25, 2018 at 07:10:10PM +0530, Balakrishna Godavarthi wrote:
In function qca_setup, we set initial and operating speeds for
Qualcomm
Bluetooth SoC's. This block
On (06/25/18 14:38), Dmitry Vyukov wrote:
> From: Dmitry Vyukov
>
> KERN_CONT leads to split lines in kernel output
> and complicates useful changes to printk like
> printing context before each line.
>
> Only acceptable use of continuations is basically
> boot-time testing.
>
> Get rid of it.
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit ca90800a91ba723d78ded634d037c1d2df8b54d6
Author: Kees Cook
AuthorDate: Thu May 10 16:40:03 2018 -0700
Commit: Kees Cook
Hi Matthias,
On 2018-06-26 04:50, Matthias Kaehlcke wrote:
On Mon, Jun 25, 2018 at 07:10:09PM +0530, Balakrishna Godavarthi wrote:
Redefinition of qca_uart_setup will help future Qualcomm Bluetooth
SoC, to use the same function instead of duplicating the function.
Added new arguments soc_type a
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/debug
commit 51bad67ffbce0aaa44579f84ef5d05597054ec6a
Author: Alexey Dobriyan
AuthorDate: Tue May 8 00:37:55 2018 +0300
Commit: Ingo
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit ef1433f717a2c63747a519d86965d73ff9bd08b3
Author: Kishon Vijay Abraham I
AuthorDate: Mon Apr 2 18:59:35 2018 +0530
Commit:
diff --git a/Documentation/devicetree/bindings/net/dsa/b53.txt
b/Documentation/devicetree/bindings/net/dsa/b53.txt
index d6c6e41648d4..6192f02af2a9 100644
--- a/Documentation/devicetree/bindings/net/dsa/b53.txt
+++ b/Documentation/devicetree/bindings/net/dsa/b53.txt
@@ -10,6 +10,7 @@ Required prop
I'm announcing the release of the 4.9.110 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index a33376204c17..e2e4009bbfed 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 51
+SUBLEVEL = 52
EXTRAVERSION =
NAME = Petit Gorille
diff --git a/arch/x86/kernel/cpu/intel_rdt.c
diff --git a/Makefile b/Makefile
index f43cd522b175..31dc3a08295a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 17
-SUBLEVEL = 2
+SUBLEVEL = 3
EXTRAVERSION =
NAME = Merciless Moray
diff --git a/arch/um/drivers/vector_transpor
I'm announcing the release of the 4.14.52 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 02a4f7f8c613..8a34b54f2a06 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 16
-SUBLEVEL = 17
+SUBLEVEL = 18
EXTRAVERSION =
NAME = Fearless Coyote
diff --git a/arch/x86/include/asm/apic.h b
1 - 100 of 816 matches
Mail list logo
