Add support for using with both wl12xx and wl18xx.
- all wilink family needs special init command for entering wspi mode.
extra clock cycles should be sent after the spi init command while the
cs pin is high.
- Use inverted chip select for sending a dummy 4 bytes command that
completes the i
The bottom two bits of radix tree entries are reserved for special use by
the radix tree code itself. A comment detailing their usage was added by:
commit 3bcadd6fa6c4 ("radix-tree: free up the bottom bit of exceptional
entries for reuse")
This comment states that if the bottom two bits are '11'
Hi Nicolas,
On Wed, Jul 20, 2016 at 6:09 AM, Nicolas Pitre wrote:
> On Tue, 19 Jul 2016, Geert Uytterhoeven wrote:
>
>> On Tue, Jul 19, 2016 at 6:52 AM, Greg Ungerer wrote:
>> > Seeing as you have modified quite a few printk calls is it worth
>> > while annotating them with appropriate KERN_ERR,
On Wed 2016-07-20 01:50:24, Michael Welling wrote:
> On Wed, Jul 20, 2016 at 08:31:06AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > Passes input_id struct to the the common probe function for the tsc200x
> > > drivers
> > > instead of just the bustype.
> > >
> > > This allows for the use of the
Hi, YT:
Some comments inline.
On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> This patch add support for the Mediatek MT2701 DISP subsystem.
> There is only one OVL engine in MT2701.
>
> Signed-off-by: YT Shen
> ---
> drivers/gpu/drm/mediatek/mtk_disp_ovl.c |6
> drivers/gpu/d
On Wed, Jul 20, 2016 at 08:31:06AM +0200, Pavel Machek wrote:
> Hi!
>
> > Passes input_id struct to the the common probe function for the tsc200x
> > drivers
> > instead of just the bustype.
> >
> > This allows for the use of the product variable to set the input_dev->name
> > variable according
On 07/20/16 at 08:32am, Thomas Gleixner wrote:
> On Wed, 20 Jul 2016, b...@redhat.com wrote:
> > On 07/20/16 at 03:54am, Wei, Jiangang wrote:
> >
> > > In fact, Eric and Ingo suggested that "it should be fixed in the bootup
> > > path of the dump kernel, not the crash kernel reboot path", which is
On Friday 15 of July 2016, Thomas Voegtle wrote:
> On Fri, 15 Jul 2016, Sasha Levin wrote:
> > On 07/15/2016 07:38 AM, Thomas Voegtle wrote:
> >> On Wed, 13 Jul 2016, Sasha Levin wrote:
> >>> I'm announcing the release of the 4.1.28 kernel.
> >>
> >> I have a serious memleak with 4.1.28 (like 20mb
On Tue 19-07-16 17:50:29, Mikulas Patocka wrote:
>
>
> On Mon, 18 Jul 2016, Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > There has been a report about OOM killer invoked when swapping out to
> > a dm-crypt device. The primary reason seems to be that the swapout
> > out IO managed to co
On Tue, 19 Jul 2016 22:33:57 -0700
Andrey Smirnov wrote:
> If no user specified chip->select_chip() function is provided, code in
> nand_base.c will automatically set this hook to nand_select_chip(),
> which in turn depends on chip->cmd_ctrl() hook being valid. Not
> providing both of those funct
On Tue, 19 Jul 2016, Andy Gross wrote:
> So not too long ago there were irq extensions that you could add in to an
> irq controller that would allow for intercepting the set wake calls. This
> went away and was replaced by the hierarchical irq design.
For a very good reason. The 'extensions' wer
On Wed, 20 Jul 2016, b...@redhat.com wrote:
> On 07/20/16 at 03:54am, Wei, Jiangang wrote:
>
> > In fact, Eric and Ingo suggested that "it should be fixed in the bootup
> > path of the dump kernel, not the crash kernel reboot path", which is
> > convincing and reasonable.
>
> Well this patch does
On Wed, 2016-07-20 at 06:02 +, Levy, Amir (Jer) wrote:
> On Tue, Jul 19 2016, 08:14 PM, Joe Perches wrote:
> > On Mon, 2016-07-18 at 13:00 +0300, Amir Levy wrote:
> > >
> > > This is version 4 of Thunderbolt(TM) driver for non-Apple hardware.
> > []
> > > Documentation/00-INDEX
Hi!
> Passes input_id struct to the the common probe function for the tsc200x
> drivers
> instead of just the bustype.
>
> This allows for the use of the product variable to set the input_dev->name
> variable according to the type of touchscreen used.
>
> Signed-off-by: Michael Welling
> ---
>
On Tue, 19 Jul 2016, Sören Brinkmann wrote:
> we are working on the PM solution for Zynq MPSOC and ran into some
> problem when setting the wake source.
>
> The situation is that when the A53 is in suspend, the GIC(v2) may be
> powered down. In that state a companion core is handling wake
> events
On Tue 19-07-16 16:27:59, Andrew Morton wrote:
> On Tue, 19 Jul 2016 14:05:39 +0200 Michal Hocko wrote:
>
> > > After this patch we should guarantee a forward progress for the OOM
> > > killer even when the selected victim is sharing memory with a kernel
> > > thread or global init.
> >
> > Coul
On 07/20/16 at 03:54am, Wei, Jiangang wrote:
> Hi Baoquan He,
>
> Well, Indeed there‘s a relationship between the dump-capture hangs in
> calibrate_delay_converge() and the interrupt mode.
>
> but there‘s no essential difference between your patches and mine that
> calls disable_IO_APIC() again.
Hi, YT:
Some comments inline.
On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> From: shaoming chen
>
> add dsi and mipi tx driver for mipi panel support
>
> Signed-off-by: shaoming chen
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 169
> ++--
> drivers/gp
Peter Ujfalusi writes:
> On 07/18/16 13:34, Russell King - ARM Linux wrote:
>> On Thu, Jul 14, 2016 at 03:42:37PM +0300, Peter Ujfalusi wrote:
>>> Before looking for the next descriptor to start, complete the just finished
>>> cookie.
>>
>> This change will reduce performance as we no longer hav
Hi!
> > > > > > > drivers/input/touchscreen/tsc2005.c:input_dev->name =
> > > > > > > "TSC2005
> > > > > > > touchscreen";
> > > > > > >
> > > > > > > to "TSC200X touchscreen". Unfortunately, X seems to propagate that
> > > > > > > name to userspace, where it is needed to be able to do
>
On Wed, Jul 20, 2016 at 02:33:18AM +0200, Rafael J. Wysocki wrote:
> On Friday, June 17, 2016 04:07:38 PM Lukas Wunner wrote:
> > On Fri, Jun 17, 2016 at 02:54:56PM +0200, Rafael J. Wysocki wrote:
> > > On Fri, Jun 17, 2016 at 12:36 PM, Lukas Wunner wrote:
> > > > On Fri, Jun 17, 2016 at 08:26:52A
On Wed, 2016-07-20 at 14:02 +0800, zhiyong tao wrote:
> On Mon, 2016-07-18 at 18:12 +0100, Jonathan Cameron wrote:
> > On 11/07/16 07:39, Zhiyong Tao wrote:
> > > Add Mediatek auxadc driver based on iio.
> > > It will register a device in iio and support iio.
> > > So thermal can read auxadc channe
Hi Stephen,
>
> After merging the wireless-drivers-next tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> drivers/net/wireless/ti/wlcore/spi.c: In function 'wlcore_probe_of':
> drivers/net/wireless/ti/wlcore/spi.c:457:6: warning: unused variable 'ret' [-
> Wunused
On Mon, 18 Jul 2016, John Stultz wrote:
> As requested, this patch implements a task_settimerslack and
> task_gettimerslack LSM hooks so that the /proc//timerslack_ns
> interface can have finer grained security policies applied to it.
>
> I've kept the CAP_SYS_NICE check in the timerslack_ns_writ
A subset of the pins and functions are exposed. The selection of
functions and pins is driven by the development of OpenBMC[1] on the
AST2400 SoC, particularly around booting the OpenPOWER Palmetto
development machine.
[1] https://github.com/openbmc/docs
Signed-off-by: Andrew Jeffery
---
arch/a
From: Joel Stanley
The Aspeed SoCs contain GPIOs grouped by letter, where each letter group
contains 8 pins. The GPIO letter groups are then banked in sets of four
in the register layout.
The implementation exposes multiple banks through the one driver, and
requests and releases pins via the pin
Hi all,
This series is an evolution of the AST2400 pinctrl RFC posted a few months
back:
http://www.spinics.net/lists/linux-gpio/msg14414.html
The approach is similar to the RFC but a number of details have changed, often
to support the weirder mux configuration cases. Unlike the RFC this seri
Signed-off-by: Andrew Jeffery
---
.../devicetree/bindings/gpio/gpio-aspeed.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-aspeed.txt
diff --git a/Documentation/devicetree/bindings/gpio/gpio-aspeed.txt
b/Doc
Hi Tejun,
Today's linux-next merge of the cgroup tree got a conflict in:
kernel/cgroup.c
between commit:
1f3fe7ebf613 ("cgroup: Add cgroup_get_from_fd")
from the net-next tree and commit:
55094f575358 ("cgroup: remove duplicated include from cgroup.c")
from the cgroup tree.
I fixed it
The pin controller's child nodes expose the functions currently
implemented in the the g4 pin controller driver.
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g4.dtsi | 284 +++
1 file changed, 284 insertions(+)
diff --git a/arch/arm/boot/dts/asp
A small subset of pins and functions are exposed. The selection of pins
and functions is driven by the development of OpenBMC[1] on the
AST2500 SoC, particularly around booting the IBM Witherspoon platform.
[1] https://github.com/openbmc/docs
Signed-off-by: Andrew Jeffery
---
arch/arm/mach-aspe
The Aspeed SoCs provide typically more than 200 pins for GPIO and other
functions. The signal enabled on a pin is determined on a priority
basis, where a given pin can provide a number of different signal types.
In addition to the priority levels, the Aspeed pin controllers describe
the signal act
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g5.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index 1b1910e5eaa3..f5ab29bf3e9e 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/arm/boot/dt
Outline expectations on the pin controller's relationship with the
System Control Unit (SCU) IP through syscon, and document the compatible
strings for 4th and 5th generation Aspeed SoC pin controllers.
Signed-off-by: Andrew Jeffery
---
.../devicetree/bindings/pinctrl/pinctrl-aspeed.txt | 45 +++
The pin controller's child nodes expose the functions currently
implemented in the g5 pin controller driver.
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g5.dtsi | 134 +++
1 file changed, 134 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-
The requested functions are parented by the pinctrl node to provide the
Palmetto's static pin configuration.
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 28 +++
1 file changed, 28 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-b
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g4.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed-g4.dtsi b/arch/arm/boot/dts/aspeed-g4.dtsi
index a62d1b5b5054..2b7da0fdfbd9 100644
--- a/arch/arm/boot/dts/aspeed-g4.dtsi
+++ b/arch/arm/boot/dt
Signed-off-by: Andrew Jeffery
---
Documentation/devicetree/bindings/mfd/aspeed-scu.txt | 16
1 file changed, 16 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/aspeed-scu.txt
diff --git a/Documentation/devicetree/bindings/mfd/aspeed-scu.txt
b/Documentati
On Tue, Jul 19 2016, 08:14 PM, Joe Perches wrote:
> On Mon, 2016-07-18 at 13:00 +0300, Amir Levy wrote:
> > This is version 4 of Thunderbolt(TM) driver for non-Apple hardware.
> []
> > Documentation/00-INDEX |2 +
> > Documentation/thunderbolt-networking.txt | 135 ++
> > dr
On Fri, Jun 24, 2016 at 10:38 PM, Rob Herring wrote:
> On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
> wrote:
>> v3 tested here multiple times ! memleak is now gone.
>>
>> Tested-by: Mathieu Malaterre
>>
>> Thanks
>>
>> On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand wrote:
>>> From: Frank R
On Mon, 2016-07-18 at 18:12 +0100, Jonathan Cameron wrote:
> On 11/07/16 07:39, Zhiyong Tao wrote:
> > Add Mediatek auxadc driver based on iio.
> > It will register a device in iio and support iio.
> > So thermal can read auxadc channel to sample data by iio device.
> > It is tested successfully on
On 07/20/2016 05:25 AM, Brian Norris wrote:
> On Wed, Jul 20, 2016 at 04:58:08AM +0200, Marek Vasut wrote:
>> On 07/20/2016 04:50 AM, Brian Norris wrote:
>>> On Wed, Jul 20, 2016 at 03:50:27AM +0200, Marek Vasut wrote:
On 07/19/2016 10:05 PM, Brian Norris wrote:
> On Tue, Jul 19, 2016 at 0
Hi, YT:
Some comments inline.
On Fri, 2016-07-15 at 18:07 +0800, YT Shen wrote:
> From: shaoming chen
>
> add dsi read/write commands for transfer function
>
> Signed-off-by: shaoming chen
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 322
>
> 1 file cha
lowing changes since commit d4d03f74a73f3b8b2801d4d02011b6b69778cbcc:
>
> apparmor: fix arg_size computation for when setprocattr is null terminated
> (2016-07-12 08:43:10 -0700)
>
> are available in the git repository at:
>
> git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-n
On Tue, Jul 19, 2016 at 02:22:36PM -0400, Vince Weaver wrote:
> On Fri, 17 Jun 2016, Huang Rui wrote:
>
> > On Thu, Jun 16, 2016 at 06:47:00PM +0200, Borislav Petkov wrote:
> > > On Thu, Jun 16, 2016 at 01:38:14PM +0800, Huang Rui wrote:
> > > > I was told this feature would be supported on fam15h
'phy' has been allocated with 'devm_kzalloc', so we should not free it
using an explicit 'kfree'. It would result in a double free if the
allocation of 'in_buf' fails.
Signed-off-by: Christophe JAILLET
---
drivers/nfc/pn533/usb.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
di
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
2b8ddd9337ee ("KVM: Extend struct kvm_msi to hold a 32-bit device ID")
from the kvm-arm tree and commit:
6502a34cfd66 ("KVM: s390: allow user space to handle instr 0x")
Using "goto" and "switch" statement only makes it harder to follow
control flow and doesn't bring any advantages. Rewrite the code to avoid
using "goto".
Signed-off-by: Brian Norris
Signed-off-by: Andrey Smirnov
---
drivers/mtd/nand/nand_base.c | 18 ++
1 file changed, 6 inserti
If no user specified chip->select_chip() function is provided, code in
nand_base.c will automatically set this hook to nand_select_chip(),
which in turn depends on chip->cmd_ctrl() hook being valid. Not
providing both of those functions in NAND controller driver (for example
by mistake) will result
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
virt/kvm/kvm_main.c
between commit:
8c18b2d2d088 ("virt: Convert kvm hotplug to state machine")
from the tip tree and commit:
8a39d00670f0 ("KVM: kvm_io_bus: Add kvm_io_bus_get_dev() call")
from the kvm-arm tree.
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
3713131345fb ("KVM: x86: add KVM_CAP_X2APIC_API")
from the kvm tree and commit:
2b8ddd9337ee ("KVM: Extend struct kvm_msi to hold a 32-bit device ID")
from the kvm-arm tree.
kmod 23 is out:
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-23.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-23.tar.sign
- Improvements:
- Don't add comment to modules.devname if it would otherwise be empty
to play nice with tools detecti
On 20/07/16 07:10, SF Markus Elfring wrote:
> @@ -606,7 +606,7 @@ static void scsiback_device_action(struct
> vscsibk_pend *pending_req,
> tmr = kzalloc(sizeof(struct scsiback_tmr), GFP_KERNEL);
> if (!tmr) {
> target_put_sess_cmd(se_cmd);
> - goto err
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
include/linux/irqchip/arm-gic-v3.h
between commits:
9347359ad0ae ("irqchip/gicv3-its: Split its_alloc_tables() into two
functions")
3faf24ea894a ("irqchip/gicv3-its: Implement two-level(indirect) device table
suppor
Replace clk_enable and clk_prepare with clk_enable_prepare and
clk_disable and clk_unprepare with clk_disable_unprepare.
The Coccinelle semantic patch used to make this change is as follows:
@@
expression e;
@@
- clk_prepare(e);
- clk_enable(e);
+ clk_prepare_enable(e);
@@
expression e;
@@
- cl
@@ -606,7 +606,7 @@ static void scsiback_device_action(struct vscsibk_pend
*pending_req,
tmr = kzalloc(sizeof(struct scsiback_tmr), GFP_KERNEL);
if (!tmr) {
target_put_sess_cmd(se_cmd);
- goto err;
+ goto do_resp;
}
>>>
On 19.07.2016 23:17, Bjorn Helgaas wrote:
On Thu, Jun 02, 2016 at 10:41:00AM +0200, Tomasz Nowicki wrote:
This series bases on pending ACPI PCI support for ARM64:
https://lkml.org/lkml/2016/5/30/468
Quirk handling relies on an idea of matching MCFG OEM ID and OEM revision
(the ones from standar
On Tue, 19 Jul 2016, Joe Perches wrote:
> On Wed, 2016-07-20 at 00:20 -0400, Nicolas Pitre wrote:
> > diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
> []
> > @@ -15,6 +15,8 @@
> > * JAN/99 -- coded full program relocation (g...@snapgear.com)
> > */
> >
> > +#define pr_fmt(fmt)"BINF
Hi all,
We are pleased to announce another update of Intel GVT-g for KVM.
Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with
mediated pass-through, starting from 5th generation Intel Core™ processors with
Intel Graphics processors. A virtual GPU instance is maintaine
On Tue, 2016-07-19 at 16:04 -0700, Jason Low wrote:
> Hi Imre,
>
> Here is a patch which prevents a thread from spending too much "time"
> waiting for a mutex in the !CONFIG_MUTEX_SPIN_ON_OWNER case.
>
> Would you like to try this out and see if this addresses the mutex
> starvation issue you are
On 11 July 2016 at 13:38, Arnd Bergmann wrote:
> On Monday, July 11, 2016 9:41:15 AM CEST Jiri Slaby wrote:
>> Hi,
>>
>> while looking at this commit:
>>
>> commit b27a6d5e636ac80b223a18ca2b3c892f1caef9e3
>> Author: Binoy Jayan
>> Date: Wed Jun 15 11:00:34 2016 +0530
>>
>> staging: wilc1000
On 19/07/16 16:56, SF Markus Elfring wrote:
>>> @@ -606,7 +606,7 @@ static void scsiback_device_action(struct vscsibk_pend
>>> *pending_req,
>>> tmr = kzalloc(sizeof(struct scsiback_tmr), GFP_KERNEL);
>>> if (!tmr) {
>>> target_put_sess_cmd(se_cmd);
>>> - goto err;
>>
In some situations the userspace memory context may live longer than
the userspace process itself so if we need to do proper memory context
cleanup, we better cache @mm and use it later when the process is gone
(@current or @current->mm are NULL).
This changes mm_iommu_xxx API to receive mm_struct
At the moment VFIO IOMMU SPAPR v2 driver pins all guest RAM pages when
the userspace starts using VFIO. When the userspace process finishes,
all the pinned pages need to be put; this is done as a part of
the userspace memory context (MM) destruction which happens on
the very last mmdrop().
This ap
This is a fix to a bug when guest memory stays Active
after QEMU process exited. This happened because the QEMU memory context
was not released in a short period of time after QEMU process exited.
More details are in the commit logs.
Please comment. Thanks.
Alexey Kardashevskiy (2):
powerpc/iom
On Wed, 2016-07-20 at 00:20 -0400, Nicolas Pitre wrote:
> diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
[]
> @@ -15,6 +15,8 @@
> * JAN/99 -- coded full program relocation (g...@snapgear.com)
> */
>
> +#define pr_fmt(fmt) "BINFMT_FLAT: : " fmt
Why the double colon?
Much more common woul
Replace the code that guarantees the device stays in direct mode
with iio_device_claim_direct_mode() which does same.
Signed-off-by: Alison Schofield
Cc: Daniel Baluta
---
Peter: I was not clear if we want to keep the data->mutex lock
in addition to claiming direct mode. I see that lock assurin
Signed-off-by: Nicolas Pitre
---
fs/binfmt_flat.c | 118 ---
1 file changed, 51 insertions(+), 67 deletions(-)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 085059d879..36f5bb6b2c 100644
--- a/fs/binfmt_flat.c
+++ b/fs/binfmt_flat.c
@@
This copying of arguments and environment is common to both NOMMU
binary formats we support. Let's make the elf_fdpic version available
to the flat format as well.
While at it, improve the code a bit not to copy below the actual
data area.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 30 +++---
1 file changed, 19 insertions(+), 11 deletions(-)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 34f815540e..28fc272d9a 100644
--- a/fs/binfmt_flat.c
+++ b/fs/binfmt_flat.c
@
Relocs are fixed up in place in user space memory. The appropriate
accessors are required for this code to work with an active MMU.
The architecture specific handlers for ARM and M68K are also
covered. SuperH and Xtensa are left out as they doesn't implement
__get_user_unaligned() and __put_user_
Ping..
On Friday 24 June 2016 10:45 PM, Hari Bathini wrote:
On 06/24/2016 10:56 AM, Michael Ellerman wrote:
On Wed, 2016-22-06 at 19:25:26 UTC, Hari Bathini wrote:
Currently, crashkernel parameter supports the below syntax to parse
size
based on memory range:
crashkernel=:[,:,...]
W
This is needed on systems with a MMU.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 28fc272d9a..0d89830f76 100644
--- a/fs/binfmt_flat.c
+++ b/fs/binf
In addition to better code clarity, this brings proper usage of
user memory accessors everywhere the stack is touched. This is essential
for making this work on MMU systems.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 117 ++-
Signed-off-by: Nicolas Pitre
---
fs/binfmt_flat.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 36f5bb6b2c..9c76d9a222 100644
--- a/fs/binfmt_flat.c
+++ b/fs/binfmt_flat.c
@@ -470,6 +470,17 @@ static int load_flat_file(struct linux_binp
Let's take the simple and obvious approach by decompressing the binary
into a kernel buffer and then copying it to user space. Those who are
looking for top performance on an MMU system are unlikely to choose this
executable format anyway.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
This gets rid of the rather ugly, open coded and suboptimal copy code.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
index 9c76d9a222..f
Not much else to do at this point except for the different stack setups.
SuperH and Xtensa could be added to the allowed list if they implement
__put_user_unaligned() and __get_user_unaligned().
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/Kconfig.binfmt | 3 ++-
fs/binfmt_fl
Remove excessive casts, do some code grouping, etc.
No functional changes.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 118 ++-
1 file changed, 56 insertions(+), 62 deletions(-)
diff --git a/fs/binfmt_flat.c
This is needed on systems with a MMU. This also gets rid of the
strangest C code I've seen lateli i.e. an integer indexed with a
pointer value within square brackets. That really looked backwards.
Signed-off-by: Nicolas Pitre
Reviewed-by: Greg Ungerer
---
fs/binfmt_flat.c | 19 +---
This series provides the necessary changes to allow "flat" executable
binaries meant for no-MMU systems to actually run on systems with a MMU.
This can also be found in the following git repo:
git://git.linaro.org/people/nicolas.pitre/linux binfmt_flat_with_mmu
*Why?*
Because developing
> From: David Miller [mailto:da...@davemloft.net]
> >> From: kbuild test robot [mailto:l...@intel.com]
> >> [auto build test WARNING on net-next/master]
> >>
> >> url:https://github.com/0day-ci/linux/commits/Dexuan-Cui/introduce-
> >> Hyper-V-VM-Sockets-hv_sock/20160715-223433
> >> config: x86_
When CONFIG_SPARSEMEM_EXTREME is disabled, __section_nr can get
the section number with a subtraction directly.
Signed-off-by: Zhou Chengming
---
mm/sparse.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/mm/sparse.c b/mm/sparse.c
index 5d0cf45..36d7bbb 10064
Hi Jiangang,
On 07/20/16 at 03:54am, Wei, Jiangang wrote:
> Hi Baoquan He,
>
> Well, Indeed there‘s a relationship between the dump-capture hangs in
> calibrate_delay_converge() and the interrupt mode.
>
> but there‘s no essential difference between your patches and mine that
> calls disable_IO_
From: Yeshaswi M R Gowda
Date: Mon, 18 Jul 2016 22:42:14 -0700
> +config CRYPTO_DEV_CHELSIO
> + tristate "Chelsio Crypto Co-processor Driver"
> + depends on PCI && NETDEVICES && ETHERNET
> + select CRYPTO_SHA1
> + select CRYPTO_SHA256
> + select CRYPTO_SHA512
> + select NE
During unrelated work, attempting to remove an include of the
linux/module.h in favour of "struct module;" in order to reduce
header entanglement, we found doing so caused a build failure in
this file.
mach-pxa/spitz.c: In function 'spitz_bl_kick_battery':
mach-pxa/spitz.c:524:2: error: implicit d
While working on some for-4.9 cleanups of linux/gpio/driver.h it was
found that changes there caused build failures when walking all the
ARM defconfigs, in ARM specific mach-* files.
The proposed GPIO header change is just this:
---
--- a/include/li
During unrelated work, attempting to remove an include of the
linux/module.h in favour of "struct module;" in order to reduce
header entanglement, we found doing so caused a build failure in
this file.
mach-pxa/corgi.c: In function 'corgi_bl_kick_battery':
mach-pxa/corgi.c:548:2: error: implicit d
During unrelated work, attempting to remove an include of the
linux/module.h in favour of "struct module;" in order to reduce
header entanglement, we found doing so caused a build failure in
this file.
It turns out this file uses __init_or_module which lives in the
module.h header, but it wasn't i
On Tue, 19 Jul 2016, Geert Uytterhoeven wrote:
> On Tue, Jul 19, 2016 at 6:52 AM, Greg Ungerer wrote:
> > Seeing as you have modified quite a few printk calls is it worth
> > while annotating them with appropriate KERN_ERR, KERN_INFO, etc?
>
> You mean pr_err(), pr_info(), ... ;-)
Done. Includ
On Tue, Jul 19, 2016 at 8:01 PM, Jeff Layton wrote:
> On Tue, 2016-07-19 at 14:27 +0200, Miklos Szeredi wrote:
>> > diff --git a/mm/mmap.c b/mm/mmap.c
>> index de2c1769cc68..a023caff19d5 100644
>> --- a/mm/mmap.c
>> +++ b/mm/mmap.c
>> @@ -126,7 +126,7 @@ static void __remove_shared_vm_struct(stru
From: Junzhi Zhao
When the resolution is set to 4k*2k, the hdmi
pixel clock will be 250MHz, however, the correct
pixel clock should be 297MHz. Fix this error by
adding the correct tvdpll clocks.
If MT8173 can support 4K, the vencpll clock should
be 800MHz. Add the vencpll clocks to support 4K.
S
From: Junzhi Zhao
In order to improve 4K resolution performance,
we have to enhance the HDMI driving currend
when clock rate is greater than 165MHz.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_mt8173_hdmi_phy.c | 89 +---
1 file
From: Junzhi Zhao
The mtk_hdmi_send_infoframe have to
be run after PLL and PIXEL clock of HDMI enable.
Make sure that HDMI inforframes can be sent
successfully.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_hdmi.c | 19 ---
1 file cha
From: Junzhi Zhao
Pixel clock should be 297MHz when resolution is 4K.
Signed-off-by: Junzhi Zhao
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 184 +---
1 file changed, 131 insertions(+), 53 deletions(-)
diff --git a/drivers/gpu/drm/medi
if MT8173 display module can support 4K HDMI output,
we have to adjust VENCPLL clock from default 660MHz
to 800MHz.
Signed-off-by: Bibby Hsieh
---
drivers/gpu/drm/mediatek/mtk_drm_drv.c |9 +
drivers/gpu/drm/mediatek/mtk_drm_drv.h |1 +
2 files changed, 10 insertions(+)
diff --g
This is MT8173 HDMI 4K support PATCH, based on 4.7-rc1.
In order to support HDMI 4K on MT8173,
we have to make some modifications.
1) Make sure that mtk_hdmi_send_infoframe is sent successfully.
2) Enhance the HDMI driving current to improve performance.
3) Make sure that pixel clock is 297MHz whe
Hi Ludovic,
I'm learning about the dmaengine subsystem and I was using the
at_xdmac as a reference.I'm not real familiar with tasklets
because I have used threaded interrupt handlers instead of them.
I noticed that the variable "txd" in the following block of code
(from the function at_xd
On 19/07/2016:04:29:07 PM, Alexandre Belloni wrote:
> Hi,
>
> On 18/07/2016 at 17:17:44 +0530, Pratyush Anand wrote :
> > Hi RTC-Maintainers,
> >
> >
> > On Mon, Jul 4, 2016 at 9:49 PM, Pratyush Anand wrote:
> > > On 27/06/2016:10:19:07 AM, Pratyush Anand wrote:
> > >> On 21/06/2016:10:25:34 AM
Hi Baoquan He,
Well, Indeed there‘s a relationship between the dump-capture hangs in
calibrate_delay_converge() and the interrupt mode.
but there‘s no essential difference between your patches and mine that
calls disable_IO_APIC() again.
Actually, disable_IO_APIC will set APIC to virtual wire m
1 - 100 of 970 matches
Mail list logo
