On Tue, 2016-02-16 at 14:48 +0100, Hans Verkuil wrote:
> Hi Tiffany,
>
> > +int mtk_vcodec_enc_queue_init(void *priv, struct vb2_queue *src_vq,
> > + struct vb2_queue *dst_vq)
> > +{
> > + struct mtk_vcodec_ctx *ctx = priv;
> > + int ret;
>
* Toshi Kani wrote:
> Add comments to __copy_user_nocache() to clarify its procedures
> and alignment requirement.
>
> Also change numeric branch target labels to named labels. The
> labels begin with ".L" and prefix "cun" (Copy User Nocache) to
> keep them local and unique to the function.
S
On Tue, Feb 16, 2016 at 10:03:24PM -0500, Martin K. Petersen wrote:
> > "Tyrel" == Tyrel Datwyler writes:
>
> >> Is there some reason you didn't carry the review tag over from this:
> >>
> >> http://mid.gmane.org/20160204084459.gw27...@c203.arch.suse.de
> >>
> >> ?
> >>
> >> James
>
> Tyr
Apparently some preprocessors have problems with interpreting
BUILD_BUG_ON such as:
var = ARRAY_SIZE(s2mps15_regulators);
BUILD_BUG_ON(S2MPS_REGULATOR_MAX < var);
so let make it more obvious for them.
Additionally add missing BUILD_BUG_ON check for S2MPS15 device (the
check ensures
From: Magnus Damm
The sh-pfc pinctrl driver is currently handling SoC-specific
PFC hardware blocks on ARM64, ARM and SH architectures.
For older SoCs using SH cores and some 32-bit ARM SoCs the PFC
hardware also provides GPIO functionality. On the majority of
32-bit ARM SoCs from Renesas and so
Mike,
On 02/16/2016 09:13 PM, Michael Turquette wrote:
> Quoting Mark Brown (2016-02-16 05:42:33)
>> On Tue, Feb 16, 2016 at 11:46:52AM +0200, Peter Ujfalusi wrote:
>>
>>> As for codecs, tlv320aic3106 is also pretty simple device from the outside,
>>> it
>>> can receive it's reference clock via:
Hi Sebastian
Am Freitag, 12. Februar 2016, 10:07:59 schrieben Sie:
...
> What about rt4? It is only the stable update so you should see here the
> numbers from rt3. If that is true and your numbers are stable it should
> be easy to run git bisect between rt4 and rt5. And looking at
> https://git
* Andy Lutomirski wrote:
> On Feb 15, 2016 12:14 PM, "Borislav Petkov" wrote:
> >
> > ---
> > From: Borislav Petkov
> > Date: Mon, 15 Feb 2016 19:50:33 +0100
> > Subject: [RFC PATCH] x86/FPU: Fix double FPU regs activation
> >
> > On the entry_INT80_32->do_syscall_32_irqs_on path on 32-bit we
On Tue, Feb 02, 2016 at 11:41:56PM +0300, Yury Norov wrote:
> > However I'll try to write an addon patch to your patch series. Maybe we can
> > still get rid of compat_wrapper.c in a way which makes both of us happy.
> > Also.. the idea with the alias names for compat wrappers does seem to have
> >
* Alexander Kuleshov wrote:
> void __init setup_arch(char **cmdline_p)
> {
> + struct ramdisk ramdisk_image = {
> + .start_addr = get_ramdisk_image(),
> + .size = get_ramdisk_size(),
> + .reserve_ramdisk = true
> + };
> +
> + /* Assume only end
* Byungchul Park wrote:
> Is there any reason keeping this statement on the code?
>
> -8<-
> From d8a387efb8199b69b6464970d6f9fc57cbcf0ab0 Mon Sep 17 00:00:00 2001
> From: Byungchul Park
> Date: Thu, 11 Feb 2016 11:50:53 +0900
> Subject: [PATCH] sched: remove an unnecessary memory acce
On 02/17/16 09:01, tiffany lin wrote:
> On Tue, 2016-02-16 at 14:48 +0100, Hans Verkuil wrote:
>> Hi Tiffany,
>>
>>> +int mtk_vcodec_enc_queue_init(void *priv, struct vb2_queue *src_vq,
>>> + struct vb2_queue *dst_vq)
>>> +{
>>> + struct mtk_vcodec_ctx
Hi Hans,
On Wed, 2016-02-17 at 08:47 +0100, Hans Verkuil wrote:
> On 02/16/2016 07:37 AM, tiffany lin wrote:
> >>> +static int fops_vcodec_open(struct file *file)
> >>> +{
> >>> + struct video_device *vfd = video_devdata(file);
> >>> + struct mtk_vcodec_dev *dev = video_drvdata(file);
> >>> + stru
The "translate_scan" function in rtl8712 uses a lot of stack, and
gets inlined into its single caller, r8711_wx_get_scan, which
in some configurations now blows the 1024 byte stack warning
limit:
drivers/staging/rtl8712/rtl871x_ioctl_linux.c: In function 'r8711_wx_get_scan':
drivers/staging/rtl871
On Tue, 16 Feb 2016, Jessica Yu wrote:
> Remove the ftrace module notifier in favor of directly calling
> ftrace_module_enable() and ftrace_release_mod() in the module loader.
> Hard-coding the function calls directly in the module loader removes
> dependence on the module notifier call chain and
Hi Magnus,
On Wed, Feb 17, 2016 at 9:15 AM, Magnus Damm wrote:
> From: Magnus Damm
>
> The sh-pfc pinctrl driver is currently handling SoC-specific
> PFC hardware blocks on ARM64, ARM and SH architectures.
>
> For older SoCs using SH cores and some 32-bit ARM SoCs the PFC
> hardware also provide
Arnd Bergmann writes:
> ixp4xx is really special in that it performs hardware swapping for
> internal devices based on CPU endianess but not on PCI devices.
Again, IXP4xx does not perform hardware (nor any other) swapping for
registers of on-chip devices. The registers are connected 1:1,
bit 0 t
* Alfredo Alvarez Fernandez wrote:
> From: Alfredo Alvarez Fernandez
>
> The chain_key hashing macro iterate_chain_key(key1, key2) does not
> generate a new different value if both key1 and key2 are 0. In that
> case the generated value is again 0. This can lead to collisions which
> can resul
Hi Mathias,
Thanks for your time.
On 02/16/2016 10:19 PM, Mathias Nyman wrote:
> Hi
>
> Most of my concerns are due to the early printk restrictions.
> As you say in the documentation:
> "Keep in mind that things such as interrupt, system memory, DMA memory,
> PCI configure space access, etc., ar
Should check and show correct return value of update_dent_inode in
->rename.
Signed-off-by: Chao Yu
---
fs/f2fs/namei.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index 6f944e5..99ed009 100644
--- a/fs/f2fs/namei.c
+++ b/fs/f2fs/nam
On 2016/2/17 8:35, David Rientjes wrote:
> On Tue, 16 Feb 2016, Greg Kroah-Hartman wrote:
>
>> On Tue, Feb 16, 2016 at 05:37:05PM +0800, Xishi Qiu wrote:
>>> Currently tasksize in lowmem_scan() only calculate rss, and not include
>>> swap.
>>> But usually smart phones enable zram, so swap space
This patch add mediatek iommu dts binding document.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../devicetree/bindings/iommu/mediatek,iommu.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
d
This patch add smi binding document and smi local arbiter header file.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../memory-controllers/mediatek,smi-common.txt | 24 +
.../memory-controllers/mediatek,smi-larb.txt | 25 +
include/dt-bindings/memory/mt8173-larb-port.h
This patch set adds support for m4u(Multimedia Memory Management Unit),
Currently it only support the m4u with 2 levels of pagetable on mt8173.
It's based on Robin Murphy's Short-descriptor v3[1].
Please check the hardware block diagram of Mediatek IOMMU.
m4u (Multimedia Me
On 02/17/2016 03:31 AM, Al Viro wrote:
> On Mon, Feb 15, 2016 at 03:35:19PM +0100, Andrzej Hajda wrote:
>> IS_ERR_VALUE should be used only with unsigned long type.
>> Otherwise it can work incorrectly. To achieve this function
>> xt_percpu_counter_alloc is modified to return unsigned long,
>> and
This patch add SMI(Smart Multimedia Interface) driver. This driver
is responsible to enable/disable iommu and control the power domain
and clocks of each local arbiter.
Signed-off-by: Yong Wu
Tested-by: Philipp Zabel
Reviewed-by: Daniel Kurtz
Tested-by: Daniel Kurtz
Signed-off-by: Matthias Bru
When doing test with fstests/generic/068 in inline_dentry enabled f2fs,
following oops dmesg will be reported:
[ cut here ]
WARNING: CPU: 5 PID: 11841 at fs/inode.c:273 drop_nlink+0x49/0x50()
Modules linked in: f2fs(O) ip6table_filter ip6_tables ebtable_nat ebtables
nf_
This patch adds support for mediatek m4u (MultiMedia Memory Management
Unit).
Signed-off-by: Yong Wu
Reviewed-by: Robin Murphy
---
drivers/iommu/Kconfig | 16 +
drivers/iommu/Makefile| 1 +
drivers/iommu/mtk_iommu.c | 732 ++
3 files change
This patch add the iommu/larbs nodes for mt8173
Signed-off-by: Yong Wu
Reviewed-by: Daniel Kurtz
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 81
1 file changed, 81 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/med
On Wed, Feb 17, 2016 at 09:31:09AM +0100, Ingo Molnar wrote:
>
> * Byungchul Park wrote:
>
> > Is there any reason keeping this statement on the code?
> >
> > -8<-
> > From d8a387efb8199b69b6464970d6f9fc57cbcf0ab0 Mon Sep 17 00:00:00 2001
> > From: Byungchul Park
> > Date: Thu, 11 Feb
On Wed, Feb 17, 2016 at 03:28:10PM +0800, qiujiang wrote:
> This patch modifies the DesignWare GPIO controller driver to
> support the GPIO-signaled ACPI Events. This is used for power
> button function on ARM server.
>
> To make it work, the _AEI and _EVT object must be defined in
> the correspon
On Tue, Feb 16, 2016 at 02:42:02PM +0100, Arnd Bergmann wrote:
> On Tuesday 16 February 2016 13:56:45 Andreas Irestål wrote:
> > Currently, it is only possible to configure HW-specific options to the
> > adau17x1 codecs by providing a platform data struct. With this patch,
> > it is possible to pro
Hi,
your first statement “bfq is using bandwidth as the virtual time" is not very
clear to me. In contrast, after that you raise a clear, important issue. So, I
will first try to sync with you on your first statement (and hopefully help
find related bugs in the documentation of BFQ). Then I will
On Tue, 16 Feb 2016 23:08:13 +0100,
Arnd Bergmann wrote:
>
> On Tuesday 16 February 2016 18:26:09 Arnd Bergmann wrote:
> > > return err;
> > > per_pin->acomp_jack = jack;
> > > - jack->private_data = per_pin;
> > > - jack->private_free = free_acomp_jack_priv;
>
On Wed, 2016-02-17 at 09:58 +0200, Heikki Krogerus wrote:
> On Tue, Feb 16, 2016 at 02:39:47PM +0100, Oliver Neukum wrote:
> > On Tue, 2016-02-16 at 11:22 +0200, Heikki Krogerus wrote:
> > > > That question has not been answered. It would be awkward for the OS
> > > > to find itself in the slave ro
Il giorno 11/feb/2016, alle ore 23:28, Tejun Heo ha scritto:
> Hello,
>
> On Mon, Feb 01, 2016 at 11:12:46PM +0100, Paolo Valente wrote:
>> From: Arianna Avanzini
>>
>> Complete support for full hierarchical scheduling, with a cgroups
>> interface. The name of the added policy is bfq.
>>
>>
change from v2 to v3
- the way to solve it in v2 is racy, so I changed the approach entirely.
- just make semaphore's trylock use spinlock's trylock.
change from v1 to v2
- remove unnecessary overhead by the redundant spin(un)lock.
Since I faced a infinite recursive printk() bug, I've tried to pr
The check and definitions related to ramdisk are similar in the
early_reserve_initrd() and reserve_initrd() functions.
This patch introduces struct ramdisk which contains information
about initrd. This structure will be filled in the setup_arch()
and passed to the reserve_initrd() and relocate_ini
On Wed, 2016-02-17 at 09:31 +0100, Hans Verkuil wrote:
> On 02/17/16 09:01, tiffany lin wrote:
> > On Tue, 2016-02-16 at 14:48 +0100, Hans Verkuil wrote:
> >> Hi Tiffany,
> >>
> >>> +int mtk_vcodec_enc_queue_init(void *priv, struct vb2_queue *src_vq,
> >>> +struct vb
Hi Takashi,
[auto build test ERROR on sound/for-next]
[also build test ERROR on v4.5-rc4 next-20160217]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Takashi-Iwai/ALSA-jack-Allow-building
* Alexander Kuleshov wrote:
> - early_reserve_initrd();
> + if (!boot_params.hdr.type_of_loader || !ramdisk_image.start_addr ||
> !ramdisk_image.size)
> + ramdisk_image.reserve_ramdisk = false; /* No initrd provided
> by bootloader */
> + else
> + memblock_
Hello,
On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
On 16.02.2016 00:21, Javier Martinez Canillas wrote:
Hello Krzysztof,
On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote:
The driver's init and exit function don't do anything besides a
* Byungchul Park wrote:
> diff --git a/kernel/locking/semaphore.c b/kernel/locking/semaphore.c
> index b8120ab..6634b68 100644
> --- a/kernel/locking/semaphore.c
> +++ b/kernel/locking/semaphore.c
> @@ -130,13 +130,14 @@ EXPORT_SYMBOL(down_killable);
> int down_trylock(struct semaphore *sem)
>
On Wed, Feb 17, 2016 at 09:16:46AM +0100, Ingo Molnar wrote:
> So I'm wondering why this started triggering only now. Is this a pre-existing
> bug
> that somehow got triggered via:
>
> 58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs
>
> ?
Well, that's an interesting question. See, the
On Tue, Feb 16, 2016 at 09:48:58PM -0800, Andy Lutomirski wrote:
> On Tue, Feb 2, 2016 at 9:46 PM, Andy Lutomirski wrote:
> > This switches virtio to use the DMA API on Xen and if requested by
> > module option.
>
> Michael, any update on this?
>
> --Andy
I was hoping for an explicit ack from D
* Toshi Kani wrote:
> x86 does not define ARCH_HAS_VALID_PHYS_ADDR_RANGE, which
> leads /dev/mem to use the default valid_phys_addr_range()
> and valid_mmap_phys_addr_range() in drivers/char/mem.c.
>
> The default valid_phys_addr_range() allows any range lower
> than __pa(high_memory), which is
Hi Andy,
Andy Shevchenko 於 2016/2/16 下午 05:11 寫道:
On Tue, 2016-02-16 at 14:55 +0800, Peter Hung wrote:
+static u32 baudrate_table[] = { 150, 1152000, 921600 };
+static u8 clock_table[] = { F81504_CLKSEL_24_MHZ,
F81504_CLKSEL_18DOT46_MHZ,
+ F81504_CLKSEL_14DOT77
On Wed 17-02-16 15:22:27, Satoru Takeuchi wrote:
> Since __GFP_NOACCOUNT is removed by the following commit,
> its description is not necessary.
>
> commit 20b5c3039863 ("Revert 'gfp: add __GFP_NOACCOUNT'")
>
> Signed-off-by: Satoru Takeuchi
Acked-by: Michal Hocko
> ---
> include/linux/gfp.h
On Monday 15 February 2016 08:00:50 Dave Chinner wrote:
> On Sat, Feb 13, 2016 at 05:46:11PM -0800, Deepa Dinamani wrote:
> > On Sat, Feb 13, 2016 at 2:08 PM, Dave Chinner wrote:
> > > On Fri, Feb 12, 2016 at 01:36:05AM -0800, Deepa Dinamani wrote:
> So, excuse me if I made a mistake and missed s
On 17.02.2016 18:27, Marek Szyprowski wrote:
> Hello,
>
> On 2016-02-16 00:20, Krzysztof Kozlowski wrote:
>> On 16.02.2016 00:21, Javier Martinez Canillas wrote:
>>> Hello Krzysztof,
>>>
>>> On 02/15/2016 03:54 AM, Krzysztof Kozlowski wrote:
On 12.02.2016 13:30, Javier Martinez Canillas wrote
* Borislav Petkov wrote:
> On Wed, Feb 17, 2016 at 09:16:46AM +0100, Ingo Molnar wrote:
> > So I'm wondering why this started triggering only now. Is this a
> > pre-existing bug
> > that somehow got triggered via:
> >
> > 58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs
> >
> > ?
>
>
On Wed, Feb 17, 2016 at 04:34:16AM +0100, Oleg Nesterov wrote:
> Finally I reproduced... let me add CC's and reply to initial message. This has
> nothing to do with arm/uprobes.
>
> I simply can't understand how perf calculates ->total_time_enabled/running.
> At all. But the problem is that
>
>
On Wed, 17 Feb 2016 10:03:50 +0100,
Takashi Iwai wrote:
> --- a/sound/core/Kconfig
> +++ b/sound/core/Kconfig
> @@ -24,11 +24,14 @@ config SND_RAWMIDI
> config SND_COMPRESS_OFFLOAD
> tristate
>
> -# To be effective this also requires INPUT - users should say:
> -#select SND_JACK if INP
On Tue, Feb 16, 2016 at 09:52:19PM -0700, Jason Gunthorpe wrote:
> On Wed, Feb 17, 2016 at 02:27:54AM +0200, Jarkko Sakkinen wrote:
> > - if (acpi_dev_resource_memory(ares, &res))
> > + if (acpi_dev_resource_memory(ares, &res)) {
> > + res.name = NULL;
>
> What? How is this not a bug
On Tue, Feb 16, 2016 at 05:03:21PM -0300, Javier Martinez Canillas wrote:
> After sub-dev registration in v4l2_async_test_notify(), the v4l2-async
> core calls the registered_async callback but if a sub-dev driver does
> not implement it, v4l2_subdev_call() will return a -ENOIOCTLCMD which
> should
On Wednesday 17 February 2016 10:35:40 Takashi Iwai wrote:
> From: Takashi Iwai
> Subject: [PATCH v2] ALSA: jack: Allow building the jack layer without
> input device
>
> Since the recent integration of kctl jack and input jack layers, we
> can basically build the jack layer even without input d
On Wed, 2016-02-17 at 11:29 +0200, Michael S. Tsirkin wrote:
>
> I was hoping for an explicit ack from David Woodhouse,
> but I guess the informal "let's not hold this up"
> that was sent on v5 will do.
Apologies; I was working under that assumption too.
--
dwmw2
smime.p7s
Description: S/MIM
This patchset is based on v4.5-rc3 tag and its tested on
Broadcom Cygnus SoC.
The patches can be fetched from iproc-tsc-v2 branch of
https://github.com/Broadcom/arm64-linux.git
Changes since v1:
- Enhanced touchscreen driver to handle syscon based register access if
"brcm,iproc-touchscreen-sy
In Cygnus SOC touch screen controller registers are shared
with ADC and flex timer. Using readl/writel could lead to
race condition. So in such case register access is handled
through syscon framework API's in the touch screen driver.
This feature is enabled if "brcm,iproc-touchscreen-syscon"
compa
In Cygnus SOC touch screen controller registers are shared
with ADC and flex timer. Using readl/writel could lead to
race condition. So touch screen driver is enhanced to support
1. If touchscreen register's are not shared. Register access
is handled through readl/writel if "brcm,iproc-touchscreen
In Cygnus SOC touch screen controller registers are shared
with ADC and flex timer. Using readl/writel could lead to
race condition. So touch screen driver is enhanced to support
1. If touchscreen register's are not shared. Register access
is handled through readl/writel if "brcm,iproc-touchscreen
* David Long wrote:
> On 02/09/2016 04:45 AM, Ingo Molnar wrote:
> >
> >* Michael Ellerman wrote:
> >
> >>On Tue, 2016-02-09 at 00:38 -0500, David Long wrote:
> >>
> >>>From: "David A. Long"
> >>>
> >>>Move duplicate and functionally equivalent code for accessing registers
> >>>and stack (CONF
On Wednesday 17 February 2016 15:13:44 Raveendra Padasalagi wrote:
> +
> + ts_adc_syscon: ts_adc_syscon@0x180a6000 {
> + compatible = "syscon";
> + reg = <0x180a6000 0xc30>;
> + };
>
This should have a more specific compatible string in addition to the
gene
Hi, Rob
On 2016年02月15日 15:15, Wei Ni wrote:
> Hi, Rob
>
> On 2016年02月12日 22:42, Rob Herring wrote:
>> On Fri, Jan 29, 2016 at 2:47 AM, Wei Ni wrote:
>>> Add hw-trips sub-node for soctherm, which is
>>> used to describe the hardware trip points for
>>> each soctherm sensors.
>>
>> I still don't u
Hi Andrew,
although this can be folded into patch 5
(mm-oom_reaper-implement-oom-victims-queuing.patch) I think it would be
better to have it separate and revert after we sort out the proper
oom_kill_allocating_task behavior or handle exclusion at oom_reaper
level.
Thanks!
---
>From 7d8c953994f97f
All the other members of the union got a nice comment
what they represent. Let's fix for context as well.
Signed-off-by: Daniel Wagner
---
parse.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/parse.h b/parse.h
index 0c34ec2..195f0fd 100644
--- a/parse.h
+++ b/parse.h
@@ -5
Signed-off-by: Daniel Wagner
---
linearize.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linearize.c b/linearize.c
index c6ada1e..da3a190 100644
--- a/linearize.c
+++ b/linearize.c
@@ -441,7 +441,7 @@ const char *show_instruction(struct instruction *insn)
b
Hi,
Locking can be tricky to get right and sometimes things go wrong. This
here is/was an attempt to come up with a simple static code analysis tool
which tries to point to problematic looking.
Especially figurering out if an access to variables wihtout holding
the right lock is happenin was of i
I was playing a bit around to see if it is possible to figure out if a
variable is accessed without holding the corresponding lock. This never
got anywhere and that's why I abandon it. In case someone wants to
use parts of it or whatever, please be my guest.
Example output:
./test-locks validatio
Add the function context attributes and the context instruction
to the model.
Signed-off-by: Daniel Wagner
---
ast-inspect.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/ast-inspect.c b/ast-inspect.c
index 24d4a4a..4502575 100644
--- a/ast-inspe
On Tue, Feb 16, 2016 at 08:31:19PM -0500, Waiman Long wrote:
> Linked list is used everywhere in the Linux kernel. However, if many
> threads are trying to add or delete entries into the same linked list,
> it can create a performance bottleneck.
>
> This patch introduces a new per-cpu list subyst
> -Original Message-
> From: Arnd Bergmann [mailto:a...@arndb.de]
> Sent: 17 February 2016 15:16
> To: Raveendra Padasalagi
> Cc: Dmitry Torokhov; Russell King; Rob Herring;
devicet...@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org; linux-in...@vger.kernel.org; Pawel
Moll;
> Mark R
The static clang and also gcc knows this attributes and they
are used to do thread safety analysis.
Signed-off-by: Daniel Wagner
Link: http://clang.llvm.org/docs/ThreadSafetyAnalysis.html
---
allocate.c | 1 +
allocate.h | 1 +
parse.c| 64 ++
On Wed, Feb 17, 2016 at 01:13:26AM +0530, Vaishali Thakkar wrote:
> Currently incorrect default hugepage pool size is reported by proc
> nr_hugepages when number of pages for the default huge page size is
> specified twice.
>
> When multiple huge page sizes are supported, /proc/sys/vm/nr_hugepages
Some Lenovo ideapad models lack a physical rfkill switch.
On Lenovo models ideapad Y700 Touch-15ISK and ideapad Y700-15ISK,
ideapad-laptop would wrongly report all radios as blocked by
hardware which caused wireless network connections to fail.
Add these models without an rfkill switch to the no_
17.02.2016 10:21, Ingo Molnar пишет:
>
> * Andy Lutomirski wrote:
>
>> + * If the kernel ever adds explicit fs, gs, fsbase, and gsbase
>> + * save/restore, it will most likely need to be opt-in and use
>> + * different context slots.
>
> Btw., that's not necessarily true: it could a
On 16/02/16 07:20, Krzysztof Kozlowski wrote:
> Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
> so it is built also on ARMv7. This does not bring any kind of benefit.
> There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like
> multi_v7 for ARMv7).
>
> Instead
On Tue, Feb 16, 2016 at 04:43:51PM -0800, Greg Kroah-Hartman wrote:
On Tue, Feb 16, 2016 at 11:14:26AM +, Brian Starkey wrote:
Hi Greg,
Is the documentation OK? Is there any chance of you picking up this
series?
I can rebase onto -next if that's the right place, but they still apply
on 4.5
Wi-Fi on ASUS X75VD laptop does not work unless asus_nb_wmi module
is loaded with wapf=4 option. Add quirk for this.
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/platform/x86/asus-nb-wmi.c
b/drivers/platform/x86/asus-nb-wmi.c
index
Hi Linus,
Linus Walleij 於 2016/2/16 下午 11:22 寫道:
On Tue, Feb 16, 2016 at 7:55 AM, Peter Hung wrote:
Suggested-by: One Thousand Gnomes
Suggested-by: Andy Shevchenko
Signed-off-by: Peter Hung
Acked-by: Linus Walleij
It's fine with me if this is queued in MFD, serial or whatever tree, or
On Wed, 17 Feb, at 08:59:18AM, Ingo Molnar wrote:
>
> I've pulled it all, so tip:x86/urgent should have everything needed. Please
> let me
> know if anything is amiss - I intend to send the fixes to Linus tomorrow-ish.
Looks good. Thanks Ingo.
Hi Andrew,
Thanks for the patches, they look good.
Do we have any reason why we should not move these drivers from
drivers/misc/eeprom to drivers/nvmem?
--srini
On 16/02/16 23:41, Andrew Lunn wrote:
This patch set converts the old EEPROM drivers in driver/misc/eeprom to
use the NVMEM fram
On 16/02/16 23:41, Andrew Lunn wrote:
The setup() callback is not used by any in kernel code. Remove it.
Any new code which requires access to the eeprom can use the NVMEM
API.
Signed-off-by: Andrew Lunn
Makes sense to clean this bits.. :-)
Acked-by: Srinivas Kandagatla
---
drivers/m
Thanks for the patch,
On 16/02/16 23:41, Andrew Lunn wrote:
Legacy AT24, AT25 EEPROMs are exported in sys so that only root can
read the contents. The EEPROMs may contain sensitive information. Add
a flag so the provide can indicate that NVMEM should also restrict
access to root only.
This pat
On 16/02/16 23:41, Andrew Lunn wrote:
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Set the NVMEM config structure to enable backward, so
that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
This patch looks good to me,
On 16/02/16 23:41, Andrew Lunn wrote:
Now that the AT24 uses the NVMEM framework, replace the
memory_accessor in the setup() callback with nvmem API calls.
Signed-off-by: Andrew Lunn
Acked-by: Srinivas Kandagatla
---
arch/arm/mach-davinci/board-mityomapl138.c | 5 +++--
arch/arm/mac
On 16/02/16 23:41, Andrew Lunn wrote:
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backwards compatibility in the NVMEM config,
so that the 'eeprom' file in sys is provided by the framework.
Signed-off-by: Andrew Lunn
Minor Nit, once fixed feel f
On 16/02/16 23:41, Andrew Lunn wrote:
Add a regmap for accessing the EEPROM, and then use that with the
NVMEM framework. Enable backward compatibility in the MVMEM config
structure, so that the 'eeprom' file in sys is provided by the
framework.
Signed-off-by: Andrew Lunn
Looks good.
Acked-
The check and definitions related to ramdisk are similar in the
early_reserve_initrd() and reserve_initrd() functions.
This patch introduces struct ramdisk which contains information
about initrd. This structure will be filled in the setup_arch()
and passed to the reserve_initrd() and relocate_ini
On 16/02/16 23:41, Andrew Lunn wrote:
Older drivers made an 'eeprom' file available in the /sys device
directory. Have the NVMEM core provide this to retain backwards
compatibility.
Signed-off-by: Andrew Lunn
---
v4: Add lockdep support
---
drivers/nvmem/core.c | 84 ++
On Wed, Feb 17, 2016 at 10:17:39AM +, Srinivas Kandagatla wrote:
>
>
> On 16/02/16 23:41, Andrew Lunn wrote:
> >Add a regmap for accessing the EEPROM, and then use that with the
> >NVMEM framework. Set the NVMEM config structure to enable backward, so
> >that the 'eeprom' file in sys is provi
Check if a EC has andy PD ports and register a USB PD charger device if
so.
Signed-off-by: Tomeu Vizoso
---
Changes in v3:
- Only register the PD charger device if there are any PD ports in this
EC.
- Dropped patch using EC_CMD_GET_FEATURES to decide whether to create a
charger device becaus
Hi,
this series contains a driver that exposes a power_supply to userspace
representing a port that support USB PD charging.
Allows userspace to display to the user if the machine is charging and
on which port, and if another device is being charged by a port.
Thanks,
Tomeu
Changes in v3:
- Re
This function returns the code for the host event that triggered the
interrupt that is being currently handled.
Is to be used by observers of the event_notifier in the EC device.
Signed-off-by: Tomeu Vizoso
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_proto.c |
From: Sameer Nanda
This driver exposes the charger functionality in the PD EC to userspace.
Signed-off-by: Tomeu Vizoso
Cc: Sameer Nanda
Cc: Benson Leung
Cc: Shawn Nematbakhsh
---
Changes in v3:
- Use do_div so it builds on 32bit (suggested by 0-day kbuild bot).
- Remove sysfs attributes ex
So that callers of cros_ec_cmd_xfer don't have to repeat boilerplate
code when checking for errors from the EC side.
Signed-off-by: Tomeu Vizoso
---
Changes in v3: None
Changes in v2: None
drivers/platform/chrome/cros_ec_proto.c | 14 ++
include/linux/mfd/cros_ec.h | 18
Copy a few structs and commands from the EC firmware headers so we can
communicate with the EC regarding PD functionality.
Signed-off-by: Tomeu Vizoso
---
Changes in v3: None
Changes in v2: None
include/linux/mfd/cros_ec_commands.h | 324 ++-
1 file changed, 319
From: Alexander Usyskin
buf_idx type was changed to size_t, and few places
missed out to change the print format from %ld to %zd.
Fixes:
commit 56988f22e097 ("mei: fix possible integer overflow issue")'
Signed-off-by: Alexander Usyskin
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/interr
Also, you _know_ you should not cross-post to closed lists, that's rude.
I am posting this patchset for smoothly merging the OOM reaper without
worrying about corner cases. This patchset also applies cleanly on top of
the current Linus tree because this patchset is meant for applying before
merging the OOM reaper.
Several problems were found in oom reaper v5 patchset
(
1 - 100 of 1017 matches
Mail list logo
