Currently perf report only shows a help message "For a higher level
overview, try: perf report --sort comm,dso" unconditionally (even if
the sort keys were used). Add more help tips and show randomly.
Load tips from ${prefix}/share/doc/perf-tip/tips.txt file.
$ perf report | tail
0.10%
Instead of checking var == NULL, the kernel coding style recommends
writing it as !var.
Signed-off-by: Sudip Mukherjee
---
sound/drivers/portman2x4.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/drivers/portman2x4.c b/sound/drivers/portman2x4.c
index
checkpatch complains about space before tab.
Signed-off-by: Sudip Mukherjee
---
sound/drivers/portman2x4.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/sound/drivers/portman2x4.c b/sound/drivers/portman2x4.c
index 4f9717b..65b0650 100644
---
Trailing whitespace is not encouraged by Kernel coding style.
Signed-off-by: Sudip Mukherjee
---
sound/drivers/portman2x4.c | 50 +++---
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/sound/drivers/portman2x4.c
It is not general practice to assign some values inside if statement.
Signed-off-by: Sudip Mukherjee
---
sound/drivers/portman2x4.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/sound/drivers/portman2x4.c b/sound/drivers/portman2x4.c
index
Dear Bjorn,
On Wed, 6 Jan 2016 12:20:03 -0600 Bjorn Helgaas wrote:
> [+cc Jisheng]
>
> On Fri, Dec 18, 2015 at 02:38:55PM +0200, Stanimir Varbanov wrote:
> > There is no guarantees that enabling ATU will hit the hardware
> > immediately, and subsequent accesses to configuration / IO spaces
> >
Hi Marcel,
On 2016-01-05 08:39, Marcel Ziswiler wrote:
> From: Petr Štetiar
>
> Signed-off-by: Petr Štetiar
> Signed-off-by: Marcel Ziswiler
> ---
>
> Changes in v2:
> - clarify exact Apalis iMX6Q/D SoM type in cover letter
> - clarify exact Apalis iMX6Q/D module type and Ixora carrier board
Hi,
On Wednesday 06 January 2016 07:43 PM, Rob Herring wrote:
> On Wed, Jan 06, 2016 at 04:19:53PM +0530, Kishon Vijay Abraham I wrote:
>> Perform syscon configurations to get x2 mode to working in DRA74x and
>> DRA72x. Also add a new compatible string to dfferentiate
>> DRA72x and DRA74x, since
Thanks for "Kbuild test robot" reminding, I forget to update
"mode_valid" function define in imx-hdmi side, would send new version out,
--
drivers/gpu/drm/imx/dw_hdmi-imx.c:181:2: warning: initialization from
incompatible pointer type
.mode_valid = imx6q_hdmi_mode_valid,
^
Some platforms don't support ATU, e.g pci-keystone.c, these platforms
use their own address translation component rather than ATU, and they
provide the rd_other_conf and wr_other_conf to programming the
translation component then do the required access, so we ignore the ATU
programming for these
Promote myself as new maintainer of the Freescale DCU DRM driver.
Signed-off-by: Stefan Agner
---
This has been previously discussed privately. The original driver
author and maintainer Jianwei does not work for Freescale anymore
and can not carve out spare time to maintain the driver.
As I
Hi Boris,
On Wed, Jan 6, 2016 at 10:29 PM, Boris Brezillon
wrote:
> On Wed, 30 Dec 2015 09:31:06 +0100
> Boris Brezillon wrote:
>
>> Hi Peter,
>>
>> On Wed, 30 Dec 2015 15:18:39 +0800
>> 潘栋 wrote:
>>
>> > Hi Boris and Ezequiel,
>> >
>> > 2015-12-29 23:11 GMT+08:00 Boris Brezillon
>> > :
>> >
On 01/06/2016 05:55 PM, Boris Brezillon wrote:
Add basic support for the sil902x RGB -> HDMI bridge.
This driver does not support audio output yet.
Signed-off-by: Boris Brezillon
---
Hello,
This patch is only adding basic support for the sil9022 chip.
As stated in the commit log, there's no
Hi Nicholas,
Today's linux-next merge of the target-updates tree got conflicts in:
drivers/infiniband/ulp/iser/iscsi_iser.h
drivers/infiniband/ulp/iser/iser_initiator.c
drivers/infiniband/ulp/iser/iser_memory.c
drivers/infiniband/ulp/iser/iser_verbs.c
Hi,
On Thursday 07 January 2016 02:16 AM, Pavel Machek wrote:
> Hi!
>
> In v4.1, both internal MMC and u-SD cards work ok.
>
> In v4.2, only the internal MMC is detected. In v4.3, not even internal
> MMC works. In v4.4, only the internal MMC is detected.
>
> Does it work for you? Any patches?
This is an update to Arnd Bergmann's RFC patch series:
https://lkml.org/lkml/2014/5/30/669 .
The syscalls and runtime libraries will be handled in separate patch series.
The filling of max and min timestamps for individual filesystems can be
leveraged from the patch series:
The current representation of inode times in struct inode, struct iattr,
and struct kstat use struct timespec. timespec is not y2038 safe.
Use scalar data types (seconds and nanoseconds stored separately) to
represent timestamps in struct inode in order to maintain same size for
times across 32
struct timespec is not y2038 safe.
The ext4 uses time_extra fields to extend {a,c,m,cr} times until
2446.
Use struct inode_timespec to replace timespec.
inode_timespec will eventually be replaced by struct timespec64
when CONFIG_FS_USES_64BIT_TIME is enabled.
Signed-off-by: Deepa Dinamani
---
Substitute inode_timespec aliases with timespec64.
Since CONFIG_FS_USES_64BIT_TIME is enabled, internally
all inode_timespec references are using timespec64
already.
Signed-off-by: Deepa Dinamani
---
fs/cifs/cache.c | 4 ++--
fs/cifs/cifsglob.h | 6 +++---
fs/cifs/cifsproto.h | 6 +++---
64 bit time support is in place for all filesystems.
Enable CONFIG_USES_64BIT_TIME to start using 64 bit time
everywhere.
Signed-off-by: Deepa Dinamani
---
fs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index a11934b..bfeefce 100644
---
Substitute inode_timespec aliases with timespec64.
Since CONFIG_FS_USES_64BIT_TIME is enabled, internally
all inode_timespec references are using timespec64
already.
Signed-off-by: Deepa Dinamani
---
fs/ext4/ext4.h| 14 +++---
fs/ext4/extents.c | 6 +++---
fs/ext4/ialloc.c | 2 +-
VFS currently uses struct timespec timestamps which are not
y2038 safe.
Change all the struct inode timestamps accesses through
accessor macros only. This will help the switch over
to 64 bit times seamlessly.
Use struct inode_timespec aliases everywhere.
This will change timestamp data types to
The current_fs_time function is not y2038 safe because
of the use of struct timespec.
The macros CURRENT_TIME and CURRENT_TIME_SEC do not represent
file system times correctly as they cannnot perform range checks
or truncations. These are also not y2038 safe. Add 64 bit versions
of the above
Substitute inode_timespec aliases with timespec64.
Since CONFIG_FS_USES_64BIT_TIME is enabled, internally
all inode_timespec references are using timespec64
already.
Signed-off-by: Deepa Dinamani
---
fs/fat/dir.c | 4 ++--
fs/fat/fat.h | 6 +++---
fs/fat/file.c| 4
All file system code is using 64 bit time already and this config
is no longer required.
Signed-off-by: Deepa Dinamani
---
fs/Kconfig | 10 --
1 file changed, 10 deletions(-)
diff --git a/fs/Kconfig b/fs/Kconfig
index bfeefce..922893f 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -8,16
Change all struct timespec references to struct inode_timespec.
Use inode timestamp accessors to access inode time fields.
This will help the switch to struct timespec64 when
CONFIG_FS_USES_64BIT_TIME is enabled.
Use current_fs_time() instead of CURRENT_TIME macros to help
range and precision
Now that CONFIG_FS_USES_64BIT_TIME is enabled, the aliases
for inode_timespec are no longer used and can be removed.
Signed-off-by: Deepa Dinamani
---
include/linux/time64.h | 21 -
1 file changed, 21 deletions(-)
diff --git a/include/linux/time64.h b/include/linux/time64.h
Substitute inode_timespec aliases with timespec64.
Since CONFIG_FS_USES_64BIT_TIME is enabled, internally
all inode_timespec references are using timespec64
already.
Signed-off-by: Deepa Dinamani
---
fs/attr.c| 2 +-
fs/bad_inode.c | 2 +-
fs/binfmt_misc.c | 2 +-
Substitute inode_timespec aliases with timespec64.
Since CONFIG_FS_USES_64BIT_TIME is enabled, internally
all inode_timespec references are using timespec64
already.
Signed-off-by: Deepa Dinamani
Conflicts:
kernel/time/time.c
Conflicts:
kernel/time/time.c
---
FAT filesystem supports timestamps until the year 2099
even though the theoretical max is 2107.
But, the struct timespec overflows in the year 2038 on
32 bit systems.
Use inode_timespec throughout the file system code so
that the timestamps can switch to y2038 safe
struct timespec64 when
This config will be used to #ifdef code that will be required for
switching over all file systems to use 64 bit time.
The config should remain turned off until all the support in vfs
and other file systems has been added.
Signed-off-by: Deepa Dinamani
---
fs/Kconfig | 10 ++
1 file
On Wed, Dec 23, 2015 at 06:28:15PM +0530, Rameshswar Prasad Sahu wrote:
> From: Rameshwar Prasad Sahu
>
> For interrupt controller that doesn't support irq_disable and hardware
> with level interrupt, an extra interrupt can be pending. This patch fixes
> the issue by setting IRQ_DISABLE_UNLAZY
Hi,
I saw the warning "Missing required AuthAttr" when testing kexec, known issue?
Idea about how to fix it?
The kernel is latest linus tree plus sevral patches from Toshi to cleanup io
resource structure.
in function pkcs7_sig_note_set_of_authattrs():
if
Stephen,
On 12/01/2015 07:01 AM, Stephen Boyd wrote:
> Add support for the global clock controller found on MSM8996
> based devices. This should allow most non-multimedia device
> drivers to probe and control their clocks.
On my 8096 board I see the following orphan clocks,
On 01/07/2016 at 10:36 AM, Minfei Huang wrote:
> On 01/07/16 at 10:14am, Xunlei Pang wrote:
+static int
+kexec_mark_range(unsigned long start, unsigned long end, bool protect)
+{
+ struct page *page;
+ unsigned int nr_pages;
+
+ /* For physical range: [start,
Hi,
On 01/06/2016 06:31 PM, Loc Ho wrote:
Hi All,
The current driver uses input clock source frequency to calculate
values for [SS|FS]_[HC|LC] registers. However, when booting ACPI, we do not
currently have a good way to provide the frequency information.
Instead, we can leverage the SSCN and
On Wed, Jan 06, 2016 at 11:05:02AM +0100, Thomas Gleixner wrote:
> On Wed, 6 Jan 2016, Vinod Koul wrote:
> > On Wed, Jan 06, 2016 at 02:51:07PM +0530, Rameshwar Sahu wrote:
> > > >> @@ -1610,6 +1611,7 @@ static int xgene_dma_request_irqs(struct
> > > >> xgene_dma *pdma)
> > > >> /* Register
Signed-off-by: Yakir Yang
---
.../devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
a/Documentation/devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt
On Thu, Jan 07, 2016 at 11:14:50AM +0800, kbuild test robot wrote:
> Hi Huang,
>
> [auto build test ERROR on bp/for-next]
> [also build test ERROR on v4.4-rc8 next-20160106]
> [cannot apply to tip/x86/core]
> [if your patch is applied to the wrong git tree, please drop us
RK3229 integrate an DesignedWare HDMI2.0 controller and an INNO HDMI2.0 phy,
the max output resolution is 4K.
Signed-off-by: Yakir Yang
---
drivers/gpu/drm/bridge/dw-hdmi.c| 33 ++-
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 380 +---
RK3229 have integrated an DesignedWare HDMI controller and an INNO HDMI phy,
so we can still reuse the dw-hdmi driver for RK3229 HDMI controller, but
we need to create an separate driver for RK3229 HDMI PHY.
Yakir Yang (2):
drm: rockchip: hdmi: add RK3229 HDMI support
dt-bindings: add
On Wed, January 6, 2016 6:47 pm, Dmitry Torokhov wrote:
> It is wrong. Aside form the fact that IMO xpad.c is the wrong place for
> this code to be in, why are we waiting for the input device to be opened by
> userspace before we do the switch instead of doing it immediately?
The 'send magic'
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
When doing node online/offline, cpuid <-> nodeid mapping is
established/destroyed,
which means, cpuid <-> nodeid mapping will
From: Gu Zheng
This patch finishes step 4.
This patch set the persistent cpuid <-> nodeid mapping for all enabled/disabled
processors at boot time via an additional acpi namespace walk for processors.
Signed-off-by: Gu Zheng
Signed-off-by: Tang Chen
---
arch/ia64/kernel/acpi.c | 2 +-
From: Gu Zheng
[Problem]
cpuid <-> nodeid mapping is firstly established at boot time. And workqueue
caches
the mapping in wq_numa_possible_cpumask in wq_numa_init() at boot time.
When doing node online/offline, cpuid <-> nodeid mapping is
established/destroyed,
which means, cpuid <-> nodeid
From: Gu Zheng
This patch finishes step 3.
There are four mappings in the kernel:
1. nodeid (logical node id) <-> pxm
2. apicid (physical cpu id) <-> nodeid
3. cpuid (logical cpu id) <-> apicid
4. cpuid (logical cpu id) <-> nodeid
1. pxm (proximity domain) is provided by
For now, x86 does not support memory-less node. A node without memory
will not be onlined, and the cpus on it will be mapped to the other
online nodes with memory in init_cpu_to_node(). The reason of doing this
is to ensure each cpu has mapped to a node with memory, so that it will
be able to
From: Gu Zheng
This patch finishes step 2.
In this patch, we introduce a new static array named cpuid_to_apicid[],
which is large enough to store info for all possible cpus.
And then, we modify the cpuid calculation. In generic_processor_info(),
it simply finds the next unused cpuid. And it is
Hello Mr. Torokhov,
Could you please help to update about below patch ?
Thanks,
Aniroop Mathur
On Tue, Jan 5, 2016 at 3:26 AM, Aniroop Mathur wrote:
> This patch introduces concept to drop partial events in evdev handler
> itself after emptying the buffer which are dropped by all evdev
>
To add new man viewer, configs like 'man..cmd',
'man..path' can be set into config file (~/.perfconfig).
But parsing config file is stopped because the config variable
contains '.' character i.e.
If setting 'man.xman.cmd' into config file,
[man]
gman.cmd = gman
when launching perf an
This commit adds support to the eeprom_93x46 driver allowing a GPIO line
to function as a 'select' or 'enable' signal prior to accessing the
EEPROM.
Signed-off-by: Cory Tusar
Tested-by: Chris Healy
Reviewed-by: Vladimir Zapolskiy
---
drivers/misc/eeprom/eeprom_93xx46.c | 35
Atmel devices in this family have some quirks not found in other similar
chips - they do not support a sequential read of the entire EEPROM
contents, and the control word sent at the start of each operation
varies in bit length.
This commit adds quirk support to the driver and modifies the read
This commit implements bindings in the eeprom_93xx46 driver allowing
device word size and read-only attributes to be specified via
devicetree.
Signed-off-by: Cory Tusar
Tested-by: Chris Healy
Reviewed-by: Vladimir Zapolskiy
---
drivers/misc/eeprom/eeprom_93xx46.c | 49
Compatible at93xx46 devices from both Microchip and Atmel expect a
word-based address, regardless of whether the device is strapped for 8-
or 16-bit operation. However, the offset parameter passed in when
reading or writing at a specific location is always specified in terms
of bytes.
This
This commit documents bindings to be added to the eeprom_93xx46 driver
which will allow:
- Device word size and read-only attributes to be specified.
- A device-specific compatible string for use with Atmel AT93C46D
EEPROMs.
- Specifying a GPIO line to function as a 'select' or 'enable'
This series of patches adds an initial set of devicetree bindings to the
eeprom_93xx46 driver which mirror the configuration options previously
available as a platform device. These bindings are then extended to
include support for specific Atmel devices in this family and also to
support
MPOL_MF_LAZY is not visible from userspace since 'commit a720094ded8c
("mm: mempolicy: Hide MPOL_NOOP and MPOL_MF_LAZY from userspace for now")'
, but it should still skip non-migratable VMAs such as VM_IO, VM_PFNMAP,
and VM_HUGETLB VMAs, and avoid useless overhead of minor faults.
Signed-off-by:
On Thu, 07 Jan 2016 10:56:56 +0800
"Zhang, Yanmin" wrote:
> How is this patch? It fixes a kernel panic.
>
Linus already pulled it. It's also marked for stable. See commit:
f36d1be2930ede0a1947686e1126ffda5d5ee1bb in Linus's tree.
I renamed the subject slightly to:
"tracing: Fix setting of
On 2016/1/7 11:50, Steven Rostedt wrote:
> On Thu, 07 Jan 2016 10:56:56 +0800
> "Zhang, Yanmin" wrote:
>
>> How is this patch? It fixes a kernel panic.
>>
> Linus already pulled it. It's also marked for stable. See commit:
> f36d1be2930ede0a1947686e1126ffda5d5ee1bb in Linus's tree.
>
> I renamed
在 2016/1/6 21:36, Rongrong Zou 写道:
在 2016/1/5 20:19, Arnd Bergmann 写道:
On Tuesday 05 January 2016 19:59:49 Rongrong Zou wrote:
在 2016/1/5 0:34, Arnd Bergmann 写道:
On Tuesday 05 January 2016 00:04:19 Rongrong Zou wrote:
在 2016/1/4 19:13, Arnd Bergmann 写道:
On Sunday 03 January 2016 20:24:14
On 2016/1/5 23:47, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 08:27:49PM +0800, Chen Feng wrote:
>> Add Document for hi655x pmic regulator driver
>
> As indicated in the driver review this seems to be a bit of an unusual
> binding that I think needs reworking, also it needs a bit more detail -
On 2016/1/5 23:44, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 08:27:51PM +0800, Chen Feng wrote:
>
>> +/*LDO 2 & LDO 14*/
>
> Please use the normal kernel coding style for comments, I'm surprised
> checkpatch didn't warn you about this.
>
ok,thanks!
>> +static const unsigned int
> From: Xiangliang Yu :
> > Main changes in V2:
> > 1. Fixed compiler warning;
> > 2. Add marcro argument of ndev in NTB_READ_REG/NTB_WRITE_REG; 3.
> Add
> > notes for flush and wakeup interfaces;
> >
> > Xiangliang Yu (3):
> > NTB: Add AMD PCI-Express NTB driver
> > NTB: Add AMD NTB support
On Wed, 2016-01-06 at 21:13 -0500, Mimi Zohar wrote:
> On Thu, 2016-01-07 at 00:34 +, David Howells wrote:
> > David Howells wrote:
> >
> > > Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893:
> > >
> > > Author: Petko Manolov
> > > Date: Wed Dec 2 17:47:55 2015 +0200
Hi Huang,
[auto build test ERROR on bp/for-next]
[also build test ERROR on v4.4-rc8 next-20160106]
[cannot apply to tip/x86/core]
[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/Huang-Rui/perf
On Wed, Jan 06, 2016 at 08:40:09PM -0500, Martin K. Petersen wrote:
> > "Mike" == mchristi writes:
>
> Mike> The following patches begin to cleanup the request->cmd_flags and
> bio-> bi_rw mess. We currently use cmd_flags to specify the operation,
> Mike> attributes and state of the
On Tue, Jan 05, 2016 at 02:53:16PM -0600, mchri...@redhat.com wrote:
> From: Mike Christie
>
> This patch has xfs set the bio bi_op to a REQ_OP, and
> rq_flag_bits to bi_rw.
>
> Note:
> I have run xfs tests on these btrfs patches. There were some failures
> with and without the patches. I have
Hi Boris,
On Wed, Dec 30, 2015 at 08:32:02PM +0100, Boris Brezillon wrote:
> Hi,
>
> This patch series aims at providing a common logic to check for bitflips
> in erased pages.
>
> Currently each driver is implementing its own logic to check for bitflips
> in erased pages. Not only this create
On 2015/12/31 13:11, Qiu, PeiyangX wrote:
> From: Qiu Peiyang
>
> When we do cat /sys/kernel/debug/tracing/printk_formats, we hit kernel
> panic at t_show.
>
> general protection fault: [#1] PREEMPT SMP
> CPU: 0 PID: 2957 Comm: sh Tainted: G W O 3.14.55-x86_64-01062-gd4acdc7 #2
> RIP:
On Wed, Dec 30, 2015 at 08:32:05PM +0100, Boris Brezillon wrote:
> The davinci drivers is manually checking for 'erased pages' while
> correcting ECC bytes.
> This logic can now done by the core infrastructure, and can thus be removed
> from this drivers.
>
> Signed-off-by: Boris Brezillon
> >
> >> > +#define ndev_pdev(ndev) ((ndev)->ntb.pdev) #define
> ndev_name(ndev)
> >> > +pci_name(ndev_pdev(ndev)) #define ndev_dev(ndev)
> >> > +(_pdev(ndev)->dev) #define ntb_ndev(ntb) container_of(ntb,
> >> > +struct amd_ntb_dev, ntb) #define hb_ndev(work) container_of(work,
> >> > +struct
> "Finn" == Finn Thain writes:
Finn> Like my previous work on the NCR5380 drivers, this patch series
Finn> has bug fixes, code cleanup and modernization. These drivers
Finn> suffer from mistakes, poor style and neglect and this long series
Finn> addresses the worst of it, covering all ten
On Wed, 2016-01-06 at 11:55 -0800, Kamal Mostafa wrote:
> On Wed, 2016-01-06 at 17:05 +, Ben Hutchings wrote:
> > On Tue, 2016-01-05 at 11:41 -0800, Kamal Mostafa wrote:
> > > 4.2.8-ckt1 -stable review patch. If anyone has any objections, please
> > > let me know.
> > >
> > >
> > +
> > +#definePCI_DEVICE_ID_AMD_NTB 0x145B
>
> This looks like a tab and not a space
I'll update it.
>
> > +#define AMD_LINK_HB_TIMEOUTmsecs_to_jiffies(1000)
> > +#define AMD_LINK_STATUS_OFFSET 0x68
> > +#define NTB_LIN_STA_ACTIVE_BIT 0x0002
> > +#define
On Wed, Dec 30, 2015 at 08:32:04PM +0100, Boris Brezillon wrote:
> The default NAND read functions are relying on the underlying controller
> driver to correct bitflips, but some of those controllers cannot properly
> fix bitflips in erased pages.
> Check for bitflips in erased pages in default
On Wed, Dec 30, 2015 at 08:32:03PM +0100, Boris Brezillon wrote:
> The error code returned by the ecc.correct() are not consistent over the
> all implementations.
>
> Document the expected behavior in include/linux/mtd/nand.h and fix
> offending implementations.
>
> Signed-off-by: Boris
Hi all,
On Thu, 31 Dec 2015 21:31:24 +1100 Stephen Rothwell
wrote:
>
> After merging the drm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/tonga_thermal.c: In function
> 'tonga_fan_ctrl_get_fan_speed_percent':
>
Hi Linus,
The following changes since commit e488ca9f8d4f62c2dc36bfa5c32f68e7f05ab381:
doc: dt: mtd: partitions: add compatible property to "partitions" node
(2015-12-08 17:10:20 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mtd.git tags/for-linu
On Wed, Nov 25, 2015 at 7:19 PM, Steinar H. Gunderson wrote:
> Add a new interface for userspace to preallocate memory that can be
> used with usbfs. This gives two primary benefits:
I got this when trying to allocate a little bit large buffer (~4MB)
using the new userspace
On 01/07/16 at 10:14am, Xunlei Pang wrote:
> >> +static int
> >> +kexec_mark_range(unsigned long start, unsigned long end, bool protect)
> >> +{
> >> + struct page *page;
> >> + unsigned int nr_pages;
> >> +
> >> + /* For physical range: [start, end] */
> >> + if (!start || !end || start >
Add an accessor function amd_get_cores_per_cu() which returns the
number of cores per compute unit.
In a subsequent patch, we will use this function in both x86 perf and
fam15h driver.
Signed-off-by: Huang Rui
---
arch/x86/include/asm/processor.h | 1 +
arch/x86/kernel/cpu/amd.c| 17
Introduce an AMD accumlated power reporting mechanism for Carrizo
(Family 15h, Model 60h) processor that should be used to calculate the
average power consumed by a processor during a measurement interval.
The feature of accumulated power mechanism is indicated by CPUID
Fn8000_0007_EDX[12].
nodes_per_socket is static and it needn't be initialized many times
during every cpu core init. So move nodes_per_socket initialization
into bsp_init_amd.
Signed-off-by: Huang Rui
---
arch/x86/kernel/cpu/amd.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git
AMD CPU family 15h model 0x60 introduces accumulated power mechanism.
It is used to report the processor power consumption and indicated by
CPUID Fn8000_0007_EDX[12].
Signed-off-by: Huang Rui
---
arch/x86/include/asm/cpufeature.h | 2 +-
arch/x86/kernel/cpu/amd.c | 4
2 files
Hi,
This series of patches introduces the perf implementation of
accumulated power reporting algorithm. It will calculate the average
power consumption for the processor. The CPU feature flag is
CPUID.8000_0007H:EDX[12].
Simple example:
root@hr-zp:/home/ray/tip# ./tools/perf/perf stat -a -e
> > drivers/ntb/hw/Kconfig | 1 +
> > drivers/ntb/hw/Makefile | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff --git a/drivers/ntb/hw/Kconfig b/drivers/ntb/hw/Kconfig index
> > 4d5535c..0c5c2a6 100644
> > --- a/drivers/ntb/hw/Kconfig
> > +++ b/drivers/ntb/hw/Kconfig
> > @@ -1 +1,2 @@
> >
On 01/07/2016 at 10:14 AM, Xunlei Pang wrote:
> On 01/07/2016 at 01:08 AM, Minfei Huang wrote:
>> On 01/06/16 at 05:50pm, Xunlei Pang wrote:
>>> diff --git a/arch/x86/kernel/machine_kexec_64.c
>>> b/arch/x86/kernel/machine_kexec_64.c
>>> index 819ab3f..cda867d 100644
>>> ---
The Exynos SoC provides a Security SubSystem block for accelerating some
cryptographic operations. Enable the driver for it - s5p-secss to
utilize the hardware acceleration.
Currently the s5p-secss driver supports AES in CBC and ECB modes.
However on Odroid XU4 (Exynos5422) and Trats2
Enable the kernel NEON mode and asm/NEON accelerated crypto algorithms
which should bring performance benefits on Exynos SoCs. Enable these as
modules because they are optional, not essential anyhow for platform
booting nor related directly to Exynos Soc. All accelerated algorithms
pass booting
On Thu, 2016-01-07 at 00:34 +, David Howells wrote:
> David Howells wrote:
>
> > Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893:
> >
> > Author: Petko Manolov
> > Date: Wed Dec 2 17:47:55 2015 +0200
> > IMA: create machine owner and blacklist keyrings
> >
>
On 01/07/2016 at 01:08 AM, Minfei Huang wrote:
> On 01/06/16 at 05:50pm, Xunlei Pang wrote:
>> diff --git a/arch/x86/kernel/machine_kexec_64.c
>> b/arch/x86/kernel/machine_kexec_64.c
>> index 819ab3f..cda867d 100644
>> --- a/arch/x86/kernel/machine_kexec_64.c
>> +++
On Thu, Jan 07, 2016 at 11:42:53AM +1100, Stephen Rothwell wrote:
> > This patch now looks like this (after changes to the orangefs tree):
> >
Guys, just set inode->i_link to ORANGEFS_I(dentry->d_inode)->link_target and
have ->get_link = simple_get_link. Killing orangefs_{follow,get}_link()
On Wed, Jan 06 2016 at 8:22pm -0500,
Scotty Bauer wrote:
>
>
> On 01/05/2016 02:13 PM, Mike Snitzer wrote:
> > On Tue, Jan 05 2016 at 3:16pm -0500,
> > Mike Snitzer wrote:
> >
> >> On Tue, Dec 08 2015 at 1:26pm -0500,
> >> Scotty Bauer wrote:
> >>
> >>> Friendly ping, is anyone
On 11/23/15 16:47, Stephen Boyd wrote:
> On 11/22, Rob Herring wrote:
>>
>> Much more reasonable now. I do find the '/' in it a bit strange though.
> I can remove the backslash if you like. Is a dash more preferred?
>
>> Acked-by: Rob Herring
>>
> and if so can I keep the ack? I'll resend with
Steven Rostedt writes:
> [ Bah, I forgot to commit the ftrace.h part, lucky I test on another
> box than what I compile test on ;-) ]
Acked-by: Rusty Russell
Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 11/17/15 16:06, Stephen Boyd wrote:
> From: "Ivan T. Ivanov"
>
> Revision ID registers are available only on devices with
> Slave IDs that are even, so don't make access to unavailable
> registers.
>
> Signed-off-by: Ivan T. Ivanov
> [sb...@codeaurora.org: Consider all slave ids that are
On Wed, Jan 06, 2016 at 05:12:47PM -0800, Stephen Boyd wrote:
> A recent patch added calls to of_irq_count() in the qcom pinctrl
> drivers and that caused module build failures because
> of_irq_count() is not an exported symbol. We shouldn't export
> of_irq_count() to modules because it's an
On Wed, Jan 06, 2016 at 03:36:57PM +0100, Jiri Kosina wrote:
> On Mon, 4 Jan 2016, Benjamin Tissoires wrote:
>
> > Jiri, I *think* this commit still is in your next pull request for
> > Linus. We might want to drop it before it hits Linus' tree.
>
> What exactly would be the reasoning for
On 2016/1/4 19:54, David Vrabel wrote:
> On 29/12/15 05:49, Ouyangzhaowei (Charles) wrote:
>> Hi David,
>>
>> This patch has been applied to for-linus-4.1b, and we wonder if this patch
>> will be applied to linux kernel, or does
>> it still needs more test to apply to linux kernel?
>
> Sorry,
Hi Richard,
This all sounds fine. Thanks for the feedback. I'll roll this into the
next patchset.
Chris
On Tue, 05 Jan 2016 07:27:32 -0800, Richard Cochran
wrote:
On Mon, Jan 04, 2016 at 04:45:22AM -0800, Christopher S. Hall wrote:
+ case PTP_SYS_OFFSET_PRECISE:
+
1 - 100 of 1814 matches
Mail list logo
