Hi Peter,
On Wed, 2015-08-26 at 12:07 +, Alexey Brodkin wrote:
> Hi Peter,
>
> On Mon, 2015-08-24 at 17:20 +0300, Alexey Brodkin wrote:
> > Hi Peter,
> >
> > This mini-series adds perf support for ARCv2 based cores, which brings in
> > overflow interupts and SMP. Additionally now raw events
Mam vzajemne mit prospech podnik pro nas oba. pokud mate zajem, muzete mi
dostat na e-mailovou adresu a pro detaily a vysvetlení.
E-mail: chn.j...@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More maj
Usually an skb does not have up to MAX_SKB_FRAGS frags. So no need to
initialize the unuse part of sg. This patch initialize the sg based on
the real number it will used:
- during xmit, it could be inferred from nr_frags and can_push.
- for small receive buffer, it will also be 2.
Cc: Michael S.
On Wed 26-08-15 15:02:49, David Rientjes wrote:
> On Wed, 26 Aug 2015, Michal Hocko wrote:
>
> > I thought the purpose was to give the amount of hugetlb based
> > resident memory.
>
> Persistent hugetlb memory is always resident, the goal is to show what is
> currently mapped.
>
> > At least th
Hi,
This series adds support for i2c block read/writes. To support the maximum 32
byte read/write operations, the regmap core is extended by max_raw_read and
max_raw_write. bulk operations are splitted depending of the size of
max_raw_read/write.
The last patch needs testing before it can be appl
On Wed, 26 Aug 2015, Nathan Lynch wrote:
> On 08/26/2015 08:08 AM, Lee Jones wrote:
> > Signed-off-by: Lee Jones
> > ---
> > drivers/remoteproc/remoteproc_debugfs.c | 25 +
> > 1 file changed, 25 insertions(+)
>
> The commit message should describe why this is needed...
On Wed, 26 Aug 2015, Nathan Lynch wrote:
> On 08/26/2015 08:08 AM, Lee Jones wrote:
> > --- /dev/null
> > +++ b/drivers/remoteproc/st_remoteproc.c
> > @@ -0,0 +1,300 @@
> > +/*
> > + * ST's Remote Processor Control Driver
> > + *
> > + * Copyright (C) 2015 STMicroelectronics - All Rights Reserved
There are some buses which have a limit on the maximum number of bytes
that can be send/received. An example for this is
I2C_FUNC_SMBUS_I2C_BLOCK which does not support any reads/writes of more
than 32 bytes. The regmap_bulk operations should still be able to
utilize the full 32 bytes in this case.
This allows to read/write up to 32 bytes of data and is to be prefered
if supported before the register read/write smbus support.
Signed-off-by: Markus Pargmann
---
drivers/base/regmap/regmap-i2c.c | 49
1 file changed, 49 insertions(+)
diff --git a/driv
Add functions to access the maximum size we can read/write using
regmap_raw_read/write().
This helps drivers that need to know how much they can write with the
raw functions without problems. There are some devices (e.g. bmc150)
that have fifos as registers which need to be read in specific chunks
Check in regmap_raw_read() and regmap_raw_write() for correct maximum
sizes of the operations. Return -E2BIG if this size is not supported
because it is too big.
Also this patch causes an uninitialized variable warning so it
initializes ret (although not necessary).
Signed-off-by: Markus Pargmann
I started in the morning to build the driver from the source provided
by the vendor, but it was written in the times of kernel-version 2.4,
and I got hopelessly stuck.
Wanting to take a break, I reset my setup, and VERY strangely, what I
now observe is ::
a)
I am NOT able to send anything from th
This series adds support for the thermal sensors included in the
MT8173 SoC. Currently only basic temperature reading is supported
without any interrupt support.
The cpufreq driver for MT8173 is currently under review, so there's no
real cooling device available in mainline. Until this is availab
This adds support for the Mediatek thermal controller found on MT8173
and likely other SoCs.
The controller is a bit special. It does not have its own ADC, instead
it controls the on-SoC AUXADC via AHB bus accesses. For this reason
we need the physical address of the AUXADC. Also it controls a mux
Signed-off-by: Sascha Hauer
Reviewed-by: Daniel Kurtz
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 27237a1..ddacb86 100644
--- a/arch/
Signed-off-by: Sascha Hauer
Reviewed-by: Daniel Kurtz
---
.../bindings/thermal/mediatek-thermal.txt | 38 ++
include/dt-bindings/thermal/mt8173.h | 13
2 files changed, 51 insertions(+)
create mode 100644
Documentation/devicetree/bindings/the
%s specifier makes bpf program and kernel debugging easier.
To make sure that trace_printk won't crash the unsafe string
is copied into stack and unsafe pointer is substituted.
String is also sanitized for printable characters.
The cost of swapping FS in probe_kernel_read is
amortized over 4 chars
On 26 August 2015 at 21:02, punnaiah choudary kalluri
wrote:
> On Wed, Aug 26, 2015 at 5:49 PM, Jagan Teki wrote:
>> On 26 August 2015 at 11:56, Ranjit Waghmode
>> wrote:
>>> This series adds dual parallel mode support for Zynq Ultrascale+
>>> MPSoC GQSPI controller driver.
>>>
>>> What is dual
Hi Alexandre,
Today's linux-next merge of the rtc tree got a conflict in:
arch/arm/boot/dts/am437x-gp-evm.dts
between commits:
d3d92af19e99 ("ARM: dts: am437x-gp-evm: McASP1 node for audio support")
cf9a4850e995 ("ARM: dts: am437x-gp-evm: Enable analog audio via simple-card")
from the ar
Add a TFT LCD panel. the TFT LCD panel is WQVGA "480x272",
and the bpp is 24.
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
Changed in V15:
Rename compatible string.
arch/arm/boot/dts/ls1021a-twr.dts | 11 +++
1 file changed, 11 insertions(+)
dif
Add DCU node, DCU is a display controller of Freescale
named 2D-ACE.
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
arch/arm/boot/dts/ls1021a.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/
On Thu, Aug 20, 2015 at 09:26:20PM +0100, Matt Fleming wrote:
> On Tue, 11 Aug, at 02:16:25PM, Lee, Chun-Yi wrote:
> > +
> > +static unsigned long efi_get_rng64(efi_system_table_t *sys_table,
> > + void **rng_handle)
> > +{
> > + const struct efi_config *efi_early = _
From: Chee Nouk Phoon
Altera Modular ADC is soft IP that wraps the hardened ADC block in a Max10
device. It can be configured to dual ADC mode that supports two channel
synchronous sampling or independent single ADCs. ADC sampled values will be
written into memory slots in sequence determined by
On Thu, Aug 27, 2015 at 10:59:22AM +0530, sundeep subbaraya wrote:
> Hi,
>
>
> On Wed, Aug 26, 2015 at 8:57 PM, Nathan Sullivan
> wrote:
> > The Xilinx Zynq udc does not need the CI_HDRC_DISABLE_STREAMING flag,
> > unlike the default platform data. Add platform data specific to the
> > Zynq ud
On Wed, Aug 26, 2015 at 06:38:12PM +0100, Mark Brown wrote:
> On Wed, Aug 26, 2015 at 03:22:46PM +0200, Markus Pargmann wrote:
> > On Wed, Aug 26, 2015 at 01:35:56PM +0100, Mark Brown wrote:
> > > On Wed, Aug 26, 2015 at 07:43:16PM +0800, Henry Chen wrote:
>
> > > Why are these format functions se
On (08/27/15 13:07), Sergey Senozhatsky wrote:
[..]
> > -struct zcomp_strm *zcomp_strm_find(struct zcomp *comp)
> > +struct zcomp_strm *zcomp_strm_find(struct zcomp *comp, bool decomp)
> >
I think we can hide zcomp_strm_find()/_release (make them static),
and instead introduce:
a) zcomp_decompres
Add initial dts files and SoC support for IPQ4019
Signed-off-by: Varadarajan Narayanan
---
All,
Missed linux-arm-msm mailing list last time and
incorrectly versioned the patch as v5.
Kindly excuse.
Changes in v2:
- Added devicetree bindings documentation
Changes in v3:
Hi,
On Wed, Aug 26, 2015 at 8:57 PM, Nathan Sullivan wrote:
> The Xilinx Zynq udc does not need the CI_HDRC_DISABLE_STREAMING flag,
> unlike the default platform data. Add platform data specific to the
> Zynq udc.
>
> Based on a patch by the same name from the Xilinx vendor tree.
I am that Xil
On 8/26/2015 7:59 PM, Benjamin Tissoires wrote:
On Aug 26 2015 or thereabouts, Sivakumar Thulasimani wrote:
On 8/18/2015 1:36 AM, Benjamin Tissoires wrote:
On Aug 14 2015 or thereabouts, Stéphane Marchesin wrote:
On Wed, Aug 5, 2015 at 12:34 PM, Benjamin Tissoires
wrote:
On Jul 30 2015 or
Use resource-managed function devm_led_classdev_register instead
of led_classdev_register to make the error-path simpler.
To be compatible with the change, goto is replaced with direct
return and unneeded label is dropped. Also, remove redundant
cobalt_qube_led_remove.
Signed-off-by: Vaishali Tha
HI Nicholas & Calvin,
Thanks for the patchset. Sure We will review and we do some unit
testing on this patch series. Currently my bandwidth is occupied with
some internal activity, so by end of next week I will acknowledge this
series if all the thing are fine with this patch series.
Thanks,
Sree
On Tue, Aug 25, 2015 at 04:46:22PM -0500, Andy Gross wrote:
> On Tue, Aug 18, 2015 at 02:10:27PM +0100, Srinivas Kandagatla wrote:
> > This patch add alias node with serial0.
> >
> > Signed-off-by: Srinivas Kandagatla
> > ---
> > arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 4
> > 1 file c
On Wed, 2015-08-26 at 16:32 -0700, Jason Low wrote:
> Perhaps to be safer, we use something like load_acquire() and
> store_release() for accessing both the ->running and ->checking_timer
> fields?
Regarding using barriers, one option could be to pair them between
sig->cputime_expires and the sig
On Thu, Aug 20, 2015 at 03:47:06PM +0100, Matt Fleming wrote:
> On Tue, 11 Aug, at 02:16:25PM, Lee, Chun-Yi wrote:
> > To grab random numbers through EFI protocol as one of the entropies
> > source of swsusp key, this patch adds the logic for accessing EFI RNG
> > (random number generator) protocol
On Tue, Jun 16, 2015 at 02:31:49PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-apq8084-mtp.dts | 8
> 1 file changed, 8 insertions(+)
Applied. Thanks
On Tue, Jun 16, 2015 at 02:31:53PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Cc: Tim Bird
> Cc: Bjorn Andersson
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts | 8
On Tue, Jun 16, 2015 at 02:31:51PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-msm8660-surf.dts | 8
> 1 file changed, 8 insertions(+)
Applied. thanks
On Tue, Jun 16, 2015 at 02:31:44PM -0700, Stephen Boyd wrote:
> Add a label to the serial nodes that are being used for the
> console.
>
> Signed-off-by: Stephen Boyd
> ---
Applied. Thanks
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
On Tue, Jun 16, 2015 at 02:31:50PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Cc: Mathieu Olivari
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-ipq8064-ap148.dts | 8
> 1 file changed, 8 inserti
On Tue, Jun 16, 2015 at 02:31:45PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Cc: Mike Rapoport
> Cc: Igor Grinberg
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 8
> 1 f
On Wed, Aug 26, 2015 at 6:42 PM, Michael Kerrisk (man-pages)
wrote:
> Hello Kees, Will,
>
> In recent times I've been asked a couple of questions about seccomp(),
> and it seems like it would be worthwhile to include these topics in
> the seccomp(2) man page. Would you be able to help out with som
`perf stat -e sunrpc:svc_xprt_do_enqueue true` results in
Warning: unknown op '->'
Warning: [sunrpc:svc_xprt_do_enqueue] unknown op '->'
Similar warning for svc_handle_xprt as well.
Actually TP_printk() should never dereference an address saved in the ring
buffer that points somewhere in the ke
On Tue, Jun 16, 2015 at 02:31:52PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-msm8960-cdp.dts | 8
> 1 file changed, 8 insertions(+)
Applied. Thanks
On Tue, Jun 16, 2015 at 02:31:48PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-apq8084-ifc6540.dts | 8
> 1 file changed, 8 insertions(+)
Applied. Tha
The SiI902x is a HDMI transmitter.
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
arch/arm/boot/dts/ls1021a-twr.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a-twr.dts
b/arch/arm/boot/dts/ls1021a-twr.dts
index a2c591e
Some Freescale SoCs, there has an DVI/HDMI controller and a PHY,
attached to one of their display controller unit's LCDC interfaces.
This patch adds a driver for SiI902x. The SiI902x is a HDMI
transmitter It supports resolutions from standard definition
480i/p and 576i/p all the way to high-definit
On Tue, Jun 16, 2015 at 02:31:47PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-apq8074-dragonboard.dts | 8
> 1 file changed, 8 insertions(+)
Thanks.
On Tue, Jun 16, 2015 at 02:31:46PM -0700, Stephen Boyd wrote:
> Use stdout-path so that we don't have to put the console on the
> kernel command line.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/
On Thu, 27 Aug 2015 04:04:42 + (UTC) Mathieu Desnoyers
wrote:
> Hi Andrew,
>
> The sys_membarrier patches you have in your tree target
> x86 32-64 and generic, but I did not allocate the system call
> number on other architectures to minimize the amount of
> collisions, and because I do not
Hi Andrew,
The sys_membarrier patches you have in your tree target
x86 32-64 and generic, but I did not allocate the system call
number on other architectures to minimize the amount of
collisions, and because I do not have all those architectures
handy.
How would you recommend to proceed to alloc
Dear Sir / Madam,
I am interested in purchasing your products , which sample image is attached
to below Login link.
Please follow the link below Login link to view the sample image I am
interested to order from your company, and we sincerely hope to establish a
long-term business relation wi
1. TRCRSCTLRn - Resource Selection Control Registers n=0~1 are reserved,
we shouldn't access them.
2. The max number of 'n' here is defined in TRCIDR4.NUMRSPAIR whoes value
indicates the number of resource selection *pairs*, and 0 indicates
one resource selection pair, 1 indicates two pair
Hi Matt,
Thanks for your reviewing and sorry for my delay.
On Thu, Aug 20, 2015 at 03:12:21PM +0100, Matt Fleming wrote:
> On Tue, 11 Aug, at 02:16:24PM, Lee, Chun-Yi wrote:
> > This patch adds the codes for generating random number array as the
> > HMAC key that will used by later EFI stub code
On (08/20/15 15:35), Joonsoo Kim wrote:
> Crypto subsystem supports noctx API which doesn't require tfm.
> To get tfm in zram, we need zstrm and it is limited resource.
> If we uses noctx API, we don't need to get zstrm so that
> we get much better performance when zstrm is insufficient.
>
> This
The patch contains too much noise and unrelated changes. Its goal is
to switch zcomp to use Crypto api.
I really would love to see zram_drv aligned with
https://lkml.org/lkml/2015/8/13/343
IOW, only zcomp_decompress_begin()/zcomp_decompress_end() changes in
zram; the rest is purely zcomp
On Wed, Aug 26, 2015 at 8:13 PM, Brian Gerst wrote:
> On Wed, Aug 26, 2015 at 1:10 PM, Andy Lutomirski wrote:
>> On Tue, Aug 25, 2015 at 10:20 PM, Brian Gerst wrote:
>> Thing 2: vdso compilation with binutils that doesn't support .cfi
>> directives
>>
>> Userspace debuggers real
This patch adds the nodes required to support the UART1 node on the
MSM8916.
Signed-off-by: Andy Gross
---
arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi |8 +++
arch/arm64/boot/dts/qcom/msm8916.dtsi | 35 -
2 files changed, 42 insertions(+), 1 deletion(-)
d
Commit 62ee783bf1f8 ("smsc911x: Fix crash seen if neither ACPI nor OF is
configured or used") introduces an error check for the return value from
device_get_phy_mode() and bails out if there is an error. Unfortunately,
there are configurations where no phy is configured. Those configurations
now fa
Return -ENXIO if device property array access functions don't find
a suitable firmware interface.
This lets drivers decide if they should use available platform data
instead.
Cc: Rafael J. Wysocki
Signed-off-by: Guenter Roeck
---
v2: Added patch
v3: Document that device_property_read_string_arr
On Thu, Aug 27, 2015 at 11:26:45AM +1000, Stephen Rothwell wrote:
> Hi Vinod,
>
> Today's linux-next merge of the slave-dma tree got conflicts in:
>
> drivers/dma/Kconfig
> drivers/dma/Makefile
>
> between commit:
>
> 667dfed98615 ("dmaengine: add a driver for Intel integrated DMA 64-bit"
A bug is reported(https://bugzilla.redhat.com/show_bug.cgi?id=1227208)
that, after resumed from S3, CPU is running at a low speed.
After investigation, it is found that, BIOS has modified the value
of THERM_CONTROL register during S3, and changes it from 0 to 0x10,
since value of 0x10 means CPU can
On Wed, Aug 26, 2015 at 1:10 PM, Andy Lutomirski wrote:
> On Tue, Aug 25, 2015 at 10:20 PM, Brian Gerst wrote:
> Thing 2: vdso compilation with binutils that doesn't support .cfi
> directives
>
> Userspace debuggers really like having the vdso properly
> CFI-annotated, and th
On Wed, 2015-08-26 at 14:44 +, Joseph Myers wrote:
> On Thu, 20 Aug 2015, Michael Ellerman wrote:
>
> > On Wed, 2015-08-19 at 14:39 +, Joseph Myers wrote:
> > > I'd like to ping this patch series, not having seen any comments on it.
> > >
> > > [PATCH 0/8] math-emu: Update kernel math-emu
On Wed, Aug 26, 2015 at 10:20:23AM -0600, Toshi Kani wrote:
> diff --git a/drivers/acpi/nfit.c b/drivers/acpi/nfit.c
> index c3fe206..6993ff2 100644
> --- a/drivers/acpi/nfit.c
> +++ b/drivers/acpi/nfit.c
> @@ -701,12 +701,13 @@ static ssize_t flags_show(struct device *dev,
> {
> u16 flags =
On Thu, 2015-08-27 at 07:49 +0530, Viresh Kumar wrote:
> Few colleagues asked me why isn't checkpatch warning for (NULL == ptr)
> or (NULL != ptr) checks, as it warns for (ptr == NULL) and (ptr != NULL).
>
> Did you miss it? or was it intentional ?
I didn't miss it.
NULL == foo is relatively unu
On Wed, Aug 26, 2015 at 01:13:22PM +0300, Heikki Krogerus wrote:
> Hi Peter,
>
> On Wed, Aug 26, 2015 at 12:53:20PM +0800, Peter Chen wrote:
> > On Tue, Aug 25, 2015 at 02:04:30PM +0300, Heikki Krogerus wrote:
> > > Hi,
> > >
> > > While converting dwc3 to the unified device property interface, I
On Wed, Aug 26, 2015 at 7:32 PM, Ard Biesheuvel
wrote:
> On 26 August 2015 at 13:12, Will Deacon wrote:
>> Hello,
>>
>> [adding Ard]
>>
>> On Wed, Aug 26, 2015 at 03:40:41AM +0100, Chunyan Zhang wrote:
>>> From: Janet Liu
>>>
>>> If process A is running on CPU 0 and do execve syscall and after s
Hi Jens,
Today's linux-next merge of the block tree got a conflict in:
fs/fs-writeback.c
between commit:
006a0973ed02 ("writeback: sync_inodes_sb() must write out I_DIRTY_TIME inodes
and always call wait_sb_inodes()")
from Linus' tree and commits:
1ed8d48c57bf ("writeback: bdi_for_each
On Wed, Aug 26, 2015 at 7:26 PM, Luis R. Rodriguez wrote:
> On Wed, Aug 26, 2015 at 03:33:04PM +0100, David Howells wrote:
> Now let's review the SELinux stuff before we jump back into firmware / system
> data stuff again as there is a joint criteria to consider for all of these.
> For other peopl
On Thu, 27 Aug 2015 08:17:29 +0800
Sean Fu wrote:
> On Thu, Aug 27, 2015 at 4:36 AM, Steven Rostedt wrote:
> > On Wed, 26 Aug 2015 23:48:01 +0800
> > Sean Fu wrote:
> >
> >
> >> > Defending the patch, I can't imagine any user space code expecting the
> >> > current behavior. The current behavio
On 2015/8/27 5:40, Thomas Gleixner wrote:
> But back to the IPIs. We need infrastructure and DT support to:
>
> 1) reserve an IPI
>
> 2) send an IPI
>
> 3) request/free an IPI
>
> #1 We have no infrastructure for that, but we definitely need one.
>
>We can look at the IPI as a single linux
On Wednesday 08/26 at 04:09 +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> These objects can be referenced concurrently throughout the driver, we
> need a way to make sure threads can't delete them out from under
> each other. This patch adds the refcount, and refactors the co
On Fri, Nov 14, 2014 at 12:27 AM, Joe Perches wrote:
> It seems there are more and more uses of "if (!ptr)"
> in preference to "if (ptr == NULL)" so add a --strict
> test to emit a message when using the latter form.
>
> This also finds (ptr != NULL).
>
> Fix it too if desired.
>
> Signed-off-by:
On Wed, Aug 26, 2015 at 03:24:14PM -0500, Han Xu wrote:
> Hi Shijie,
>
> The features for MX6 and MX7 are not identical, I would love to use
> two macros in this patch and will push another patch to use quirks to
> distinguish them, is that Okay for you?
okay, no problem.
Actually, you should be
From: Rafael J. Wysocki
Add infrastructure needed to expose data-only subnodes of ACPI
device objects introduced previously via sysfs.
Each data-only subnode is represented as a sysfs directory under
the directory corresponding to its parent object (a device or a
data-only subnode). Each of the
From: Rafael J. Wysocki
Move the extraction of _DSD properties from acpi_init_properties()
to a separate routine called acpi_extract_properties() to make the
subsequent changes more straightforward.
Signed-off-by: Rafael J. Wysocki
Tested-by: Mika Westerberg
---
drivers/acpi/property.c | 69
From: Rafael J. Wysocki
Split acpi_get_gpiod_by_index() into three smaller routines to
allow the subsequent change of the generic firmware node properties
code to be more strarightforward.
Signed-off-by: Rafael J. Wysocki
Tested-by: Mika Westerberg
---
drivers/gpio/gpiolib-acpi.c | 113 +
From: Rafael J. Wysocki
Make device_get_next_child_node() work with ACPI data-only subnodes
introduced previously.
Namely, replace acpi_get_next_child() with acpi_get_next_subnode()
that can handle (and return) child device objects as well as child
data-only subnodes of the given device and modi
From: Rafael J. Wysocki
Modify is_acpi_node() to return "true" for ACPI data-only subnodes as
well as for ACPI device objects and change the name of to_acpi_node()
to to_acpi_device_node() so it is clear that it covers ACPI device
objects only. Accordingly, introduce to_acpi_data_node() to cover
Hi Everyone,
This has been in the works for some time, but the official document it is
based on was not quite ready before the last week. It now is available at
http://www.uefi.org/sites/default/files/resources/_DSD-hierarchical-data-extension-UUID-v1.pdf
The issue at hand is that we need to be
From: Rafael J. Wysocki
In some cases, the information expressed via device properties is
hierarchical by nature. For example, the properties of a composite
device consisting of multiple semi-dependent components may need
to be represented in the form of a tree of property data sets
correspondin
On (08/20/15 15:35), Joonsoo Kim wrote:
> zram regards zstrm's buffer as compression destination buffer, but,
> it is not intuitive and there is no document about it. Providing
> destination buffer to zcomp_compress() directly seems more intuitive
> interface to me so this patch changes zcomp_compr
On Wednesday 08/26 at 04:09 +, Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger
>
> The fw_event_work struct is concurrently referenced at shutdown, so
> add a refcount to protect it, and refactor the code to use it.
>
> Additionally, refactor _scsih_fw_event_cleanup_queue() such that
None of the patches are reaching Viresh or Daniel directly as
get_maintainers doesn't report us as maintainers. Looks like file header
or history of commits isn't able to do that properly.
Add a separate entry for cpu_cooling driver in MAINTAINERS.
Acked-by: Eduardo Valentin
Acked-by: Amit Danie
Smack labeling is always done in user space, not in kernel space.
Because kernel can't know which node or preocess should has the certain label
and it shouldn't be neither. Therefore there is a distinct time gap between
file creation and the labeling which might be about few miliseconds or even
ind
Current Smack object's label is always given by userspace.
So there might be a certain gap between the time of file creation
and the time of applying actual label. And because of the time gap,
it results unintended Smack denial time to time.
If accessing a file occurs ahead of labeling, Smack modu
On (08/20/15 15:35), Joonsoo Kim wrote:
>
> lz4hc's decompression doesn't requires any scratch buffer so
> it doesn't need tfm context. Hence, it can support
> crypto compression noctx API and this patch implements it.
>
> Signed-off-by: Joonsoo Kim
> ---
> crypto/lz4hc.c | 17 -
I don’t have any problem changing this in ACPICA if/when you all agree.
> -Original Message-
> From: Toshi Kani [mailto:toshi.k...@hp.com]
> Sent: Wednesday, August 26, 2015 4:36 PM
> To: Rafael J. Wysocki
> Cc: Williams, Dan J; Wysocki, Rafael J; Moore, Robert; linux-
> nvd...@lists.01.o
On Wed, Aug 19, 2015 at 11:52 AM, Vaishali Thakkar
wrote:
> In the function cpufreq_get_requested_power, the memory allocated
> for load_cpu is live within the function only. And after the
> allocation it is immediately freed with devm_kfree. There is no
> need to allocate memory for load_cpu with
On (08/20/15 15:34), Joonsoo Kim wrote:
> lz4's decompression doesn't requires any scratch buffer so
> it doesn't need tfm context. Hence, it can support
> crypto compression noctx API and this patch implements it.
>
> Signed-off-by: Joonsoo Kim
> ---
> crypto/lz4.c | 17 -
> 1 f
On (08/20/15 15:34), Joonsoo Kim wrote:
> lzo's decompression doesn't requires any scratch buffer so
> it doesn't need tfm context. Hence, it can support
> crypto compression noctx API and this patch implements it.
>
> Signed-off-by: Joonsoo Kim
> ---
> crypto/lzo.c | 18 +-
> 1
> -Original Message-
> From: Liam Girdwood [mailto:liam.r.girdw...@linux.intel.com]
> Sent: Wednesday, August 26, 2015 5:01 PM
> To: Jie, Yang
> Cc: Takashi Iwai; Dmitry Torokhov; Luis R. Rodriguez;
> joonas.lahti...@linux.intel.com; Tom Gundersen; Ming Lei; Al Viro; Greg
> Kroah-Hartman; K
In multi-segment system, uncore devices may belong to buses whose segment
number is other than 0.
:ff:10.5 System peripheral: Intel Corporation Xeon E5 v3/Core i7
Scratchpad & Semaphore Registers (rev 03)
...
0001:7f:10.5 System peripheral: Intel Corporation Xeon E5 v3/Core i7
S
On 08/19/15 08:41, Michal Marek wrote:
On Mon, Jul 13, 2015 at 08:59:33PM +1000, Anton Blanchard wrote:
Hi,
> When the host's C compiler is clang, and when attempting to
> cross-compile Linux e.g. to MIPS with mipsel-linux-gcc, the
> Makefile would incorrectly detect the use
Hello Kees, Will,
In recent times I've been asked a couple of questions about seccomp(),
and it seems like it would be worthwhile to include these topics in
the seccomp(2) man page. Would you be able to help out with some
answers?
=== Use of the instruction pointer in seccomp filters ===
The sec
On Thu, 2015-08-13 at 08:43 -0700, K. Y. Srinivasan wrote:
> From: Keith Mange
>
> Currently we are making decisions based on vmbus protocol versions
> that have been negotiated; use storage potocol versions instead.
>
> Tested-by: Alex Ng
> Signed-off-by: Keith Mange
> Signed-off-by: K. Y. Sr
> From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
>
> On 08/24/2015 10:53 PM, 河合英宏 / KAWAI，HIDEHIRO wrote:
> >> From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
> >>
> >> On 08/23/2015 08:52 PM, 河合英宏 / KAWAI，HIDEHIRO wrote:
> From: Corey
On Wed, Aug 26, 2015 at 6:44 PM, Viresh Kumar wrote:
> On 26-08-15, 14:09, Javi Merino wrote:
>> On Wed, Aug 26, 2015 at 01:51:58PM +0100, Viresh Kumar wrote:
>> > On 26-08-15, 13:47, Javi Merino wrote:
>> > > I missed this because I wasn't CCed :( Thankfully, I'll be in
>> > > MAINTAINERS for th
> I can include your patch in the series and then use boolean for the new
> checking_timer field. However, it looks like this applies on an old
> kernel. For example, the spin_lock field has already been removed from
> the structure.
Apologies; that was 4.1.6. A 4.2-rc8 patch is appended (it's a
Hi Vinod,
Today's linux-next merge of the slave-dma tree got conflicts in:
drivers/dma/Kconfig
drivers/dma/Makefile
between commit:
667dfed98615 ("dmaengine: add a driver for Intel integrated DMA 64-bit")
from the pm, mfd and rtc trees and commits:
3c21619077be ("dmaengine: sort the K
1 - 100 of 803 matches
Mail list logo
