Commit-ID: 6d13491e2d4944180c9b4fb6ddca4e34b1537836
Gitweb: http://git.kernel.org/tip/6d13491e2d4944180c9b4fb6ddca4e34b1537836
Author: David Carrillo-Cisneros
AuthorDate: Mon, 10 Apr 2017 13:14:28 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 11 Apr 2017 15:23:41 -0300
per
Commit-ID: c9d1c93421e3b3c7051b193c9cf648a3bc55cb3e
Gitweb: http://git.kernel.org/tip/c9d1c93421e3b3c7051b193c9cf648a3bc55cb3e
Author: David Carrillo-Cisneros
AuthorDate: Mon, 10 Apr 2017 13:14:32 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 11 Apr 2017 16:22:22 -0300
per
Commit-ID: 0973ad97c187e06aece61f685b9c3b2d93290a73
Gitweb: http://git.kernel.org/tip/0973ad97c187e06aece61f685b9c3b2d93290a73
Author: David Carrillo-Cisneros
AuthorDate: Mon, 10 Apr 2017 13:14:30 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 11 Apr 2017 16:22:20 -0300
per
Hi Tobias,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.11-rc6 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/Tobias-Klauser/fpga-allow-to-compile
On Tue, Apr 11, 2017 at 10:43:26PM +0200, Richard Weinberger wrote:
> Artem, do you remember why UBIFS didn't set s_uuid in first place?
It's an extremely odd field - only a hand full of file systems set it
(e.g. XFS doesn't, although according to Mimi IMA supports XFS), and
it's never even used o
On 12.04.2017 04:59, Bob Tracy wrote:
> (Adding linux-kernel to the distribution. The issue seems to be
> architecture-specific, but I'm trying to understand what broke.)
>
> The 4.10-rc1 patch set made fairly extensive modifications to
> "a/kernel/module.c" (I'm leaving the "a" there so there's
Hi,
Greg KH writes:
> On Tue, Apr 11, 2017 at 10:12:01AM -0400, Alan Stern wrote:
>> On Tue, 11 Apr 2017, Felipe Balbi wrote:
>>
>> > > Oddly enough, yes. But it doesn't explain why this code doesn't blow
>> > > up every time it gets called, in its current form.
>> >
>> > Well, it does :-)
>
> Il giorno 11 apr 2017, alle ore 20:31, Bart Van Assche
> ha scritto:
>
> 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?
On Wed, Apr 12, 2017 at 02:01:59PM +0900, Hoeun Ryu wrote:
> vm_area_add_early/vm_area_register_early() are used to reserve vmalloc area
> during boot process and those virtually mapped areas are never unmapped.
> So `OR` VM_STATIC flag to the areas in vmalloc_init() when importing
> existing vmlis
Hi Sergey,
you're new thunderx_edac driver uses pci_enable_msix_exact for no
good reason. Can you please switch it to use pci_alloc_irq_vectors
before it gets merged to mainline?
Thanks,
Christoph
On Tue, Apr 11, 2017 at 11:13:24PM +0200, Richard Weinberger wrote:
> Am 11.04.2017 um 18:05 schrieb Christoph Hellwig:
> > On Tue, Apr 11, 2017 at 11:50:54AM +0200, Oleksij Rempel wrote:
> >> increment i_version to notify security/IMA about changes
> >> made in inode.
> >>
> >> Signed-off-by: Olek
On Wed, Apr 12, 2017 at 08:05:34AM +0200, Oleksij Rempel wrote:
> The code seems to confirm it. So i assumed that IMA don't care if
> i_version is stored to disk or not. And i_version is the only way
> to notify IMA about inode changes.
> Since IMA documentation explecitley set i_version as reqiere
On 11-04-17, 10:33, Eduardo Valentin wrote:
> On Thu, Mar 16, 2017 at 10:59:38AM +0530, Viresh Kumar wrote:
> > Objects of "struct cpufreq_cooling_device" are named a bit
> > inconsistently. Lets use cpufreq_dev everywhere.
> >
>
> Naming is always a matter of taste.. but I frankly cannot see how
On dra7, as per TRM, the HW shutdown (TSHUT) temperature is hardcoded
to 123C and cannot be modified by SW. This means when the temperature
reaches 123C HW asserts TSHUT output which signals a warm reset.
This reset is held until the temperature goes below the TSHUT low (105C).
While in SW, the th
On Tue, Apr 11, 2017 at 08:35:00AM -0500, Rob Herring wrote:
> On Mon, Apr 10, 2017 at 11:36 PM, Oleksij Rempel wrote:
> > Hi,
> > On 04/10/2017 08:22 PM, Rob Herring wrote:
> >>
> >> On Thu, Apr 06, 2017 at 09:31:07AM +0200, Oleksij Rempel wrote:
> >>>
> >>> Documenation bindings for the Low Powe
On Thu, 2017-03-30 at 16:12 -0600, Logan Gunthorpe wrote:
> Hello,
>
> As discussed at LSF/MM we'd like to present our work to enable
> copy offload support in NVMe fabrics RDMA targets. We'd appreciate
> some review and feedback from the community on our direction.
> This series is not intended t
On 04/11/2017 10:43 AM, Petr Mladek wrote:
On Mon 2017-04-10 21:00:35, Aleksey Makarov wrote:
On 04/10/2017 05:22 PM, Petr Mladek wrote:
On Wed 2017-04-05 23:20:00, Aleksey Makarov wrote:
[..]
Thank you for review. Can you (or anybody else) ACK it?
I am going to resend the whole series
On 04/10/2017, 09:35 PM, Josh Poimboeuf wrote:
> The code should be in a mergeable state after each patch. If only
> patches 1-3 were merged, the code would be in an inconsistent state,
> with some functions having confusing ENTRY/SYM_FUNC_END pairs. That
> complicates git history and also makes
On 11-04-17, 10:43, Eduardo Valentin wrote:
> On Thu, Mar 16, 2017 at 10:59:40AM +0530, Viresh Kumar wrote:
> > There is only one user of cpufreq_cooling_get_level() and that already
> > has pointer to the cpufreq_dev structure. It can directly call
> > get_level() instead and we can get rid of cpu
On Tue, Apr 11, 2017 at 06:40:30PM -0700, Guenter Roeck wrote:
> On 04/11/2017 08:17 AM, Tony Lindgren wrote:
> > * Greg Kroah-Hartman [170410 21:45]:
> > > On Mon, Apr 10, 2017 at 08:07:17PM -0700, Guenter Roeck wrote:
> > > > The arm builds fail as follows.
> > > >
> > > > Building arm:overo:om
On Tue, Apr 11, 2017 at 11:31:41AM +0800, Jeffy Chen wrote:
> After unbinding drm, the user space may still owns the drm dev fd,
> and may still be able to call drm ioctl.
>
> We're using an unplugged state to prevent something like that, so
> let's reuse it here.
>
> Signed-off-by: Jeffy Chen
>
On Tue, Apr 11, 2017 at 11:31:42AM +0800, Jeffy Chen wrote:
> We are freeing all framebuffers in drm_mode_config_cleanup without
> sync the drm_file's fbs list.
>
> So if someone try to unbind drm before release drm dev fd, the fbs
> list would remain some invalid fb references. And that would cau
* Masami Hiramatsu wrote:
> On Thu, 30 Mar 2017 08:53:32 +0200
> Ingo Molnar wrote:
>
> >
> > * Masami Hiramatsu wrote:
> >
> > > > So this is something I missed while the original code was merged, but
> > > > the concept
> > > > looks a bit weird: why do we do any "allocation" while a ha
On Wed, Apr 12, 2017 at 09:01:44AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Greg KH writes:
> > On Tue, Apr 11, 2017 at 10:12:01AM -0400, Alan Stern wrote:
> >> On Tue, 11 Apr 2017, Felipe Balbi wrote:
> >>
> >> > > Oddly enough, yes. But it doesn't explain why this code doesn't blow
> >> > > u
Hi Andrew,
Today's linux-next merge of the akpm-current tree got conflicts in:
drivers/block/nbd.c
drivers/scsi/iscsi_tcp.c
net/core/dev.c
net/core/sock.c
between commit:
717a94b5fc70 ("sched/core: Remove 'task' parameter and rename
tsk_restore_flags() to current_restore_flags()")
f
The build of JVMTI depends on LIBELF (-lelf). Make Makefile.conf
check this dependendancy and notify user when not present.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/Makefile.config | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tools/perf/Makefile.config b/to
Minor build fixes and error condition hints.
David Carrillo-Cisneros (6):
perf tools: pass PYTHON config to feature detection
tools build: fix feature detection redefinion of build flags
perf util: hint missing file when tool tips fail to load
perf report: hint .perfconfig error when inval
( This is a rebased version of https://lkml.org/lkml/2017/2/7/662 )
Python's CC and link Makefile variables were not passed to feature
detection, causing feature detection to use system's Python rather than
PYTHON_CONFIG's one. This created a mismatch between the detected Python
support and the on
This change is a follow up of https://lkml.org/lkml/2017/2/2/16
The patch above avoided redefining CC, CXX and PKG_CONFIG in feature
detection. The patch was not merged due to a unsolved concern with
the -MD flag.
Later, commit c8c188679c ("tools build: Use the same CC for feature
detection and
My fat-fingering of sort keys in .perfconfig was a common cause of
perf report silently terminating without apparent error.
This was because 1) error in setup_sorting in cmd_report was ignored
and 2) no message was log in UI browser that would prevent UI from
exit before user prompt. Fix both.
Si
In https://lkml.org/lkml/2017/2/2/16 I reported a build error
that I believed was caused by wrong uapi includes. The synthom
was fixed by Arnaldo in:
commit 2f7db5557994 ("perf tools: Fix include of linux/mman.h")
but I was wrong attributing the problem to the uapi include.
The root cause was t
Besides memory allocation failure, tips.txt may fail to load
because the file is not found (a more likely cause).
Communicate that to the user in tips failure warning.
Signed-off-by: David Carrillo-Cisneros
---
tools/perf/util/util.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
On 2017-04-11 at 17:21:19 +0200, Alan Tull wrote:
> On Tue, Apr 11, 2017 at 9:35 AM, Tobias Klauser wrote:
> > Hi Alan,
> >
> > On 2017-04-11 at 16:27:03 +0200, Alan Tull wrote:
> >> On Tue, Apr 11, 2017 at 4:22 AM, Tobias Klauser
> >> wrote:
> >>
> >> Hi Tobias,
> >>
> >> Thanks for your fixe
This change is a follow up of https://lkml.org/lkml/2017/2/2/16
The patch above avoided redefining CC, CXX and PKG_CONFIG in feature
detection. The patch was not merged due to a unsolved concern with
the -MD flag.
Later, commit c8c188679ccf ("tools build: Use the same CC for feature
detection a
* Jiri Slaby wrote:
> On 04/10/2017, 09:35 PM, Josh Poimboeuf wrote:
> > The code should be in a mergeable state after each patch. If only
> > patches 1-3 were merged, the code would be in an inconsistent state,
> > with some functions having confusing ENTRY/SYM_FUNC_END pairs. That
> > compli
On Tue, Apr 11, 2017 at 06:43:22PM +, Bart Van Assche wrote:
> 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_requ
Hi,
On Mon, Apr 10, 2017 at 2:07 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 05 April 2017 07:40 PM, Raviteja Garimella wrote:
>> Hi Kishon,
>>
>> On Wed, Apr 5, 2017 at 7:04 PM, Kishon Vijay Abraham I wrote:
>>> Hi Ravi,
>>>
>>> On Wednesday 05 April 2017 06:30 PM, Raviteja Garimel
On Tue, Apr 11, 2017 at 9:47 PM, Nicholas A. Bellinger
wrote:
> Hi Linus,
>
> Here are the outstanding target-pending bug-fixes for v4.11-rc7.
So I'm pulling this, but I'm getting real tired of this crap. We're
late in the rc's, I shouldn['t be getting pull requests of hundreds of
lines any more.
Hi,
On Wed, 12 Apr 2017 13:27:32 +0800
Xunlei Pang wrote:
[...]
> The more I read the code, the more I am confused why
> dl_entity_overflow() is needed, if the task is before its deadline,
> just let it run.
Sorry for jumping in this thread; I did not read all of the previous
emails, but I think
901 - 939 of 939 matches
Mail list logo