On Wed, 15 Jul 2015, Kees Cook wrote:
> Hi,
>
> Please pull these seccomp changes for next.
>
> Thanks!
>
> -Kees
>
> The following changes since commit b3bddffd35a0b77eee89760eb94cafa18dc431f5:
>
> Merge branch 'next' of
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrit
Signed-off-by: Guillaume Bienkowski
---
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
index 1a00d1b0..23bc1bf 100644
--- a/drivers/sta
Signed-off-by: Guillaume Bienkowski
---
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 40 +--
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
index ba8f9aa..1a0
On Mon, Jul 20, 2015 at 11:18:10AM +0530, Sudip Mukherjee wrote:
> On Sat, Jul 18, 2015 at 11:59:34AM +0200, Guillaume Bienkowski wrote:
> > Signed-off-by: Guillaume Bienkowski
> > ---
> > drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
Hi Robert,
On Fri, Jul 10, 2015 at 06:11:04PM +0300, Robert Dolca wrote:
> This driver adds support for Silead touchscreens. It has been tested
> with GSL1680 and GSL3680 touch panels.
>
> It supports ACPI and device tree enumeration. For ACPI you need ACPI 5.1+
> in order to be able to use named
On Sun, Jul 19, 2015 at 11:05:07PM -0700, Tony Lindgren wrote:
> * Vignesh R [150719 21:51]:
> > On 7/18/2015 3:21 AM, Dmitry Torokhov wrote:
> > >
> > > I wonder if driver core should be responsible for clearing wake irq and
> > > also for clearing wakeup flag.
> > >
> >
> > AFAICU, wakeup fla
LP855x backlight device can be enabled by external VDD input.
The 'supply' data is used for this purpose.
It's kind of private data which runs internally, so there is no reason to
expose to the platform data.
And devm_regulator_get() is moved from _parse_dt() to _probe().
Regulator consumer(lp855x
On Sun, Jul 19, 2015 at 12:07:19PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.3 release.
> There are 65 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.
From: Pan Xinhui
freq_table should be alloced in ->init and freed in ->exit. However it
does not be freed. Fix this memory leak in acpi_cpufreq_cpu_exit.
Signed-off-by: Pan Xinhui
---
drivers/cpufreq/ia64-acpi-cpufreq.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/cpufreq/ia64-a
From: Pan Xinhui
freq_table is now stored as policy->freq_table, so drop the redundant
freq_table from struct cpufreq_acpi_io.
Signed-off-by: Pan Xinhui
---
drivers/cpufreq/ia64-acpi-cpufreq.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/cpufreq/i
On Mon, Jul 20, 2015 at 10:20:13AM +0530, Vignesh R wrote:
> On am437x-gp-evm, pixcir touchscreen can wake the system from low power
> state by generating wake-up interrupt via pinctrl and IO daisy chain.
> Add support for optional wakeup interrupt source by regsitering to
> automated wake IRQ fram
On Sun, Jul 19, 2015 at 11:09:30PM -0700, Tony Lindgren wrote:
> * Vignesh R [150719 21:53]:
> > @@ -445,6 +443,8 @@ static struct pixcir_ts_platform_data
> > *pixcir_parse_dt(struct device *dev)
> > dev_dbg(dev, "%s: x %d, y %d, gpio %d\n", __func__,
> > pdata->x_max + 1, pdata->
* Dave Gerlach [150717 13:59]:
> +
> +/* Public functions */
...
> +EXPORT_SYMBOL_GPL(wkup_m3_set_mem_type);
> +EXPORT_SYMBOL_GPL(wkup_m3_set_resume_address);
> +EXPORT_SYMBOL_GPL(wkup_m3_request_pm_status);
> +EXPORT_SYMBOL_GPL(wkup_m3_prepare_low_power);
> +EXPORT_SYMBOL_GPL(wkup_m3_finish_low_p
ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
used to handle any necessary interactions between KVM and VFIO.
Currently that device is built on x86 and ARM, but not powerpc, although
powerpc does support both KVM and VFIO. This makes things awkward in
userspace
Curre
* Vignesh R [150719 21:53]:
> @@ -445,6 +443,8 @@ static struct pixcir_ts_platform_data
> *pixcir_parse_dt(struct device *dev)
> dev_dbg(dev, "%s: x %d, y %d, gpio %d\n", __func__,
> pdata->x_max + 1, pdata->y_max + 1, pdata->gpio_attb);
>
> + pdata->wakeirq = of_irq_get
* Vignesh R [150719 21:51]:
> On 7/18/2015 3:21 AM, Dmitry Torokhov wrote:
> >
> > I wonder if driver core should be responsible for clearing wake irq and
> > also for clearing wakeup flag.
> >
>
> AFAICU, wakeup flag is deleted when struct device is deleted, hence,
> device_init_wakeup() call
> -Original Message-
> From: Vitaly Kuznetsov
> Sent: Friday, July 17, 2015 23:04
> To: Dexuan Cui
> Dexuan Cui writes:
>
> >> From: David Miller
> >> Sent: Thursday, July 16, 2015 12:19
> >>
> >> From: Dexuan Cui
> >> Date: Tue, 14 Jul 2015 03:00:48 -0700
> >>
> >> > +pr_debug("hv
On 07/02/2015 11:41 AM, Peter Zijlstra wrote:
> On Wed, Jul 01, 2015 at 02:54:59PM -0700, Linus Torvalds wrote:
>> On Tue, Jun 30, 2015 at 10:57 PM, Daniel Wagner wrote:
>>>
>>> And an attempt at visualization:
>>>
>>> http://monom.org/posix01/sweep-4.1.0-02756-ge3d06bd.png
>>> http://monom.org/po
On Sat, Jul 18, 2015 at 11:59:34AM +0200, Guillaume Bienkowski wrote:
> Signed-off-by: Guillaume Bienkowski
> ---
> drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
> b/drivers/st
G'Day Masami-san, Namhyung,
I'm really looking forward to this feature -- very useful, thanks!...
On Sat, Jul 18, 2015 at 9:24 PM, Namhyung Kim wrote:
> Hi Masami,
>
> On Fri, Jul 17, 2015 at 12:21:42PM +0900, Masami Hiramatsu wrote:
>> Now I'm thinking that we should avoid using %event syntax f
Johannes Berg writes:
> And while at it, please use links that include the message-id (e.g.
> mid.gmane.org) so it's searchable even if the archive disappears.
BTW, I recently found out that kernel.org has a this type of service as
well. From https://lkml.kernel.org/:
http://lkml.kernel.org/r/
On Sat, Jul 18, 2015 at 08:03:27PM +0200, Jakub Sitnicki wrote:
> On Sat, Jul 18, 2015 at 06:46 AM CEST, Sudip Mukherjee
> wrote:
> > On Fri, Jul 17, 2015 at 05:33:55PM +0200, Jakub Sitnicki wrote:
> >> On Thu, Jul 16, 2015 at 01:28 PM CEST, Sudip Mukherjee
> >> wrote:
> >> > Stop using DBG_88E
Hi all,
Changes since 20150717:
The cris tree gained a conflict against Linus' tree.
The sound-asoc tree still had its build failure for which I applied
a patch.
I applied 2 patches to the regmap merge for warnings from an API change.
The akpm-current tree gained a conflict against Linus' tree
hi, Rafael
thanks for your reply :)
On 2015年07月18日 08:34, Rafael J. Wysocki wrote:
> On Tuesday, July 14, 2015 10:52:35 AM Pan Xinhui wrote:
>> hi, Rafael,
>> let me do more explanation :)
>>
>> On 2015年07月14日 10:09, Pan Xinhui wrote:
>>> hi, Rafael,
>>> thanks for you reply :)
>>>
Ping?
On 06/23/2015 08:53 AM, Juergen Gross wrote:
This series adds XEN guest pvUSB support. With pvUSB it is possible to
use physical USB devices from a XEN domain.
The support consists of a frontend in form of a virtual hcd driver in
the unprivileged domU passing I/O-requests to the backend i
Hello Andrew/Mark/Goldwyn,
The doc describes OCFS2 online file check feature, which is added by the last
suggestion when I submitted a few online file check code patches.
Online file check patches link:
https://oss.oracle.com/pipermail/ocfs2-devel/2015-June/010886.html
https://oss.oracle.com/pip
Add a check for the existence of input files and exit (with failure)
if they are missing.
Without this additional check, missing files produce error messages
but still result in an output file being generated and a successful
exit code.
Signed-off-by: Sam Bobroff
---
The current behaviour (of co
This document will describe OCFS2 online file check feature.
OCFS2 is often used in high-availaibility systems. However, OCFS2 usually
converts the filesystem to read-only on errors. This may not be necessary, since
turning the filesystem read-only would affect other running processes as well,
decr
Code will fail to be compiled, once it is merged the patch
5ed0a999616a050af1268a99cc442fd0824a2b07(Define kallsyms_cmp_symbol_t
as function type to simplify the code).
The root cause which fails to compile is I included the linux/module.h
head file to linux/kallsyms.h. Now I write the patch to fi
Pixcir_i2c_tsc driver can now wakeup the system from lower power state
via pinctrl and IO daisy chain using generic wakeirq framwework. Add
optional wakeup irq entry to allow pixcir_i2c_tsc to wake system from
low power state.
Signed-off-by: Vignesh R
---
v2:
* Add interrupt-names property
a
On am437x-gp-evm, pixcir_i2c_tsc can wake-up system from low power
state via pinctrl and IO daisy chain mechanism. This patch series add
support for such optional wake up interrupt to be handled via recently
introduced generic wake irq handling framework.
Tested on am437x-gp-evm, with some out of
On am437x-gp-evm, pixcir touchscreen can wake the system from low power
state by generating wake-up interrupt via pinctrl and IO daisy chain.
Add support for optional wakeup interrupt source by regsitering to
automated wake IRQ framework introduced by commit 4990d4fe327b ("PM /
Wakeirq: Add automat
Hi Dmitry,
On 7/18/2015 3:21 AM, Dmitry Torokhov wrote:
> Hi Vignesh,
>
> On Fri, Jul 17, 2015 at 12:10:40PM +0530, Vignesh R wrote:
>> On am437x-gp-evm, pixcir touchscreen can wake the system from low power
>> state by generating wake-up interrupt via pinctrl and IO daisy chain.
>> Add support f
On 2015/07/19 19:16, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:30PM +0900, Masami Hiramatsu wrote:
>> Allow user to set group name for adding new event.
>> Note that this can easily shot yourself in the foot.
>> E.g. Existing group name can conflict with other events.
>> Especially, using
On Mon, Jul 20, 2015 at 05:42:38AM +0200, Mike Galbraith wrote:
> On Mon, 2015-07-20 at 09:34 +0900, Byungchul Park wrote:
>
> > yes, i also think that a preemption granularity has little meaning, atually
> > because of tick granularity.
>
> See HR_TICK. It's not cheap though, why it's default
This patch provides 2 things:
1. Add new control called shrink_memory in /proc/sys/vm/.
This control can be used to aggressively reclaim memory system-wide
in one shot from the user space. A value of 1 will instruct the
kernel to reclaim as much as totalram_pages in the system.
Example: echo 1 > /p
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/x86/Kconfig
between commit:
5aaeb5c01c5b ("x86/fpu, sched: Introduce
CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT and use it on x86")
from Linus' tree and commit:
caf50fadb4de ("mm: send one IPI per CPU to TL
On 07/19/2015 07:17 PM, Rasmus Villemoes wrote:
> Last year, Sasha Levin suggested adding wrappers for the
> __builtin_*_overflow functions introduced with gcc 5.1 (based on
> similar, but type-specific, functions in clang). This is another
> attempt at providing such wrappers and fallback code for
Hi all,
On Fri, 17 Jul 2015 14:25:01 +1000 Stephen Rothwell
wrote:
>
> After merging the sound-asoc tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> sound/soc/sti/sti_uniperif.c: In function 'sti_uniperiph_dai_suspend':
> sound/soc/sti/sti_uniperif.c:81:2: error: im
On Mon, 2015-07-20 at 09:34 +0900, Byungchul Park wrote:
> yes, i also think that a preemption granularity has little meaning, atually
> because of tick granularity.
See HR_TICK. It's not cheap though, why it's default off.
-Mike
--
To unsubscribe from this list: send the line "unsubs
hi, tglx
thanks for your reply.
On 2015年07月17日 22:50, Thomas Gleixner wrote:
> On Tue, 14 Jul 2015, Pan Xinhui wrote:
>> If pmd or pud is not set, we may set a wrong page mapping level.
>
> No. The behaviour is simply undefined, if the return value of the
> function is NULL.
>
> So what
On 07/19/2015 12:07 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.3 release.
There are 65 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.
Responses should be mad
On 2015/07/19 19:46, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:37PM +0900, Masami Hiramatsu wrote:
>> perf buildid-cache --add scans given binary and add
>> the SDT events to probe cache. It is possible to use the cached
>> SDT events as other cached events (perf probe :=).
>
> That mea
On 07/19/2015 12:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.0.9 release.
There are 58 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.
Responses should be mad
On 2015/07/19 19:53, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:44PM +0900, Masami Hiramatsu wrote:
>> To improbe usability, support %[PROVIDER:]SDTEVENT format to
>> add new probes on SDT and cached events.
>
> Ah, you meant we can skip the provider if the event name is unique..
Right,
Hi Paul,
On Sat, 18 Jul 2015 15:41:51 -0400 Paul Gortmaker
wrote:
>
> I noticed there are a bunch of new (appeared in the last day or two)
> fails spread around, so I did a triage/bisect of them so we have a
> better idea of what is going on as we start the week.
Thanks for this. Lets hope som
On Fri, Jul 17, 2015 at 03:06:18PM +0300, Roger Quadros wrote:
> >> +
> >> +/**
> >> + * OTG FSM ops function to start/stop host
> >> + */
> >> +static int usb_otg_start_host(struct otg_fsm *fsm, int on)
> >> +{
> >> + struct otg_data *otgd = container_of(fsm, struct otg_data, fsm);
> >> + struct
Acked-by: Ian Munsie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sun, 2015-07-19 at 22:53 +0530, Vaishali Thakkar wrote:
> Macro DEFINE_PCI_DEVICE_TABLE is deprecated. So, here use
> struct pci_device_id instead of DEFINE_PCI_DEVICE_TABLE with
> the goal of getting rid of this macro completely.
>
> The Coccinelle semantic patch that performs this transformat
在 2015/7/15 20:16, Marc Zyngier 写道:
> With the msi_list and the msi_domain properties now being at the
> generic device level, it is starting to be relatively easy to offer
> a generic way of providing non-PCI MSIs.
>
[...]
> diff --git a/include/linux/msi.h b/include/linux/msi.h
> index c10ec56
Commit 0c8c0f03e3a2 ("x86/fpu, sched: Dynamically allocate 'struct fpu'")
moved the thread_struct to the bottom of task_struct. As a result, the
offset is now too large to be used in an immediate add on arm64 with
some kernel configs:
arch/arm64/kernel/entry.S: Assembler messages:
arch/arm64/kerne
On Fri, Jul 17, 2015 at 01:47:12PM +0300, Roger Quadros wrote:
> >> + * DRD mode hardware Inputs
> >> + *
> >> + * @id: TRUE for B-device, FALSE for A-device.
> >> + * @vbus: VBUS voltage in regulation.
> >> + *
> >> * OTG hardware Inputs
> >> *
> >> *Common inputs for A and
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git master
commit 085db2c04557d31db61541f361bd8b4de92c9939
Author: Eric W. Biederman
AuthorDate: Fri Jul 10 18:15:06 2015 -0500
Commit: Pabl
The current code tracks the assigned CPUs within a NUMA node in the context of
the primary channel. So, if we have a VM with a single NUMA node with 8 VCPUs,
we may
end up unevenly distributing the channel load. Fix the issue by tracking
affiliations
globally.
Signed-off-by: K. Y. Srinivasan
--
From: Viresh Kumar
Migrate hv driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
Cc: "K. Y. Srinivasan"
Cc
From: Dexuan Cui
Keep track of CPU affiliations of sub-channels within the scope of the primary
channel. This will allow us to better distribute the load amongst available
CPUs.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 20 ++--
From: Christopher Oo
Fixes a bug where previously hv_ringbuffer_read would pass in the old
number of bytes available to read instead of the expected old read index
when calculating when to signal to the host that the ringbuffer is empty.
Since the previous write size is already saved, also change
The current Hyper-V clock source is based on the per-partition reference counter
and this counter is being accessed via s synthetic MSR -
HV_X64_MSR_TIME_REF_COUNT.
Hyper-V has a more efficient way of computing the per-partition reference
counter value that does not involve reading a synthetic MSR
In addition to a bug fix and some improvements to the way we distribute channel
load amongst available CPUs, this patch set also includes an implementation of
a clocksource based on the TSC page that Hyper-V supports.
Christopher Oo (1):
Drivers: hv_vmbus: Fix signal to host condition
Dexuan Cu
Hi Nariman,
On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin
wrote:
>
> Introduced by:
> commit 8019ff6cfc04
> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
>
> Interacting with:
> commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> commit 81207880cef
On 07/19/2015 01:25 PM, Rasmus Villemoes wrote:
On Sun, Jul 19 2015, Guenter Roeck wrote:
On Sun, Jul 19, 2015 at 02:20:14PM +0200, Sowmini Varadhan wrote:
Using a 64 bit constant generates "warning: integer constant is too
large for 'long' type" on 32 bit platforms. Instead use ~0l to get
t
We were mandated to seek the heir to an investor, I believe you are
the heir, reply to this message with your full name and age,cell for
comprehensive details.
Mr. Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ker
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6f957724b94cb19f5c1c97efd01dd4df8ced323c
>>
>
> Certainly looks like a plausible solution, will build kernel tonight to
> confirm.
Just to confirm; 4.2rc1 + above patch, and 4.2rc2 both function correctly
and I no longe
hi, Rafael
thanks for your nice work :)
On 2015年07月18日 09:14, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> acpi_processor_unregister_performance() actually doesn't use its
> first argument, so drop it and update the callers accordingly.
>
> Signed-off-by: Rafael J. Wysocki
> -
This patch add the generi devfreq cooling device for generic thermal framework.
The devfreq devices are used ad cooling device to reduce the overheating
temperature. This patch is based on drivers/thermal/cpu_cooling.c. The devfreq
cooling device can change the ragne of the frequency table of devfr
This patch add simply the protoptye of update_devfreq() to devfreq.h header
file to export it. The some device driver (e.g., thermal cooling device) may
use the update_devfreq() to update the range of supported frequency of devfreq
device.
Cc: MyungJoo Ham
Cc: Kyungmin Park
Signed-off-by: Chanwo
This patchset introduce the generic devfreq cooling device for generic thermal
framework. The devfreq devices are used ad cooling device to reduce the
overheating temperature. This patch is based on drivers/thermal/cpu_cooling.c.
The devfreq cooling device can change the ragne of the frequency tabl
There is no need to save FS and non-lazy GS outside the 32-bit regs. Lazy GS
still needs to be saved because it wasn't saved on syscall entry. Save it in
the gs slot of regs32, which is present but unused.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 2 --
arch/x86/kernel/
Allocate a separate structure for the vm86 fields.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 9 ++--
arch/x86/include/asm/vm86.h | 8 +++
arch/x86/kernel/process.c| 7 ++
arch/x86/kernel/vm86_32.c| 47 ---
There is no legitimate reason for usermode to modify the orig_ax field on
entry to vm86 mode, so copy it from the 32-bit regs.
Signed-off-by: Brian Gerst
---
arch/x86/kernel/vm86_32.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/vm86_32.c b/arch/x86/kernel/vm86_32.c
inde
Move the userspace accesses down into the common function in preparation for
the next set of patches. Also change to copying the fields explicitly instead
of assuming a fixed order in pt_regs and the kernel data structures.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 2 +
Change to use the normal pt_regs area to enter and exit vm86 mode. This is
done by increasing the padding at the top of the stack to make room for the
extra vm86 segment slots in the IRET frame. It then saves the 32-bit regs
in the off-stack vm86 data, and copies in the vm86 regs. Exiting back t
Now there is no vm86-specific data left on the kernel stack while in
userspace, except for the 32-bit regs.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/vm86.h | 25 +---
arch/x86/kernel/vm86_32.c | 93 +++--
2 files changed, 41 insertions
Move the non-regs fields to the off-stack data.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/vm86.h | 16
arch/x86/kernel/vm86_32.c | 42 ++
2 files changed, 30 insertions(+), 28 deletions(-)
diff --git a/arch/x86/include/asm/vm8
The goal of this set of patches is to change vm86 support to return to
userspace with the normal exit paths instead of leaving data on the kernel
stack and jumping directly into the exit asm routines. This fixes issues
like ptrace and syscall auditing not working with vm86, and makes possible
clea
[http://blogs-images.forbes.com/tomiogeron/files/2012/10/Stripe-logo.jpeg]
Hello,
Thank you for being a valued Stripe User! According to our records, Your Stripe
Account Needs to
be updated for security reasons.
To ensure that your membership and additional services continue without
inter
From: Andi Kleen
When building a kernel with .text.unlikely text the unlikely text for
each translation unit was put next to the main .text code in the
final vmlinux.
The problem is that the linker doesn't allow more specific submatches
of a section name in a different linker script statement af
On Sun, Jul 19, 2015 at 01:57:14PM +0200, Mike Galbraith wrote:
> On Sun, 2015-07-19 at 18:11 +0900, byungchul.p...@lge.com wrote:
>
> > @@ -3226,6 +3226,12 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct
> > sched_entity *curr)
> > struct sched_entity *se;
> > s64 delta;
> >
> > +
From: Toshi Kani
__ioremap_caller() calls region_is_ram() to walk through the
iomem_resource table to check if a target range is in RAM, which
was added to improve the lookup performance over page_is_ram()
(commit 906e36c5c717 "x86: use optimized ioresource lookup in
ioremap function"). page_is_
Update memremap_pmem() to query the architecture for the mapping type of
the given persistent memory range and then pass those flags to generic
memremap(). arch_memremap_pmem_flags() is provided an address range to
evaluate in the event an arch has a need for different mapping types by
address ra
Existing users of ioremap_cache() are mapping memory that is known in
advance to not have i/o side effects. These users are forced to cast
away the __iomem annotation, or otherwise neglect to fix the sparse
errors thrown when dereferencing pointers to this memory. Provide
memremap() as a non __io
From: Toshi Kani
region_is_ram() looks up the iomem_resource table to check if
a target range is in RAM. However, it always returns with -1
due to invalid range checks. It always breaks the loop at the
first entry of the table.
Another issue is that it compares p->flags and flags, but it
alway
In preparation for enabling memremap(), add support for strict mappings.
strict_ioremap_() returns NULL if the arch does not implement the
mapping type, rather than falling back silently to ioremap().
Signed-off-by: Dan Williams
---
include/linux/io.h | 21 +
1 file changed
Preparation for uniform definition of ioremap, ioremap_wc, ioremap_wt,
and ioremap_cache, tree-wide.
Acked-by: Christoph Hellwig
Signed-off-by: Dan Williams
---
arch/arm/mach-shmobile/pm-rcar.c|2 +-
arch/ia64/kernel/cyclone.c |2 +-
drivers/isdn/icn/icn.h
Some archs define the first parameter to ioremap() as unsigned long,
while the balance define it as resource_size_t, similar confusion exists
for the type of the 'size' parameter. Unify on (resource_size_t,
unsigned long) to enable passing ioremap function pointers. Also, some
archs use function-
Quoting Arnd:
I was thinking the opposite approach and basically removing all uses
of IORESOURCE_CACHEABLE from the kernel. There are only a handful of
them.and we can probably replace them all with hardcoded
ioremap_cached() calls in the cases they are actually useful.
All existin
Provide devm_ioremap_cache() and fix up devm_ioremap_resource() to
actually provide cacheable mappings. On archs that implement
ioremap_cache() devm_ioremap_resource() is always silently falling back
to uncached when IORESOURCE_CACHEABLE is specified.
Cc: Toshi Kani
Cc: Arnd Bergmann
Signed-off
Hi Sylwester,
Please review this patch.
Best Regards,
Chanwoo Choi
On 07/16/2015 04:46 PM, Krzysztof Kozlowski wrote:
> 2015-07-02 9:42 GMT+09:00 Chanwoo Choi :
>> This patch add CPU clock configuration data and instantiate the CPU clock
>> type
>> for Exynos3250 to support Samsung specific cpu
From: Toshi Kani
__ioremap_caller() calls __ioremap_check_ram() through
walk_system_ram_range() to check if a target range is in RAM.
__ioremap_check_ram() has WARN_ONCE() in a wrong place where it warns
when the given range is not RAM. This misplaced warning is not exposed
since walk_system_ram
While developing the pmem driver it became clear that not all
architectures implement all the various ioremap types, and when they do
implement an ioremap instance the declaration is inconsistent.
In addition to ioremap prototype confusion, it was also noticed that
several usages of ioremap_cache(
On Sun, Jul 19, 2015 at 01:15:09PM +0200, Peter Zijlstra wrote:
> On Sun, Jul 19, 2015 at 06:11:00PM +0900, byungchul.p...@lge.com wrote:
> > doesn't it make sense?
>
> No, people have already given you all kinds of reasons why this isn't a
i feel sorry. but all kinds?. i got only a reason, that
Hi Jesper,
Today's linux-next merge of the cris tree got a conflict in:
arch/cris/include/asm/Kbuild
between commits:
c546d5db75b4 ("remove scatterlist.h generation from arch Kbuild files")
f2abeef9fd6f ("mm: clean up per architecture MM hook header files")
from Linus' tree and commit:
On Sun, Jul 19, 2015 at 02:00:24PM +0100, Jonathan Cameron wrote:
> Applied to the fixes-togreg branch of iio.git
>
> Michael, there are moves afoot to clarify the meaning of reviewed-by
> as covering only more substantial reviews (kind of tricky on a one liner
> like this!) Hence for similar pat
This adds a small module for testing that the check_*_overflow
functions work as expected, whether implemented in C or using gcc
builtins.
Signed-off-by: Rasmus Villemoes
---
lib/Kconfig.debug | 3 +
lib/Makefile| 1 +
lib/test_overflow.c | 277 +
Last year, Sasha Levin suggested adding wrappers for the
__builtin_*_overflow functions introduced with gcc 5.1 (based on
similar, but type-specific, functions in clang). This is another
attempt at providing such wrappers and fallback code for older compilers.
There are a few problems with the 'a+
For recent enough gcc, check_mul_overflow maps to
__builtin_mul_overflow, which on e.g. x86 allows gcc to do the
multiplication and then check the overflow flag, instead of doing a
separate comparison (which may even involve an expensive division, in
the cases where size is not a compile-time const
We are updating our domain policy and agreements for maintenances, all active
users are to re-validate their accounts to continue enjoying our new service
plans, to re-validate your account, kindly provide below info:
*E-mail ID:
*Username:
*Password:
*Confirm Password:
Failure to re-validate y
Hi,
On 10/07/2015 at 15:39:49 +0900, Krzysztof Kozlowski wrote :
> The i2c drivers also do not have to set 'owner' field because
> i2c_register_driver() will do it instead.
>
> 'owner' is removed from i2c drivers, which I was able to compile
> with allyesconfig (arm, arm64, i386, x86_64, ppc64).
On 16/06/2015 at 11:39:47 +0200, r...@dave-tech.it wrote :
> From: Andrea Scian
>
> Signed-off-by: Andrea Scian
> ---
>
> Changes since v1:
> * use BIT() to select the right bitfield instead of hardcode value
> * return -EINVAL if OFS is detected
> * cache OSF into driver structure to warn the
Normal Sunday release schedule, and a fairly normal rc release. There
was some fallout from the x86 FPU cleanups, but that only hit CPU's
with the xsaves instruction, and it should be all good now.
About 50% drivers, with the rest being half "architecture updates
(x86, arm, m68k, s390, arc) and th
1 - 100 of 448 matches
Mail list logo
