FYI, we noticed that blogbench.write_score +6.5% improvement on
https://github.com/0day-ci/linux
Rik-van-Riel/cpuidle-use-predicted_us-not-interactivity_req-to-consider-polling/20160312-043358
commit 256126a34c2a087a2a9900c2c7ac9a7c4f5e54e4 ("SKL BOOT FAILURE unless
idle=nomwait (was Re: PROBLEM
On 14/03/16 12:01, Eddie Huang wrote:
Hi,
Mediatek PMIC chip have some spare registers used to store information.
The value of these registers will exist until user unplug battery or
battery depletion. One of our usage example is store battery utilization
in these spare registers. We want to i
rom the rdma tree.
>
> Its a bit of a pain finding these conflicts now - it would have been
> better a few weeks ago.
>
> For now, all I can do is to use the rdma tree from next-20160315 for
> today.
>
> Herbert, any hints for Doug, Faisal?
crypto_hash is obsolete. You s
On Mon, Mar 07, 2016 at 12:24:18PM +0100, Thierry Reding wrote:
> On Fri, Mar 04, 2016 at 10:31:45PM -0600, Rob Herring wrote:
> > On Fri, Mar 04, 2016 at 05:19:31PM +0100, Thierry Reding wrote:
> > > From: Thierry Reding
> > >
> > > The NVIDIA Tegra XUSB pad controller provides a set of pads, ea
On Fri, Mar 04, 2016 at 05:19:37PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Extend the Tegra XUSB controller device tree binding with Tegra210
> support.
>
> Signed-off-by: Thierry Reding
> ---
> .../devicetree/bindings/usb/nvidia,tegra124-xusb.txt | 12
>
>
> -Original Message-
> From: Wangweidong (Dan)
> Sent: Tuesday, March 15, 2016 9:25 PM
> To: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> linux-kernel@vger.kernel.org; torva...@linux-foundation.org
> Cc: Fengtiantian; Liuyongan; Wangweidong (Dan)
> Subject: [Ask
On Wed, Mar 16, 2016 at 04:49:00PM +1100, Alexey Kardashevskiy wrote:
> On 03/16/2016 04:10 PM, Eli Cohen wrote:
> >On Wed, Mar 16, 2016 at 01:07:58PM +1100, Alexey Kardashevskiy wrote:
> >>
> >>So with v4.5 as a host, there is no actual distro available today to
> >>use as a guest in the next 6 mo
Hi all,
Please do not add any v4.7 related material to your linux-next included
trees until after v4.6-rc1 is released.
Changes since 20160315:
The kbuild tree gained a build failure for which I reverted a commit.
The rdma tree gained conflicts against the net-next tree and also build
failures
Hi Dmitry, Arnd,
Do you have any comments on this patch set [PATCH v4 0/3] ?
Thanks,
Raveendra
On Sat, Feb 27, 2016 at 12:29 PM, Raveendra Padasalagi
wrote:
> This patchset is based on v4.5-rc3 tag and its tested on
> Broadcom Cygnus SoC.
>
> The patches can be fetched from iproc-tsc-v4 branch
Hi,
On 03/16/2016 12:22 AM, Paolo Bonzini wrote:
Why is this necessary? The APIC access page is a peculiarity of Intel
>>processors (and the special memslot for only needs to map 0xfee0 to
>>0xfee00fff; after that there is the MSI area).
>
>The current lapic regs page is allocated using ge
Hi Vinod,
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Wednesday, March 16, 2016 8:47 AM
> To: Appana Durga Kedareswara Rao
> Cc: dan.j.willi...@intel.com; Michal Simek; Soren Brinkmann; Appana Durga
> Kedareswara Rao; moritz.fisc...@ettus.com;
> laurent.pi
Add myself as a co-maintainer for ti-soc-thermal
Signed-off-by: Keerthy
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 57adf39..480ed29 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10876,6 +10876,7 @@ F: drivers/platform/x86/thinkpad_ac
Hi Vinod,
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Wednesday, March 16, 2016 8:41 AM
> To: Moritz Fischer
> Cc: Appana Durga Kedareswara Rao; Dan Williams; Michal Simek; Soren
> Brinkmann; Appana Durga Kedareswara Rao; Laurent Pinchart; Luis de
> Bethen
Hi Vinod,
> -Original Message-
> From: dmaengine-ow...@vger.kernel.org [mailto:dmaengine-
> ow...@vger.kernel.org] On Behalf Of Vinod Koul
> Sent: Wednesday, March 16, 2016 8:44 AM
> To: Appana Durga Kedareswara Rao
> Cc: dan.j.willi...@intel.com; Michal Simek; Soren Brinkmann; Appana Durg
Hi Moritz,
> -Original Message-
> From: Moritz Fischer [mailto:moritz.fisc...@ettus.com]
> Sent: Wednesday, March 16, 2016 7:00 AM
> To: Appana Durga Kedareswara Rao
> Cc: Dan Williams; Vinod Koul; Michal Simek; Soren Brinkmann; Appana Durga
> Kedareswara Rao; Laurent Pinchart; Luis de Be
Hi Moritz,
> -Original Message-
> From: Moritz Fischer [mailto:moritz.fisc...@ettus.com]
> Sent: Wednesday, March 16, 2016 7:04 AM
> To: Appana Durga Kedareswara Rao
> Cc: Dan Williams; Vinod Koul; Michal Simek; Soren Brinkmann; Appana Durga
> Kedareswara Rao; Laurent Pinchart; Luis de Be
Hi Matt,
> -Original Message-
> From: Matt Fleming [mailto:m...@codeblueprint.co.uk]
> Sent: Tuesday, March 15, 2016 4:01 AM
> To: Chen, Yu C
> Cc: linux-a...@vger.kernel.org; linux...@vger.kernel.org; Rafael J. Wysocki;
> Len Brown; Thomas Gleixner; Ingo Molnar; H. Peter Anvin; Zhang, Rui
On 2016年03月16日 03:49, Eduardo Valentin wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 15, 2016 at 05:12:12PM +0800, Wei Ni wrote:
>>
>>
>> On 2016年03月15日 03:16, Eduardo Valentin wrote:
Old Signed by an unknown key
>>>
>>> On Fri, Mar 11, 2016 at 11:11:12AM +0800, Wei Ni wrote:
On 03/16/2016 04:10 PM, Eli Cohen wrote:
On Wed, Mar 16, 2016 at 01:07:58PM +1100, Alexey Kardashevskiy wrote:
So with v4.5 as a host, there is no actual distro available today to
use as a guest in the next 6 months (or whatever it takes to
backport this partucular patch back there).
You could
On 15/03/2016:06:47:52 PM, James Morse wrote:
> Hi David,
>
> On 09/03/16 05:32, David Long wrote:
> > From: "David A. Long"
> > diff --git a/arch/arm64/lib/copy_from_user.S
> > b/arch/arm64/lib/copy_from_user.S
> > index 4699cd7..0ac2131 100644
> > --- a/arch/arm64/lib/copy_from_user.S
> > +++
On Fri, Mar 11, 2016 at 11:34:40AM +0300, Vladimir Davydov wrote:
> On Thu, Mar 10, 2016 at 03:50:13PM -0500, Johannes Weiner wrote:
> > When setting memory.high below usage, nothing happens until the next
> > charge comes along, and then it will only reclaim its own charge and
> > not the now pote
> From: Wang Hongcheng [mailto:annie.w...@amd.com]
> Sent: Friday, March 11, 2016 5:28 PM
> To: Rafael J. Wysocki; Len Brown; linux-a...@vger.kernel.org; linux-
> ker...@vger.kernel.org; SPG_Linux_Kernel
> Cc: Wang, Annie
> Subject: [PATCH V2] ACPI: APD: Add device HID for future AMD UART
> control
On Tue, Mar 15, 2016 at 11:07:38PM +0900, Sergey Senozhatsky wrote:
>
> something like this (*minimally tested so far*).
>
> -- move wake_up() and friends under the logbuf section; so we can detect
^^
On Wed, Mar 16, 2016 at 01:07:58PM +1100, Alexey Kardashevskiy wrote:
>
> So with v4.5 as a host, there is no actual distro available today to
> use as a guest in the next 6 months (or whatever it takes to
> backport this partucular patch back there).
>
> You could have added a module parameter t
> From: Wang Hongcheng [mailto:annie.w...@amd.com]
> Sent: Friday, March 11, 2016 10:59 AM
> To: Linus Walleij; linux-g...@vger.kernel.org; linux-kernel@vger.kernel.org;
> SPG_Linux_Kernel
> Cc: Wang, Annie
> Subject: [PATCH] pinctrl: amd:Add device HID for future AMD GPIO controller
>
> Add devic
On Fri, Mar 11, 2016 at 12:19:31PM +0300, Vladimir Davydov wrote:
> On Fri, Mar 11, 2016 at 09:18:25AM +0100, Michal Hocko wrote:
> > On Thu 10-03-16 15:50:14, Johannes Weiner wrote:
> ...
> > > @@ -5037,9 +5040,36 @@ static ssize_t memory_max_write(struct
> > > kernfs_open_file *of,
> > > if (e
On Tue, 2016-03-15 at 16:12 -0700, James Bottomley wrote:
> On Tue, 2016-03-15 at 15:39 -0700, Ming Lin wrote:
> > From: Ming Lin
> >
> > Hi list,
> >
> > This moves the mempool based chained scatterlist alloc/free code
> > from
> > scsi_lib.c to lib/scatterlist.c.
> >
> > So other drivers(for
On Tue, Mar 15, 2016 at 10:35 PM, Nishanth Menon wrote:
> On Tue, Mar 15, 2016 at 12:31 AM, Jassi Brar wrote:
>> On Tue, Mar 8, 2016 at 8:07 PM, Nishanth Menon wrote:
>>> Jassi,
>>>
>>> On Tue, Mar 8, 2016 at 1:10 AM, Jassi Brar wrote:
On Tue, Mar 8, 2016 at 2:18 AM, Nishanth Menon wrote:
On Mon, Mar 14, 2016 at 3:24 AM, Jacek Anaszewski
wrote:
>
> New LED class driver:
>
> - Add driver for the ISSI IS31FL32xx family of LED controllers.
Grr. This has apparently not gotten with the program, and causes a few
annoying warnings:
drivers/leds/leds-is31fl32xx.c: In function ‘is31fl32xx
On Tue, Mar 15, 2016 at 12:51 AM, Jacek Anaszewski
wrote:
>
> I just wanted to make sure that no unexpected problem has occurred
> after rebasing onto 4.5 release. Is it in some way more advantageous to
> base a pull request on rc7, than on a final release?
I'd rather see the pull request based o
On 03/15/2016 10:46 PM, David Lechner wrote:
On 03/15/2016 05:45 PM, Sergei Shtylyov wrote:
No, this register is shared b/w MUSB and OHCI. The proper thing to
do is to write the PHY driver and let it control this shared register.
OK. I've started working on this. I am looking at using st
>
> The following series adds the ability for a hypervisor to set an MTU on the
> guest during feature negotiation phase. This is useful for VM orchestration
> when, for instance, tunneling is involved and the MTU of the various systems
> should be homogenous.
>
> The first patch adds the featur
On 03/15/2016 12:24 AM, Arnd Bergmann wrote:
> gcc-6 warns about code in the nouveau driver that is obviously silly:
>
> drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c: In function
> 'nv40_perfctr_next':
> drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c:62:19: warning: self-comparison
> always eval
On 09-03-16, 14:13, Rafael J. Wysocki wrote:
> On Wed, Mar 9, 2016 at 10:41 AM, Viresh Kumar wrote:
> > On 03-03-16, 18:29, Rafael J. Wysocki wrote:
> >> Srinivas, can you please take this and rebase your patch on top of it?
> >> Or if you prefer, I can take it into my linux-next branch.
> >
> >
On 16-03-16, 01:51, Rafael J. Wysocki wrote:
> OK, so the problem with doing that in syscore ops is that the I2C bus
> needed for it may not be available at that point, which is fair
> enough.
Not just that. We wouldn't call syscore-ops for the boot-cpu. It never went
away.
> Still, though, the w
Hi Al Stone,
On Wed, Mar 16, 2016 at 1:58 AM, Al Stone wrote:
> The ACPI 6.1 specification was recently released at the end of January 2016,
> but the arm64 kernel documentation for the use of ACPI was written for the
> 5.1 version of the spec. There were significant additions to the spec that
>
On 15-03-16, 13:11, Rafael J. Wysocki wrote:
> On Tue, Mar 15, 2016 at 7:10 AM, Viresh Kumar wrote:
> > On 12-03-16, 03:05, Rafael J. Wysocki wrote:
> >> From: Rafael J. Wysocki
> >>
> >> cpufreq_resume() attempts to resync the current frequency with
> >> policy->cur for the first online CPU, but
Hello,
On 2016-03-10 12:31, Evgenii Lepikhin wrote:
> We need help to understand the source of the problem and may be to create a
> bugreport. Here is crash report:
>
> Mar 10 04:03:51 l28 kernel: [2075560.434445] BUG: unable to handle kernel
> paging request at 40008021
> Mar 10 04:03:
Hi Sinan,
On 03/13/2016 06:25 PM, Sinan Kaya wrote:
> On 3/11/2016 11:54 AM, Sinan Kaya wrote:
>> The code was allowing platform devices to be used without a supporting VFIO
>> reset driver. The hardware can be left in some inconsistent state after a
>> guest machine abort.
>>
>> The reset driver w
On Tue, Mar 15, 2016 at 9:17 PM, Al Viro wrote:
>
> Take a look at drivers/staging/rdma/hfi1/file_ops.c in -next and
> compare hfi1_write_iter() with hfi1_file_write(). Folks, this ABI is too
> ugly to live, let alone to be allowed breeding.
>
> It's also brittle as hell - trivial
Folks, we'd discussed that kind of crap already; why, in name of
everything unholy, is that kind of garbage brought back in a new driver?
Having both ->write() and ->write_iter() *AND* having entirely
unrelated interpretation of user input on those two on the same device
is bogus,
On Tue, Mar 15, 2016 at 08:08:09PM -0700, Guenter Roeck wrote:
> On 03/14/2016 10:52 AM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.10.101 release.
> >There are 18 patches in this series, all will be posted as a response
> >to this one. If anyone has any is
Hi Mike,
On 03/15/2016 03:06 PM, Michael Turquette wrote:
>>> > > void cpufreq_set_freq_update_hook(int cpu, struct freq_update_hook
>>> > > *hook,
>>> > > + void (*func)(struct freq_update_hook *hook,
>>> > > + enum sched_class_util sched_cla
On 03/16/2016 03:32 AM, Paolo Bonzini wrote:
On 15/03/2016 19:27, Andy Lutomirski wrote:
On Mon, Mar 14, 2016 at 6:17 AM, Paolo Bonzini wrote:
On 11/03/2016 22:33, David Matlack wrote:
Is this better than just always keeping the host's XCR0 loaded outside
if the KVM interrupts-disabled
On Tue, Mar 15, 2016 at 8:43 PM, Xiao Guangrong
wrote:
>
>
> On 03/16/2016 03:01 AM, David Matlack wrote:
>>
>> On Mon, Mar 14, 2016 at 12:46 AM, Xiao Guangrong
>> wrote:
>>>
>>>
>>>
>>> On 03/12/2016 04:47 AM, David Matlack wrote:
>>>
I have not been able to trigger this bug on Linux 4.3, a
On 2016年03月16日 03:56, Eduardo Valentin wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 15, 2016 at 02:21:53PM +0800, Wei Ni wrote:
>>
>>
>> On 2016年03月15日 04:05, Eduardo Valentin wrote:
Old Signed by an unknown key
>>>
>>> On Fri, Mar 11, 2016 at 11:09:14AM +0800, Wei Ni wrote:
On 03/15/2016 05:45 PM, Sergei Shtylyov wrote:
No, this register is shared b/w MUSB and OHCI. The proper thing to
do is to write the PHY driver and let it control this shared register.
OK. I've started working on this. I am looking at using struct usb_phy,
however, enum usb_phy_type only
On 03/16/2016 03:01 AM, David Matlack wrote:
On Mon, Mar 14, 2016 at 12:46 AM, Xiao Guangrong
wrote:
On 03/12/2016 04:47 AM, David Matlack wrote:
I have not been able to trigger this bug on Linux 4.3, and suspect
it is due to this commit from Linux 4.2:
653f52c kvm,x86: load guest FPU co
On Tue, Mar 15, 2016 at 2:14 AM, Christoph Hellwig wrote:
> On Fri, Mar 11, 2016 at 02:05:16PM -0600, Steve French wrote:
>> A loosely related question is what can be done for tools around existing
>> interfaces for ACLs. I recently found out NTFS-3g has this xattr:
>>
>> static const char nf
For those wrapper drivers which only implement Programmed IO, have
NCR5380_dma_xfer_len() evaluate to zero. That allows PDMA to be easily
disabled at run-time and so the PSEUDO_DMA macro is no longer needed.
Also remove the spin counters used for debugging pseudo DMA drivers.
Signed-off-by: Finn
For the NCR5380.c core driver, these macros are never used.
If REAL_DMA were to be defined, compilation would fail.
For the atari_NCR5380.c core driver, REAL_DMA is always defined.
Hence these macros are pointless.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR53
This change brings a number of improvements: fewer macros, better test
coverage, simpler code and sane Kconfig options. The downside is a small
chance of incompatibility (which seems unavoidable).
CONFIG_SCSI_GENERIC_NCR53C400 exists to enable or inhibit pseudo DMA
transfers when the driver is use
The only chip that needs the workarounds enabled is an early NMOS
device. That means that the common case is to disable them.
Unfortunately the sense of the flag is such that it has to be set
for the common case.
Rename the flag so that zero can be used to mean "no errata workarounds
needed". Thi
On 03/15/2016 03:37 PM, Michael Turquette wrote:
Yuck sysfs.. I would really rather we did not expose this per default.
> > > And certainly not in this weird form.
>>> > >
>>> > > I'm happy to change capacity_margin to up_threshold and use a
>>> > > percentage.
>>> > >
>>> > > The sysfs
Adopt the DMA implementation from atari_NCR5380.c. This means that
atari_scsi and sun3_scsi can make use of the NCR5380.c core driver
and the atari_NCR5380.c driver fork can be made redundant.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR5380.c | 170 +++
Those wrapper drivers which use DMA define the REAL_DMA macro and
those which use pseudo DMA define PSEUDO_DMA. These macros need to be
removed for a number of reasons, not least of which is to have drivers
share more code.
Redefine the PDMA send and receive hooks as DMA setup hooks, so that the
D
Add support for the custom Sun 3 DMA logic to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
The Sun 3 DMA code is still configured by macros. I have simplified things
slightly but I have avoided more ambitious re
The io_recovery_delay macro is intended to insert a microsecond delay
between the chip register accesses that begin a DMA operation. This
is reportedly needed for some ISA boards.
Reverse the sense of the macro test so that in the common case,
where no delay is required, drivers need not define th
Add support for the Atari ST DMA chip to the NCR5380.c core driver.
This code is copied from atari_NCR5380.c.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR5380.c| 32
drivers/scsi/atari_scsi.c |6 +++---
2 files changed,
Standardize the DMA setup hooks so that the DMA implementation in
atari_NCR5380.c can be reconciled with pseudo DMA implementation in
NCR5380.c.
Calls to NCR5380_dma_recv_setup() and NCR5380_dma_send_setup() return
a negative value on failure, zero on PDMA transfer success and a positive
byte coun
Fix various issues: Comments about bus errors are incorrect. The
PDMA asm must return the size of the memory access that faulted so the
transfer count can be adjusted accordingly. A phase change may cause a
bus error but should not be treated as failure. A bus error does not
always imply a phase ch
The driver has a limit of eight LUs because of the byte-sized bitfield
that is used for busy flags. That means the maximum LUN is 7. The default
is 8.
Signed-off-by: Finn Thain
---
Changed since v1:
- Reduce shost->max_lun limit instead of adding 'MAX_LUN' limit.
---
drivers/scsi/NCR5380.c |
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR5380.c | 12 +---
drivers/scsi/NCR5380.h |4
drivers/scsi/arm/oak.c |2 --
drivers/scsi/dmx3191d.c |2 --
drivers/scsi/dtc.c | 12 +++-
drivers/scsi/g_NCR5380.c |2 --
Now that atari_scsi and sun3_scsi have been converted to use the NCR5380.c
core driver, remove atari_NCR5380.c. Also remove the last vestiges of its
Tagged Command Queueing implementation from the wrapper drivers.
The TCQ support in atari_NCR5380.c is abandoned by this patch. It is not
merged into
Only the atari_scsi and sun3_scsi drivers define DMA_MIN_SIZE.
Both drivers also define NCR5380_dma_xfer_len, which means
DMA_MIN_SIZE can be removed from the core driver.
This removes another discrepancy between the two core drivers.
Signed-off-by: Finn Thain
---
Changes since v1:
- Retain MI
This patch series has more macro elimination and some tweaks to the
DMA hooks so that all the wrapper drivers can share the same core
DMA algorithm. This resolves the major discrepancies between the two
core drivers, which relate to code conditional on the REAL_DMA and
PSEUDO_DMA macros.
After al
This setting does not need to be conditional on Atari ST or TT.
Signed-off-by: Finn Thain
---
Changed since v1:
- Set the default cmd_per_lun to 4 based on test results.
---
drivers/scsi/atari_scsi.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: linux/drivers/scsi/atari_s
The benefit of limiting can_queue to 1 is that atari_scsi shares the
ST DMA chip more fairly with other drivers (e.g. falcon-ide).
Unfortunately, this can limit SCSI bus utilization. On systems without
IDE, atari_scsi should issue SCSI commands whenever it can arbitrate for
the bus. Make that poss
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR5380.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index: linux/drivers/scsi/NCR5380.c
===
--- linux.orig/drivers/scsi/NCR5380.c 2016-
The dmx3191d driver is not capable of DMA or PDMA so all transfers
use PIO. Now that large slow PIO transfers periodically stop and call
cond_resched(), the max_sectors limit can go away.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/dmx3191d.c |1 -
1 file change
Decode all bits in the chip registers. They are all useful at times.
Fix printk severity so that this output can be suppressed along with
the other debugging output.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
drivers/scsi/NCR5380.c | 42 +--
Update kernel parameter documentation for atari_scsi, mac_scsi and
g_NCR5380 drivers. Remove duplication.
Signed-off-by: Finn Thain
Reviewed-by: Hannes Reinecke
---
Documentation/scsi/g_NCR5380.txt | 17 ++-
Documentation/scsi/scsi-parameters.txt | 11 +++---
drivers/
Drivers that define PSEUDO_DMA also define NCR5380_dma_xfer_len.
The core driver must call NCR5380_dma_xfer_len which means
FLAG_NO_PSEUDO_DMA can be eradicated from the core driver.
dmx3191d doesn't define PSEUDO_DMA and has no use for FLAG_NO_PSEUDO_DMA,
so remove it there also.
Signed-off-by:
On Tue, Mar 15, 2016 at 3:17 PM, Volker Lendecke
wrote:
> On Tue, Mar 15, 2016 at 08:45:14AM -0700, Jeremy Allison wrote:
>> On Tue, Mar 15, 2016 at 12:11:03AM -0700, Christoph Hellwig wrote:
>> > People have long learned that we only have 'alloc' permissions. Any
>> > model that mixes allow and
On Mon, Mar 14, 2016 at 12:46:41PM +0100, Maxime Ripard wrote:
> On Fri, Mar 11, 2016 at 04:48:26PM +0530, Vinod Koul wrote:
> > > > But this nees to be property for clients and not driver. Client can then
> > > > program these
> > >
> > > Yes, totally. The question here is how the clients give th
+ Jim and Jani from gfx team.
Thanks
Mengdong
> -Original Message-
> From: Lin, Mengdong
> Sent: Wednesday, March 16, 2016 12:11 AM
> To: Takashi Iwai
> Cc: Yang, Libin; kernel test robot; l...@01.org; LKML; Wu, Fengguang
> Subject: RE: [lkp] [ALSA] ca53fbf3a6: WARNING: CPU: 0 PID: 151 at
On Tue, Mar 15, 2016 at 10:53:09PM +0530, Kedareswara rao Appana wrote:
> This patch updates the device-tree binding doc for
> adding support for AXI DMA.
Binding patch should precced the driver. and the title doesn't tell me its a
binding patch and might get ignore by folks.
Pls cc device tree M
On Tue, Mar 15, 2016 at 10:53:07PM +0530, Kedareswara rao Appana wrote:
> This patch adds quirks support in the driver to differentiate differnet IP
> cores.
Wouldn't it help to explain why quirks are needed for these cores in
changelog?
Also limit your changelogs properly. Am sure checkpatch wo
On 03/14/2016 10:52 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.101 release.
There are 18 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Hi Greg,
The proj
On Tue, Mar 15, 2016 at 06:29:38PM -0700, Moritz Fischer wrote:
> Hi,
>
> On Tue, Mar 15, 2016 at 10:23 AM, Kedareswara rao Appana
> wrote:
> > This patch series does some enhancments to the VDMA driver
> > which includes
> > --> Adding support for AXI DMA IP.
> > --> Adding support for AXI CDMA
From: Robert Jarzmik
Date: Tue, 15 Mar 2016 23:56:58 +0100
> Robert Jarzmik writes:
>
>> Fabio Estevam writes:
>>> Tested-by: Fabio Estevam
>>
>> Thanks Fabio for the test.
>>
>> I also tried with a different different approach.
>>
>> I built the different platforms (imx v6, etc ...) :
>> -
On 03/13/2016 10:22 PM, Michael Turquette wrote:
> +unsigned long cfs_capacity_margin = CAPACITY_MARGIN_DEFAULT;
> +
> #ifdef CONFIG_CFS_BANDWIDTH
> /*
> * Amount of runtime to allocate from global (tg) to local (per-cfs_rq) pool
> @@ -2840,6 +2853,8 @@ static inline void update_load_avg(struct
On Tue, Mar 15, 2016 at 7:25 PM, Paul Gortmaker
wrote:
> On Tue, Mar 15, 2016 at 5:45 PM, Paul Gortmaker
> wrote:
>> On Mon, Mar 14, 2016 at 11:49 AM, Steven Rostedt wrote:
>>>
>>> Dear RT Folks,
>>>
>>> 3.14 release on PI(E) Day!
>>>
>>> I'm pleased to announce the 3.14.64-rt67 stable release.
On (03/16/16 11:10), Byungchul Park wrote:
> > > What about this?
> > >
> > > int need_flush_console;
> > >
> > > while(1) {
> > > set_current_state(TASK_INTERRUPTIBLE);
> > > if (!need_flush_console)
> > > schedule();
>
> else // This shou
On Wed, Mar 16, 2016 at 11:01:15AM +0900, Sergey Senozhatsky wrote:
> Hello Petr,
>
> On (03/15/16 16:58), Petr Mladek wrote:
> [..]
> > > +static bool __read_mostly printk_sync = !IS_ENABLED(CONFIG_SMP);
> > > +module_param_named(synchronous, printk_sync, bool, S_IRUGO | S_IWUSR);
> >
> > If we
On 03/15/2016 09:40 PM, Or Gerlitz wrote:
On Tue, Mar 15, 2016 at 12:19 PM, Alexey Kardashevskiy wrote:
This reverts commit 85743f1eb34548ba4b056d2f184a3d107a3b8917.
Without this revert, POWER "pseries" KVM guests with a VF passed to a guest
using VFIO fail to bring the driver up:
mlx4_core:
On Tue, Mar 15, 2016 at 11:09 PM, Ming Lei wrote:
> Hi,
>
> On Mon, Mar 14, 2016 at 8:00 PM, wrote:
>> Hello,
>>
>> I see possible race in _request_firmware_load function, on which I wanted to
>> take your opinion.
>>
>> When system is going to low power mode, device_cache_fw_images() is called
On Mon, Mar 14, 2016 at 01:17:48PM +0900, Byungchul Park wrote:
> On Mon, Mar 14, 2016 at 11:40:55AM +0900, Sergey Senozhatsky wrote:
> > Hi,
> >
> > On (03/14/16 11:30), Byungchul Park wrote:
> > [..]
> > > > so can it be
> > > >
> > > > vprintk_emit()
> > > > __spin_dump_deferred()
> > > > v
Hello Petr,
On (03/15/16 16:58), Petr Mladek wrote:
[..]
> > +static bool __read_mostly printk_sync = !IS_ENABLED(CONFIG_SMP);
> > +module_param_named(synchronous, printk_sync, bool, S_IRUGO | S_IWUSR);
>
> If we make it writtable, we also need to handle the situation that
> it gets disabled at r
On 2016/3/15 23:37, Catalin Marinas wrote:
> On Tue, Mar 15, 2016 at 10:12:11AM +0800, Zhen Lei wrote:
>> 1. In swiotlb_alloc_coherent, the branch of __get_free_pages. Directly
>>return vaddr on success, and pass vaddr to free_pages on failure.
>> 2. So, we can directly transparent pass vaddr
On Tue, Mar 15, 2016 at 06:52:24PM -0400, Theodore Ts'o wrote:
> On Wed, Mar 16, 2016 at 09:33:13AM +1100, Dave Chinner wrote:
> >
> > Stale data escaping containment is a security issue. Enabling
> > generic kernel mechanisms to *enable containment escape* is
> > fundamentally wrong, and relying
On 03/16/2016 02:29 AM, Christoph Hellwig wrote:
On Tue, Mar 15, 2016 at 04:23:33PM +0200, Or Gerlitz wrote:
Let us check. I was under (the maybe wrong) impression, that before this
patch both PF/VF drivers were not operative on some systems, so on those
systems it's fair to require the VF drive
On Fri, Mar 11, 2016 at 03:13:52PM -0700, Toshi Kani wrote:
> Hi Ingo,
>
> My apology for the delay...
>
> On Wed, 2016-03-09 at 10:15 +0100, Ingo Molnar wrote:
> > * Toshi Kani wrote:
> >
> > > On Tue, 2016-03-08 at 13:16 +0100, Ingo Molnar wrote:
> > > > * Toshi Kani wrote:
> > > >
> > > >
Hi there,
On Tue, Mar 15, 2016 at 10:23 AM, Kedareswara rao Appana
wrote:
> AXI DMA support is added to the existing AXI VDMA driver.
> The binding doc for AXI DMA should also be updated in the
> VDMA device-tree binding doc.
>
> Signed-off-by: Kedareswara rao Appana
> ---
> .../devicetree/bind
Hi,
On Tue, Mar 15, 2016 at 10:23 AM, Kedareswara rao Appana
wrote:
> This patch series does some enhancments to the VDMA driver
> which includes
> --> Adding support for AXI DMA IP.
> --> Adding support for AXI CDMA IP.
> --> Fixing checkpatch warnings.
>
> Kedareswara rao Appana (7):
> dmaeng
> > > > > > I'm just catching back up on this thread; so without
> > > > > > reference to any particular previous mail in the thread.
> > > > > >
> > > > > > 1) How many of the free pages do we tell the host about?
> > > > > > Your main change is telling the host about all the
> > > > > >
adb3a94 ("i40iw: add puda code")
4e9042e647ff ("i40iw: add hw and utils files")
(at least) from the rdma tree.
Its a bit of a pain finding these conflicts now - it would have been
better a few weeks ago.
For now, all I can do is to use the rdma tree from next-20160315 fo
On 03/09, Stefan Agner wrote:
> Signed-off-by: Stefan Agner
> ---
Acked-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Hi Guenter,
On Tue, Mar 15, 2016 at 2:24 AM, Guenter Roeck wrote:
> Hi Alexey,
>
>
> On 03/14/2016 06:02 PM, Alexey Klimov wrote:
>>
>> Hi Guenter,
>>
>> On Thu, Mar 10, 2016 at 3:54 AM, Guenter Roeck wrote:
>>>
>>> On 03/09/2016 06:29 PM, Alexey Klimov wrote:
This patch creates n
Hi all,
Today's linux-next merge of the rdma tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c
between commit:
60ab4584f5bf ("net/mlx5_core: Set flow steering dest only for forward rules")
from the net-next tree and commit:
b3638e1a7664 ("net/mlx5_core: Introduce
1 - 100 of 732 matches
Mail list logo
