On 08/18/15 at 11:36pm, Toshi Kani wrote:
> On 8/18/2015 8:53 PM, Baoquan He wrote:
> >On 08/18/15 at 09:01am, Toshi Kani wrote:
> >>On Tue, 2015-08-18 at 16:53 +0800, Baoquan He wrote:
> >>>Rethink it again, maybe it's better to pass PMEM as PRAM to kdump
> >>>kernel if user really want to use
Hi,
On Tue, Jul 28, 2015 at 05:58:38PM +0800, Haibo Chen wrote:
> Here we apply required documentation for the imx6ul touch screen
> controller driver which describe available properties and how to
> use them.
>
> Signed-off-by: Haibo Chen
> ---
> .../bindings/input/touchscreen/imx6ul_tsc.txt
In little endian cases, the macro htons unfolds to __swab16 which
provides special case for constants. In big endian cases,
__constant_htons and htons expand directly to the same expression.
So, replace __constant_htons with htons with the goal of getting
rid of the definition of __constant_htons
Nick Meier reported a regression with HyperV that "
After rebooting the VM, the following messages are logged in syslog
when trying to load the tulip driver:
tulip: Linux Tulip drivers version 1.1.15 (Feb 27, 2007)
tulip: :00:0a.0: PCI INT A: failed to register GSI
tulip:
2015-08-19 14:45 GMT+09:00 Masahiro Yamada :
> This SoC is integrated with 4 Cortex-A9 cores. The GIC bindings
> says that the bits[15:8] of the 3rd cell of the interrupts property
> represents PPI interrupt CPU mask. Because the timer interrupts are
> wired to all of the 4 cores, bits[15:8]
This SoC is integrated with 4 Cortex-A9 cores. The GIC bindings
document says that the bits[15:8] of the 3rd cell of the interrupts
property represents PPI interrupt CPU mask. Because the timer
interrupts are wired to all of the 4 cores, bits[15:8] should be set
to 0xf.
Signed-off-by: Masahiro
In little endian cases, the macro htons unfolds to __swab16 which
provides special case for constants. In big endian cases,
__constant_htons and htons expand directly to the same expression.
So, replace __constant_htons with htons with the goal of getting
rid of the definition of __constant_htons
Hi Linus,
Here are the outstanding target-pending fixes for v4.2-rc7 code.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
It contains a v4.2-rc specific RCU module unload regression bug-fix, a
long-standing iscsi-target bug-fix for duplicate
This SoC is integrated with 4 Cortex-A9 cores. The GIC bindings
says that the bits[15:8] of the 3rd cell of the interrupts property
represents PPI interrupt CPU mask. Because the timer interrupts are
wired to all of the 4 cores, bits[15:8] should be set to 0xf.
Signed-off-by: Masahiro Yamada
This patch fixes the warning generated by sparse
"Using plain integer as NULL pointer" by using NULL
instead of zero.
Signed-off-by: Ronit halder
---
drivers/staging/most/aim-network/networking.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Aug 17, 2015 at 12:18:12PM +0300, Andrey Ryabinin wrote:
> This bug is similar to recently found bug in 9p:
> http://thread.gmane.org/gmane.linux.kernel/1931799/focus=1936542
Ow. For those who'd missed that fun: the bug in question had turned out to
be caused by improper reuse of
On 19-08-15, 10:05, Pi-Cheng Chen wrote:
> Mediatek MT8173 is an ARMv8 based quad-core (2*Cortex-A53 and
> 2*Cortex-A72) SoC with duall clusters. For each cluster, two voltage
> inputs, Vproc and Vsram are supplied by two regulators. For the big
> cluster, two regulators come from different PMICs.
On 8/18/2015 8:53 PM, Baoquan He wrote:
On 08/18/15 at 09:01am, Toshi Kani wrote:
On Tue, 2015-08-18 at 16:53 +0800, Baoquan He wrote:
Rethink it again, maybe it's better to pass PMEM as PRAM to kdump
kernel if user really want to use memmap way by specifying
--pass-memmap-cmdline. Then I need
Hi Shuah Khan,
On 18 August 2015 at 03:14, Shuah Khan wrote:
> On 08/17/2015 02:39 PM, naresh.kamb...@linaro.org wrote:
>> From: Naresh Kamboju
>
> Are you using git send-email to send this patch? Not sure why
> I see this From and the one below.
I do use git send-email to send this patch.
On Wed, 2015-08-19 at 15:12 +1000, Ian Munsie wrote:
> Excerpts from Michael Ellerman's message of 2015-08-19 14:49:30 +1000:
> > Do we really need the accessors? They don't buy anything I can see over just
> > using ctx->priv directly.
>
> The reasoning there is because we don't currently expose
In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
provides special case for constants. In little endian cases,
__constant_cpu_to_le16 and cpu_to_le16 expand directly to the
same expression. So, replace __constant_cpu_to_le16 with
cpu_to_le16 with the goal of getting rid of the
On Wed, 2015-08-19 at 14:19 +1000, Ian Munsie wrote:
> From: Ian Munsie
>
> This adds an afu_driver_ops structure with event_pending and
> deliver_event callbacks. An AFU driver can fill these out and associate
> it with a context to enable passing custom AFU specific events to
> userspace.
On Mon, Aug 17, 2015 at 5:03 PM, Bjorn Helgaas wrote:
> On Mon, Jul 27, 2015 at 04:29:40PM -0700, Yinghai Lu wrote:
>> On system with several pcie switches, BIOS allocate very tight resources
>> to the bridge bar, and it is not aligned to min_align as kernel allocation
>> code.
>
> I can't parse
In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
provides special case for constants. In little endian cases,
__constant_cpu_to_le16 and cpu_to_le16 expand directly to the
same expression. So, replace __constant_cpu_to_le16 with
cpu_to_le16 with the goal of getting rid of the
Excerpts from Michael Ellerman's message of 2015-08-19 14:49:30 +1000:
> Do we really need the accessors? They don't buy anything I can see over just
> using ctx->priv directly.
The reasoning there is because we don't currently expose the contents of
stuct cxl_context to afu drivers, rather they
Hi Haibo,
On Tue, Jul 28, 2015 at 05:58:37PM +0800, Haibo Chen wrote:
> Freescale i.MX6UL contains a internal touchscreen controller,
> this patch add a driver to support this controller.
>
This looks pretty reasonable; just a few comments below.
> Signed-off-by: Haibo Chen
> ---
>
Hi,
On 06/30/2015 10:54 AM, Archit Taneja wrote:
We are currently restricted when it comes to supporting DSI on devices
that have a non-DSI control bus. For example, DSI encoder chips are
available in the market that are configured via i2c. Configuring their
registers via DSI bus is either
On Fri, Jun 12, 2015 at 1:12 PM, Ursula Braun wrote:
> Thanks Vaishali. I have added your patch to our local kernel git, and
> will submit it within a following upstream shipment.
Hi Ursula,
Can you please tell me when this patch is going to be added in
linux-next? I don't see them in
The Qualcomm NAND controller is found in SoCs like IPQ806x, MSM7xx,
MDM9x15 series.
It exists as a sub block inside the IPs EBI2 (External Bus Interface 2)
and QPIC (Qualcomm Parallel Interface Controller). These IPs provide a
broader interface for external slow peripheral devices such as LCD and
We currently register a platform device for e820 type-12 memory and
register a nvdimm bus beneath it. Registering the platform device
triggers the device-core machinery to probe for a driver, but that
search currently comes up empty. Building the nvdimm-bus registration
into the e820_pmem
Add DT bindings document for the Qualcomm NAND controller driver.
Cc: devicet...@vger.kernel.org
v4:
- No changes
v3:
- Don't use '0x' when specifying nand controller address space
- Add optional property for on-flash bbt usage
Acked-by: Andy Gross
Signed-off-by: Archit Taneja
---
Enable the NAND controller node on the AP148 platform. Provide pinmux
information.
v4:
- Move bias-disable out of mux and create a separate group for it.
- Place the dma node inside soc node and give the full path with address.
v3, v2, v1:
- No changes
Cc: devicet...@vger.kernel.org
On Wed, 2015-08-19 at 14:19 +1000, Ian Munsie wrote:
> From: Michael Neuling
>
> This provides AFU drivers a means to associate private data with a cxl
> context. This is particularly intended for make the new callbacks for
> driver specific events easier for AFU drivers to use, as they can
The nand controller in IPQ806x is of the 'EBI2 type'. Use the corresponding
compatible string.
Cc: devicet...@vger.kernel.org
Reviewed-by: Andy Gross
Signed-off-by: Archit Taneja
---
arch/arm/boot/dts/qcom-ipq8064.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git
Some controllers can access the factory bad block marker from OOB only
when they read it in raw mode. When ECC is enabled, these controllers
discard reading/writing bad block markers, preventing access to them
altogether.
The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks.
This
Add support for the NAND controller driver for SoC's that contain EBI2.
For now, the only SoC upstream that has EBI2 is IPQ806x.
The original version was posted a while back. The main comments were
about the driver not being able to use nand_bbt. This was because the
controller could read factory
From: Michael Neuling
This provides AFU drivers a means to associate private data with a cxl
context. This is particularly intended for make the new callbacks for
driver specific events easier for AFU drivers to use, as they can easily
get back to any private data structures they may use.
Reduced Serial Bus is a proprietary 2-line push-pull serial bus
supporting multiple slave devices.
It was developed by Allwinner, Inc. and used by Allwinner and X-Powers,
Inc. for their line of PMICs and other peripheral ICs.
Signed-off-by: Chen-Yu Tsai
---
This patch adds a device node for the Reduced Serial Bus (RSB)
controller and the defacto pinmux setting to the A23/A33 dtsi.
Since there is only one possible pinmux setting for RSB, just
set it in the dtsi.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23-a33.dtsi | 21
The Reduced Serial Bus controller is used to talk to the onboard PMIC.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a33-sinlinx-sina33.dts
Signed-off-by: Chen-Yu Tsai
---
drivers/base/regmap/Kconfig | 6 +-
drivers/base/regmap/Makefile | 1 +
drivers/base/regmap/regmap-rsb.c | 121 +++
include/linux/regmap.h | 36
4 files changed, 163 insertions(+), 1
The Reduced Serial Bus controller is used to talk to the onboard PMIC.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts
b/arch/arm/boot/dts/sun8i-a23-ippo-q8h-v5.dts
Hi everyone,
This is my third attempt at adding support for Allwinner's Reduced
Serial Bus (RSB), which is used to communicate with PMICs and other
peripherals on their newer SoCs, such as the A23/A33/A80.
RSB is a simplified two wire interface using push-pull outputs,
supporting multiple
From: Ian Munsie
This adds an afu_driver_ops structure with event_pending and
deliver_event callbacks. An AFU driver can fill these out and associate
it with a context to enable passing custom AFU specific events to
userspace.
The cxl driver will call event_pending() during poll, select, read,
Signed-off-by: Chen-Yu Tsai
---
drivers/rsb/Kconfig | 15 ++
drivers/rsb/Makefile| 2 +
drivers/rsb/rsb-sunxi.c | 441
3 files changed, 458 insertions(+)
create mode 100644 drivers/rsb/rsb-sunxi.c
diff --git a/drivers/rsb/Kconfig
Reduced Serial Bus (RSB) is an Allwinner proprietery interface
used to communicate with PMICs and other peripheral ICs.
RSB is a two-wire push-pull serial bus that supports 1 master
device and up to 15 active slave devices.
Signed-off-by: Chen-Yu Tsai
---
drivers/Kconfig| 2 +
Recent Allwinner SoCs, starting with the A23, have a Reduced Serial Bus
(RSB) controller. This is used to talk to the PMIC, and later with the
A80 and A83 platform, the audio codec IC.
Signed-off-by: Chen-Yu Tsai
---
.../devicetree/bindings/rsb/rsb-sunxi.txt | 34 ++
This is a collection of new Mediatek clocks support and fixes. These
patches come from Joe [1], Pi-cheng [2] and me [3], including clock
support for subsystems, CPU, GPT and some minor fixes.
[1] https://patchwork.kernel.org/patch/6777041/
[2] https://patchwork.kernel.org/patch/7023951/
[3]
On Tue, Aug 18, 2015 at 12:10:25PM +0200, Jiri Olsa wrote:
> buut anyway, it looks like latest AMD firmware issue:
>
> [root@amd-pike-07 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version
> 0x6000822
> [root@amd-pike-07 perf]# ./perf test 18
> 18: Test breakpoint overflow signal handler
Change in this patch:
1. revise coding styles.
2. delete redundant clock in prepare/unprepare_hardware.
3. fix incorrect endian usage on big-endian system.
Leilk Liu (3):
spi: mediatek: revise coding style
spi: mediatek: remove redundant clock in
prepare_hardware/unprepare_hardware
spi:
clock in prepare_hardware/unprepare_hardware is redundant
with pm_runtime, so remove them.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c | 17 -
1 file changed, 17 deletions(-)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index 814bca4..1c2b215
This patch revises mediatek spi driver coding styles.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c | 125 ---
1 file changed, 65 insertions(+), 60 deletions(-)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index
TX_ENDIAN/RX_ENDIAN bits define whether to reverse the endian
order of the data DMA from/to memory. The endian order should
keep the same with cpu endian.
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c | 43
Removed some checkpatch.pl warnings saying there was an unwanted space
between function names and their arguments.
Signed-off-by: Chase Metzger
---
drivers/usb/core/hub.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/core/hub.c
/sys/class/watchdog/watchdogn/device/modalias can help to identify the
driver/module for a given watchdog node. However, many wdt devices does not set
its parent and so, we do not see an entry for device in sysfs for such devices.
This patch fixes parent of watchdog_device so that
On Tue, Aug 18, 2015 at 05:18:16PM +0200, Oleg Nesterov wrote:
> On 08/18, Oleg Nesterov wrote:
> >
> > When I tried to run all tests, I
> > got the new reports from lockdep.
>
> Just in case... when I run all tests I see misc failures (with or without
> the changes above) which I didn't try to
On Tue, 2015-08-18 at 13:31 -0700, Tejun Heo wrote:
> So, this is a trade-off we're consciously making. If there are
> common-enough use cases which require jumping across different cgroup
> domains, we'll try to figure out a way to accomodate those but by
> default migration is a very cold and
Just setting fixed_uV is not enough, the regulator core will also check
n_voltages setting. The fixed_uV only works when n_voltages is 1.
Signed-off-by: Axel Lin
---
drivers/regulator/qcom_smd-regulator.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/qcom_smd-regulator.c
The MALLOC_WILC_BUFFER() macro was using a return statement, and didn't
take care of possible memory leaks and subsequent bugs when it was failing
after succeeding some allocations. This patch corrects this behavior.
Signed-off-by: Raphaël Beamonte
---
On 08/10/15 02:31, Raymond Jennings wrote:
I noticed that vfs.txt looked kinda funky, so I went ahead and
reformatted it.
Signed-off-by: Raymond Jennings
Cc: Andrew Morton
---
diff --git a/Documentation/filesystems/vfs.txt
b/Documentation/filesystems/vfs.txt
index 5eb8456..8ddfe06 100644
---
It was just a wrapper around kfree(), so call that instead.
Signed-off-by: Raphaël Beamonte
---
drivers/staging/wilc1000/wilc_exported_buf.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_exported_buf.c
Hi,
As requested, here are the two remaining ready patches of this
patchset. I pulled and rebased against staging-testing just now.
They should thus be usable without problem!
Thanks,
Raphaël
Raphaël Beamonte (2):
staging: wilc1000: remove FREE_WILC_BUFFER()
staging: wilc1000: replace
Peter Zijlstra writes:
> On Mon, Aug 17, 2015 at 04:20:09PM -0700, Laura Abbott wrote:
>> Hi,
>>
>> We received a few bug backtraces:
>>
>> [ 41.536933] [ cut here ]
>> [ 41.537545] WARNING: CPU: 1 PID: 813 at kernel/module.c:291
>>
On Tue, Aug 18, 2015 at 04:49:00PM +0200, Oleg Nesterov wrote:
> Jan, Dave, perhaps you can take a look...
>
> On 08/14, Oleg Nesterov wrote:
> >
> > Plus another patch which removes the "trylock"
> > hack in __sb_start_write().
>
> I meant the patch we already discussed (attached at the end).
From: Ma Jun
Mbigen means Message Based Interrupt Generator(MBIGEN).
Its a kind of interrupt controller that collects
the interrupts from external devices and generate msi interrupt.
Mbigen is applied to reduce the number of wire connected interrupts.
As the peripherals increasing, the
On 2015/8/14 5:49, Alexei Starovoitov wrote:
On 8/13/15 2:35 PM, pi3orama wrote:
I was thinking about whether to add a "type" field there, so we will
have an explicit
mov const instruction before the call instruction, which can act as a
mark. Also, if
we generate the type code automatically,
On Tue, Aug 18, 2015 at 10:32:17PM +0530, Chandra S Gorentla wrote:
> This patch allows setting all options in the module's debug region
> options file 'wilc_debug_region'. This functionality allows the user
> to enable logging from all regions (initialization, locks, firmware
> etc.) of the
On Tue, Aug 18, 2015 at 01:06:39PM -0400, Raphaël Beamonte wrote:
> 2015-08-18 5:15 GMT-04:00 Dan Carpenter :
> > To be honest, I have lost track of this patchset. If you are planning
> > to redo the other patches can you send it in a new thread?
>
> Actually, Greg already included the "return
On Mon, Aug 17, 2015 at 07:06:40PM -0400, Raphaël Beamonte wrote:
> Signed-off-by: Raphaël Beamonte
You can't submit a patch with no changelog information, sorry.
Always build your patches, otherwise you make maintainers really grumpy
as it breaks their build.
greg k-h
--
To unsubscribe from
From: Ma Jun
This patch adds the driver of mbigen and binding document for Hisilicon
Mbigen chips.
Compared with previous version, this version changed much.
Because during the time between V3 and V4 of my patch, there are two
related patches were committed by Mr.Marc Zyngier and Mr. Mark
From: Ma Jun
Add the mbigen msi interrupt controller bindings document.
Change since v3:
--- Change the interrupt cells definition.
--- Change the mbigen node definition.
--- Add mbigen device node as sub node of mbigen.
Signed-off-by: Ma Jun
---
On 08/18/15 at 09:01am, Toshi Kani wrote:
> On Tue, 2015-08-18 at 16:53 +0800, Baoquan He wrote:
> > Rethink it again, maybe it's better to pass PMEM as PRAM to kdump
> > kernel if user really want to use memmap way by specifying
> > --pass-memmap-cmdline. Then I need add the PMEM and PRAM
On Tue, Aug 18, 2015 at 09:04:35PM -0400, gr...@linuxhacker.ru wrote:
> From: Oleg Drokin
>
> Removed references to ib_reg_phsy_mr() and PMR which was added
> to deal with some Chelsio specific scenario, but no longer needed
> now.
>
> Signed-off-by: Amir Shehata
> Signed-off-by: Oleg Drokin
On Wed, Aug 19, 2015 at 6:02 AM, Brian Norris
wrote:
>
> On Tue, Jul 07, 2015 at 12:53:45PM +0530, Vaishali Thakkar wrote:
> > Use module_pci_driver for drivers whose init and exit functions
> > only register and unregister, respectively.
> >
> > A simplified version of the Coccinelle semantic
On Tue, Aug 18, 2015 at 6:38 PM, Andrew Morton
wrote:
> On Tue, 18 Aug 2015 16:06:00 -0400 Dan Streetman wrote:
>
>> Add ZPOOL_MAX_TYPE_NAME define, and change zpool_driver *type field to
>> type[ZPOOL_MAX_TYPE_NAME]. Remove redundant type field from struct zpool
>> and use zpool->driver->type
Mediatek MT8173 is an ARMv8 based quad-core (2*Cortex-A53 and
2*Cortex-A72) SoC with duall clusters. For each cluster, two voltage
inputs, Vproc and Vsram are supplied by two regulators. For the big
cluster, two regulators come from different PMICs. In this case, when
scaling voltage inputs of the
From: Eugene Shatokhin
Date: Fri, 14 Aug 2015 19:58:36 +0300
> 2. The second race is on dev->flags.
>
> dev->flags is set to 0 here:
> *0 usbnet_stop (usbnet.c:816)
> /* deferred work (task, timer, softirq) must also stop.
> * can't flush_scheduled_work() until we drop rtnl (later),
>
On 19 August 2015 at 00:04, Greg KH wrote:
> On Tue, Aug 18, 2015 at 07:14:19PM +0800, Baolin Wang wrote:
>> The usb charger framework is based on usb gadget, and each usb gadget
>> can be one usb charger to set the current limitation.
>>
>> This patch adds a notifier mechanism for usb charger to
On Wed, Aug 19, 2015 at 3:22 AM, Dinh Nguyen wrote:
> On Mon, Aug 17, 2015 at 4:09 AM, Ley Foon Tan wrote:
>> This patch adds the bindings for Altera PCIe host controller driver and
>> Altera PCIe MSI driver.
>>
>> Signed-off-by: Ley Foon Tan
>> ---
>>
On Wed, Aug 19, 2015 at 3:11 AM, Dinh Nguyen wrote:
>
> On Mon, Aug 17, 2015 at 4:09 AM, Ley Foon Tan wrote:
> > This patch adds the Altera PCIe host controller driver.
> >
> > Signed-off-by: Ley Foon Tan
> > ---
> > drivers/pci/host/Kconfig | 7 +
> > drivers/pci/host/Makefile |
On Tue, Aug 18, 2015 at 09:12:00AM -0700, Mark Brown wrote:
> On Tue, Aug 18, 2015 at 01:20:12PM +0800, Peter Chen wrote:
>
> > ok, I just had suspected below function's correctness, after looking
> > it again, it always set 1800 as charging limit, does it be expected?
>
> > + /* Find the
On Tue, Aug 18, 2015 at 10:59:10AM +0200, Antoine Tenart wrote:
> When keeping the configuration set by the bootloader (by using
> the marvell,nand-keep-config property), the pxa3xx_nand_detect_config()
> function is called and set the chunk size to 512 as a default value if
> NDCR_PAGE_SZ is not
From: Oleg Drokin
Removed references to ib_reg_phsy_mr() and PMR which was added
to deal with some Chelsio specific scenario, but no longer needed
now.
Signed-off-by: Amir Shehata
Signed-off-by: Oleg Drokin
---
This fixes a build failure in Lustre due to ib_reg_phys_mr being removed.
On Fri, Jul 17, 2015 at 11:37:52AM +0100, Colin King wrote:
> From: Colin Ian King
>
> static analysis by smatch caught the following error:
>
> drivers/mtd/maps/physmap_of.c:135 of_get_probes()
>error: potential null dereference 'res'. (kzalloc returns null)
>
> Check for failed kzalloc
On Tue, 2015-08-18 at 12:35 +0200, Javier Martinez Canillas wrote:
> Hello Michael,
>
> On 08/18/2015 12:24 PM, Michael Ellerman wrote:
> > On Thu, 2015-30-07 at 16:18:30 UTC, Javier Martinez Canillas wrote:
> >> The I2C core always reports the MODALIAS uevent as "i2c: >> regardless if the driver
Hi Robert,
On Mon, Aug 17, 2015 at 09:15:48PM +0200, Robert Jarzmik wrote:
> Ezequiel Garcia writes:
> > So unless I'm completely off, the current patch is right, and a comment
> > would be helpful.
> Ok Ezequiel, I'll wait for your Tested-by, and respin with something like :
>
> /* Clear
On Fri, Aug 14, 2015 at 01:37:47AM +0300, Alexey Khoroshilov wrote:
> If mtd_device_register() fails in nettel_init(), iomap left mapped.
>
> The patch adds failure handling for mtd_device_register().
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey
On Tue, Jul 07, 2015 at 12:53:45PM +0530, Vaishali Thakkar wrote:
> Use module_pci_driver for drivers whose init and exit functions
> only register and unregister, respectively.
>
> A simplified version of the Coccinelle semantic patch that performs
> this transformation is as follows:
>
> @a@
>
On Tue, Aug 18, 2015 at 12:11 PM, Andy Lutomirski wrote:
> This fixes a couple minor holes if we took an IRQ very early in syscall
> processing:
>
The patch is buggy. v2 coming soon, hopefully.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tue, Jul 07, 2015 at 10:54:03PM -0700, Rajat Jain wrote:
> Use module_pci_driver, since init and exit functions only register
> and unregister the pci driver, respectively.
>
> Signed-off-by: Rajat Jain
> Signed-off-by: Rajat Jain
I pushed an identical patch to l2-mtd.git from another
On Tue, 18 Aug 2015 01:07:58 -0700 Tony Lindgren
wrote:
> * NeilBrown [150729 17:29]:
> > Now that twl4030_bci_probe can safely return -EPROBE_DEFER,
> > do so when devm_usb_get_phy_by_node returns that error.
> >
> > Signed-off-by: NeilBrown
> > ---
> > drivers/power/twl4030_charger.c |
On 8/18/2015 2:41 AM, Yunzhi Li wrote:
> We initiate dwc2 usb controller in BIOS, dwc2_core_reset() should
> be called before dwc2_get_hwparams() to reset core registers to
> default value. Without this the FIFO setting might be incorrect
> because calculating FIFO size need power-on value of
>
Hello!
On Aug 18, 2015, at 8:05 PM, Stephen Rothwell wrote:
> Hi Trond,
>
> On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
> wrote:
>>
>> After merging the nfs tree, today's linux-next build (x86_64 allmodconfig)
>> failed like this:
>>
>>
Hi Trond,
On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
wrote:
>
> After merging the nfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c: In function
> 'kiblnd_pmr_pool_map':
>
On Tue, Aug 18, 2015 at 1:18 PM, Mauro Carvalho Chehab
wrote:
>
> - Revert the IR encode patches, as the API is not mature enough.
> So, better to postpone the changes to a latter Kernel;
What the hell have you done with the commit messages?
The first line is completely
Previously, we used the kernel-internal netlink actions length to
calculate the size of messages to serialize back to userspace.
However,the sw_flow_actions may not be formatted exactly the same as the
actions on the wire, so store the original actions length when
de-serializing and re-use the
The following patches will reuse this code from OVS.
Signed-off-by: Joe Stringer
---
v2-v4: No change.
---
net/netfilter/nf_conntrack_labels.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/netfilter/nf_conntrack_labels.c
b/net/netfilter/nf_conntrack_labels.c
index bb53f12..daa7c13
Add functions to change connlabel length into nf_conntrack_labels.c so
they may be reused by other modules like OVS and nftables without
needing to jump through xt_match_check() hoops.
Suggested-by: Florian Westphal
Signed-off-by: Joe Stringer
Acked-by: Florian Westphal
---
v2: Protect
Hello Linus,
I have these last minute fixes on the thermal-soc tree. It has gone through
linux-next. There is a fix of a long lasting bug in cpu cooling device,
thanks for RMK for being pushing this.
So, if there is still time, please pull from:
Allow matching and setting the conntrack label field. As with ct_mark,
this is populated by executing the CT action, and is a writable field.
Specifying a label and optional mask allows the label to be modified,
which takes effect on the entry found by the lookup of the CT action.
E.g.:
On Tue, 18 Aug 2015 17:18:19 +0200 Dongsu Park wrote:
> To allow devpts to be mounted with options of uid/gid of uint32_t,
> use kstrtouint() instead of match_int(). Doing that, mounting devpts
> with uid or gid > (2^31 - 1) will work as expected, e.g.:
>
> # mount -t devpts devpts
Add support for using conntrack helpers to assist protocol detection.
The new OVS_CT_ATTR_HELPER attribute of the ct action specifies a helper
to be used for this connection.
Example ODP flows allowing FTP connections from ports 1->2:
in_port=1,tcp,action=ct(helper=ftp,commit),2
Expose the kernel connection tracker via OVS. Userspace components can
make use of the "ct()" action, followed by "recirculate", to populate
the conntracking state in the OVS flow key, and subsequently match on
that state.
Example ODP flows allowing traffic from 1->2, only replies from 2->1:
Allow matching and setting the conntrack mark field. As with conntrack
state and zone, these are populated when the CT action is executed,
and are made available for matching via RECIRC. To write to this field,
a value and optional mark can be passed as part of the conntrack action.
E.g.:
Signed-off-by: Joe Stringer
Acked-by: Thomas Graf
Acked-by: Pravin B Shelar
---
v4: Add ack.
---
net/ipv6/netfilter/nf_conntrack_reasm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv6/netfilter/nf_conntrack_reasm.c
b/net/ipv6/netfilter/nf_conntrack_reasm.c
index 6d02498..701cd2b
1 - 100 of 1202 matches
Mail list logo
