On Tue, 2017-04-11 at 16:09 +0200, Greg Kroah-Hartman wrote:
> Care to use "real" kernel variable types please? u8, u16, and others
> are you friend, uint8_t really isn't what we prefer, and checkpatch
> should tell you that...
checkpatch doesn't warn about "u?int\d+_t" types unless
--strict is e
Em Tue, Apr 11, 2017 at 11:49:06AM +0200, Jiri Olsa escreveu:
> On Mon, Apr 10, 2017 at 01:14:25PM -0700, David Carrillo-Cisneros wrote:
> > Various fixes for perf tool pipe-mode for bugs that arose while trying
> > to make this work:
> >
> > perf record -o - noploop | perf inject -b | perf an
Hi Bjorn,
On Fri, Mar 31, 2017 at 09:40:15AM -0700, Brian Norris wrote:
> Sure, I can grok that. Just let me know if you want any more action from
> me.
Any thoughts here? Would you like me to prepare my patches any
differently?
Brian
Hi Niranjan,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.11-rc6]
[cannot apply to next-20170411]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Niranjan-Dighe
> Am 11.04.2017 um 19:10 schrieb Jim Mattson :
>
> This might be more useful if it could be dynamically toggled on and
> off, depending on system load.
What would trapping mwait (currently) buy you?
As it stands today, before this patch, mwait is simply implemented as a nop, so
enabling the t
From: Markus Elfring
Date: Tue, 11 Apr 2017 20:22:10 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use kcalloc() in goldfish_tty_create_driver()
Adjust five checks for null pointers
drivers/tty/goldfish.c | 14 +++---
1 f
On Tue, 11 Apr 2017 19:03:14 +0800
Peter Xu wrote:
> On Thu, Apr 06, 2017 at 08:53:43AM -0600, Alex Williamson wrote:
> > If the mmap_sem is contented then the vfio type1 IOMMU backend will
> > defer locked page accounting updates to a workqueue task. This has
> > a few problems and depending on
From: Markus Elfring
Date: Tue, 11 Apr 2017 20:00:23 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kcalloc".
This issue was detected by using the Coccinelle software.
Sign
On 04/11/2017 06:17 PM, Andrey Smirnov wrote:
> In anticipation of supporting chips that need it, extend the size of
> struct flash_info's 'jedec_id' field to make room 2 byte of extended
> device information as well as add code to fetch this data during
> jedec_probe().
>
> Cc: cphe...@gmail.com
From: Markus Elfring
Date: Tue, 11 Apr 2017 20:15:30 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written !…
Thus fix the affected source code pl
On Tue 11-04-17 13:03:01, Cristopher Lameter wrote:
> On Tue, 11 Apr 2017, Michal Hocko wrote:
>
> > >
> > > There is a flag SLAB_DEBUG_OBJECTS that is available for this check.
> >
> > Which is way too late, at least for the kfree path. page->slab_cache
> > on anything else than PageSlab is just
On Fri, 31 Mar 2017, Kees Cook wrote:
> As found in PaX, this adds a cheap check on heap consistency, just to
> notice if things have gotten corrupted in the page lookup.
Ok this only affects kmem_cache_free() and not kfree(). For
kmem_cache_free() we already have a lot of stuff in the hotpath du
On 04/10/2017 06:52 PM, Ludovic BARRE wrote:
> hi Marek
>
> tomorrow, I send a v3 with your/Rob reviews.
Super, thanks! I'll be pretty busy till Friday, so please keep in mind
the final review might take a bit.
> BR
>
> Ludo
>
>
> On 04/10/2017 06:15 PM, Marek Vasut wrote:
>> On 04/10/2017 11
On Tue, 2017-04-11 at 19:37 +0200, Paolo Valente wrote:
> Just pushed:
> https://github.com/Algodev-github/bfq-mq/tree/add-bfq-mq-logical
Thanks!
But are you aware that the code on that branch doesn't build?
$ make all
[ ... ]
ERROR: "bfq_mark_bfqq_busy" [block/bfq-wf2q.ko] undefined!
ERROR: "bf
I did my best to fix those issues in perf inject and perf report, but
yeah, other commands may have issues.
On Tue, Apr 11, 2017 at 11:12 AM, Arnaldo Carvalho de Melo
wrote:
> Em Mon, Apr 10, 2017 at 01:14:31PM -0700, David Carrillo-Cisneros escreveu:
>> A common pattern in in pipe-mode bugs is a
On Mon, Apr 10, 2017 at 12:35:12PM -0700, John Stultz wrote:
> This patch adds a few extra error returns in cases that
> shouldn't happen, some style nits adding breaks to final
> default cases in switch statements, and tweaks to use
> devm_ variant of snd_soc_register_component.
Please don't mak
Ideas? Will dig deeper later, the warning in the perf test output
doesn't help.
Using perf as in acme/perf/core
[root@jouet ~]# perf test bpf
38: BPF filter :
38.1: Basic BPF filtering : Skip
38.2: BPF pinning : Ski
> Also, the latest benchmarks I've seen were mostly for user space
> while I'm more concerned with the user-kernel interface
> (https://marc.info/?l=linux-arm-kernel&m=148690490713310&w=2).
> On the glibc testing side, have the regressions been identified/fixed?
I run LTP for testing the ABI and
Em Tue, Apr 11, 2017 at 03:35:58PM -0300, Arnaldo Carvalho de Melo escreveu:
> Ideas? Will dig deeper later, the warning in the perf test output
> doesn't help.
>
> Using perf as in acme/perf/core
Humm, I had a long running 'perf top' session, as soon as I exited it
and tried again:
[root@jouet
On Tue, 2017-04-11 at 10:41 -0700, Wei Wang wrote:
> From: Wei Wang
>
> Currently checkpatch.pl does not recognize revert commits and
> complains about the commit hash format.
> Add special audit for revert commit to fix it.
The commit wording seems a bit off, but I guess it's OK.
The 'This rev
Em Mon, Apr 10, 2017 at 01:14:30PM -0700, David Carrillo-Cisneros escreveu:
> Session sets a number parameters that rely on evlist. These parameters
> are not used in pipe-mode and should not be set, since evlist is
> unavailable. Fix that.
Ditching this one as well, until further investigation, w
Em Tue, Apr 11, 2017 at 03:40:14PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Apr 10, 2017 at 01:14:30PM -0700, David Carrillo-Cisneros escreveu:
> > Session sets a number parameters that rely on evlist. These parameters
> > are not used in pipe-mode and should not be set, since evlist is
On Tue, Apr 11, 2017 at 11:15:54AM -0700, Joe Perches wrote:
> On Tue, 2017-04-11 at 16:09 +0200, Greg Kroah-Hartman wrote:
> > Care to use "real" kernel variable types please? u8, u16, and others
> > are you friend, uint8_t really isn't what we prefer, and checkpatch
> > should tell you that...
>
On 04/11/2017 08:36 PM, Yury Norov wrote:
Also, the latest benchmarks I've seen were mostly for user space
while I'm more concerned with the user-kernel interface
(https://marc.info/?l=linux-arm-kernel&m=148690490713310&w=2).
On the glibc testing side, have the regressions been identified/fixe
On Tue, 2017-04-11 at 09:46 +0200, Johannes Thumshirn wrote:
> When instrumenting the SCSI layer to run into the
> !blk_rq_nr_phys_segments(rq) case the following warning emitted from the
> block layer:
>
> blk_peek_request: bad return=-22
>
> This happens because since commit fd3fc0b4d730 ('scs
On Tue, 11 Apr 2017, Michal Hocko wrote:
> > So we are already handling that condition. Why change things? Add a BUG_ON
> > if you want to make SLAB consistent.
>
> I hate to repeat myself but let me do it for the last time in this
> thread. BUG_ON for something that is recoverable is completely
>
Em Tue, Apr 11, 2017 at 03:40:50PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Apr 11, 2017 at 03:40:14PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Apr 10, 2017 at 01:14:30PM -0700, David Carrillo-Cisneros escreveu:
> > > Session sets a number parameters that rely on evlist. The
Em Tue, Apr 11, 2017 at 03:37:43PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Apr 11, 2017 at 03:35:58PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Ideas? Will dig deeper later, the warning in the perf test output
> > doesn't help.
> >
> > Using perf as in acme/perf/core
>
> Humm, I h
On Tue, 2017-04-11 at 20:42 +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 11, 2017 at 11:15:54AM -0700, Joe Perches wrote:
> > On Tue, 2017-04-11 at 16:09 +0200, Greg Kroah-Hartman wrote:
> > > Care to use "real" kernel variable types please? u8, u16, and others
> > > are you friend, uint8_t real
On Tue, 11 Apr 2017 12:27:55 -0600
Alex Williamson wrote:
> On Tue, 11 Apr 2017 19:03:14 +0800
> Peter Xu wrote:
>
> > On Thu, Apr 06, 2017 at 08:53:43AM -0600, Alex Williamson wrote:
> > > If the mmap_sem is contented then the vfio type1 IOMMU backend will
> > > defer locked page accounting
On Mon, 10 Apr 2017, Thomas Gleixner wrote:
On Wed, 5 Apr 2017, Luck, Tony wrote:
On Wed, Apr 05, 2017 at 05:20:24PM +0200, Thomas Gleixner wrote:
That's just wrong.
The proper behaviour for a new control group is, that at the time when it
is created it copies the CBM values of the default
On 04/11/17 04:12, Felipe Balbi wrote:
> With a growing amount of Kernel configuration, it's
> getting ever more difficult to find anything on
> menuconfig. Because of that, implement mergesort for
> kconfig to make it a little easier for anybody
> building kernels.
Search works for me, but I don'
On Tue, 11 Apr 2017, Petr Mladek wrote:
> klp_init_transition() does not set func->transition for immediate patches.
> Then klp_ftrace_handler() could use the new code immediately. As a result,
> it is not safe to put the livepatch module in klp_cancel_transition().
>
> This patch reverts most of
On Tue 11-04-17 13:44:02, Cristopher Lameter wrote:
> On Tue, 11 Apr 2017, Michal Hocko wrote:
>
> > > So we are already handling that condition. Why change things? Add a BUG_ON
> > > if you want to make SLAB consistent.
> >
> > I hate to repeat myself but let me do it for the last time in this
>
free_dup_event is called in two places
1) ordered_events__free
2) ordered_events__delete
without this patch, calling 1) after 2) would cause a double
de-allocation, but that's exactly what happens in
__perf_session__process_pipe_events. It wasn't triggered before
because events where not copie
Only the second one is needed. file is already checked for the first one.
On Tue, Apr 11, 2017 at 11:44 AM, Arnaldo Carvalho de Melo
wrote:
> Em Tue, Apr 11, 2017 at 03:40:50PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Tue, Apr 11, 2017 at 03:40:14PM -0300, Arnaldo Carvalho de Melo escreveu
On Tue, 11 Apr 2017, Michal Hocko wrote:
> I didn't say anything like that. Hence the proposed patch which still
> needs some more thinking and evaluation.
This patch does not even affect kfree(). Could you start another
discussion thread where you discuss your suggestions for the changes in
the
+CC linux-api
On 11.4.2017 19:24, Christoph Lameter wrote:
> On Tue, 11 Apr 2017, Vlastimil Babka wrote:
>
>> The root of the problem is that the cpuset's mems_allowed and mempolicy's
>> nodemask can temporarily have no intersection, thus get_page_from_freelist()
>> cannot find any usable zone. T
On Tue, Feb 28, 2017 at 5:11 PM, Paul Moore wrote:
> On Tue, Feb 21, 2017 at 2:15 AM, Reshetova, Elena
> wrote:
>>> On Mon, Feb 20, 2017 at 5:19 AM, Elena Reshetova
>>> wrote:
>>> > refcount_t type and corresponding API should be
>>> > used instead of atomic_t when the variable is used as
>>> >
On 11.4.2017 19:32, Christoph Lameter wrote:
> On Tue, 11 Apr 2017, Vlastimil Babka wrote:
>
>> The task->il_next variable remembers the last allocation node for task's
>> MPOL_INTERLEAVE policy. mpol_rebind_nodemask() updates interleave and
>> bind mempolicies due to changing cpuset mems. Current
On Tue, Apr 11, 2017 at 11:34 AM, Mark Brown wrote:
> On Mon, Apr 10, 2017 at 12:35:12PM -0700, John Stultz wrote:
>
>> This patch adds a few extra error returns in cases that
>> shouldn't happen, some style nits adding breaks to final
>> default cases in switch statements, and tweaks to use
>> de
On Tue, Apr 11, 2017, at 02:07 PM, Eric Blake wrote:
>
> A good idea on the surface. But reading the man page of openat(), the
> section on O_PATH says:
>The file
> itself is not opened, and other file operations (e.g.,
> read(2),
> write(2), fchmod(2), fchown(2),
Hi Guillaume,
Please see inline:
On Tue, Apr 11, 2017 at 10:05 AM, Guillaume Nault wrote:
> On Tue, Apr 11, 2017 at 09:39:58AM -0700, R Parameswaran wrote:
>> Hi Guillaume,
>>
>> On Tue, Apr 11, 2017 at 3:40 AM, Guillaume Nault
>> wrote:
>> > On Wed, Apr 05, 2017 at 05:00:07PM -0700, R. Parame
On 04/07/2017 12:02 PM, Will Deacon wrote:
> Please pull these two arm64 fixes for -rc6. We've got a regression fix for
> the signal raised when userspace makes an unsupported unaligned access and a
> revert of the contiguous (hugepte) support for hugetlb, which has once again
> been found to be b
This patch addresses feedback from Mark Brown, adding a few
extra error returns in cases that shouldn't happen
Cc: Zhangfei Gao
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Wei Xu
Cc: Rob Herring
Cc: Andy Green
Cc: Dave Long
Cc: Guodong Xu
Signed-off-by: John Stultz
---
soun
Per feedback from Mark Brown, this patch updates the hi6210-i2s
driver to use devm_snd_soc_register_component which simplifies
the logic a bit.
Cc: Zhangfei Gao
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Wei Xu
Cc: Rob Herring
Cc: Andy Green
Cc: Dave Long
Cc: Guodong Xu
Sign
Mark Brown suggested a style change to use break in the final
default of a switch statement, so this patch addresses that.
Cc: Zhangfei Gao
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc: Wei Xu
Cc: Rob Herring
Cc: Andy Green
Cc: Dave Long
Cc: Guodong Xu
Signed-off-by: John Stult
From: Wei Wang
Currently checkpatch.pl does not recognize git's default
commit revert message and will complain about the hash format.
Add special audit for revert commit message line to fix it.
Signed-off-by: Wei Wang
---
scripts/checkpatch.pl | 1 +
1 file changed, 1 insertion(+)
diff --git
Besides reusing existing code this removes the special case handling
for 64-bit masks, which causes clang to raise a shift count overflow
warning due to https://bugs.llvm.org//show_bug.cgi?id=10030.
Suggested-by: Dmitry Torokhov
Signed-off-by: Matthias Kaehlcke
---
include/linux/clocksource.h |
gpio-only driver operation never clears the SLEEP bit, which can
cause the gpios to become unusable.
Example:
1. user requests first pwm -> driver clears SLEEP bit
2. user frees last pwm -> driver sets SLEEP bit
3. user requests gpio
4. user switches gpio on-> output does
v2:
the pm_runtime framework controls the SLEEP bit, as suggested by
Mika Westerberg.
v1:
the SLEEP bit is always on.
Sven Van Asbroeck (1):
pwm: pca9685: fix gpio-only operation.
drivers/pwm/pwm-pca9685.c | 110 --
1 file ch
On Mon, Apr 10, 2017 at 1:11 PM, Mark Brown wrote:
> On Mon, Apr 10, 2017 at 12:49:17PM -0500, Rob Herring wrote:
>
>> Same question as Mark. Should this share bindings with arizona? The
>> arizona one looks a bit strange, so not sure we'd want to just copy it.
>
> In what way? Other than the -gp
On Tue, 2017-04-11 at 12:15 -0700, Wei Wang wrote:
> From: Wei Wang
>
> Currently checkpatch.pl does not recognize git's default
> commit revert message and will complain about the hash format.
> Add special audit for revert commit message line to fix it.
>
> Signed-off-by: Wei Wang
Acked-by:
When a blkfront device is resized from dom0, emit a KOBJ_CHANGE uevent to
notify the guest about the change. This allows for custom udev rules, such
as automatically resizing a filesystem, when an event occurs.
Signed-off-by: Marc Olson
---
drivers/block/xen-blkfront.c | 3 +++
1 file changed, 3
Sounds good to me! Sorry that my initial pull request didn't have "cc: stable"
added to it...
Anna
On 04/09/2017 04:14 PM, Mkrtchyan, Tigran wrote:
> The problem was introduced in 4.10.
>
> Anna, can you comment?
>
>
> -Tigran
>
> - Reply message -
> From: "Greg KH"
> To: "Mkrtchya
If the mmap_sem is contented then the vfio type1 IOMMU backend will
defer locked page accounting updates to a workqueue task. This has a
few problems and depending on which side the user tries to play, they
might be over-penalized for unmaps that haven't yet been accounted or
race the workqueue to
2017-04-11 10:37+0100, James Hogan:
> Hi Paolo,
>
> On Tue, Apr 11, 2017 at 01:25:04PM +0800, Paolo Bonzini wrote:
>> On 07/04/2017 05:02, James Hogan wrote:
>> > This presumably changes the behaviour on x86, from != OUTSIDE_GUEST_MODE
>> > to == IN_GUEST_MODE. so:
>> > - you'll no longer get IPIs
On Mon, Apr 10, 2017 at 10:43:28AM -0500, Bjorn Helgaas wrote:
> On Wed, Apr 05, 2017 at 02:22:20PM +0530, Kishon Vijay Abraham I wrote:
> > Hi Bjorn,
> >
> > Please find the pull request for PCI endpoint support below. I've
> > also included all the history here.
>
> Thanks, I applied these (wit
Hi Jerome,
On Thu, Apr 06, 2017 at 04:27:00PM -0400, Jerome Glisse wrote:
> Do we have an open source toolchain to generate the FPGA configuration
> (bitstream) ? As it is required for the GPU sub-system that any driver
> API must comes with open source userspace.
As far as I know, no FPGA vendo
2017-04-01 5:38 GMT+09:00 Arnd Bergmann :
> From: Mark Charlebois
>
> Clang will warn about unknown warnings but will not return false
> unless -Werror is set. GCC will return false if an unknown
> warning is passed.
>
> Adding -Werror make both compiler behave the same.
>
> [arnd: it turns out we
On Tue 11-04-17 13:59:44, Cristopher Lameter wrote:
> On Tue, 11 Apr 2017, Michal Hocko wrote:
>
> > I didn't say anything like that. Hence the proposed patch which still
> > needs some more thinking and evaluation.
>
> This patch does not even affect kfree().
Ehm? Are we even talking about the
.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
> (2017-03-17 15:13:28 +0100)
>
> 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.11-20170411
>
> for you to fetch cha
On 11/04/17 19:21, Milan Broz wrote:
> On 04/11/2017 05:33 PM, Enric Balletbo i Serra wrote:
>> From: Will Drewry
>>
>> Version 0 of the on-disk format is compatible with the format used in the
>> Chromium OS. This patch adds support for this version.
>>
>> Format type 0 is the original Chrome O
Em Tue, Apr 11, 2017 at 11:59:18AM -0700, David Carrillo-Cisneros escreveu:
> Only the second one is needed. file is already checked for the first one.
Right, fixed, tested.
- Arnaldo
- Original Message -
> From: "Radim Krčmář"
> To: "James Hogan"
> Cc: "Paolo Bonzini" , linux-kernel@vger.kernel.org,
> k...@vger.kernel.org, "Christoffer Dall"
> , "Andrew Jones" , "Marc Zyngier"
> , "Christian
> Borntraeger" , "Cornelia Huck"
> , "Paul Mackerras"
>
> Sent: Wednesd
Commit-ID: 3c1a427954399fd1bda1ee7e1b356f47b61cee74
Gitweb: http://git.kernel.org/tip/3c1a427954399fd1bda1ee7e1b356f47b61cee74
Author: Christian Borntraeger
AuthorDate: Thu, 6 Apr 2017 09:51:51 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 7 Apr 2017 12:33:10 -0300
perf an
On 4/10/2017 9:43 PM, Kees Cook wrote:
> On Mon, Apr 10, 2017 at 1:00 PM, Djalal Harouni wrote:
>> On Mon, Apr 10, 2017 at 9:26 PM, Casey Schaufler
>> wrote:
>>> I think that would be the prudent approach. There is still
>>> the possibility that blob sharing (or full stacking, if you
>>> prefer)
On Tue, Apr 11, 2017 at 12:54 PM, Casey Schaufler
wrote:
> On 4/10/2017 9:43 PM, Kees Cook wrote:
>> On Mon, Apr 10, 2017 at 1:00 PM, Djalal Harouni wrote:
>>> On Mon, Apr 10, 2017 at 9:26 PM, Casey Schaufler
>>> wrote:
I think that would be the prudent approach. There is still
the po
On Tue, Apr 11, 2017 at 02:20:31PM -0500, Rob Herring wrote:
> On Mon, Apr 10, 2017 at 1:11 PM, Mark Brown wrote:
> > In what way? Other than the -gpios stuff (which would just be a trivial
> > thing if we wanted to change it)?
> That's mainly it.
I don't see that as meaningful or a good reaso
On Tue, Apr 11, 2017 at 12:24:09PM -0700, Marc Olson wrote:
> When a blkfront device is resized from dom0, emit a KOBJ_CHANGE uevent to
> notify the guest about the change. This allows for custom udev rules, such
> as automatically resizing a filesystem, when an event occurs.
Looks pretty reasonab
Dan Williams writes:
> As a minimal fix, disable error clearing when the BTT is enabled. For
> the final fix a larger rework of the poison list locking is needed.
> @@ -243,7 +243,15 @@ static int nsio_rw_bytes(struct nd_namespace_common
> *ndns,
> }
>
> if (unlikely(is_bad_pmem(&
On Tue, Apr 11, 2017 at 1:08 PM, Jeff Moyer wrote:
> Dan Williams writes:
>
>> As a minimal fix, disable error clearing when the BTT is enabled. For
>> the final fix a larger rework of the poison list locking is needed.
>
>> @@ -243,7 +243,15 @@ static int nsio_rw_bytes(struct nd_namespace_common
On Sat, Apr 8, 2017 at 1:58 PM, Deepa Dinamani wrote:
>> I have no problem merging this patch into audit/next for v4.12, would
>> you prefer me to do that so at least this patch is merged?
>
> This would be fine.
> But, I think whoever takes the last 2 deletion patches should also take them.
> I'm
Hi!
> On Mon, Mar 06, 2017 at 11:11:47PM +0100, Pavel Machek wrote:
> > > Motorola CPCAP is a PMIC found in multiple smartphones.
> > > This driver adds support for the chip's LED controllers.
> > > It has explicit support for all controllers used by the
> > > Droid 4. Since no datasheets are avai
On Tue 2017-03-07 08:26:40, Tony Lindgren wrote:
> * Pavel Machek [170307 03:57]:
> > 2 cores and more importantly 1GB of RAM. Nice. OTOH, I'm avoiding N950
> > due to its crazy "security" system and this one is even worse.
>
> Yeah this security crap sucks big time in general. It just slows
> do
On Wed, Apr 5, 2017 at 6:58 AM, Wu Hao wrote:
> On Mon, Apr 03, 2017 at 04:44:15PM -0500, Alan Tull wrote:
>> On Thu, Mar 30, 2017 at 7:08 AM, Wu Hao wrote:
>> > From: Xiao Guangrong
>> >
>> > Device Featuer List structure creates a link list of feature headers
>> > within the MMIO space to prov
On Wed, Apr 12, 2017 at 09:58:43AM +0800, Dong Aisheng wrote:
> Mandatorily set the initdata->supply_regulator while it actually not
> exist will cause regulator core to resolve supply each time whenever
> a new regulator registered which is meaningless and waste CPU mips.
>
> We can observe more
On Tue, Apr 11, 2017 at 05:38:35PM +0200, Greg KH wrote:
> I haven't seen this at all, nor heard of it. As systemctl only gets
> what udev reports to it, have you tried using 'udevadm' to monitor your
> devices when you plug them in, to ensure it is really seeing them?
The problem is that the pro
On Mon, 10 Apr 2017 21:33:51 -0400 (EDT) Jerome Glisse
wrote:
> > On Mon, 10 Apr 2017 10:43:26 +0200 Michal Hocko wrote:
> >
> > > There are more for alpha allmodconfig
> >
> > HMM is rather a compile catastrophe, as was the earlier version I
> > merged.
> >
> > Jerome, I'm thinking you need
Rather than just not resolving the supply when there is explicitly no
supply mapping fall through and allow a dummy supply to be substituted.
Signed-off-by: Mark Brown
---
drivers/regulator/core.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regul
On Tue, Apr 11, 2017 at 09:34:37PM +0100, Mark Brown wrote:
> Rather than just not resolving the supply when there is explicitly no
> supply mapping fall through and allow a dummy supply to be substituted.
I should mention that this is completely untested, sorry.
signature.asc
Description: PGP s
On Wed, Apr 12, 2017 at 09:58:46AM +0800, Dong Aisheng wrote:
> rdesc->name/regulator-name is optional according to standard regulator
> binding doc. Use it conditionally to avoid a kernel NULL point crash.
It is optional in the standard binding because it is used to override
the name statically p
On Wed, Apr 12, 2017 at 09:58:47AM +0800, Dong Aisheng wrote:
> Set the initial voltage selector for vddpcie in case it's disabled
> by default.
Why is this the only anatop regulator which can have this problem and
how do we know this is a good value?
signature.asc
Description: PGP signature
The patch
regulator: anatop: use of_property_read_string to read the name
has been applied to the regulator tree at
git://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 n
The patch
regulator: anatop: remove unneeded name field of struct anatop_regulator
has been applied to the regulator tree at
git://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
The patch
regulator: anatop: check return value of of_get_regulator_init_data
has been applied to the regulator tree at
git://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 t
Oleksij,
Am 11.04.2017 um 11:50 schrieb Oleksij Rempel:
> From: Steffen Trumtrar
>
> This is need to provide uuid based integrity functionlity for:
> imy_policy (fsuuid option) and evmctl (--uuid option).
>
> Signed-off-by: Steffen Trumtrar
> Signed-off-by: Oleksij Rempel
> ---
> fs/ubifs/s
2017-04-11 13:25+0800, Paolo Bonzini:
> On 07/04/2017 05:02, James Hogan wrote:
>> - you'll no longer get IPIs if its in EXITING_GUEST_MODE (i.e. if you
>> get two of these in quick succession only the first will wait for the
>> IPI, which might work as long as they're already serialised but it
Hi Guillaume,
Am Dienstag, 11. April 2017, 18:40:37 CEST schrieb Guillaume Tucker:
> On 03/04/17 09:12, Neil Armstrong wrote:
> > On 04/02/2017 09:59 AM, Guillaume Tucker wrote:
> >> +Optional:
> >> +
> >> +- clocks : Phandle to clock for the Mali Midgard device.
> >> +- clock-names : Shall be "cl
On Tue, Apr 11, 2017 at 08:42:24PM +0200, Florian Weimer wrote:
> On 04/11/2017 08:36 PM, Yury Norov wrote:
> >>Also, the latest benchmarks I've seen were mostly for user space
> >>while I'm more concerned with the user-kernel interface
> >>(https://marc.info/?l=linux-arm-kernel&m=148690490713310&w
On Tue, Apr 11, 2017 at 3:57 AM, Joel Fernandes wrote:
> On Mon, Apr 10, 2017 at 1:59 PM, Rafael J. Wysocki wrote:
> [..]
+ sg_cpu->util = cfs_util;
+ sg_cpu->max = cfs_max;
+ }
}
>>
>>
>> Well, that's the idea. :-)
>>
>> During the discussio
On Tue, Apr 11, 2017 at 04:28:39AM +0100, Al Viro wrote:
> On Mon, Apr 10, 2017 at 11:05:32PM -0400, Dave Jones wrote:
> > On Tue, Apr 11, 2017 at 01:22:15AM +0100, Al Viro wrote:
> >
> > > * in do_splice_to(): WARN_ON(pipe->nrbufs == pipe->buffers)
> >
> > Hit this one.
>
> But
This patch moves as is the legacy DSA code from dsa.c to legacy.c,
except the few shared symbols which remain in dsa.c.
Compile legacy.o only if a new CONFIG_NET_DSA_LEGACY symbol is enabled,
which is true by default.
DSA drivers without legacy support don't need the probe function as well
as dri
On Mon, Apr 10, 2017 at 03:50:44PM -0400, Aaron Conole wrote:
> There are no in-tree callers of this function and it isn't exported.
>
> Signed-off-by: Aaron Conole
Thanks, applied to ipvs-next.
On Tue, 11 Apr 2017 10:56:45 +0530 Pushkar Jambhlekar
wrote:
> Changing rc value from VM_FAULT_FALLBACK to VM_FAULT_SIGBUS for an unknown /
> unsupported fault size.
>
> ...
>
> --- a/drivers/dax/dax.c
> +++ b/drivers/dax/dax.c
> @@ -590,7 +590,7 @@ static int dax_dev_huge_fault(struct vm_faul
My previous patch (c5d8fac2bf drm: Unplug drm device when unregistering
it) calls drm_unplug_dev when unregistering drm dev. But if open_count
is 0, the unplug will try to unregister the drm dev again and cause
deadlock.
Fix it by dropping drm_unplug_dev and use drm_device_set_plug_state
directly
On 04/11/2017 01:52 PM, Vivien Didelot wrote:
> This patch moves as is the legacy DSA code from dsa.c to legacy.c,
> except the few shared symbols which remain in dsa.c.
>
> Compile legacy.o only if a new CONFIG_NET_DSA_LEGACY symbol is enabled,
> which is true by default.
>
> DSA drivers without
Russell King - ARM Linux writes:
> On Tue, Apr 11, 2017 at 09:06:31AM -0700, Eric Anholt wrote:
>> Russell King - ARM Linux writes:
>>
>> > On Mon, Apr 10, 2017 at 06:18:01PM -0700, Eric Anholt wrote:
>> >> v5: Move register definitions inside the driver directory, fix build
>> >> in COMPIL
On Apr 11, 2017, at 12:48 AM, Al Viro wrote:
> On Mon, Apr 10, 2017 at 11:10:19PM -0700, Linus Torvalds wrote:
>
>> It looks odd because the lock part is
>>
>>if (flags & LOOKUP_RCU)
>>rcu_read_lock();
>>
>> ie it's locked conditionally, and the code in b
On Tue, Apr 11, 2017 at 9:00 AM, Juri Lelli wrote:
> On 10/04/17 23:13, Rafael J. Wysocki wrote:
>> On Mon, Apr 10, 2017 at 1:26 PM, Juri Lelli wrote:
>
> [...]
>
>> > Given that for RT (and still for DL as well) the next event is a
>> > periodic tick, couldn't happen that the required frequency
601 - 700 of 939 matches
Mail list logo
