On Tue, 2017-03-21 at 12:30 -0400, J. Bruce Fields wrote:
> On Tue, Mar 21, 2017 at 06:45:00AM -0700, Christoph Hellwig wrote:
> > On Mon, Mar 20, 2017 at 05:43:27PM -0400, J. Bruce Fields wrote:
> > > To me, the interesting question is whether this allows us to turn on
> > > i_version updates by
On Tue, Mar 21, 2017 at 05:41:22PM +0100, Jan Kara wrote:
> On Tue 21-03-17 11:38:49, J. Bruce Fields wrote:
> > On Sun, Mar 19, 2017 at 11:19:43AM +0100, Jan Kara wrote:
> > > On Tue 14-03-17 13:18:01, Amir Goldstein wrote:
> > > > On Tue, Mar 14, 2017 at 1:03 AM, Filip Štědronský
On Tue, Mar 21, 2017 at 10:34:01PM +0530, SIMRAN SINGHAL wrote:
> On Tue, Mar 21, 2017 at 10:18 PM, Alison Schofield
> wrote:
> > On Mon, Mar 20, 2017 at 01:36:21AM +0530, simran singhal wrote:
> >
> > Hi Simran,
> >
> > I going to ask for a v7 without looking at the code
Hi Vincent,
On 17/03/17 13:47, Vincent Guittot wrote:
[...]
> Reported-by: ying.hu...@linux.intel.com
> Signed-off-by: Vincent Guittot
> Fixes: 4e5160766fcc ("sched/fair: Propagate asynchrous detach")
I thought I can see a difference by running:
perf stat --null
On Tue, Mar 21, 2017 at 03:17:17PM +0100, Tomasz Nowicki wrote:
> Hi Bjorn,
>
> On 21.03.2017 14:47, Bjorn Helgaas wrote:
> >On Tue, Mar 21, 2017 at 07:38:07AM -0400, Jon Masters wrote:
> >>On 03/16/2017 12:25 PM, David Daney wrote:
> >>>On 03/16/2017 07:32 AM, Jon Masters wrote:
> >>
> >Yes,
On Tue, Mar 21, 2017 at 10:17 AM, Cyrill Gorcunov wrote:
> On Tue, Mar 21, 2017 at 07:37:12PM +0300, Dmitry Safonov wrote:
> ...
>> diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c
>> index d6b784a5520d..d3d4d9abcaf8 100644
>> ---
2017-03-14 4:33 GMT+09:00 Nicolas Iooss :
> When building the kernel with clang, the compiler complains about the
> presence of a condition inside two pairs of parentheses:
>
> scripts/kconfig/gconf.c:917:19: error: equality comparison with
> extraneous
Michael Zoran writes:
> On Mon, 2017-03-20 at 10:22 -0700, Eric Anholt wrote:
>> Michael Zoran writes:
>>
>> > > > Since the API is completely documented, I see no reason we or
>> > > > anybody
>> > > > couldn't essentially rewrite the driver while
Start to populate the device tree of the Armada 37xx with the pincontrol
configuration used on the board providing a dts.
Signed-off-by: Gregory CLEMENT
---
arch/arm64/boot/dts/marvell/armada-3720-db.dts | 8 +-
The Armada 37xx SoCs can handle interrupt through GPIO. However it can
only manage the edge ones.
The way the interrupt are managed are classical so we can use the generic
interrupt chip model.
The only unusual "feature" is that many interrupts are connected to the
parent interrupt controller.
Add the nodes for the two pin controller present in the Armada 37xx SoCs.
Initially the node was named gpio1 using the same name that for the
register range in the datasheet. However renaming it pinctr_nb (nb for
North Bridge) makes more sens.
Signed-off-by: Gregory CLEMENT
On Tue, Mar 21, 2017 at 09:09:40PM +0300, Dmitry Safonov wrote:
>
> I guess the question comes from that we're releasing CRIU 3.0 with
> 32-bit C/R and some other cool stuff, but we don't support x32 yet.
> As we don't want release a thing that we aren't properly testing.
> So for a while we
On Tue, 21 Mar 2017 17:05:40 +0100
wrote:
> From: Lionel Debieve
>
> The lock is a sleeping lock and local_irq_save() is not the
> standard implementation now. Working for both -RT and non
> RT.
If this is for both RT and non RT then the patch
On Tue, Mar 21, 2017 at 01:23:24PM -0400, Jeff Layton wrote:
> On Tue, 2017-03-21 at 12:30 -0400, J. Bruce Fields wrote:
> > - It's durable; the above comparison still works if there were reboots
> > between the two i_version checks.
> > - I don't know how realistic this is--we may need to
2017-03-21 10:29-0700, Nadav Amit:
>
> > On Mar 21, 2017, at 9:58 AM, Radim Krčmář wrote:
>
> > In '-smp 2', the writing VCPU always does 1 wakeups by writing into
> > monitored memory, but the mwaiting VCPU can be also woken up by host
> > interrupts, which might add a
On Tue, Mar 21, 2017 at 10:19:01PM +0300, Dmitry Safonov wrote:
> >
> > indeed, thanks!
>
> Also, even more simple-minded: for now we could just check binary magic
> from /proc/.../exe, for now stopping on x32 binaries.
File may not exist and elfheader wiped out as well.
On Tue, Mar 21, 2017 at 11:09 AM, Dmitry Safonov wrote:
> On 03/21/2017 08:45 PM, Andy Lutomirski wrote:
>>
>> On Tue, Mar 21, 2017 at 10:17 AM, Cyrill Gorcunov
>> wrote:
>>>
>>> On Tue, Mar 21, 2017 at 07:37:12PM +0300, Dmitry Safonov wrote:
>>> ...
On 21/03/17 15:05, SIMRAN SINGHAL wrote:
> On Tue, Mar 21, 2017 at 8:01 PM, kbuild test robot <l...@intel.com> wrote:
>> Hi simran,
>>
>> [auto build test WARNING on iio/togreg]
>> [also build test WARNING on v4.11-rc3 next-20170321]
>> [if your patch is app
On Mon, Mar 20, 2017 at 04:36:14PM -0700, Eric Anholt wrote:
> +static struct amba_driver pl111_amba_driver = {
> + .drv = {
> + .name = "clcd-pl11x",
either:
.name = "clcd-pl111",
or:
.name = "drm-clcd-pl111",
otherwise the driver names will
On Tue, 21 Mar 2017, Arushi Singhal wrote:
>
>
> On Tue, Mar 21, 2017 at 10:32 PM, Alison Schofield
> wrote:
> On Tue, Mar 21, 2017 at 05:39:38PM +0100, Julia Lawall wrote:
> >
> >
> > On Tue, 21 Mar 2017, Arushi Singhal wrote:
> >
> >
On March 21, 2017 9:37:12 AM PDT, Dmitry Safonov wrote:
>After my changes to mmap(), its code now relies on the bitness of
>performing syscall. According to that, it chooses the base of
>allocation:
>mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall.
>It
On Tue, Mar 21, 2017 at 01:37:04PM -0400, J. Bruce Fields wrote:
> On Tue, Mar 21, 2017 at 01:23:24PM -0400, Jeff Layton wrote:
> > On Tue, 2017-03-21 at 12:30 -0400, J. Bruce Fields wrote:
> > > - NFS doesn't actually require that it increases, but I think it
> > > should. I assume 64 bits
After my changes to mmap(), its code now relies on the bitness of
performing syscall. According to that, it chooses the base of allocation:
mmap_base for 64-bit mmap() and mmap_compat_base for 32-bit syscall.
It was done by:
commit 1b028f784e8c ("x86/mm: Introduce mmap_compat_base() for
32-bit
This moves code used in MFD probing to a new sun4i_gpadc_probe_mfd
function.
This driver was initially written for A10, A13 and A31 SoCs which
already had a DT binding for this IP, thus we needed to use an MFD to
probe the different drivers without changing the DT binding of these
SoCs.
For SoCs
On 20 March 2017 at 19:09, Alexander Shishkin
wrote:
> Chunyan Zhang writes:
>
>> Hi Alex,
>>
>> On 20 March 2017 at 16:49, Alexander Shishkin
>> wrote:
>>> Hi Chunyan,
>>>
>>> A couple of
Hi Marc,
Thank you very much for your review.
On 2017/3/20 21:58, Marc Zyngier wrote:
> On 20/03/17 12:28, gengdongjiu wrote:
>>
>>
>> On 2017/3/20 19:24, Marc Zyngier wrote:
>>> Please include James Morse on anything RAS related, as he's already
>>> looking at related patches.
>>>
>>> On
On CPU online the cpufreq core restores the previous governor (or
the previous "policy" setting for ->setpolicy drivers), but it does
not restore the min/max limits at the same time, which is confusing,
inconsistent and real pain for users who set the limits and then
suspend/resume the system
On Mon, Mar 20, 2017 at 12:31 AM, Icenowy Zheng wrote:
> Orange Pi One features a MicroUSB port that can work in both host mode
> and peripheral mode.
>
> When in host mode, its VBUS is controlled via a GPIO; when in peripheral
> mode, its VBUS cannot be used to power up the
On Tue, Mar 21, 2017 at 10:38:20AM +0900, Byungchul Park wrote:
> When cpudl_find() returns any among free_cpus, the cpu might not be
> closer than others, considering sched domain. For example:
>
>this_cpu: 15
>free_cpus: 0, 1,..., 14 (== later_mask)
>best_cpu: 0
>
>topology:
>
On 05/03/17 02:43, Sebastian Reichel wrote:
> From: Tony Lindgren
>
> With manual mode displays we need to flush the panel manually.
>
> Let's add flushing so we get Tomi's fbtest, kmstest, kmstest --flip,
> and X and wayland working.
>
> Signed-off-by: Tony Lindgren
On 20-03-17, 22:46, Rafael J. Wysocki wrote:
> Index: linux-pm/kernel/sched/cpufreq_schedutil.c
> +static void sugov_update_commit(struct sugov_cpu *sg_cpu,
> + struct sugov_policy *sg_policy,
> + u64 time, unsigned int next_freq)
> {
>
On 05/03/17 02:43, Sebastian Reichel wrote:
> This reverts commit 5a35876e2830511cb8110667fc426c6a6165a593.
>
> Revert the removal of manual update display support in
> preparation for DSI command mode panels.
I think it's much better to just add the manual update support from
scratch rather
Commit-ID: 249eed53152167c64c6dc66fa269a1d8b415a7b4
Gitweb: http://git.kernel.org/tip/249eed53152167c64c6dc66fa269a1d8b415a7b4
Author: Changbin Du
AuthorDate: Fri, 17 Mar 2017 13:53:42 +0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 17
On Tue, 21 Mar 2017 16:43:05 +1100
Gavin Shan wrote:
> On Mon, Mar 20, 2017 at 10:57:08PM -0600, Alex Williamson wrote:
> >On Mon, 20 Mar 2017 18:34:23 -0500
> >Bodong Wang wrote:
>
> .../...
>
> >> > Bodong, I'm not sure if there is a
On Sun, Mar 19, 2017 at 06:44:53PM +0530, Arushi Singhal wrote:
> Improve readability by fixing multiple checkpatch.pl
> issues in speakup driver.
>
> Arushi Singhal (2):
> staging: speakup: Moved OR operator to previous line.
> staging: speakup: spaces preferred around operator
You have
Hi,
I think it again.
The "cht_wcove_pwrsrc' is ok, if the register use the 'pwrsrc' word
and using the 'wcove' instead of 'wc'. It is not big matter.
I agree to use the 'cht_wcove_pwrsrc'.
Best Regards,
Chanwoo Choi
On 2017년 03월 21일 14:21, Chanwoo Choi wrote:
> On 2017년 03월 21일 12:54,
On 2017/3/20 23:08, James Morse wrote:
> Hi Dongjiu Geng,
>
> On 20/03/17 13:58, Marc Zyngier wrote:
>> On 20/03/17 12:28, gengdongjiu wrote:
>>> On 2017/3/20 19:24, Marc Zyngier wrote:
Please include James Morse on anything RAS related, as he's already
looking at related patches.
>
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 61f63e383784bd0ab6529cfc95ddc59c713afcc9:
>
> Merge tag
Commit-ID: f371594a514a4d3bc8fca6913ce9b5d9e325095d
Gitweb: http://git.kernel.org/tip/f371594a514a4d3bc8fca6913ce9b5d9e325095d
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 17 Mar 2017 11:23:21 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: b40e36121e23031f1e8916a70110ffc841230670
Gitweb: http://git.kernel.org/tip/b40e36121e23031f1e8916a70110ffc841230670
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 17 Mar 2017 11:16:02 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Hello,
On Mon, Mar 20, 2017 at 10:49:16AM -0700, Kees Cook wrote:
> On Fri, Mar 17, 2017 at 2:52 AM, Chris Wilson
> wrote:
> > In order to prevent a cyclic recursion between psi->read_mutex and the
> > inode_lock, we need to move the pse->erase to a worker.
> >
> > [
On 20.03.2017 04:05, Mike Galbraith wrote:
On Sun, 2017-03-19 at 17:02 +0100, Gerhard Wiesinger wrote:
mount | grep cgroup
Just because controllers are mounted doesn't mean they're populated. To
check that, you want to look for directories under the mount points
with a non-empty 'tasks'. You
If this frame contains IV/ICV fields, ether_type field located a little farther.
This bug already fixed here:
https://github.com/lwfinger/rtl8188eu/blob/master/core/rtw_recv.c#L569 .
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_recv.c | 2 +-
1 file
On Mon, 20 Mar 2017 14:51:31 +0100
Thierry Reding wrote:
> On Fri, Mar 17, 2017 at 10:17:47AM +0100, Ralph Sennhauser wrote:
> > On Thu, 16 Mar 2017 17:03:05 +0100
> > Linus Walleij wrote:
> [...]
> > > > +static void
On Mon, 20 Mar 2017 14:42:52 +0100
Thierry Reding wrote:
> > diff --git a/Documentation/devicetree/bindings/gpio/gpio-mvebu.txt
> > b/Documentation/devicetree/bindings/gpio/gpio-mvebu.txt index
> > a6f3bec..86932e3 100644 ---
> >
* Andrei Vagin wrote:
> Here is my bisect log:
> [avagin@laptop linux-next]$ git bisect log
> # bad: [f921b263d9602fb7873710c2df70671f2ffcf658] Add linux-next
> specific files for 20170320
> # good: [4495c08e84729385774601b5146d51d9e5849f81] Linux 4.11-rc2
> git bisect start
Commit-ID: 05a1f47ed47a83736aca117aeee96e926cc0dfd0
Gitweb: http://git.kernel.org/tip/05a1f47ed47a83736aca117aeee96e926cc0dfd0
Author: Alexander Shishkin
AuthorDate: Thu, 16 Mar 2017 18:41:59 +0200
Committer: Arnaldo Carvalho de Melo
Commit-ID: 38a33f07122f6e6194bf5402c0cd057d1cc50be8
Gitweb: http://git.kernel.org/tip/38a33f07122f6e6194bf5402c0cd057d1cc50be8
Author: Alexander Shishkin
AuthorDate: Thu, 16 Mar 2017 18:41:59 +0200
Committer: Arnaldo Carvalho de Melo
Commit-ID: b9835a90084bd3cc45d7ab80c37f282046bc13d3
Gitweb: http://git.kernel.org/tip/b9835a90084bd3cc45d7ab80c37f282046bc13d3
Author: Alexander Shishkin
AuthorDate: Thu, 16 Mar 2017 18:41:59 +0200
Committer: Arnaldo Carvalho de Melo
Subject: RE: [v4 3/3] mmc: sdhci-cadence: Update PHY delay configuration
In-reply-to:
Hi Manish,
(Added target-devel CC')
On Mon, 2017-03-20 at 15:05 +0530, Manish Narani wrote:
> This patch corrects the argument in usb_ep_free_request as it is
> mistakenly set to ep_out. It should be ep_in for status request.
>
> Signed-off-by: Manish Narani
> ---
>
speakup_allocate used GFP_ATOMIC for allocations
even while during initialization due to it's use
in notifier call.
Pass GFP_ flags as well to speakup_allocate depending
on the context it is called in.
Signed-off-by: Pranay Kr. Srivastava
---
drivers/staging/speakup/main.c |
Vendor specific infoframe is mandatory for 4K2K resolution.
Without this, the HDMI protocol compliance fails.
Signed-off-by: Nickey Yang
Reviewed-by: Jose Abreu
---
drivers/gpu/drm/bridge/dw-hdmi.c | 53
On Wed, Mar 15, 2017 at 12:01:08PM +0530, Pushkar Jambhlekar wrote:
> Fixing 'if' block coding style. '{' should follow 'if' for multiline block
>
> Signed-off-by: Pushkar Jambhlekar
> ---
> drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c | 3 +--
> 1 file
This patch removes the unnecessary allocation of
current foreground vc during initialization.
This initialization is already handled in the loop
that follows it for all available virtual consoles.
Signed-off-by: Pranay Kr. Srivastava
Reviewed-by: Samuel Thibault
On Tue, Mar 21, 2017 at 12:35 AM, Winkler, Tomas
wrote:
>
>>
>> On Mon, Mar 20, 2017 at 11:01:36PM +, Winkler, Tomas wrote:
>>
>> > I believe that in this case the #ifdefs can be done correctly quite
>> > easily, but now I'm not against your solution as well, just
On Thu, Mar 16, 2017 at 01:28:04AM +0800, Icenowy Zheng wrote:
> Many Allwinner SoCs after A31 have a CCU in PRCM block.
>
> Give the ones on H3 and A64 compatible strings.
>
> Signed-off-by: Icenowy Zheng
> ---
> Changes in v2:
> - Add iosc for R_CCU's on H3/A64. (A31, A23
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. With DbC
hardware initialized, the system will present a debug device
through the USB3 debug port (normally the first USB3 port).
The debug device is fully compliant with the USB framework
Add a simple udelay calibration in x86 architecture-specific
boot-time initializations. This will get a workable estimate
for loops_per_jiffy. Hence, udelay() could be used after this
initialization.
Cc: Ingo Molnar
Cc: x...@kernel.org
Signed-off-by: Lu Baolu
On 03/20/2017 10:30 PM, Alex Williamson wrote:
> On Mon, 20 Mar 2017 20:50:39 +0800
> Cao jin wrote:
>
>> Sorry for late.
>>
>> On 03/14/2017 06:06 AM, Alex Williamson wrote:
>>> On Mon, 27 Feb 2017 15:28:43 +0800
>>> Cao jin wrote:
>>>
Hi,
Baolin Wang writes:
>>> I don't yet understand why we can't just keep runtime pm disabled as a
>>> default for xhci platform devices.
>>> It could be enabled by whatever creates the platform device by setting some
>>> device property
>>> (or equivalent), which would
On Sun, Mar 19, 2017 at 01:07:17PM +1300, Derek Robson wrote:
> Fixed style of all block comments across whole driver
> Found by checkpatch
>
> Signed-off-by: Derek Robson
> ---
> drivers/staging/ks7010/ks7010_sdio.c | 3 ++-
> drivers/staging/ks7010/ks_hostif.h | 35
Fixed the checkpatch.pl issues like:
CHECK: spaces preferred around that '&' (ctx:VxV)
CHECK: spaces preferred around that '|' (ctx:VxV)
CHECK: spaces preferred around that '-' (ctx:VxV)
CHECK: spaces preferred around that '+' (ctx:VxV)
etc.
Signed-off-by: Arushi Singhal
Fixed coding style for null comparisons in speakup driver to be more
consistant with the rest of the kernel coding style.
Replaced 'x != NULL' with 'x' and 'x = NULL' with '!x'.
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/selection.c | 2 +-
Moved logical OR operator to previous line to fix the following
checkpatch issue:
CHECK: Logical continuations should be on the previous line.
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 8
1 file changed, 4 insertions(+), 4
This patch fixes the checks reported by checkpatch.pl
for braces {} should be used on all arms of this statement.
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 35 +++-
This patch fixes the checkpatch.pl warning "multiple assignments
should be avoided."
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/speakup/main.c
Hi Bjorn,
> compile-testing fails when QCOM_SMD is a loadable module:
>
> drivers/bluetooth/built-in.o: In function `btqcomsmd_send':
> btqca.c:(.text+0xa8): undefined reference to `qcom_smd_send'
> drivers/bluetooth/built-in.o: In function `btqcomsmd_probe':
> btqca.c:(.text+0x3ec): undefined
Hi,
Backported and successfully tested on currently stable Gentoo kernel 4.9.6-r1.
>From [1], gcc 4.9.4 was first problematic release.
[1] http://marc.info/?l=linux-ia64=147993347915422
Émeric
2017-03-19 17:20 GMT+01:00 Sergei Trofimovich :
> Starting from gcc-5.4+ gcc
Some functions like kmalloc/kzalloc return NULL on failure. When NULL
represents failure, !x is commonly used.
This was done using Coccinelle:
@@
expression *e;
identifier l1;
@@
e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...);
...
- e == NULL
+ !e
Signed-off-by: simran singhal
Some functions like kmalloc/kzalloc return NULL on failure. When NULL
represents failure, !x is commonly used.
@@
expression *e;
identifier l1;
@@
e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...);
...
- e == NULL
+ !e
Signed-off-by: simran singhal
---
--This is
Some functions like kmalloc/kzalloc return NULL on failure. When NULL
represents failure, !x is commonly used.
This was done using Coccinelle:
@@
expression *e;
identifier l1;
@@
e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...);
...
- e == NULL
+ !e
Signed-off-by: simran singhal
Some functions like kmalloc/kzalloc return NULL on failure. When NULL
represents failure, !x is commonly used.
This was done using Coccinelle:
@@
expression *e;
identifier l1;
@@
e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...);
...
- e == NULL
+ !e
Signed-off-by: simran singhal
Some functions like kmalloc/kzalloc return NULL on failure. When NULL
represents failure, !x is commonly used.
This was done using Coccinelle:
@@
expression *e;
identifier l1;
@@
e = \(kmalloc\|kzalloc\|kcalloc\|devm_kzalloc\)(...);
...
- e == NULL
+ !e
Signed-off-by: simran singhal
On 21.03.2017 05:18, Wanpeng Li wrote:
> From: Wanpeng Li
>
> This can be reproduced by running L2 on L1, and disable VPID on L0 if w/o
> commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2 crash as below:
>
> KVM: entry failed, hardware error 0x7
>
2017-03-21 16:50 GMT+08:00 David Hildenbrand :
> On 21.03.2017 05:18, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> This can be reproduced by running L2 on L1, and disable VPID on L0 if w/o
>> commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2
On 20 March 2017 at 22:46, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The way the schedutil governor uses the PELT metric causes it to
> underestimate the CPU utilization in some cases.
>
> That can be easily demonstrated by running
On Mon, Mar 20, 2017 at 9:45 PM, David Daney wrote:
> On 03/17/2017 07:13 AM, Ulf Hansson wrote:
>> My point is really that we should avoid exporting SoC specific APIs
>> which shall be called from drivers. This is old fashion.
>
>
> Some people find it objectionable to
2017-03-21 17:01 GMT+08:00 David Hildenbrand :
>
>> The same as cpu_has_vmx_ept_4levels().
>>
>>>
enable_vpid = 0;
+
>>>
>>> unrelated change
>>
>> To make the vpid codes more clear. Please refer to other callees in
>> hardware_setup().
>
> I was talking
On Tue, 21 Mar 2017, Arnd Bergmann wrote:
> On Mon, Mar 20, 2017 at 9:40 PM, Thomas Gleixner wrote:
> > On Mon, 20 Mar 2017, Deepa Dinamani wrote:
> >> >> -static int ptp_clock_getres(struct posix_clock *pc, struct timespec
> >> >> *tp)
> >> >> +static int
On 03/20/2017 11:07 PM, Florian Fainelli wrote:
>
> (snip)
>>
>> However, it is kind of sad that drivers are so inconsistent of what goes
>> in probe and what goes in ndo_open...which is tied together with the
>> whole mess of when certain ethtool commands work or do not work.
> Well, inconsistent
in_interrupt() semantics are confusing and wrong for most users
as it also returns true when bh is disabled. Thus we open coded
a proper check for interrupts in __sanitizer_cov_trace_pc()
with a lengthy explanatory comment.
Use the new in_task() predicate instead.
Signed-off-by: Dmitry Vyukov
On Sun, Mar 19, 2017 at 4:57 AM, Deepa Dinamani wrote:
> From: Deepa Dinamani
>
> struct timespec is not y2038 safe. The plan is to
> get rid of all uses of timespec internally in the
> kernel. Replace uses of timespec with timespec64.
> The
in_interrupt() also returns true when bh is disabled in task context.
That's not what fail_task() wants to check.
Use the new in_task() predicate that does the right thing.
Signed-off-by: Dmitry Vyukov
Cc: akinobu.m...@gmail.com
Cc: linux-kernel@vger.kernel.org
Cc: Andrew
On Tue, Mar 21, 2017 at 02:17:21PM +0530, Anup Patel wrote:
> On Tue, Mar 21, 2017 at 2:00 PM, Vinod Koul wrote:
> > On Mon, Mar 06, 2017 at 03:13:24PM +0530, Anup Patel wrote:
> >> The Broadcom SBA RAID is a stream-based device which provides
> >> RAID5/6 offload.
> >>
> >>
+ Joao
please Joao, could you do a check if new changes have any impact on that?
peppe
On 3/20/2017 8:54 PM, Corentin Labbe wrote:
Hello
Just pushed next-20170320 to my boards and stmmac stop working on both intree
dwmac-sunxi and my dev dwmac-sun8i.
It seems that interrupts never fire, and
On March 21, 2017 5:10 PM Dmitry Vyukov wrote:
>
> @@ -60,15 +60,8 @@ void notrace __sanitizer_cov_trace_pc(void)
> /*
>* We are interested in code coverage as a function of a syscall inputs,
>* so we ignore code executed in interrupts.
> - * The checks for whether we
On Mon, 20 Mar 2017 13:50:31 +0800
Xunlei Pang wrote:
> As Eric said,
> "what we need to do is move the variable vmcoreinfo_note out
> of the kernel's .bss section. And modify the code to regenerate
> and keep this information in something like the control page.
>
>
On Mon, Mar 20, 2017 at 08:33:42AM -0700, Tony Lindgren wrote:
> * Charles Keepax [170320 08:15]:
> > On Thu, Mar 16, 2017 at 05:36:30PM -0700, Tony Lindgren wrote:
> > > At least Motorola CPCAP PMIC needs it's device interrupts re-read
> > > until there are
On Tue, Mar 21, 2017 at 12:03:50PM +0530, Arushi Singhal wrote:
>
>
> On Tue, Mar 21, 2017 at 11:41 AM, Greg KH wrote:
>
> On Sun, Mar 19, 2017 at 06:44:53PM +0530, Arushi Singhal wrote:
> > Improve readability by fixing multiple checkpatch.pl
> > issues
Commit-ID: f2ba3ee08eb9af666c6f948ccbb866ae6d3c9107
Gitweb: http://git.kernel.org/tip/f2ba3ee08eb9af666c6f948ccbb866ae6d3c9107
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 15 Mar 2017 17:40:19 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
* Thomas Garnier wrote:
> This patch removes fixmap headers on non-x86 code introduced by the
> adaptable MODULE_END change. It is also removed in the 32-bit pgtable
> header. Instead, it is added by default in the pgtable generic header
> for both architectures.
>
>
Changelog from v2:
Fixed the message subject line.
Changelog from v1:
1. fixed kbuild warning for i386 build as reported by kbuild robot
2. split initialization code in two patches.
Pranay Kr. Srivastava (3):
return same error value from spk_set_key_info
remove
Hi Elena,
On Mon, 2017-03-06 at 16:21 +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
>
Hi Mathias,
On 21 February 2017 at 10:09, Baolin Wang wrote:
>> Do you have any comments about this patch? Thanks.
>>
>>>drivers/usb/host/xhci-plat.c | 41
>>> -
>>>1 file changed, 36 insertions(+), 5
When cpudl_find() returns any among free_cpus, the cpu might not be
closer than others, considering sched domain. For example:
this_cpu: 15
free_cpus: 0, 1,..., 14 (== later_mask)
best_cpu: 0
topology:
0 --+
+--+
1 --+ |
+-- ... --+
2 --+ | |
Hi Heiko:
Is there any advice about the big dtsi?
I would like to send next version , thanks.
在 2017年03月17日 16:45, Heiko Stuebner 写道:
Am Freitag, 17. März 2017, 10:26:13 CET schrieb 陈亮:
在 2017年03月17日 00:18, Andre Przywara 写道:
Hi Chen,
On 16/03/17 01:45, c...@rock-chips.com
Hi Rob,
On Mon, Mar 20, 2017 at 6:00 PM, Rob Herring wrote:
> On Mon, Mar 20, 2017 at 10:27 AM, Geert Uytterhoeven
> wrote:
>> On Mon, Mar 20, 2017 at 4:15 PM, Rob Herring wrote:
>>> On Fri, Mar 10, 2017 at 03:15:20PM +0100, Geert
Hi Masahiro,
> Hi Piotr,
>
> 2017-03-20 17:47 GMT+09:00 Piotr Sroka :
> >
> >>
> >> > @@ -227,6 +267,7 @@ static int sdhci_cdns_probe(struct platform_device
> >> > *pdev)
> >> > struct sdhci_cdns_priv *priv;
> >> > struct clk *clk;
> >> > int ret;
>
This patch fixes the checkpatch.pl warning "multiple assignments
should be avoided."
Signed-off-by: Arushi Singhal
---
drivers/staging/speakup/main.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git
101 - 200 of 1866 matches
Mail list logo