On Wed, Apr 6, 2016 at 4:32 AM, Greg Ungerer wrote:
> From: Greg Ungerer
>
> The ColdFire architecture specific gpio support code registers a sysfs
> bus device named "gpio". This clashes with the new generic API device
> added in commit 3c702e99 ("gpio: add a userspace chardev ABI for GPIOs").
* Hugh Dickins wrote:
> --- a/arch/x86/include/asm/pgtable.h
> +++ b/arch/x86/include/asm/pgtable.h
> @@ -181,6 +181,7 @@ static inline int pmd_trans_huge(pmd_t p
> return (pmd_val(pmd) & (_PAGE_PSE|_PAGE_DEVMAP)) == _PAGE_PSE;
> }
>
> +#define has_transparent_hugepage has_transparent_h
* Srikar Dronamraju wrote:
> * tip-bot for Dongsheng Yang [2016-03-31 02:27:39]:
>
> > Commit-ID: d740037fac7052e49450f6fa1454f1144a103b55
> > Gitweb:
> > http://git.kernel.org/tip/d740037fac7052e49450f6fa1454f1144a103b55
> > Author: Dongsheng Yang
> > AuthorDate: Tue, 22 Mar 2016 1
On Tue, Apr 05, 2016 at 04:48:19PM +0300, Roger Quadros wrote:
> Peter,
>
> On 05/04/16 15:52, Roger Quadros wrote:
> > Peter,
> >
> > On 05/04/16 11:52, Peter Chen wrote:
> >> On Thu, Mar 31, 2016 at 12:41:19PM +0300, Roger Quadros wrote:
> >>> If usb/otg-fsm.h and usb/composite.h are included t
Hi Yuri,
On Wed, Apr 6, 2016 at 12:08 AM, Yury Norov wrote:
> This version is rebased on kernel v4.6-rc2, and has fixes in signal subsystem.
> It works with updated glibc [1] (though very draft), and tested with LTP.
>
> It was tested on QEMU and ThunderX machines. No major difference found.
> Th
On 06/04/2016 03:12, Hugh Dickins wrote:
> Hah, you've lighted on precisely a line of code where I changed around
> what Andres had - I thought it nicer to pass down vcpu, because that
> matched the function above, and in many cases vcpu is not dereferenced
> here at all. So, definitely blame me
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit d1b26c70246bc72922ae61d9f972d5c2588409e7:
>
> perf/ring_buffer: Prepare writing into the ring-buffer from the end
> (2016-03-31 10:30:49 +0200)
>
> are ava
Hi,
On 03/14/2016 11:27 AM, Greg Kroah-Hartman wrote:
> On Mon, Mar 14, 2016 at 09:09:22AM +0800, Lu Baolu wrote:
>> On 03/11/2016 08:06 AM, Greg Kroah-Hartman wrote:
>>> On Tue, Mar 08, 2016 at 03:53:44PM +0800, Lu Baolu wrote:
+struct intel_mux_dev {
+ struct device *dev;
+ ch
Guennadi Liakhovetski writes:
Hi Guennadi,
> Not sure I understand, what should the purpose of this patch be?
See in [1].
> Why do you want to move some function(s) from one file to another? And you
> aren't even calling the new soc_mbus_build_fmts_xlate() function
I'm calling it in pxa_camera_
On 06/04/16 09:09, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
>> index 2ca2cef..6b1930d 100644
>> --- a/drivers/usb/core/hcd.c
>> +++ b/drivers/usb/core/hcd.c
>> @@ -2706,6 +2706,7 @@ int usb_add_hcd(struct usb_hcd *hcd,
Hi,
On 06/04/16 06:23, Yoshihiro Shimoda wrote:
> Hi,
>
>> Sent: Tuesday, April 05, 2016 11:05 PM
>>
>> Host controllers that are part of an OTG/dual-role instance
>> need to somehow pass the OTG controller device information
>> to the HCD core.
>>
>> We use platform data to pass the OTG controll
On Wed, 2016-04-06 at 07:17 +0200, Julia Lawall wrote:
> I have the impression that __iomem is in the wrong place in the following
> code. Perhaps checkpatch could do something about that? Coccinelle,
> unfortunately, skips over such annotations, to simplify parsing...
[]
> __iomem struc
> -Original Message-
> From: Ulf Hansson [mailto:ulf.hans...@linaro.org]
> Sent: Tuesday, April 05, 2016 7:28 PM
> To: Yangbo Lu
> Cc: devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> c...@vger.kernel.o
On 05-04-16, 13:28, Joe Perches wrote:
> Use the more common kernel style adding a define for pr_fmt.
>
> Miscellanea:
>
> o Remove now unused PFX defines
>
> Signed-off-by: Joe Perches
> ---
> drivers/cpufreq/acpi-cpufreq.c| 8 ++---
> drivers/cpufreq/cpufreq-nforce2.c |
On 04/01/2016 09:04 PM, Eric Dumazet wrote:
> On Fri, 2016-04-01 at 12:49 +0800, Jason Wang wrote:
>> On 04/01/2016 10:55 AM, Eric Dumazet wrote:
>>> On Fri, 2016-04-01 at 10:13 +0800, Jason Wang wrote:
>>>
>>>
The problem is we want to support busy polling for tun. This needs
napi_id t
On 05-04-16, 13:28, Joe Perches wrote:
> Use the more common logging style.
>
> Miscellanea:
>
> o Coalesce formats
> o Realign arguments
> o Add a missing space between a coalesced format
>
> Signed-off-by: Joe Perches
> ---
> drivers/cpufreq/acpi-cpufreq.c| 10 ++--
> drivers/cpu
Hi,
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Octavian Purdila
> Subject: Re: [RFC PATCH 02/10] acpi: install SSDT tables from initrd
>
> On Tue, Apr 5, 2016 at 3:49 AM, Zheng, Lv wrote:
> > Hi,
> >
> >> From: Octavian Purdila [mailto:octa
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
tsens-8960.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/thermal/qcom/tsens-8960.c
+++ b/drivers/thermal/qcom/tsens-8960.c
@
On 05-04-16, 13:28, Joe Perches wrote:
> Prefix the output using the more common kernel style.
>
> Signed-off-by: Joe Perches
> ---
> drivers/cpufreq/intel_pstate.c | 18 ++
> 1 file changed, 10 insertions(+), 8 deletions(-)
Acked-by: Viresh Kumar
--
viresh
On Mon, Mar 21, 2016 at 11:54 AM, Pavel Emelyanov wrote:
> On 03/20/2016 03:42 PM, Mike Rapoport wrote:
>> Hi,
>>
>> This set is to address the issues that appear in userfaultfd usage
>> scenarios when the task monitoring the uffd and the mm-owner do not
>> cooperate to each other on VM changes su
On 04/06/2016 06:38 AM, Ezequiel Garcia wrote:
On 5 April 2016 at 18:36, Jacek Anaszewski wrote:
Hi Ezequiel,
On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
Now that we can mark any LED (even those in use by delayed blink
triggers) to trigger on a kernel panic, let's introduce a nosleep
led
Hi,
Roger Quadros writes:
> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
> index 2ca2cef..6b1930d 100644
> --- a/drivers/usb/core/hcd.c
> +++ b/drivers/usb/core/hcd.c
> @@ -2706,6 +2706,7 @@ int usb_add_hcd(struct usb_hcd *hcd,
> int retval;
> struct usb_device *rhdev
Commit <2330b05c095bdeaaf1261c54cd2d4b9127496996> ("regulator: twl: Make
sure we have access to powerbus before trying to write to it")
has implemented the needed logic to correctly access powerbus through i2c,
however it brought a typo when powerbus configuration is restored, which
results in writ
Hi,
> From: Octavian Purdila [mailto:octavian.purd...@intel.com]
> Subject: Re: [RFC PATCH 10/10] acpi: add support for loading SSDTs via
> configfs
>
> On Tue, Apr 5, 2016 at 6:11 AM, Zheng, Lv wrote:
> > Hi,
> >
> >> From: Octavian Purdila [mailto:octavian.purd...@intel.com]
> >> Subject: Re:
On Tue, Apr 05, 2016 at 04:44:25PM -0700, Vinod Koul wrote:
> On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote:
> > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++
> > drivers/dma/qcom/bam_dma.c | 7 +++
>
> The binding should be a se
Hi,
On 03/11/2016 07:57 AM, Greg Kroah-Hartman wrote:
> On Thu, Mar 10, 2016 at 01:39:43PM +0100, Oliver Neukum wrote:
>> On Tue, 2016-03-08 at 15:53 +0800, Lu Baolu wrote:
>>
>>> diff --git a/Documentation/ABI/testing/sysfs-bus-platform
>>> b/Documentation/ABI/testing/sysfs-bus-platform
>>> inde
在 2016年04月06日 03:04, Sam Ravnborg 写道:
On Tue, Apr 05, 2016 at 10:06:21AM +0800, Zeng Zhaoxiu wrote:
From: Zhaoxiu Zeng
These patches provide generic and architecture-specific odd parity
calculations.
Hi Zeng.
Can you please fix your mail script.
I see only 1/30 (sent to linux-arch) - and pat
On (04/05/16 17:02), Rui Salvaterra wrote:
[..]
> > For some reason it never got merged, sorry, I don't remember why.
> >
> > Have you tested this patch? If so, can you resend it with your
> > tested-by: line added to it?
> >
> > thanks,
> >
> > greg k-h
>
> Hi, Greg
>
>
> No, I haven't tested
On Wed, 30 Mar 2016, Jiri Kosina wrote:
> > __module_put_and_exit() is makred noreturn in module.h declaration, but is
> > lacking the attribute in the definition, which makes some tools (such as
> > sparse) unhappy. Amend the definition with the attribute as well (and
> > reformat the declaration
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/health/afe4404.c | 38 +++---
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/gyro/bmg160_core.c | 86 +---
Hi,
On 04/05/2016 11:44 PM, Brian Norris wrote:
> + Mark, Cyrille
>
> On Tue, Mar 29, 2016 at 11:16:17AM +0530, Vignesh R wrote:
>> Certain SPI controllers may provide accelerated hardware interface to
>> read from m25p80 type flash devices in order to provide better read
>> performance. SPI core
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/health/afe4403.c | 36 +---
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/accel/mma7455_core.c | 5 ++---
1 file changed, 2 insertions
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/accel/mxc4005.c | 26 +++---
1 file chan
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/adc/qcom-spmi-vadc.c | 37 --
On 04/06/2016 12:47 PM, Andy Lutomirski wrote:
> On Apr 5, 2016 8:17 PM, "Alex Shi" wrote:
>>
>> It seems Intel core still share the TLB pool, flush both of threads' TLB
>> just cause a extra useless IPI and a extra flush. The extra flush will
>> flush out TLB again which another thread just int
This patch adds support for the AXI Central Direct Memory Access
(AXI CDMA) core to the existing vdma driver, AXI CDMA is a
soft Xilinx IP core that provides high-bandwidth
Direct Memory Access(DMA) between a memory-mapped
source address and a memory-mapped destination address.
Signed-off-by: Keda
This patch updates the device-tree binding doc for
adding support for AXI CDMA.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> Modified commit message as suggested by Vinod.
---> Moved the patch to forward in the series as suggested by vinod.
.../devicetree/bindings/dma/xilinx/x
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/adc/qcom-spmi-iadc.c | 32 +---
This patch updates the device-tree binding doc for
adding support for AXI DMA.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> Modified commit message as suggested by Vinod.
---> Moved the patch to forward in the series as suggested by vinod.
.../devicetree/bindings/dma/xilinx/xi
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/accel/bmc150-accel-core.c | 99 +++--
This patch adds support for the AXI Direct Memory Access (AXI DMA)
core in the existing vdma driver, AXI DMA Core is a
soft Xilinx IP core that provides high-bandwidth
direct memory access between memory and AXI4-Stream
type target peripherals.
Signed-off-by: Kedareswara rao Appana
---
Changes fo
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 (6):
dmaengine: vdma: Fix checkpatch.pl warnings
dmaengine: vdma: Rename xilinx_vdma_ prefix t
Driver includes struct regmap and struct device in its global data.
Remove the struct device and use regmap API to retrieve device info.
Patch created using Coccinelle plus manual edits.
Signed-off-by: Alison Schofield
---
drivers/iio/adc/exynos_adc.c | 18 +-
1 file changed, 9
This patch renames the xilinx_vdma_ prefix to xilinx_dma
for the API's and masks that will be shared b/w three DMA
IP cores.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
---> New patch as suggested by Laurent Pinchart.
drivers/dma/xilinx/xilinx_vdma.c | 636 +++-
This patch fixes the below checkpatch.pl warnings.
WARNING: void function return statements are not generally useful
+ return;
+}
WARNING: void function return statements are not generally useful
+ return;
+}
WARNING: Missing a blank line after declarations
+ u32 errors
These drivers include both struct regmap and struct device in their
global data. Remove the redundant copy by deleting struct device
from the drivers global data and using regmap API to retrieve when
needed.
This patchset removes all such redundancies in drivers/iio/.
Patches created using Cocc
When VDMA is configured in Non-sg mode
Users can queue descriptors greater than h/w configured frames.
Current driver allows the user to queue descriptors upto h/w configured.
Which is wrong for non-sg mode configuration.
This patch fixes this issue.
Signed-off-by: Kedareswara rao Appana
---
C
Hi Vinod,
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Wednesday, April 06, 2016 3:23 AM
> To: Appana Durga Kedareswara Rao
> Cc: dan.j.willi...@intel.com; Michal Simek ; Soren
> Brinkmann ; Appana Durga Kedareswara Rao
> ; moritz.fisc...@ettus.com;
> laur
This VDMA is a soft ip, which can be programmed to support
32 bit addressing or greater than 32 bit addressing.
When the VDMA ip is configured for 32 bit address space
the buffer address is specified by a single register
(0x5C for MM2S and 0xAC for S2MM channel).
When the VDMA core is configure
On 2016-04-04 22:53, Andy Gross wrote:
On Mon, Apr 04, 2016 at 02:08:24PM -0700, Sreedhar Sambangi wrote:
From: Kirthik Srinivasan
Add LDO regulator driver to enable SD /MMC card to
switch between 3.0 volts and 1.8 volts
Change-Id: I66f770878570b1f5b1db044ba626e0f6989acc3f
Signed-off-by: Kir
On 04/04/2016 09:44 PM, Eric Anholt wrote:
dsb() requires an argument on arm64, so we needed to add "sy".
Instead, take this opportunity to switch to the same smp_wmb() call
that gic uses for its IPIs. This is a less strong barrier than we
were doing before (dmb(ishst) compared to dsb(sy)), but
On 2016-04-04 22:59, Andy Gross wrote:
On Mon, Apr 04, 2016 at 02:08:10PM -0700, Sreedhar Sambangi wrote:
This adds the regulator nodes to DK04 device tree to support
Change-Id: I9c1df0e720a330bf6db1889fd2247f6a70ea6faa
Signed-off-by: Sreedhar Sambangi
---
.../bindings/regulator/ipq4019-r
On Apr 5, 2016 8:17 PM, "Alex Shi" wrote:
>
> It seems Intel core still share the TLB pool, flush both of threads' TLB
> just cause a extra useless IPI and a extra flush. The extra flush will
> flush out TLB again which another thread just introduced.
> That's double waste.
Do you have a referenc
On 5 April 2016 at 18:37, Jacek Anaszewski wrote:
> Hi Ezequiel,
>
> On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
>>
>> It's desirable to specify which LEDs are to be blinked on a kernel
>> panic. Therefore, introduce a devicetree boolean property to mark
>> which LEDs should be treated this way
On 5 April 2016 at 18:36, Jacek Anaszewski wrote:
> Hi Ezequiel,
>
>
> On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
>>
>> Now that we can mark any LED (even those in use by delayed blink
>> triggers) to trigger on a kernel panic, let's introduce a nosleep
>> led_trigger_event API.
>>
>> This API
On Wednesday 06 April 2016 04:05 AM, Jonas Rabenstein wrote:
> The directory arch/arm/mach-omap2 is only selected for compilation if
> CONFIG_ARCH_OMAP2PLUS is selected. CONFIG_ARCH_OMAP2PLUS itself is a
> silent option and all machines selecting this option are multiplatform
> devices. As a cons
Hi all,
Changes since 20160405:
Non-merge commits (relative to Linus' tree): 2369
2200 files changed, 93285 insertions(+), 58570 deletions(-)
I have created today's linux-next tree at
git://git.kernel.o
On Wed, Apr 6, 2016 at 10:21 AM, Kent Overstreet
wrote:
> On Wed, Apr 06, 2016 at 10:11:27AM +0800, Ming Lei wrote:
>> On Wed, Apr 6, 2016 at 9:46 AM, Kent Overstreet
>> wrote:
>> > On Wed, Apr 06, 2016 at 09:34:34AM +0800, Ming Lei wrote:
>> >> On Wed, Apr 6, 2016 at 8:18 AM, Kent Overstreet
>>
Replace the code that guarantees the device stays in direct mode with
iio_device_{claim|release}_direct_mode() which does same.
Signed-off-by: Alison Schofield
---
Changed in v2:
- removed improper application of claim/release from intr handler
- updated changelog
drivers/staging/iio/adc/ad76
Hi David,
Please feel free to squash this patch with yours of the same name (12/12).
Just replace the .ima_mok keyring with the .secondary_trusted_keys.
Signed-off-by: Mimi Zohar
---
include/keys/system_keyring.h| 4 +--
security/integrity/digsig.c | 9 ++
security/integrity/ima
Hi Robert,
Not sure I understand, what should the purpose of this patch be? Why do
you want to move some function(s) from one file to another? And you aren't
even calling the new soc_mbus_build_fmts_xlate() function, and you aren't
replacing the currently used analogous soc_camera_init_user_for
Hi all,
On 2016/4/5 13:59, Kefeng Wang wrote:
> Use helper of_platform_default_populate() in linux/of_platform
> when possible, instead of calling of_platform_populate() with
> the default match table.
>
> Then it is possible for driver code build as a module, and no
> need to export of_default_b
On Wed, Apr 06, 2016 at 11:43:32AM +0800, Ming Lei wrote:
> After arbitrary bio size is supported, the incoming bio may
> be very big. We have to split the bio into small bios so that
> each holds at most BIO_MAX_PAGES bvecs for safety reason, such
> as bio_clone().
>
> This patch fixes the follow
In most cases, EPERM is returned on immutable inode, and there're only a
few places returning EACCES. I noticed this when running LTP on
overlayfs, setxattr03 failed due to unexpected EACCES on immutable
inode.
So converting all EACCES to EPERM on immutable inode.
Acked-by: Dave Chinner
Signed-o
After arbitrary bio size is supported, the incoming bio may
be very big. We have to split the bio into small bios so that
each holds at most BIO_MAX_PAGES bvecs for safety reason, such
as bio_clone().
This patch fixes the following kernel crash:
> [ 172.660142] BUG: unable to handle kernel NULL
Radim,
On 04/05/2016 09:56 PM, Radim Krčmář wrote:
I meant to change the place where we remember that is_running must not
be true. Something like
svm_vcpu_blocking(struct kvm_vcpu *vcpu):
vcpu->is_blocking = true;
avic_set_running(vcpu, false);
avic_vcpu_load(struct
On 2016/4/6 8:00, Gavin Shan wrote:
On Tue, Apr 05, 2016 at 09:46:44PM +0800, Yongji Xie wrote:
This patch enables mmapping MSI-X tables if
hardware supports interrupt remapping which
can ensure that a given pci device can only
shoot the MSIs assigned for it.
Signed-off-by: Yongji Xie
---
driv
On 03/30/2016 02:39 PM, Xiao Guangrong wrote:
On 03/30/2016 02:36 PM, Paolo Bonzini wrote:
On 30/03/2016 03:56, Xiao Guangrong wrote:
x86/access.flat is currently using the "other" definition, i.e., PFEC.PK
is only set if W=1 or CR0.WP=0 && PFEC.U=0 or PFEC.W=0. Can you use it
(with ept=
Hi,
> Sent: Tuesday, April 05, 2016 11:05 PM
>
> Host controllers that are part of an OTG/dual-role instance
> need to somehow pass the OTG controller device information
> to the HCD core.
>
> We use platform data to pass the OTG controller device.
>
> Signed-off-by: Roger Quadros
> ---
> dri
On 2016/4/6 8:11, Gavin Shan wrote:
On Tue, Apr 05, 2016 at 09:46:43PM +0800, Yongji Xie wrote:
I'm trying to find a proper way to indicate
the capability of interrupt remapping on PPC64
because we need this to determine whether it is
safe to mmap MSI-X table in VFIO driver.
There is a existing
It seems Intel core still share the TLB pool, flush both of threads' TLB
just cause a extra useless IPI and a extra flush. The extra flush will
flush out TLB again which another thread just introduced.
That's double waste.
The micro testing show memory access can save about 25% time on my
haswel
Hi Andrew,
Andrew Lunn writes:
>> -- port_stp_update: bridge layer function invoked when a given switch port
>> STP
>> +- port_stp_state: bridge layer function invoked when a given switch port STP
>
> port_stp_state_set might be a better name, to make it clear it is
> setting the state, not get
Hi Andrew,
Andrew Lunn writes:
>> mutex_lock(&ps->smi_mutex);
>> -ret = _mv88e6xxx_port_fdb_load(ds, port, fdb->addr, fdb->vid, state);
>> +if (_mv88e6xxx_port_fdb_load(ds, port, fdb->addr, fdb->vid, state))
>> +netdev_warn(ds->ports[port], "cannot load address\n");
>
>
On Wed, Apr 06 2016, Shaohua Li wrote:
> On Tue, Apr 05, 2016 at 03:36:57PM +0200, Lars Ellenberg wrote:
>> blk_check_plugged() will return a pointer
>> to an object linked on current->plug->cb_list.
>>
>> That list may "at any time" be implicitly cleared by
>> blk_flush_plug_list()
>> flush_plu
On 2016/4/6 8:48, Gavin Shan wrote:
On Tue, Apr 05, 2016 at 09:43:29PM +0800, Yongji Xie wrote:
The resource_alignment will releases memory
resources allocated by firmware so that kernel
can reassign new resources later on. But this
will cause the problem that no resources can be
allocated by ke
On Wed, Apr 06, 2016 at 10:51:40AM +0800, Ming Lei wrote:
> On Wed, Apr 6, 2016 at 10:40 AM, Kent Overstreet
> wrote:
> > On Wed, Apr 06, 2016 at 10:37:05AM +0800, Ming Lei wrote:
> >> On Wed, Apr 6, 2016 at 10:34 AM, Kent Overstreet
> >> wrote:
> >> > On Wed, Apr 06, 2016 at 10:30:22AM +0800, Mi
On Wed, Apr 6, 2016 at 10:40 AM, Kent Overstreet
wrote:
> On Wed, Apr 06, 2016 at 10:37:05AM +0800, Ming Lei wrote:
>> On Wed, Apr 6, 2016 at 10:34 AM, Kent Overstreet
>> wrote:
>> > On Wed, Apr 06, 2016 at 10:30:22AM +0800, Ming Lei wrote:
>> >> Now limit.max_segments is for limiting segments fr
On Thu, 2016-03-31 at 16:07 +0200, John Crispin wrote:
>
> On 31/03/2016 15:41, Yingjoe Chen wrote:
> > On Thu, 2016-03-31 at 11:08 +0200, John Crispin wrote:
> >>
> >> On 31/03/2016 04:32, Yingjoe Chen wrote:
> >>> On Thu, 2016-03-31 at 09:40 +0800, Henry Chen wrote:
> On Wed, 2016-03-30 at
On Wed, Apr 06, 2016 at 10:37:05AM +0800, Ming Lei wrote:
> On Wed, Apr 6, 2016 at 10:34 AM, Kent Overstreet
> wrote:
> > On Wed, Apr 06, 2016 at 10:30:22AM +0800, Ming Lei wrote:
> >> Now limit.max_segments is for limiting segments from hw view, one this
> >> segment may include lots of pages/bve
Boris sent out the first HVMLite series of patches to add a new Xen guest type
February 1, 2016 [0]. We've been talking off list with a few folks now over
the prospect of instead of adding yet-another-boot-entry we instead fixate
HVMLite to use the x86 EFI boot entry. There's a series of reasons to
When using GDB built with python 2.7,
Inferior.read_memory (address, length)
returns a buffer object. When using GDB built with python 3.X,
it returns a memoryview object, which cannot be added to another
memoryview object.
Replace the addition (+) of 2 python memoryview objects
with the additio
On Wed, Apr 6, 2016 at 10:34 AM, Kent Overstreet
wrote:
> On Wed, Apr 06, 2016 at 10:30:22AM +0800, Ming Lei wrote:
>> Now limit.max_segments is for limiting segments from hw view, one this
>> segment may include lots of pages/bvecs.
>>
>> The current bio_clone() issue is that we can't clone from
On Sat, 2016-04-02 at 05:46 +0200, Sebastian Reichel wrote:
> Hi,
>
> On Thu, Mar 31, 2016 at 10:42:31AM +0800, YH Huang wrote:
> > On Wed, 2016-03-30 at 17:09 +0200, Sebastian Reichel wrote:
> > > Hi,
> > >
> > > On Wed, Mar 30, 2016 at 04:58:30PM +0800, YH Huang wrote:
> > > > If I revise the d
On Wed, Apr 06, 2016 at 10:30:22AM +0800, Ming Lei wrote:
> Now limit.max_segments is for limiting segments from hw view, one this
> segment may include lots of pages/bvecs.
>
> The current bio_clone() issue is that we can't clone from one bio which
> includes more than 256 bvecs, maybe all these
From: Greg Ungerer
The ColdFire architecture specific gpio support code registers a sysfs
bus device named "gpio". This clashes with the new generic API device
added in commit 3c702e99 ("gpio: add a userspace chardev ABI for GPIOs").
The old ColdFire sysfs gpio device was never used for anything
POWER_SUPPLY_STATUS_NOT_CHARGING is used for AC connected, but
battery not charging (e.g. because battery temperature is out
of acceptable range).
When battery is charging near dry and BATTERY_FULL_DISCHARGED is set,
it is wrong to set as POWER_SUPPLY_STATUS_NOT_CHARGING.
Just use BATTERY_DISCHARG
On Wed, Apr 6, 2016 at 10:22 AM, Kent Overstreet
wrote:
> On Wed, Apr 06, 2016 at 09:51:02AM +0800, Ming Lei wrote:
>> On Wed, Apr 6, 2016 at 9:28 AM, Kent Overstreet
>> wrote:
>> > On Wed, Apr 06, 2016 at 09:20:59AM +0800, Ming Lei wrote:
>> >> On Wed, Apr 6, 2016 at 9:10 AM, Kent Overstreet
>>
On Wed, Apr 06, 2016 at 09:51:02AM +0800, Ming Lei wrote:
> On Wed, Apr 6, 2016 at 9:28 AM, Kent Overstreet
> wrote:
> > On Wed, Apr 06, 2016 at 09:20:59AM +0800, Ming Lei wrote:
> >> On Wed, Apr 6, 2016 at 9:10 AM, Kent Overstreet
> >> wrote:
> >> > On Wed, Apr 06, 2016 at 08:59:31AM +0800, Ming
On Wed, Apr 06, 2016 at 10:11:27AM +0800, Ming Lei wrote:
> On Wed, Apr 6, 2016 at 9:46 AM, Kent Overstreet
> wrote:
> > On Wed, Apr 06, 2016 at 09:34:34AM +0800, Ming Lei wrote:
> >> On Wed, Apr 6, 2016 at 8:18 AM, Kent Overstreet
> >> wrote:
> >> > On Tue, Apr 05, 2016 at 07:56:46PM +0800, Ming
On 2016/4/6 8:55, Gavin Shan wrote:
On Tue, Apr 05, 2016 at 09:43:30PM +0800, Yongji Xie wrote:
Now we use the IORESOURCE_STARTALIGN to identify
bridge resources in __assign_resources_sorted().
That's quite fragile. We can't make sure that
the PCI devices' resources will not use
IORESOURCE_START
On Wed, Apr 6, 2016 at 9:46 AM, Kent Overstreet
wrote:
> On Wed, Apr 06, 2016 at 09:34:34AM +0800, Ming Lei wrote:
>> On Wed, Apr 6, 2016 at 8:18 AM, Kent Overstreet
>> wrote:
>> > On Tue, Apr 05, 2016 at 07:56:46PM +0800, Ming Lei wrote:
>> >> Some drivers access bio->bi_vcnt and bio->bi_io_vec
Fix following DTC warnings in cros-adc-thermistors:
Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@3 has a unit name,
but no reg property
Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@4 has a unit name,
but no reg property
Warning (unit_address_vs_reg): Node /adc@12D
Fix following DTC warnings in all Exynos4 boards:
Warning (unit_address_vs_reg): Node /soc/video-phy@10020710 has a unit name,
but no reg property
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
Changes since v1:
1. Add Javier's tag.
---
arch/arm/boot/dts/exynos
Fix following DTC warnings in Exynos5420 Peach Pit:
Warning (unit_address_vs_reg): Node /dp-controller@145B/ports/port@0 has a
unit name, but no reg property
Warning (unit_address_vs_reg): Node /i2c@12CD/lvds-bridge@48/ports/port@0
has a unit name, but no reg property
Warning (unit_addre
Fix following DTC warnings in Exynos5440 boards:
Warning (unit_address_vs_reg): Node /pinctrl has a reg or ranges property, but
no unit name
Warning (unit_address_vs_reg): Node /rtc has a reg or ranges property, but no
unit name
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez C
Fix following DTC warnings in all Exynos5250 boards:
Warning (unit_address_vs_reg): Node
/dp-controller@145B/display-timings/timing@0 has a unit name, but no reg
property
Warning (unit_address_vs_reg): Node /usb@1200 has a unit name, but no reg
property
Warning (unit_address_vs_reg): No
Fix following DTC warnings in all Exynos542x/5800 boards:
Warning (unit_address_vs_reg): Node /video-phy@10040728 has a unit name, but no
reg property
Warning (unit_address_vs_reg): Node /video-phy@10040714 has a unit name, but no
reg property
Warning (unit_address_vs_reg): Node /usb@1200 ha
Fix following DTC warnings in SMDKv210 board:
Warning (unit_address_vs_reg): Node /soc/fimd@f800/display-timings/timing@0
has a unit name, but no reg property
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Javier Martinez Canillas
---
Changes since v1:
1. Don't add unit name to memory.
1 - 100 of 1025 matches
Mail list logo