Add CRG driver for Hi3798CV200 SoC. CRG(Clock and Reset
Generator) module generates clock and reset signals used
by other module blocks on SoC.
Signed-off-by: Jiancheng Xue
Acked-by: Rob Herring
---
change log
v3:
- Added ethernet and combo-phy clocks.
v2:
- Fixed compiling error when compiled a
Add CRG driver for Hi3516CV300 SoC. CRG(Clock and Reset
Generator) module generates clock and reset signals used
by other module blocks on SoC.
Signed-off-by: Pan Wen
---
drivers/clk/hisilicon/Kconfig | 8 +
drivers/clk/hisilicon/Makefile| 1 +
drivers/clk/his
Add CRG driver for Hi3798CV200 and Hi3516CV200 SoCs.
Jiancheng Xue (2):
clk: hisilicon: add CRG driver for Hi3798CV200 SoC
clk: hisilicon: add CRG driver for Hi3516CV300 SoC
.../clock/{hi3519-crg.txt => hisi-crg.txt} | 12 +-
drivers/clk/hisilicon/Kconfig | 16
From: Frank Rowand
Add a single pr_err() to cover a range of errors that were reported
by several pr_err() that were removed earlier in this series.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/dri
From: Frank Rowand
Convert comparisons to zero or NULL to logical expressions. A
small number of such comparisons remain where they provide more
clarity of the numeric nature of a variable.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 42 --
From: Frank Rowand
Remove a redundant check of buffer size.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 708daca1d522..76c09cb57eae 100644
--- a/drivers/of/resolver.
From: Frank Rowand
Value of pointer was calculated in an earlier block than
where it was used. Move it down into the block where it
is used, immediately before where is is checked to be valid.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 3 +--
1 file changed, 1 insertion(+), 2 del
From: Frank Rowand
Some function names are misleading or do not provide a good
sense of what they do. Rename the functions to ne more
informative.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a
From: Frank Rowand
Remove unused pointer to node "__symbols__".
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 53353cc8f2bb..783bd09463b5 100644
--- a/drivers/of/r
From: Frank Rowand
Remove extra debug and error printks. A single pr_err() will
be added at the end of this series to replace many of these
error messages.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 53 ---
1 file changed, 8 inserti
From: Frank Rowand
Remove comments that report what is obvious from the code.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 31 ++-
1 file changed, 2 insertions(+), 29 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 46325d639
From: Frank Rowand
Remove BUG_ON(), which is frowned upon and not needed here.
Restructure to remove some excessive complexity.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 48 +---
1 file changed, 17 insertions(+), 31 deletions(-)
diff -
From: Frank Rowand
drivers/of/resolve.c is a bit difficult to read. Clean it up so
that review of future overlay related patches will be easier.
Most of the patches are intended to be reformatting, with no functional
change. Patches that are expected to have a functional change are:
Remove
From: Frank Rowand
Update comments to better explain what functions are doing.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 66 ---
1 file changed, 47 insertions(+), 19 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/reso
From: Frank Rowand
Rename variables to better reflect what their purpose is. As a side
effect, this reduces the need for some of the comments previously
removed in this series.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 172 +-
1 fi
From: Frank Rowand
Remove "__of_" prefix from local function names. The pattern of
a leading "__" is used in drivers/of/ to signify a function that
must be called with a lock held. These functions do not fit
that pattern.
Signed-off-by: Frank Rowand
---
drivers/of/resolver.c | 10 +-
The latest maintenance release Git v2.10.2 is now available at
the usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.10.2'
tag and the 'maint' branch that the tag points at:
url = https://kern
From: zhong jiang
Since 'commit 3e89e1c5ea84 ("hugetlb: make mm and fs code explicitly
non-modular")'
bring in the mainline. mount hugetlbfs will result in the following issue.
mount: unknown filesystme type 'hugetlbfs'
because previous patch remove the module_alias_fs, when we mount the fs ty
On Fri, Oct 28, 2016 at 5:40 PM, Andrey Konovalov wrote:
> Hi,
>
> I've got the following error report while running the syzkaller fuzzer:
>
> [ cut here ]
> WARNING: CPU: 0 PID: 4608 at kernel/sched/core.c:7724
> __might_sleep+0x14c/0x1a0 kernel/sched/core.c:7719
> do not
This is to announce the first major ~stable public release of MuQSS (pronounced
mux), the Multiple Queue Skiplist Scheduler.
MuQSS for linux 4.8:
http://ck.kolivas.org/patches/muqss/4.0/4.8/4.8-sched-MuQSS_120.patch
MuQSS for linux 4.7:
http://ck.kolivas.org/patches/muqss/4.0/4.7/4.7-sched-MuQS
> Il giorno 26 ott 2016, alle ore 18:12, Jens Axboe ha
> scritto:
>
> On 10/26/2016 10:04 AM, Paolo Valente wrote:
>>
>>> Il giorno 26 ott 2016, alle ore 17:32, Jens Axboe ha
>>> scritto:
>>>
>>> On 10/26/2016 09:29 AM, Christoph Hellwig wrote:
On Wed, Oct 26, 2016 at 05:13:07PM +0200,
在 2016/10/29 03:38, Konrad Rzeszutek Wilk 写道:
On Fri, Oct 28, 2016 at 04:11:16AM -0400, Pan Xinhui wrote:
change from v5:
spilt x86/kvm patch into guest/host part.
introduce kvm_write_guest_offset_cached.
fix some typos.
rebase patch onto 4.9.2
change from v4:
On 10/27/2016 05:29 AM, Kirti Wankhede wrote:
> +int mdev_register_device(struct device *dev, const struct parent_ops *ops)
> +{
> + int ret;
> + struct parent_device *parent;
> +
> + /* check for mandatory ops */
> + if (!ops || !ops->create || !ops->remove || !ops->supported_type_
On Thu, Oct 27, 2016 at 12:32 AM, Baolin Wang wrote:
> On 18 October 2016 at 14:47, Baolin Wang wrote:
>> From the trace log, we can find out the 'Binder:3292_2' process
>> set one alarm timer which resumes the system.
>>
>> Signed-off-by: Baolin Wang
>> Acked-by: Steven Rostedt
>> ---
>> Chang
On Fri, Oct 28, 2016 at 03:12:32PM -0400, Tejun Heo wrote:
> Hello, Peter.
>
> On Fri, Oct 28, 2016 at 09:07:02PM +0200, Peter Zijlstra wrote:
> > One alternative is to inherit the iowait state of the task we block on.
> > That'll not get rid of the branches much, but it will remove the new
> > mu
On Fri, Oct 28, 2016 at 12:11:21PM -0500, David Lechner wrote:
> On 10/28/2016 07:39 AM, Alexandre Bailon wrote:
> >On 10/28/2016 04:56 AM, David Lechner wrote:
> >>On 10/26/2016 05:58 AM, Alexandre Bailon wrote:
> >>>When the phy is forced in host mode, only the first hot plug and
> >>>hot remove
On Fri, Oct 28, 2016 at 2:53 PM, Hans Verkuil wrote:
> Hi Matt,
>
> On 28/10/16 22:14, Matt Ranostay wrote:
>>
>> So want to toss a few thoughts on adding support for thermopile
>> devices (could be used for FLIR Lepton as well) that output pixel
>> data.
>> These typically aren't DMA'able devices
On Fri, Oct 28, 2016 at 1:30 PM, Devin Heitmueller
wrote:
> Hi Matt,
>
>> Need some input for the video pixel data types, which the device we
>> are using (see datasheet links below) is outputting pixel data in
>> little endian 16-bit of which a 12-bits signed value is used. Does it
>> make sense
On Fri, Oct 28, 2016 at 1:40 PM, Marek Vasut wrote:
> On 10/28/2016 10:30 PM, Devin Heitmueller wrote:
>> Hi Matt,
>>
>>> Need some input for the video pixel data types, which the device we
>>> are using (see datasheet links below) is outputting pixel data in
>>> little endian 16-bit of which a 12
If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
complaining:
Use of uninitialized value $root in concatenation (.) or string at
/path/to/checkpatch.pl line 764.
Let's just give the safe answer instead -- don't warn about "obsolete"
files.
Fixes: 85b0ee18bbf8 ("checkpa
On Fri, Oct 28, 2016 at 07:26:31PM -0700, Brian Norris wrote:
> From: Brian Norris
>
> If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
> complaining:
>
> Use of uninitialized value $root in concatenation (.) or string at
> /path/to/checkpatch.pl line 764.
>
> Let's j
Hi Sarangdhar,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.9-rc2 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience)
From: Brian Norris
If checkpatch.pl gets copied out of the tree, --no-tree shouldn't start
complaining:
Use of uninitialized value $root in concatenation (.) or string at
/path/to/checkpatch.pl line 764.
Let's just give the safe answer instead -- don't warn about "obsolete"
files.
Fixes: 8
On Sat, 29 Oct 2016, Paul Bolle wrote:
> On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> > When POSIX timers are configured out, the PTP clock subsystem should be
> > left out as well. However a bunch of ethernet drivers currently *select*
> > the later in their Kconfig entries. Therefor
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-4.9-rc3
with top-most commit 21e2d9d5292f8a5cd1aa4e63891437589d233d35
Merge branches 'acpica-fixes', 'acpi-pci-fixes' and 'acpi-apei-fixes'
on top of commit 07d9a380680d1c0eb51ef87ff2
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.9-rc3
with top-most commit 8b2ada27dc1045e8191673bf769a1136ce8a0127
Merge branches 'pm-cpufreq-fixes' and 'pm-sleep-fixes'
on top of commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69
Hi,
I've got the following error report while running the syzkaller fuzzer:
[ cut here ]
WARNING: CPU: 0 PID: 4608 at kernel/sched/core.c:7724
__might_sleep+0x14c/0x1a0 kernel/sched/core.c:7719
do not call blocking ops when !TASK_RUNNING; state=1 set at
[] prepare_to_wait+
Add SCM DT node to enable SCM functionality on MSM8996.
Signed-off-by: Sarangdhar Joshi
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
b/arch/arm64/boot/dts/qcom/msm8996.dtsi
index 9e960c1..4927097 100644
Add SCM DT bindings for Qualcomm's MSM8996 platform.
Signed-off-by: Sarangdhar Joshi
---
Documentation/devicetree/bindings/firmware/qcom,scm.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.txt
b/Documentation/devicetree/bindings/firm
Core, iface and bus clocks are not required to be voted from SCM
driver for some of the Qualcomm chipsets. Remove dependency on
these clocks from driver.
Suggested-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
drivers/firmware/qcom_scm.c | 65 --
When devm_clk_get fails for core clock, the failure was ignored
and the core_clk was explicitly set to NULL so that other
remaining clocks can be queried. However, now that we have a
clean way of expressing the clock dependency, return failure when
devm_clk_get fails for core clock.
Signed-off-by:
On earlier chiptsets (APQ8064, MSM8660, MSM8690, MSM8916,
APQ8084, MSM8974) crypto operations of TZ were depends on crypto
clocks controlled by users/clients. However on MSM8996 crypto clocks
control is handled internally in TZ itself. The current series of
patches handle this clock dependency in S
Hi Linus,
Please pull
Thx,
-Vineet
-->
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/ tags/arc-4.9-rc3
for you
29.10.2016 02:26, Linus Torvalds пишет:
On Fri, Oct 28, 2016 at 2:36 PM, Stas Sergeev wrote:
On Fri, Oct 28, 2016 at 2:03 PM, Stas Sergeev wrote:
Hello.
For the long time dosemu used /dev/mem for vga pass-through.
Now it appears /dev/mem has this check:
http://lxr.free-electrons.com/source/d
On Fri, Oct 28, 2016 at 1:40 AM, SF Markus Elfring
wrote:
> + if (printf("cmd_%s := %s\n\n", target, cmdline) < 10) {
Rather than scatter fragile magic numbers, like 10, throughout the
code, if you're hell-bent on checking for printf errors you could
write a little wrapper function that hi
On 10/28, Laura Abbott wrote:
> ioremaped addresses are not linearly mapped so the physical
> address can not be figured out via __pa. More generally, there
> is no guarantee that backing value of an ioremapped address
> is a physical address at all. The value here is only used
> for debugging so j
Arnd Bergmann wrote:
> The newly added nft fib code produces two warnings:
>
> net/ipv4/netfilter/nft_fib_ipv4.c: In function 'nft_fib4_eval':
> net/ipv4/netfilter/nft_fib_ipv4.c:80:6: error: unused variable 'i'
> [-Werror=unused-variable]
> net/ipv4/netfilter/nft_fib_ipv4.c: In function ‘nft_fi
On Fri, Oct 28, 2016 at 2:36 PM, Stas Sergeev wrote:
On Fri, Oct 28, 2016 at 2:03 PM, Stas Sergeev wrote:
>
> Hello.
>
> For the long time dosemu used /dev/mem for vga pass-through.
> Now it appears /dev/mem has this check:
> http://lxr.free-electrons.com/source/drivers/char/mem.c#L51
> whic
On 10/28/2016 03:03 PM, Arnd Bergmann wrote:
> On Friday, October 28, 2016 2:58:33 PM CEST Vineet Gupta wrote:
>> On 10/28/2016 02:52 PM, Vineet Gupta wrote:
>>> On 10/28/2016 02:44 PM, Vineet Gupta wrote:
This is configuration specific, and something caused your compiler to
> be built ass
Instead of using #ifdef, let's mark suspend and resume methods as
__maybe_unused to provide better compile coverage.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/gpio_keys.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/input/keyboard/gpio_keys.c
Commit 633a21d80b4a ("input: gpio_keys_polled: Add support for GPIO
descriptors") placed gpio descriptor into gpio_keys_button structure, which
is supposed to be part of platform data and not modifiable by the driver.
To keep the data constant, let's move the descriptor to
gpio_keys_button_data str
From: Geert Uytterhoeven
GPIO descriptors are the preferred way over legacy GPIO numbers
nowadays. Convert the driver to use GPIO descriptors internally but
still allow passing legacy GPIO numbers from platform data to support
existing platforms.
Based on commits 633a21d80b4a2cd6 ("input: gpio_k
for_each_available_child_of_node(node, pp) takes reference to 'pp' and
drops it when attempting next iteration. However if we exit the loop early
we need to drop the reference ourselves.
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/gpio_keys.c | 3 +++
1 file changed, 3 insertions(+
Make use of the device property API in this driver so that both OF based
systems and ACPI based systems can use this driver.
Suggested-by: Geert Uytterhoeven
Suggested-by: Mika Westerberg
Signed-off-by: Dmitry Torokhov
---
drivers/input/keyboard/gpio_keys.c | 141 ++
Hi Chris,
It's time for the annual question of: where do I find the TAB minutes?
I was sure I had a bookmark of the link, but I seem to have misplaced it.
Thanks,
Frank
On 10/28/16 12:39, Chris Mason wrote:
> Hello everyone,
>
> A few updates about the TAB election. It is scheduled for 5pm
It does not matter if given GPIO may sleep or not when reading state,
polling is always done in a non-atomic context, so we should always
be able to simply use gpiod_get_value_cansleep().
Also let's note in the logs when we fail to read gpio state.
Reviewed-by: Hans de Goede
Reviewed-by: Mika We
mv_u3d_req_to_trb() does not check for dma mapping errors.
By the way, the patch improves readability of mv_u3d_start_queue()
by rearranging its code with two semantic modifications:
- assignment zero to ep->processing if usb_gadget_map_request() fails;
- propagation of error code from mv_u3d_req_
On Thu, 27 Oct 2016 09:28:24 +0200 Sebastian Andrzej Siewior
wrote:
> > Building with gcc 3.3 is apparently still possible, although it produces
> > tons of warnings and a modpost section mismatch. Still, requiring gcc
> > 4.1 or newer would not be unreasonable, I think (still released a few
>
This is corresponding part for blk-mq. Disk with multiple hardware
queues doesn't need this as we only hold 1 request at most.
Signed-off-by: Shaohua Li
---
block/blk-mq.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index f3d27a6..961
Currently block plug holds up to 16 non-mergeable requests. This makes
sense if the request size is small, eg, reduce lock contention. But if
request size is big enough, we don't need to worry about lock
contention. Holding such request makes no sense and it lows the disk
utilization.
In practice,
On Tue, 2016-10-25 at 22:28 -0400, Nicolas Pitre wrote:
> When POSIX timers are configured out, the PTP clock subsystem should be
> left out as well. However a bunch of ethernet drivers currently *select*
> the later in their Kconfig entries. Therefore some more work was needed
> to break that hard
Fixed all the "errors" reported by checkpath.pl in ks7010_stio.c
The "TODO" file ask to take the 80 character limit lightly, so
the file still has some warnings about character limit. All the
errors have been removed.
Signed-off-by: Manoj Sawai
---
drivers/staging/ks7010/ks7010_sdio.c | 60 +
On Fri, Oct 28, 2016 at 1:31 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Thu, 27 Oct 2016 16:15:04 +0200
>
> Return values were not checked from five calls of the function "printf".
>
> This issue was detected also by using the Coccinelle software.
>
>
> * Add a bit of exception h
> On Oct 28, 2016, at 17:05, Sebastian Andrzej Siewior
> wrote:
>
> The raw_write_seqcount_begin() in nfs4_reclaim_open_state() bugs me
> because it maps to preempt_disable() in -RT which I can't have at this
> point. So I took a look at the code.
> It the lockdep part was removed in commit abb
On Sat, Oct 29, 2016 at 03:48:17AM +0530, Manoj Sawai wrote:
> Fixed all the "errors" reported by checkpath.pl in ks7010_stio.c
"all"? Please break this up into one-patch-per-thing series of patches.
And no, as my patchbot told you earlier today, "all coding style issues"
is not one thing.
thank
Richard,
On Fri, 2016-10-28 at 19:07 +0200, Richard Weinberger wrote:
> Jörg,
>
> On 28.10.2016 18:19, Jörg Krause wrote:
> > Hi,
> >
> > On Fri, 2016-10-28 at 11:53 +0200, Richard Weinberger wrote:
> > > Commit c83ed4c9dbb35 ("ubifs: Abort readdir upon error") broke
> > > overlayfs support beca
On Fri, 28 Oct 2016, Colin King wrote:
Thanks.
On Thu, 2016-10-27 at 23:10 -0400, Nicolas Pitre wrote:
> On Fri, 28 Oct 2016, Paul Bolle wrote:
> > And in your example BAR is bool, right? Does the above get more
> > complicated if BAR would be tristate?
>
> If BAR=m then implying BAZ from FOO=y will force BAZ to y or n,
> bypassing the restri
OK, thanks for the prompt reply, Andy!
I'll try your sysfs suggestion.
Let me just add a bit of CCs to get more people involved.
I believe the ram size involvement makes this smell like a bug,
plus it looks like a regression. Not that I am going to suffer
much (this pass-through stuff always brea
From: Tony Luck
We use the cpu hotplug notifier to catch each cpu in turn and look at
its cache topology w.r.t each of the resource groups. As we discover
new resources, we initialize the bitmask array for each to the default
(full access) value.
Signed-off-by: Tony Luck
Signed-off-by: Fenghua
From: Tony Luck
Now we populate each directory with a read/write (mode 0644) file
named "cpus". This is used to over-ride the resources available
to processes in the default resource group when running on specific
CPUs. Each "cpus" file reads as a cpumask showing which CPUs belong
to this resour
From: Fenghua Yu
Hook the x86 scheduler code to update closid based on whether the current
task is assigned to a specific closid or running on a CPU assigned to a
specific closid.
Signed-off-by: Fenghua Yu
---
arch/x86/include/asm/intel_rdt.h | 42
arch
From: Fenghua Yu
Use kernfs as basis for our user interface filesystem. This patch
supports mount/umount, and one mount parameter "cdp" to enable code/data
prioritization (though all we do at this point is ensure that the system
can support CDP). The file system is not populated yet in this patc
From: Fenghua Yu
The root directory all subdirectories are automatically populated
with a read/write (mode 0644) file named "tasks". When read it will
show all the task IDs assigned to the resource group. Tasks can be
added (one at a time) to a group by writing the task ID to the file.
E.g.
Memb
From: Tony Luck
Last of the per resource group files. Also mode 0644. This one shows
the resources available to the group. Syntax depends on whether the
"cdp" mount option was given. With code/data prioritization disabled
it is simply a list of masks for each cache domain. Initial value
allows ac
From: Fenghua Yu
Resource control groups are represented as directories in the resctrl
file system. The root directory describes the default resources available
to tasks that have not been assigned specific resources. Other directories
can be created at the root level to make new resource groups.
diff --git a/arch/arm64/mm/physaddr.c b/arch/arm64/mm/physaddr.c
new file mode 100644
index 000..6c271e2
--- /dev/null
+++ b/arch/arm64/mm/physaddr.c
@@ -0,0 +1,17 @@
+#include
+
+#include
+
+unsigned long __virt_to_phys(unsigned long x)
+{
+phys_addr_t __x = (phys_addr_t)x;
+
+if (_
From: Fenghua Yu
The documentation describes user interface of how to allocate resource
in Intel RDT.
Please note that the documentation covers generic user interface. Current
patch set code only implemente CAT L3. CAT L2 code will be sent later.
Signed-off-by: Fenghua Yu
---
Documentation/x8
From: Fenghua Yu
This version is supposed to cover all comments from Thomas.
Patch 1-4, 6-9 of 18 v5 patches are in tip x86/cache branch. We
have rest of 10 patches in v6 on top of tip tree.
Change log in v6:
patch 1 (i.e. patch 5 in v5): Change max_cbm_val to cbm_mask.
patch 2 (i.e. patch 10
From: Fenghua Yu
For the convenience of applications we make the decoded values of some
of the CPUID values available in read-only (0444) files.
Signed-off-by: Fenghua Yu
---
arch/x86/include/asm/intel_rdt.h | 24
arch/x86/kernel/cpu/intel_rdt_rdtgroup.c | 185 +++
From: Fenghua Yu
We create five new files for Intel RDT resource allocation:
arch/x86/kernel/cpu/intel_rdt.c
arch/x86/kernel/cpu/intel_rdt_rdtgroup.c
arch/x86/kernel/cpu/intel_rdt_schemata.c
arch/x86/include/asm/intel_rdt.h
Documentation/x86/intel_rdt_ui.txt
Fenghua Yu will maintain this code.
On Fri, Oct 28, 2016 at 11:39:44AM +0200, Paolo Bonzini wrote:
>
>
> On 27/10/2016 19:06, Radim Krčmář wrote:
> > 2016-10-27 19:51+0300, Michael S. Tsirkin:
> >> On Thu, Oct 27, 2016 at 06:44:00PM +0200, Radim Krčmář wrote:
> >>> 2016-10-27 00:42+0300, Michael S. Tsirkin:
> On Wed, Oct 26, 2
On Friday, October 28, 2016 2:58:33 PM CEST Vineet Gupta wrote:
> On 10/28/2016 02:52 PM, Vineet Gupta wrote:
> > On 10/28/2016 02:44 PM, Vineet Gupta wrote:
> >> This is configuration specific, and something caused your compiler to
> >>> be built assuming that size_t is unsigned long, while the ke
On Fri, 28 Oct 2016, Paul Bolle wrote:
> On Thu, 2016-10-27 at 23:10 -0400, Nicolas Pitre wrote:
> > On Fri, 28 Oct 2016, Paul Bolle wrote:
> > > What happens when a tristate symbol is implied by a symbol set to 'y'
> > > and by a symbol set to 'm'?
> >
> > That's respectively the third and secon
Hi Linus,
Please pull some more powerpc fixes for 4.9:
The following changes since commit 78914ff0843623ee6dbeae92fa0bb8761828684e:
powerpc: Ignore the pkey system calls for now (2016-10-19 20:36:24 +1100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/gi
On Friday, October 28, 2016 2:56:10 PM CEST Dmitry Torokhov wrote:
> On Fri, Oct 28, 2016 at 2:47 PM, Arnd Bergmann wrote:
> > On Friday, October 28, 2016 2:39:35 PM CEST Deepa Dinamani wrote:
> >> >> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
> >> >> >>
> >> >> >> static inline size_t inpu
On 10/28/2016 02:52 PM, Vineet Gupta wrote:
> On 10/28/2016 02:44 PM, Vineet Gupta wrote:
>> This is configuration specific, and something caused your compiler to
>>> be built assuming that size_t is unsigned long, while the kernel
>>> headers are assuming it should be unsigned int.
>
> So yes thi
On Fri, Oct 28, 2016 at 2:47 PM, Arnd Bergmann wrote:
> On Friday, October 28, 2016 2:39:35 PM CEST Deepa Dinamani wrote:
>> >> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>> >> >>
>> >> >> static inline size_t input_event_size(void)
>> >> >> {
>> >> >> - return (in_compat_syscall() &
Hi Matt,
On 28/10/16 22:14, Matt Ranostay wrote:
So want to toss a few thoughts on adding support for thermopile
devices (could be used for FLIR Lepton as well) that output pixel
data.
These typically aren't DMA'able devices since they are low speed
(partly to limiting the functionality to be in
On 10/28/2016 02:44 PM, Vineet Gupta wrote:
> This is configuration specific, and something caused your compiler to
>> be built assuming that size_t is unsigned long, while the kernel
>> headers are assuming it should be unsigned int.
So yes this seems to be target specific gcc thing
for ARC 4.8
If the dax_pmem driver is passed a resource that is already busy the
driver probe attempt should fail with a message like the following:
dax_pmem dax0.1: could not reserve region [mem 0x1-0x11fff]
However, if we do not catch the error we crash for the obvious reason of
accessing mem
On Friday, October 28, 2016 2:44:13 PM CEST Vineet Gupta wrote:
>
> Indeed if I hack include/linux/types.h
>
> -typedef __kernel_size_tsize_t;
> +typedef unsigned long size_t;
>
> then the warning goes away, so gcc is indeed assuming size_t to be unsigned
> long
> and n
On Friday, October 28, 2016 2:39:35 PM CEST Deepa Dinamani wrote:
> >> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
> >> >>
> >> >> static inline size_t input_event_size(void)
> >> >> {
> >> >> - return (in_compat_syscall() && !COMPAT_USE_64BIT_TIME) ?
> >> >> - sizeof(str
On 10/28/2016 02:33 PM, Arnd Bergmann wrote:
> On Friday, October 28, 2016 2:03:21 PM CEST Vineet Gupta wrote:
>>
>> I'm trying to use about to be released ARC gcc 6.x with current kernels and
>> see a
>> flood of warnings due to these legit fixes - i.e.g arc gcc 6.2 complains
>> when it
>> sees
On Fri, 28 Oct 2016 17:15:57 -0400
Luiz Capitulino wrote:
> On Fri, 28 Oct 2016 15:50:10 -0400
> Steven Rostedt wrote:
>
> > On Fri, 28 Oct 2016 15:49:22 -0400
> > Steven Rostedt wrote:
> >
> > > Sorry it took so long to look at this, but I finally got around to
> > > it ;-)
> > >
> >
> >
>> >> @@ -55,24 +60,24 @@ struct ff_effect_compat {
>> >>
>> >> static inline size_t input_event_size(void)
>> >> {
>> >> - return (in_compat_syscall() && !COMPAT_USE_64BIT_TIME) ?
>> >> - sizeof(struct input_event_compat) : sizeof(struct
>> >> input_event);
>> >> + ret
The raw_write_seqcount_begin() in nfs4_reclaim_open_state() bugs me
because it maps to preempt_disable() in -RT which I can't have at this
point. So I took a look at the code.
It the lockdep part was removed in commit abbec2da13f0 ("NFS: Use
raw_write_seqcount_begin/end int nfs4_reclaim_open_state"
On Friday, October 28, 2016 2:03:21 PM CEST Vineet Gupta wrote:
>
> I'm trying to use about to be released ARC gcc 6.x with current kernels and
> see a
> flood of warnings due to these legit fixes - i.e.g arc gcc 6.2 complains when
> it
> sees -zx formats.
>
> CC mm/percpu.o
> ../mm/percpu
On Thu, 2016-10-27 at 23:10 -0400, Nicolas Pitre wrote:
> On Fri, 28 Oct 2016, Paul Bolle wrote:
> > What happens when a tristate symbol is implied by a symbol set to 'y'
> > and by a symbol set to 'm'?
>
> That's respectively the third and second rows in the table above.
I meant: two separate sy
On Fri, Oct 28, 2016 at 08:49:58PM +0100, Al Viro wrote:
> On Fri, Oct 28, 2016 at 11:21:24AM -0700, Linus Torvalds wrote:
>
> > End result: either commit 1c109fabbd51 shouldn't be backported (it's
> > really not that important - if people properly check the exception
> > error results it shouldn'
1 - 100 of 675 matches
Mail list logo
