On Fri, Apr 06, 2018 at 09:25:27AM -0700, Nathan Chancellor wrote:
> On Fri, Apr 06, 2018 at 03:23:01PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.127 release.
> > There are 72 patches in this series, all will be posted as a response
> > to this
On Fri, Apr 06, 2018 at 05:25:24PM -0500, Dan Rue wrote:
> On Fri, Apr 06, 2018 at 03:22:41PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.93 release.
> > There are 102 patches in this series, all will be posted as a response
> > to this one. If
On Fri, Apr 06, 2018 at 09:35:35PM +0200, Arend van Spriel wrote:
> Op vr 6 apr. 2018 4:46 PM schreef Greg Kroah-Hartman
> :
> >
> > On Fri, Apr 06, 2018 at 12:13:38PM +0200, Arend van Spriel wrote:
> > > On Sat, Mar 24, 2018 at 10:04 AM, Greg Kroah-Hartman
> > >
Hi Eric et al,
In a number of windowing environments (eg GNOME 3) on Raspberry Pi 3B
on 4.16.0 arm64, the mouse cursor top-left gets down to x,y -4,-4,
tripping WARN_ON_ONCE(plane->state->crtc_x < 0 || plane->state->crtc_y
< 0) [1], which therefore seems false-positive.
Git history doesn't turn
On Sat, Apr 7, 2018 at 2:31 AM, Casey Schaufler wrote:
> On 4/5/2018 9:12 PM, Peter Dolding wrote:
>> On Fri, Apr 6, 2018 at 11:31 AM, Sargun Dhillon wrote:
>>>
>>> On Thu, Apr 5, 2018 at 9:29 AM, Casey Schaufler
>>> wrote:
Hi Laurent
On Fri, Apr 06, 2018 at 06:40:14PM +0300, Laurent Pinchart wrote:
> Hi Jacopo,
>
> (CC'ing Mark Brown)
Hi Mark
[snip]
> >
> > Anyway, we spent enough time on naming issues, starting from my first
> > stupid 'pdwn' permutations then on this semi-standard names.
> >
> > I'll send next
Hi,
On 4.04.2018 20:30, risha...@codeaurora.org wrote:
Hi Stanimir,
We incorporated all your comments except the following:
1. Removing the driver that maintains the SCT (system cache table)
per chipset. As responded earlier the data is expected to change
from chipset to chipset and would
Hi,
On 06-04-18 16:08, Luis R. Rodriguez wrote:
On Thu, Apr 05, 2018 at 07:43:49AM +0200, Lukas Wunner wrote:
On Wed, Apr 04, 2018 at 01:18:36PM -0400, Peter Jones wrote:
On Tue, Apr 03, 2018 at 08:07:11PM +0200, Lukas Wunner wrote:
* Add the EFI Firmware Volume Protocol to
Hello,
syzbot hit the following crash on upstream commit
3fd14cdcc05a682b03743683ce3a726898b20555 (Fri Apr 6 19:15:41 2018 +)
Merge tag 'mtd/for-4.17' of git://git.infradead.org/linux-mtd
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=7810ed2e0cb359580c17
Unfortunately, I
On Fri, Apr 06, 2018 at 03:00:11PM -0700, Oliver Smith-Denny wrote:
> On Fri, Apr 06, 2018 at 07:07:52AM +0200, Greg Kroah-Hartman wrote:
> > Why is this a drivers/staging/ driver at all? What is keeping you from
> > getting this merged into the "proper" place in the kernel?
> >
> > If you have
On Sat, Apr 07, 2018 at 12:41:38AM +0530, Harsh Shandilya wrote:
>
>
> On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman
> wrote:
> >This is the start of the stable review cycle for the 3.18.103 release.
> >There are 93 patches in this series, all will be posted as
On Fri, Apr 06, 2018 at 04:07:38PM -0600, Shuah Khan wrote:
> On 04/06/2018 07:24 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.1 release.
> > There are 31 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Fri, Apr 06, 2018 at 05:20:12PM -0300, Thadeu Lima de Souza Cascardo wrote:
> On Fri, Apr 06, 2018 at 03:23:35PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.15.16 release.
> > There are 72 patches in this series, all will be posted as a response
>
On 6 April 2018 at 18:53, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.127 release.
> There are 72 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
Tidy the naming convention for compat syscall subs. Hints which describe
the purpose of the stub go in front and receive a double underscore to
denote that they are generated on-the-fly by the COMPAT_SYSCALL_DEFINEx()
macro.
For the generic case, this means:
tkernel_waitid #
This rename allows us to have a coherent syscall stub naming convention on
64-bit x86 (0x prefix removed):
810f0af0 tkernel_waitid # common (32/64) kernel helper
__in_sys_waitid # inlined helper doing actual work
810f0be0 t __do_sys_waitid # C
Tidy the naming convention for compat syscall subs. Hints which describe
the purpose of the stub go in front and receive a double underscore to
denote that they are generated on-the-fly by the SYSCALL_DEFINEx() macro.
For the generic case, this means (0x prefix removed):
810f08d0 t
Ingo,
as discussed yesterday, here is a mini-series (mostly) implementing your
suggestion on how to tidy up the naming convention for syscall stubs.
For the generic case, we now will have:
t kernel_waitid # common C function (see kernel/exit.c)
i __in_sys_waitid #
On Fri, Apr 06, 2018 at 04:50:19PM -0400, Waiman Long wrote:
> # of threads 4.16 kernel patched 4.16 kernel
> --- ---
> 1 7,417 kop/s 7,408 kop/s
> 2 5,755 kop/s 4,486 kop/s
> 3 4,214 kop/s
On Fri, 06 Apr 2018 23:14:01 +0200,
syzbot wrote:
>
> syzbot has found reproducer for the following crash on upstream commit
> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +)
> Merge tag 'armsoc-drivers' of
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>
Hi Jacopo,
On Saturday, 7 April 2018 12:45:56 EEST jacopo mondi wrote:
> On Fri, Apr 06, 2018 at 06:40:14PM +0300, Laurent Pinchart wrote:
> > Hi Jacopo,
> >
> > (CC'ing Mark Brown)
>
> Hi Mark
>
> [snip]
>
> >> Anyway, we spent enough time on naming issues, starting from my first
> >> stupid
The q->id is used as an index within the blkg_tree radix tree.
If the entry is not released before reclaiming the blk_queue_ida's id
blkcg_init_queue() within a different driver from which this id
was originally for can fail due to the entry at that index within
the radix tree already existing.
On Sat 2018-04-07 10:10:00, Pavel Machek wrote:
> Hi!
>
> It seems qmicli can be used while unicsy_demo/ofone talks to the modem
> using the AT commands.
>
> So I could do:
>
> qmicli -d /dev/cdc-wdm0 --wds-follow-network
> --wds-start-network=apn=internet.t-mobile.cz
> route del default
>
On Sat, Apr 07, 2018 at 05:58:49AM +0900, Stafford Horne wrote:
> Following Peter Z's patch ("asm-generic: Disallow no-op mb() for SMP
> systems") which makes mb() mandatory for SMP architectures we define it
> as l.msync. On OpenRISC this will flush the current cores write buffer
> and trigger
On Fri, Apr 06, 2018 at 02:03:37PM +0530, Nayna Jain wrote:
> On 04/05/2018 03:42 PM, Jarkko Sakkinen wrote:
> > On Mon, Apr 02, 2018 at 09:50:06PM +0530, Nayna Jain wrote:
> > > Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to
> > > handle the TPM2_RC_RETRY error. The loop
On Sat, 07 Apr 2018 12:19:33 +0200,
Dmitry Vyukov wrote:
>
> On Sat, Apr 7, 2018 at 11:56 AM, Takashi Iwai wrote:
> > On Fri, 06 Apr 2018 23:14:01 +0200,
> > syzbot wrote:
> >>
> >> syzbot has found reproducer for the following crash on upstream commit
> >>
#syz dup: INFO: rcu detected stall in io_playback_transfer
On Fri, Apr 6, 2018 at 2:04 PM, syzbot
wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> e02d37bf55a9a36f22427fd6dd733fe104d817b6 (Thu Apr 5 17:42:07 2018
On 07/04/18 13:25, Dongli Zhang wrote:
> This is to introduce "xenwatch multithreading" (or "multithreaded xenwatch",
> abbreviated as 'mtwatch'). The implementation of xen mtwatch involves below
> components:
>
> * dom0 linux kernel
> * xen toolstack
>
> Here are what the RFC is going to
#syz dup: INFO: rcu detected stall in io_playback_transfer
On Sat, Apr 7, 2018 at 1:00 PM, Takashi Iwai wrote:
> On Sat, 07 Apr 2018 12:19:33 +0200,
> Dmitry Vyukov wrote:
>>
>> On Sat, Apr 7, 2018 at 11:56 AM, Takashi Iwai wrote:
>> > On Fri, 06 Apr 2018 23:14:01
On 6 April 2018 at 18:54, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.16.1 release.
> There are 31 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
On 06/04/18 18:54, Damjan Georgievski wrote:
> Since the 4.16 kernel my uvcvideo webcam on Thinkpad X1 Carbon (5th
> gen) stopped working with gst-launch-1.0, kamoso (kde webcam app),
> Firefox and Chromium on sites like appear.in, talky.io, Google
> Hangouts and meet.jit.si.
Do you see a
Hi Corey,
Since IPMI 2.0 just defined minimum, no maximum:
KCS/SMIC Input : Required: 40 bytes IPMI Message, minimum
KCS/SMIC Output : Required: 38 bytes IPMI Message, minimum
We can enlarge the block size for avoiding waste, and make our driver
support most worst message size
Hi!
It seems qmicli can be used while unicsy_demo/ofone talks to the modem
using the AT commands.
So I could do:
qmicli -d /dev/cdc-wdm0 --wds-follow-network
--wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0
to get GPRS/UMTS connection. AT
On Fri, Apr 06, 2018 at 02:08:32PM +, Luis R. Rodriguez wrote:
> How do you get the GUIDs for each driver BTW?
They're used as filenames when extracting a Firmware Volume with
UEFIExtract.
E.g. let's say I'm looking for the EFI driver containing the UCS-2
string "ThunderboltDROM" in the
On Sat, Apr 7, 2018 at 11:56 AM, Takashi Iwai wrote:
> On Fri, 06 Apr 2018 23:14:01 +0200,
> syzbot wrote:
>>
>> syzbot has found reproducer for the following crash on upstream commit
>> 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +)
>> Merge tag
On 7 April 2018 at 11:11, Hans Verkuil wrote:
> On 06/04/18 18:54, Damjan Georgievski wrote:
>> Since the 4.16 kernel my uvcvideo webcam on Thinkpad X1 Carbon (5th
>> gen) stopped working with gst-launch-1.0, kamoso (kde webcam app),
>> Firefox and Chromium on sites like
This patch is based on xen-4.10.0.
This patch introduces xenwatch multithreading (or multithreaded xenwatch,
abbreviated as 'mtwatch') on xen toolstack side.
In addition to the existing single xenwatch thread, each domU has its own
kernel thread ([xen-mtwatch-]) to process its xenwatch event.
This patch is based on v4.16-rc7.
This patch introduces xenwatch multithreading (or multithreaded xenwatch,
abbreviated as 'mtwatch') to dom0 kernel. In addition to the existing
single xenwatch thread, each domU has its own kernel thread
([xen-mtwatch-]) to process its xenwatch event.
The
This is to introduce "xenwatch multithreading" (or "multithreaded xenwatch",
abbreviated as 'mtwatch'). The implementation of xen mtwatch involves below
components:
* dom0 linux kernel
* xen toolstack
Here are what the RFC is going to discuss:
- what is the problem
- what is the objective
-
On Fri, 06 Apr 2018 11:47:29 -0500
Tom Zanussi wrote:
> > > > Can you print out the error with which event we should see? e.g.
> > > >
> > > > ERROR: Variable already defined at sched_wakeup: ts0
> > > >
> > >
> > > How about printing the event name along with
On 06.04.2018 22:53, Andi Kleen wrote:
> On Fri, Apr 06, 2018 at 10:06:26PM +0300, Alexey Budankov wrote:
>> On 06.04.2018 18:31, Andi Kleen wrote:
diff --git a/arch/x86/kernel/perf_regs.c b/arch/x86/kernel/perf_regs.c
index e47b2dbbdef3..9284048cf5b0 100644
---
/linux/commits/Steven-Rostedt/init-tracing/20180407-130743
config: i386-randconfig-x006-201813 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
>>
On Fri, Apr 06, 2018 at 02:09:53PM -0700, Paul E. McKenney wrote:
> It would indeed be good to not be in the position of having to trade off
> forward-progress guarantees against performance, but that does appear to
> be where we are at the moment.
Depends of course on how unfair cmpxchg is. On
From: Wenle Chen
The %d in printf need get a int
But the real type of these vars is unsigned.
It may let some compilers show a warning.
Signed-off-by: Wenle Chen
---
scripts/recordmcount.c | 6 +++---
1 file changed, 3 insertions(+), 3
--
Good-Day!,
Can you assist me to handle this transaction? I will forward you the
full details about the transaction if you are ready.
Yours faithfully
Mr. Malik Sanfo
--
This patch adds a driver for the BMS (Battery Monitoring System)
block of the PM8941 PMIC, it uses a lookup table defined in the
device tree to generate a capacity from the BMS supplied OCV, it
then ammends the coulomb counter to that to increase the accuracy
of the estimated capacity.
Add bindings for the Qualcomm Battery Monitoring system.
Signed-off-by: Craig Tatlor
---
.../bindings/power/supply/qcom_bms.txt| 93 +++
1 file changed, 93 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/supply/qcom_bms.txt
Signed-off-by: Craig Tatlor
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0c3ad62c638c..aaf54b665f86 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11605,6 +11605,12 @@ W:
Fix checkpatch warnings about S_IRUSR | S_IWUSR being less readable than
providing the permissions octal as '0600'.
Signed-off-by: Paul McQuade
---
mm/failslab.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/failslab.c b/mm/failslab.c
index
Fix checkpatch warnings about S_IRUGO being less readable than
providing the permissions octal as '0444'.
Signed-off-by: Paul McQuade
---
mm/cleancache.c | 8
mm/cma_debug.c | 12 ++--
mm/dmapool.c| 2 +-
mm/frontswap.c | 8
4 files
Fix checkpatch warnings about S_IWUSR being less readable than
providing the permissions octal as '0200'.
Signed-off-by: Paul McQuade
---
mm/cma_debug.c | 4 ++--
mm/compaction.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/mm/cma_debug.c
://github.com/0day-ci/linux/commits/Greg-Thelen/writeback-safer-lock-nesting/20180407-122200
config: mips-db1xxx_defconfig (attached as .config)
compiler: mipsel-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin
On Fri, 2018-04-06 at 13:38 +0200, Markus Heiser wrote:
>
> Sorry, not yet. Johannes started a discussion about this. Its a long
> time ago and I do not have any new ideas yet :/ see:
>
> https://www.mail-archive.com/linux-doc@vger.kernel.org/msg07035.html
I still think the tools themselves
On Sat, Apr 07, 2018 at 01:31:34PM +0530, Naresh Kamboju wrote:
> On 6 April 2018 at 18:54, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.16.1 release.
> > There are 31 patches in this series, all will be posted as a response
>
Quoting Rajendra Nayak (2018-03-15 21:08:18)
> From: Viresh Kumar
>
> This adds a new helper to let the power domain drivers to access
> opp->np, so that they can read platform specific properties from the
> node.
>
> Signed-off-by: Viresh Kumar
On Wed, 2018-04-04 at 10:58 +0200, Petr Mladek wrote:
> Move the non-trivial code from the long pointer() function. We are
> going
> to add a check for the access to the address that will make it even
> more
> complicated.
>
> Also it is better to warn about unknown specifier instead of falling
>
The message about constraining number of online cpus to be less than or
equal to ND_MAX_LANES (256) is only useful for block-aperture
configurations and BTT. Make it debug since its only relevant when
debugging performance.
Signed-off-by: Dan Williams
---
The following NULL dereference results from incorrectly assuming that
ndd is valid in this print:
struct nvdimm_drvdata *ndd = to_ndd(_region->mapping[i]);
/*
* Give up if we don't find an instance of a uuid at each
* position (from 0 to nd_region->ndr_mappings - 1), or if we
* find
In crb_map_io() function, __crb_request_locality() is called prior
to crb_cmd_ready(), but if one of the consecutive function fails
the flow bails out instead of trying to relinquish locality.
This patch adds goto jump to __crb_relinquish_locality() on the error path.
Fixes: 888d867df441 (tpm:
Dmitry Vyukov wrote:
> On Sat, Apr 7, 2018 at 5:39 PM, Peter Zijlstra wrote:
> > On Sat, Apr 07, 2018 at 09:31:19PM +0900, Tetsuo Handa wrote:
> >> are for replacing debug_show_all_locks() in check_hung_task() for cases
> >> like
> >>
On 04/07/2018 06:59 AM, Craig Tatlor wrote:
> This patch adds a driver for the BMS (Battery Monitoring System)
> block of the PM8941 PMIC, it uses a lookup table defined in the
> device tree to generate a capacity from the BMS supplied OCV, it
> then ammends the coulomb counter to that to increase
On Saturday, April 7, 2018 4:36:25 AM CEST Frederic Weisbecker wrote:
> On Wed, Apr 04, 2018 at 10:41:13AM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > In order to address the issue with short idle duration predictions
> > by the idle governor
On Sat, Apr 07, 2018 at 09:37:21AM -0700, Randy Dunlap wrote:
> On 04/07/2018 06:59 AM, Craig Tatlor wrote:
> > This patch adds a driver for the BMS (Battery Monitoring System)
> > block of the PM8941 PMIC, it uses a lookup table defined in the
> > device tree to generate a capacity from the BMS
On Sat, Apr 7, 2018 at 10:19 AM, Al Viro wrote:
>
> That, of course, can be dealt with after merge, but since that commit
> has to be at least rebased to avoid bisection hazard... might as well
> get rid of dget_parent() there at the same time.
Ok, I will skip the afs
As suggested by Laura Abbott[2], I'm resending my patch with
MAX_BLOCKSIZE and MAX_ALIGNMASK defined in an header, so they
can be used in other places.
I take this opportuinuty to deal with some other VLAs not
handled in the old patch.
[1]
We avoid 2 VLAs[1] by always allocating MAX_BLOCKSIZE +
MAX_ALIGNMASK bytes.
We also check the selected cipher at instance creation time, if
it doesn't comply with these limits, the creation will fail.
[1]
On Thu, Apr 5, 2018 at 2:03 PM, Michael S. Tsirkin wrote:
>
> nr = get_user_pages_fast(addr, nr, gup->flags & 1, pages + i);
> - i += nr;
> + if (nr > 0)
> + i += nr;
Can we just make this robust while at it, and
On Sat, Apr 07, 2018 at 10:37:33PM +0530, Naresh Kamboju wrote:
> >> Results from Linaro’s test farm.
> >> No regressions on arm64, arm and x86_64.
> >>
> >> Summary
> >>
> >>
> >> kernel: 4.16.1-rc1
> >> git repo:
> >>
Hello,
syzbot hit the following crash on
https://github.com/google/kmsan.git/master commit
e2ab7e8abba47a2f2698216258e5d8727ae58717 (Fri Apr 6 16:24:31 2018 +)
kmsan: temporarily disable visitAsmInstruction() to help syzbot
syzbot dashboard link:
We avoid 2 VLAs[1] by always allocating MAX_BLOCKSIZE*2 bytes.
We also check the selected cipher at instance creation time, if
it doesn't comply with these limits, the creation will fail.
[1]
http://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qpxydaacu1rq...@mail.gmail.com
We avoid 3 VLAs[1] by always allocating MAX_BLOCKSIZE bytes or,
when needed for alignement, MAX_BLOCKSIZE + MAX_ALIGNMASK bytes.
We also check the selected cipher at instance creation time, if
it doesn't comply with these limits, the creation will fail.
[1]
We avoid a VLA[1] by always allocating MAX_BLOCKSIZE +
MAX_ALIGNMASK bytes.
We also check the selected cipher at initialization time, if
it doesn't comply with these limits, the initialization will
fail.
[1]
Creating 2 new compile-time constants for internal use,
in preparation for the removal of VLAs[1] from crypto code.
All ciphers implemented in Linux have a block size less than or
equal to 16 bytes and the most demanding hw require 16 bytes
alignment for the block buffer.
[1]
We avoid 2 VLAs[1] by always allocating MAX_BLOCKSIZE bytes.
We also check the selected cipher at instance creation time, if
it doesn't comply with these limits, the creation will fail.
[1]
http://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qpxydaacu1rq...@mail.gmail.com
[ adding Paul and Josh ]
On Wed, Apr 4, 2018 at 2:46 AM, Jan Kara wrote:
> On Fri 30-03-18 21:03:30, Dan Williams wrote:
>> Background:
>>
>> get_user_pages() in the filesystem pins file backed memory pages for
>> access by devices performing dma. However, it only pins the memory
On Sat, Apr 7, 2018 at 11:38 AM, Salvatore Mesoraca
wrote:
> As suggested by Laura Abbott[2], I'm resending my patch with
> MAX_BLOCKSIZE and MAX_ALIGNMASK defined in an header, so they
> can be used in other places.
> I take this opportuinuty to deal with some other VLAs
On Sat, 2018-04-07 at 19:47 +0100, Paul McQuade wrote:
> Fix checkpatch warnings about S_IRUGO being less readable than
> providing the permissions octal as '0444'.
Hey Paul.
I sent a cleanup a couple weeks ago to Andrew Morton for the
same thing.
https://lkml.org/lkml/2018/3/26/638
Andrew
Benötigen Sie ein persönliches oder geschäftliches Darlehen mit 2% Zinssatz?
Wir bieten Projektfinanzierung Business Loans Personal Loans. für weitere
Informationen kontaktieren Sie uns bitte
On Sun, Apr 8, 2018 at 11:48 AM, Steven Rostedt wrote:
> On Sun, 8 Apr 2018 10:16:23 +0800
> Zhaoyang Huang wrote:
>
>> Don't choose the process with adj == OOM_SCORE_ADJ_MIN which
>> over-allocating pages for ring buffers.
>
> Why?
>
> -- Steve
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16 next-20180406]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull powerpc updates for 4.17.
A bit late unfortunately, not due to anything terrible, but just a
trickle of small fixes through the week.
There's one minor merge conflict in the lib/raid6/test/Makefile, between
our changes and
Signed-off-by: Craig Tatlor
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0c3ad62c638c..b7ffa9268384 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11605,6 +11605,12 @@ W:
On Tue, Apr 03, 2018 at 10:08:58AM -0700, Paul E. McKenney wrote:
> On Tue, Apr 03, 2018 at 01:41:31PM +0200, Frederic Weisbecker wrote:
> > On Mon, Apr 02, 2018 at 03:04:38PM -0700, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > I am hitting the following on today's mainline under rcutorture,
Add bindings for the Qualcomm Battery Monitoring system.
Signed-off-by: Craig Tatlor
---
.../bindings/power/supply/qcom_bms.txt| 93 +++
1 file changed, 93 insertions(+)
create mode 100644 Documentation/devicetree/bindings/power/supply/qcom_bms.txt
Signed-off-by: Craig Tatlor
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0c3ad62c638c..aaf54b665f86 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11605,6 +11605,12 @@ W:
On Thu, 2018-04-05 at 16:46 +0200, Petr Mladek wrote:
> On Thu 2018-04-05 16:04:45, Andy Shevchenko wrote:
> > On Wed, 2018-04-04 at 10:58 +0200, Petr Mladek wrote:
> > > restricted_pointer() pretends that it prints the address when
> > > kptr_restrict
> > > is set to zero. But it is never called
On Wed, Apr 04, 2018 at 10:45:39AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The next set of changes will need to compute the time to the next
> hrtimer event over all hrtimers except for the scheduler tick one.
>
> To that end introduce a new
Bart Van Assche wrote:
> On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote:
> > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null.
> > I added a dev_printk in scsi_print_command where the 2 if statements return.
> > Logs:
> > [ 29.866415] sr 3:0:0:0: cmd->cmnd is NULL
Quoting Leo Yan (2018-04-03 20:14:35)
> From: Daniel Lezcano
>
> The current defconfig is inconsistent as it selects the mailbox and
> the clock for the hi6220 and the hi3660 without having their Kconfigs
> making sure the dependencies are correct. It ends up when
Hi Stafford,
Commit
bf118b74c385 ("openrisc: remove unused __ARCH_HAVE_MMU define")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpcLeOn4PoNJ.pgp
Description: OpenPGP digital signature
This patch adds a driver for the BMS (Battery Monitoring System)
block of the PM8941 PMIC, it uses a lookup table defined in the
device tree to generate a capacity from the BMS supplied OCV, it
then ammends the coulomb counter to that to increase the accuracy
of the estimated capacity.
On Fri, 2018-04-06 at 11:15 +0200, Petr Mladek wrote:
> On Thu 2018-04-05 15:30:51, Rasmus Villemoes wrote:
> > On 2018-04-04 10:58, Petr Mladek wrote:
> > > We are going to check the address using probe_kernel_address(). It
> > > will
> > > be more expensive and it does not make sense for well
This patch corrects the function definition style of CARDvSafeResetRx.
Issue found by checkpatch.
CHECK: Lines should not end with a '('
Signed-off-by: Danilo Alves
---
drivers/staging/vt6655/card.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
On Fri, Apr 06, 2018 at 10:37:29PM -0700, João Paulo Rechi Vita wrote:
> When the module is removed the led workqueue is destroyed in the remove
> callback, before the led device is unregistered from the led subsystem.
>
> This leads to a NULL pointer derefence when the led device is
>
ARS is an operation that can take 10s to 100s of seconds to find media
errors that should rarely be present. If the platform crashes due to
media errors in persistent memory, the expectation is that the BIOS will
report those known errors in a 'short' ARS request.
A 'short' ARS request asks
After attempting to quickly retrieve known errors the kernel proceeds to
kick off a long running ARS. Add a module option to disable this
behavior at initialization time, or at new region discovery time.
Otherwise, ARS can be started manually regardless of the state of this
setting.
Changes since v2 [1]:
* Handle -EAGAIN (no result) ars_status responses
---
Given the fact that ARS can take 10s to 100s of seconds it is not
feasible to wait for ARS completion before publishing persistent memory
namespaces. Instead convert the ARS implementation to perform a short
ARS for
acpi_nfit_query_poison() is awkward in that it requires an nfit_spa
argument in order to determine what max_ars value to use. Instead probe
for the minimum max_ars across all scrub-capable ranges in the system
and drop the nfit_spa argument.
This enables a larger rework / simplification of the
On Sat, Apr 07, 2018 at 11:36:24PM +1000, Stephen Rothwell wrote:
> Hi Stafford,
>
> Commit
>
> bf118b74c385 ("openrisc: remove unused __ARCH_HAVE_MMU define")
>
> is missing a Signed-off-by from its committer.
Thanks this is updated now.
-Stafford
At least on droid 4 with control channel in ADM mode, there is no response
to Modem Status Command (MSC). Currently gsmtty_modem_update() expects to
have data in dlci->modem_rx unless debug & 2 is set. This means that on
droid 4, things only work if debug & 2 is set.
Let's fix the issue by
1 - 100 of 400 matches
Mail list logo