On Monday, April 18, 2016 07:07:39 PM Lauri Kasanen wrote:
> The previous text was confusing, leading readers to think this
> driver was a duplicate, and so didn't need to be enabled.
>
> After the removal of the older staging driver, this is the only
> driver in mainline for these devices.
>
>
On Monday, April 18, 2016 06:45:09 PM Kalle Valo wrote:
> Lauri Kasanen writes:
>
> > The previous text was confusing, leading readers to think this
> > driver was a duplicate, and so didn't need to be enabled.
> >
> > After the removal of the older staging driver, this is the only
On Mon, Apr 18, 2016 at 04:08:38PM +0200, Oliver Neukum wrote:
> On Mon, 2016-04-18 at 06:57 -0700, Guenter Roeck wrote:
> > On 04/18/2016 01:32 AM, Oliver Neukum wrote:
> > > On Mon, 2016-04-18 at 03:53 +0100, Alexey Klimov wrote:
> > >> This patch creates new driver that supports StreamLabs usb
On 04/17, kbuild test robot wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: b9f5dba225aede4518ab0a7374c2dc38c7c049ce
> commit: 5eeb50de42fd3251845d03c556db012267c72b3f uprobes: Change
> handle_trampoline() to flush the frames invalidated
On Mon, Apr 18, 2016 at 04:55:36PM +0200, Julia Lawall wrote:
> Add __init attribute on a function that is only called from other __init
> functions and that is not inlined, at least with gcc version 4.8.4 on an
> x86 machine with allyesconfig. Currently, the function is put in the
>
On Mon, Apr 18, 2016 at 8:35 AM, Andrea Merello
wrote:
> On Thu, Apr 14, 2016 at 6:10 PM, Rob Herring wrote:
>> On Wed, Apr 13, 2016 at 10:36:31AM +0200, Andrea Merello wrote:
>>> According to Documentation/i2c/smbus-protocol, a smbus controller driver
On Monday, April 18, 2016 07:42:05 PM Kalle Valo wrote:
> Christian Lamparter writes:
>
> > On Monday, April 18, 2016 06:45:09 PM Kalle Valo wrote:
> >> Lauri Kasanen writes:
> >>
> >> > --- a/drivers/net/wireless/ath/carl9170/Kconfig
> >> > +++
On Mon, Apr 18, 2016 at 10:05:22AM -0700, John Stultz wrote:
> On Mon, Apr 11, 2016 at 5:57 PM, Shaohua Li wrote:
> > Calvin found 'perf record -a --call-graph dwarf -- sleep 5' making
> > clocksource
> > switching to hpet. We found similar symptom in another machine. Here is an
>
On Mon, Apr 18, 2016 at 10:32 AM, Shaohua Li wrote:
> On Mon, Apr 18, 2016 at 10:05:22AM -0700, John Stultz wrote:
>> On Mon, Apr 11, 2016 at 5:57 PM, Shaohua Li wrote:
>> > Calvin found 'perf record -a --call-graph dwarf -- sleep 5' making
>> > clocksource
>> >
On Mon, 2016-04-18 at 19:15 +0200, Sebastian Andrzej Siewior wrote:
> take 2. There is this else case in pin_current_cpu() where I take
> hp_lock. I didn't manage to get in there. So I *think* we can get rid of
> the lock now. Since there is no lock (or will be) we can drop the whole
>
On Friday 08 April 2016 14:02:11 Baolin Wang wrote:
> security_settime() uses a timespec, which is not year 2038 safe
> on 32bit systems. Thus this patch introduces the security_settime64()
> function with timespec64 type. We also convert the cap_settime() helper
> function to use the 64bit types.
The previous text was confusing, leading readers to think this
driver was a duplicate, and so didn't need to be enabled.
After the removal of the older staging driver, this is the only
driver in mainline for these devices.
Signed-off-by: Lauri Kasanen
---
v3: Remove all firmware
On 18 April 2016 at 18:04, Ard Biesheuvel wrote:
> These patches allow the arch to define the page_to_virt() conversion that
> is used in lowmem_page_address(). This is desirable for arm64, where this
> conversion is trivial when CONFIG_SPARSEMEM_VMEMMAP is enabled,
On Fri, 15 Apr 2016 05:39:24 -0500, mchri...@redhat.com wrote:
> From: Mike Christie
>
> This has submit_bh users pass in the operation and flags separately,
> so submit_bh_wbc can setup bio->bi_op and bio-bi_rw on the bio that
> is submitted.
>
> Signed-off-by: Mike
From: Yinghai Lu
Since the boot_params can be found using the real_mode global variable,
there is no need to pass around a pointer to it. This slightly simplifies
the choose_kernel_location function and its callers.
Signed-off-by: Yinghai Lu
[kees:
The name "choose_kernel_location" isn't specific enough, and doesn't
describe the primary thing it does: choosing a random location. This
patch renames it to "choose_random_location", and clarifies the what
routines are contained in the kaslr.c source file.
Suggested-by: Ingo Molnar
Christian Lamparter writes:
> On Monday, April 18, 2016 06:45:09 PM Kalle Valo wrote:
>> Lauri Kasanen writes:
>>
>> > --- a/drivers/net/wireless/ath/carl9170/Kconfig
>> > +++ b/drivers/net/wireless/ath/carl9170/Kconfig
>> > @@ -5,12 +5,10 @@ config
On Fri, Apr 15, 2016 at 04:13:18PM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Apr 15, 2016 at 09:43:34AM +0900, Chanwoo Choi wrote:
> > This patch removes the deprecated notifier API of extcon framework and then
> > use
> > the new extcon API[2] with the unique id[1] to indicate the each
On Mon, Apr 18, 2016 at 06:09:09AM -0700, Christoph Hellwig wrote:
> On Thu, Apr 14, 2016 at 10:45:50AM -0600, Jason Gunthorpe wrote:
> > On Thu, Apr 14, 2016 at 08:41:35AM -0700, Dennis Dalessandro wrote:
> > > This patch series removes the write() interface for user access in favor
> > > of an
From: Dan Carpenter
Date: Mon, 18 Apr 2016 11:44:49 +0300
> We deleted a line of code and accidentally made the "return put_user()"
> part of the if statement when it's supposed to be unconditional.
>
> Fixes: 9f9a45beaa96 ('udp: do not expect udp headers on ioctl
Hi all,
There is confusion about the usage of format for me.
E.g. The event config is not continuous for uncore.
cat /sys/devices/uncore_qpi_0/format/event
config:0-7,21
I once thought that the user input should be
uncore_qpi_0/event=0x200038,/
So I submitted this patch and previous patch
On 04/17/2016 08:25 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.67 release.
> There are 37 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Mon, Apr 18, 2016 at 11:25:32AM +0900, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.67 release.
> There are 37 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
Add documentation for the tpm_vtpm device driver that implements
support for providing TPM functionality to Linux containers.
Parts of this documentation were recycled from the Xen vTPM
device driver documentation.
Update the documentation for the ioctl numbers.
Signed-off-by: Stefan Berger
Introduce TPM_CHIP_FLAG_VIRTUAL to be used when the chip device has no
parent device.
Prevent sysfs entries requiring a parent device from being created.
Signed-off-by: Stefan Berger
Reviewed-by: Jason Gunthorpe
---
This patch implements a proxy driver for supporting multiple emulated TPMs
in a system.
The driver implements a device /dev/vtpmx that is used to created
a client device pair /dev/tpmX (e.g., /dev/tpm10) and a server side that
is accessed using a file descriptor returned by an ioctl.
The device
On Mon, 18 Apr 2016, Ralf Baechle wrote:
> I extracted a rather simple test case:
>
> $ echo >> testcase .s << EOF
> .setmips3
> dli $2, 0x90008000
> EOF
> $ mips-linux-as -mips3 -march=r4600 -o testcase.o testcase.s
> testcase.s: Assembler messages:
>
On Fri, 15 Apr 2016 14:15:51 -0500, mchri...@redhat.com wrote:
> From: Mike Christie
>
> This patch has nilfs use bio->bi_op for REQ_OPs and rq_flag_bits
> to bio->bi_rw.
>
> Signed-off-by: Mike Christie
> Reviewed-by: Christoph Hellwig
>
From: Herbert Xu
Date: Mon, 18 Apr 2016 16:02:02 +0800
> In fact this strikes me as a kbuild bug because CRYPTO_GCM already
> selects (indirectly) CRYPTO_ALGAPI so why is this happening at all?
Selects don't trigger selects.
On Mon, Apr 18, 2016 at 06:01:33PM +0200, Arnd Bergmann wrote:
> I seem to have only received patches 3 and 4, both on my personal
> address and on lkml. Any idea what happened?
> Unless you did not mean to send these patches at all, could you resend
> the entire series and put me and the y2038
On Mon, Apr 18, 2016 at 06:45:38PM +0800, l...@kernel.org wrote:
> From: Zefan Li
>
> This is the start of the stable review cycle for the 3.4.112 release.
> There are 92 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with
Add scope parameter to the arm64_cpu_capabilities::matches(), so that
this can be reused for checking the capability on a given CPU vs the
system wide. The system uses the default scope associated with the
capability for initialising the CPU_HWCAPs and ELF_HWCAPs.
Cc: James Morse
In order to make improvements to KASLR behavior, it has been suggested
that the code should be cleaned up a bit first. This is the start of
those changes. Since there are no stand-alone bug fixes in the later
patches, I will begin here. First with a rename followed by variable
name changes and
In order to avoid confusion over what this file provides, rename it to
kaslr.c since it is used exclusively for the kernel ASLR, not userspace
ASLR.
Suggested-by: Ingo Molnar
Signed-off-by: Kees Cook
---
arch/x86/boot/compressed/Makefile | 2 +-
The variable "random" is also the name of a libc function. It's better
coding style to avoid overloading such things, so rename it to the more
accurate "random_addr".
Suggested-by: Ingo Molnar
Signed-off-by: Kees Cook
---
The function "decompress_kernel" now performs many more duties, so this
patch renames it to "extract_kernel" and updates callers and comments.
Additionally the file header comment for misc.c is improved to actually
describe what is contained.
Suggested-by: Ingo Molnar
The non-compressed boot code uses the (much more obvious) name
"boot_params" for the global pointer to the x86 boot parameters. The
compressed kernel loader code, though, was using the legacy name
"real_mode". There is no need to have a different name, and changing it
improves readability.
From: Herbert Xu
Date: Mon, 18 Apr 2016 18:43:36 +0800
> Right, the problem is that nothing within crypto ever selects
> CRYPTO since it's also used as a way of hiding the crypto menu
> options.
As far as I understand it, this won't help. Because selects do not
On Thu, Apr 7, 2016 at 11:02 PM, Baolin Wang wrote:
> security_settime() uses a timespec, which is not year 2038 safe
> on 32bit systems. Thus this patch introduces the security_settime64()
> function with timespec64 type. We also convert the cap_settime() helper
>
On Tue, Apr 12, 2016 at 04:16:40PM +0100, Peter Griffin wrote:
> This patch adds the DT doc for the flashss regulator driver which is
> found in stih407 based silicon.
>
> Signed-off-by: Peter Griffin
> ---
> .../devicetree/bindings/regulator/st-flashss.txt | 43
>
On Tue, Apr 12, 2016 at 06:22:25PM -0700, Tai Nguyen wrote:
> Documentation: Add documentation for APM X-Gene SoC PMU DTS binding
>
> Signed-off-by: Tai Nguyen
> ---
> .../devicetree/bindings/perf/apm-xgene-pmu.txt | 116
> +
> 1 file changed, 116
On Mon, 2016-04-18 at 16:52 +, KY Srinivasan wrote:
[]
> > > +bool ixgbevf_on_hyperv(struct ixgbe_hw *hw)
> > > +{
> > > + if (hw->mbx.ops.check_for_msg == NULL)
> > > + return true;
> > > + else
> > > + return false;
> > > +}
trivia:
bool func(...)
{
* Mike Galbraith | 2016-04-08 18:49:28 [+0200]:
>On Fri, 2016-04-08 at 16:51 +0200, Sebastian Andrzej Siewior wrote:
>
>> Is there anything you can hand me over?
>
>Sure, I'll send it offline (yup, that proud of my scripting;)
>
> -Mike
take 2. There is this else case in pin_current_cpu()
mes kmalloc(128)/kfree -> 127 cycles
1 times kmalloc(256)/kfree -> 119 cycles
1 times kmalloc(512)/kfree -> 112 cycles
1 times kmalloc(1024)/kfree -> 112 cycles
1 times kmalloc(2048)/kfree -> 112 cycles
10000 times kmalloc(4096)/kfree -> 112 cycles
1 times
I will send the next version today. Note that I get_random_bytes_arch
is used because at that stage we have 0 bits of entropy. It seemed
like a better idea to use the arch version that will fallback on
get_random_bytes sub API in the worse case.
On Fri, Apr 15, 2016 at 3:47 PM, Thomas Garnier
On Sun, Apr 17, 2016 at 10:22 PM, K. Y. Srinivasan wrote:
> On Hyper-V, the VF/PF communication is a via software mediated path
> as opposed to the hardware mailbox. Make the necessary
> adjustments to support Hyper-V.
>
> Signed-off-by: K. Y. Srinivasan
>
On 04/18/2016 02:46 AM, Laxman Dewangan wrote:
NVIDIA's Tegra210 support the HW debounce in the GPIO
controller for all its GPIO pins.
Add support for setting debounce timing by implementing the
set_debounce callback of gpiochip.
diff --git a/drivers/gpio/gpio-tegra.c
Christian Lamparter wrote:
> Sure, but this could be a different patch then. I think Intel devices
> (iwlwifi, iwlegacy and ipw2x00) have a similar text about "download
> firmware from this device from our homepage here" too. So if we want,
> we can remove them altogether?
linux-firmware.git
On Mon, Apr 18, 2016 at 09:25:57AM +0200, Wadim Egorov wrote:
> It seems this topic has been already discussed here [1].
> So the right solution is just to rename the rk808 struct in rk808.h,
> don't touch the driver names and config options and naming the
> additional RK818 PMIC in the Kconfig?
Hello Krzysztof,
On 04/18/2016 09:33 AM, Krzysztof Kozlowski wrote:
> Driver did not provide default value for ramp delay for LDOs which lead
> to warning in dmesg, e.g. on Odroid XU4:
>
> [1.486076] vdd_ldo9: ramp_delay not set
> [1.506875] vddq_mmc2: ramp_delay not set
> [1.523766]
On Mon, Apr 11, 2016 at 5:57 PM, Shaohua Li wrote:
> We use watchdog clocksource to detect unstable clocksource. This assumes
> watchdog clocksource is correct. But it's possible watchdog clocksource
> is crappy, please see previous patch. Double check if watchdog interval
> is too
On 18 April 2016 17:49:39 BST, Laxman Dewangan wrote:
>
>On Sunday 17 April 2016 04:24 PM, Jonathan Cameron wrote:
>> On 14/04/16 15:41, Laxman Dewangan wrote:
>> +static int gadc_thermal_read_channel(struct gadc_thermal_info *gti,
>int *val)
>> +{
>> +int ret;
>> +
>>
On Mon, Apr 18, 2016 at 10:42:38AM -0700, John Stultz wrote:
> On Mon, Apr 18, 2016 at 10:32 AM, Shaohua Li wrote:
> > On Mon, Apr 18, 2016 at 10:05:22AM -0700, John Stultz wrote:
> >> On Mon, Apr 11, 2016 at 5:57 PM, Shaohua Li wrote:
> >> > Calvin found 'perf record
On Mon, Apr 18, 2016 at 05:09:42PM +0200, Ard Biesheuvel wrote:
> We can simply use a relocated 64-bit literal to store the address of
> __secondary_switched(), and the relocation code will ensure that it
> holds the correct value at secondary entry time, as long as we make sure
> that the literal
On 04/15/2016 09:54 PM, Tony Lindgren wrote:
> * santosh shilimkar [160415 08:22]:
>> On 4/15/2016 2:26 AM, Grygorii Strashko wrote:
>>>
>>> Santosh, Tony, do you want me to perform any additional actions regarding
>>> this patch?
>>>
>> This patch should be run
On Mon, 4 Apr 2016 21:52:46 -0700
Alexei Starovoitov wrote:
> Hi Steven, Peter,
>
> last time we discussed bpf+tracepoints it was a year ago [1] and the reason
> we didn't proceed with that approach was that bpf would make arguments
> arg1, arg2 to trace_xx(arg1, arg2) call to be
On 18/04/2016 at 06:15:40 +, Qianyu Gong wrote :
> Hi Akinobu,
>
> I got an rtc call trace when booting 4.6 kernel on our board and I found it
> was caused by this patch:
>
> commit fc1dcb0b39dbb10d3290f2fcd6e154670f699166
> Author: Akinobu Mita
> Date: Mon Mar 7
On 04/18/2016 02:46 AM, Laxman Dewangan wrote:
Use of_device_get_match_data() for getting matched data
instead of implementing this locally.
This patch,
Reviewed-by: Stephen Warren
On Mon, Apr 18, 2016 at 06:50:52PM +0300, Peter Ujfalusi wrote:
> On 02/17/2016 09:52 PM, Peter Ujfalusi wrote:
> > On the other hand this ABI is backwards compatible since if it is missing it
> > will default to the configuration we right now have regarding to sysclk_dir
> > and sysclk_id.
> >
On Mon, Apr 18, 2016 at 11:27:42AM +0900, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.8 release.
> There are 137 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 04/17/2016 08:27 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.8 release.
> There are 137 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri, Apr 15, 2016 at 1:09 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> This change makes later calculations about where the kernel is located
>> easier to reason about. To better understand this change,
On Monday, April 18, 2016 06:47:44 PM Xose Vazquez Perez wrote:
> Christian Lamparter wrote:
>
> > Sure, but this could be a different patch then. I think Intel devices
> > (iwlwifi, iwlegacy and ipw2x00) have a similar text about "download
> > firmware from this device from our homepage here"
On Monday 18 April 2016 09:59 PM, Stephen Warren wrote:
On 04/18/2016 02:46 AM, Laxman Dewangan wrote:
Remove the file static device handle variable as this is just
required for prints. The required handle can be stored in
tegra_gpio_chip and hence it become redundancy.
This seems fine as
On Monday 18 April 2016 10:08 PM, Stephen Warren wrote:
On 04/18/2016 02:46 AM, Laxman Dewangan wrote:
+
+/* There is only one debounce count register per port and hence
+ * set the maximum of current and requested debounce time.
+ */
+max_dbc =
On Mon, 2016-04-18 at 11:20 -0400, Eric Sandeen wrote:
>
> On 4/14/16 10:17 PM, Dave Chinner wrote:
> > On Thu, Apr 14, 2016 at 09:57:07AM +0200, Florian Margaine wrote:
> > > This lets userland get the filesystem freezing status, aka
> > > whether the
> > > filesystem is frozen or not. This is
On 4/18/16 1:20 PM, Florian Margaine wrote:
> On Mon, 2016-04-18 at 11:20 -0400, Eric Sandeen wrote:
>> >
>> > On 4/14/16 10:17 PM, Dave Chinner wrote:
>>> > > On Thu, Apr 14, 2016 at 09:57:07AM +0200, Florian Margaine wrote:
> > > This lets userland get the filesystem freezing status, aka
On 4/18/2016 11:40 AM, Christoph Hellwig wrote:
> On Mon, Apr 18, 2016 at 11:21:12AM -0400, Sinan Kaya wrote:
>> I was looking at the code. I don't see how removing virt_to_page + vmap
>> would solve the issue.
>>
>> The code is trying to access the buffer space with direct.buf member
>> from the
Le lundi 18 avril 2016 à 16:22 +0800, tiffany lin a écrit :
> > > We are plaining to remove m2m framework in th feature, although
> we think
> >
> > Remove it for just the decoder driver or both encoder and decoder?
> >
> Remove it from decoder driver.
Did you look at how CODA handle it
On Sun, 17 Apr 2016, Davidlohr Bueso wrote:
diff --git a/kernel/locking/qspinlock_stat.h b/kernel/locking/qspinlock_stat.h
index 72722334237a..ddcd653c942c 100644
--- a/kernel/locking/qspinlock_stat.h
+++ b/kernel/locking/qspinlock_stat.h
@@ -225,12 +225,18 @@ static int __init
On 04/18/2016 02:46 AM, Laxman Dewangan wrote:
Remove the file static device handle variable as this is just
required for prints. The required handle can be stored in
tegra_gpio_chip and hence it become redundancy.
This seems fine as far as it goes, but if it's worth doing this, please
move
On Mon, Apr 18, 2016 at 4:46 AM, Mark Brown wrote:
> On Mon, Apr 18, 2016 at 06:20:00PM +0800, Xing Zheng wrote:
>> On 2016年04月18日 18:03, Xing Zheng wrote:
>
>> sound {
>> ..
>> simple-audio-card,dai-link@0 {
>> format = "i2s";
>>
> -Original Message-
> From: Alexander Duyck [mailto:alexander.du...@gmail.com]
> Sent: Monday, April 18, 2016 9:18 AM
> To: KY Srinivasan
> Cc: David Miller ; Netdev
> ; linux-kernel@vger.kernel.org;
>
Hello Krzysztof,
On 04/18/2016 03:44 AM, Krzysztof Kozlowski wrote:
> The bindings like s2mps11,buck6-ramp-enable or s2mps11,buck2-ramp-delay
> where ignored. They were never parse by s2mps11 regulator driver. Also
> the values used in these bindings were equal to default reset values of
>
On Sunday 17 April 2016 04:24 PM, Jonathan Cameron wrote:
On 14/04/16 15:41, Laxman Dewangan wrote:
+static int gadc_thermal_read_channel(struct gadc_thermal_info *gti, int *val)
+{
+ int ret;
+
+ ret = iio_read_channel_processed(gti->channel, val);
+ if (ret < 0)
+
On Mon, Apr 18, 2016 at 03:53:36AM +0100, Alexey Klimov wrote:
> This patch creates new driver that supports StreamLabs usb watchdog
> device. This device plugs into 9-pin usb header and connects to
> reset pin and reset button on common PC.
>
> USB commands used to communicate with device were
mes kmalloc(128)/kfree -> 127 cycles
1 times kmalloc(256)/kfree -> 119 cycles
1 times kmalloc(512)/kfree -> 112 cycles
1 times kmalloc(1024)/kfree -> 112 cycles
1 times kmalloc(2048)/kfree -> 112 cycles
10000 times kmalloc(4096)/kfree -> 112 cycles
1 times
From: Jason Gunthorpe
The final thing preventing this was the way the sysfs files were
attached to the pdev. Follow the approach developed for ppi and move
the sysfs files to the chip->dev with symlinks from the pdev
for compatibility. Everything in the core now
The following series of patches implements a multi-instance vTPM
proxy driver that can dynamically create TPM 'server' and client device
pairs.
Using an ioctl on the provided /dev/vtpmx, a client-side vTPM device
and a server side file descriptor is created. The file descriptor must
be passed to
Hi, how are you? My name is J Eric Denials, External Financial Auditor at
Lloyds Banking Group plc., London. It is a pleasure to contact you at this time
through this medium. I have a cool and legitimate deal to do with you as you're
a foreigner, it will be mutually beneficial to both. If
On Mon, Apr 18, 2016 at 11:51:41AM -0400, David Woodhouse wrote:
> On Mon, 2016-04-18 at 18:30 +0300, Michael S. Tsirkin wrote:
> >
> > > Setting (only) VIRTIO_F_IOMMU_PASSTHROUGH indicates to the guest that
> > > its own operating system's IOMMU code is expected to be broken, and
> > > that the
On Mon, Apr 18, 2016 at 11:27:52AM +0900, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.5.2 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 04/17/2016 08:27 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.5.2 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
This series is an attempt at fixing the maxcpus=n behavior
on arm64. So far we have disabled hotplugging a CPU > n,
when maxcpus=n is in effect, due to following reasons.
1) Possible cpu feature incompatibilities with the new CPU
in heterogeneous systems.
2) New CPU requiring an errata work
On Mon, Apr 18, 2016 at 08:43:39PM +0800, PC Liao wrote:
> +Optional properties:
> +- sound-dai: audio codec dai on capture path
> + < 0> : Default setting. Connect rt5650 I2S1 for capture. (dai_name
> = rt5645-aif1)
> + < 1> : Connect rt5650 I2S2 for capture. (dai_name = rt5645-aif2)
Stephen Boyd writes:
> On 04/13, Eric Anholt wrote:
>> Signed-off-by: Eric Anholt
>> ---
>
> Acked-by: Stephen Boyd
>
> Or can I merge this? It wasn't addressed To: me so who knows.
Yeah, please merge it.
signature.asc
On Monday 18 April 2016 11:01 PM, Jonathan Cameron wrote:
On 18 April 2016 17:49:39 BST, Laxman Dewangan wrote:
On Sunday 17 April 2016 04:24 PM, Jonathan Cameron wrote:
On 14/04/16 15:41, Laxman Dewangan wrote:
+static int gadc_thermal_read_channel(struct
From: ok...@codeaurora.org
Date: Mon, 18 Apr 2016 01:06:27 -0400
> On 2016-04-18 00:00, David Miller wrote:
>> From: Sinan Kaya
>> Date: Sat, 16 Apr 2016 18:23:32 -0400
>>
>>> Current code is assuming that the address returned by
>>> dma_alloc_coherent
>>> is a logical
The open coded conversion from struct page address to virtual address in
lowmem_page_address() involves an intermediate conversion step to pfn
number/physical address. Since the placement of the struct page array
relative to the linear mapping may be completely independent from the
placement of
On 4/18/2016 11:59 AM, David Miller wrote:
> From: ok...@codeaurora.org
> Date: Mon, 18 Apr 2016 01:06:27 -0400
>
>> On 2016-04-18 00:00, David Miller wrote:
>>> From: Sinan Kaya
>>> Date: Sat, 16 Apr 2016 18:23:32 -0400
>>>
Current code is assuming that the address
To align with generic code and other architectures that expect the macro
page_to_virt to produce an expression whose type is 'void*', drop the
arch specific definition, which is never referenced anyway.
Signed-off-by: Ard Biesheuvel
---
Signed-off-by: Maarten ter Huurne
---
drivers/mtd/nand/jz4740_nand.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mtd/nand/jz4740_nand.c b/drivers/mtd/nand/jz4740_nand.c
index 673ceb2..2f39ee1 100644
--- a/drivers/mtd/nand/jz4740_nand.c
+++
These patches allow the arch to define the page_to_virt() conversion that
is used in lowmem_page_address(). This is desirable for arm64, where this
conversion is trivial when CONFIG_SPARSEMEM_VMEMMAP is enabled, while
breaking it up into __va(PFN_PHYS(page_to_pfn(page))), as is done currently
in
To align with other architectures, the expression produced by expanding
the macro page_to_virt() should be of type void*, since it returns a
virtual address. Fix that, and also fix up an instance where page_to_virt
was expected to return 'unsigned long', and drop another instance that was
entirely
maxcpu=n sets the number of CPUs activated at boot time to a max of n,
but allowing the remaining CPUs to be brought up later if the user
decides to do so. However, on arm64 due to various reasons, we disallowed
hotplugging CPUs beyond n, by marking them not present. Now that
we have checks in
CPU Errata work arounds are detected and applied to the
kernel code at boot time and the data is then freed up.
If a new hotplugged CPU requires a work around which
was not applied at boot time, there is nothing we can
do but simply fail the booting.
Cc: Will Deacon
Cc: Mark
From: Marc Zyngier
When introducing the whole CPU feature detection framework,
we lost the capability to detect a mismatched GIC configuration
(using the GICv2 MMIO interface, but having the system register
interface enabled).
In order to solve this, use the new
From: Marc Zyngier
Now that the capabilities are only available once all the CPUs
have booted, we're unable to check for a particular feature
in any subsystem that gets initialized before then.
In order to support this, introduce a local_cpu_has_cap() function
that tests
Hello.
On 04/18/2016 05:24 PM, James Hartley wrote:
Now that there are different revisions of the Pistachio SoC
in circulation, add this information to the boot log to make
it easier for users to determine which hardware they have.
Signed-off-by: James Hartley
On Mon, Apr 11, 2016 at 5:57 PM, Shaohua Li wrote:
> Calvin found 'perf record -a --call-graph dwarf -- sleep 5' making clocksource
> switching to hpet. We found similar symptom in another machine. Here is an
> example:
>
> [8224517.520885] timekeeping watchdog: Marking clocksource
1 - 100 of 1884 matches
Mail list logo