On 05/02/2017 07:08 AM, Catalin Marinas wrote:
> On Tue, May 02, 2017 at 12:39:13AM +0200, Heinrich Schuchardt wrote:
>> There is no need to hide the model name in processes
>> that are not PER_LINUX32.
>>
>> So let us always provide a model name that is easily readable.
>>
>> Fixes: e47b020a323d (
On Fri, May 5, 2017 at 9:21 PM, Robin Murphy wrote:
> On 04/05/17 19:52, Oza Oza wrote:
>> On Thu, May 4, 2017 at 11:50 PM, Robin Murphy wrote:
>>> On 03/05/17 05:46, Oza Pawandeep wrote:
this patch reserves the iova for PCI masters.
ARM64 based SOCs may have scattered memory banks.
>>>
If 'devm_kzalloc' fails, a NULL pointer will be dereferenced.
Return -ENOMEM instead, as done for some other memory allocation just a
few lines above.
Fixes: 98cd1552ea27 ("net: dsa: Mock-up driver")
Signed-off-by: Christophe JAILLET
---
drivers/net/dsa/dsa_loop.c | 3 +++
1 file changed, 3 ins
On Fri, May 5, 2017 at 8:55 PM, Robin Murphy wrote:
> On 04/05/17 19:41, Oza Oza wrote:
> [...]
5) leaves scope of adding PCI flag handling for inbound memory
by the new function.
>>>
>>> Which flags would ever actually matter? DMA windows aren't going to be
>>> to config or I/O space, s
Hi Linus,
On Fri, 5 May 2017 13:01:34 -0700 Linus Torvalds
wrote:
>
> I actually would have preferred to not get any early merges, but what
> I was unhappy about is that I also didn't really get any heads-up
> about the cdev_device_add() conflict.
>
> I did get notified about the other conflict
Le 05/05/2017 à 21:56, Greg KH a écrit :
On Fri, May 05, 2017 at 09:08:44PM +0200, Christophe JAILLET wrote:
This patch fixes several issues:
- if the 1st 'kzalloc' fails, we dereference a NULL pointer
- if the 2nd 'kzalloc' fails, there is a memory leak
- if 'sysfs_create_bin_file'
On Fri, May 05, 2017 at 09:42:40PM -0700, Joe Perches wrote:
> On Fri, 2017-05-05 at 21:07 -0700, Greg KH wrote:
> > From: Chris Fries
> >
> > Add %paP and %padP for physical address that need to always be shown
> > regardless of kptr restrictions.
>
> The commit message could be improved.
Good
The compressed boot function error() is used to halt execution, but it
wasn't marked with "noreturn". This fixes that in preparation for
supporting kernel FORTIFY_SOURCE, which uses the noreturn annotation
on panic, and calls error(). GCC would warn about a noreturn function
calling a non-noreturn
On Sat, May 6, 2017 at 6:49 AM, Bjorn Andersson
wrote:
> On Fri 05 May 13:22 PDT 2017, Jassi Brar wrote:
>> How is it supposed to work if a client queues more than one request?
>
> One such example is found in patch 5 in this series. There are two FIFOs
> in shared memory, one in each direction.
On Fri, 2017-05-05 at 21:07 -0700, Greg KH wrote:
> From: Chris Fries
>
> Add %paP and %padP for physical address that need to always be shown
> regardless of kptr restrictions.
The commit message could be improved.
I had to look at the actual code to see if %papP was supported.
> diff --git a
On 2017-05-05 17:47, Thomas Garnier wrote:
On Fri, May 5, 2017 at 1:23 AM, Daniel Gruss
wrote:
On 04.05.2017 17:28, Thomas Garnier wrote:
Please read the documentation on submitting patches [1] and coding
style [2].
I will have a closer look at that.
- How this approach prevent the ha
ERROR: "devm_create_dev_dax" [drivers/dax/dax_pmem.ko] undefined!
ERROR: "alloc_dax_region" [drivers/dax/dax_pmem.ko] undefined!
ERROR: "dax_region_put" [drivers/dax/dax_pmem.ko] undefined!
Signed-off-by: Mike Galbraith
---
drivers/dax/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deleti
From: Chris Fries
The addr and size on the UIO devices are required by userspace to function
properly. Let's unrestrict these by adding the 'P' modifier to %p and %pa.
Cc: William Roberts
Cc: Dave Weinstein
Signed-off-by: Chris Fries
Signed-off-by: Greg Kroah-Hartman
---
drivers/uio/uio.c
From: Chris Fries
Add %paP and %padP for physical address that need to always be shown
regardless of kptr restrictions.
Cc: William Roberts
Cc: Dave Weinstein
Signed-off-by: Chris Fries
Signed-off-by: Greg Kroah-Hartman
---
Documentation/printk-formats.txt | 10 ++
lib/vsprintf.c
From: Dave Weinstein
Add the kptr_restrict setting of 4 which results in %pa and
%p[rR] values being replaced by zeros.
Cc: William Roberts
Cc: Chris Fries
Signed-off-by: Dave Weinstein
Signed-off-by: Greg Kroah-Hartman
---
Documentation/sysctl/kernel.txt | 8 +++-
kernel/sysctl.c
From: Dave Weinstein
Set the initial value of kptr_restrict to the maximum
setting rather than the minimum setting, to ensure that
early boot logging is not leaking information.
Cc: William Roberts
Cc: Chris Fries
Signed-off-by: Dave Weinstein
Signed-off-by: Greg Kroah-Hartman
---
lib/vspri
From: Dave Weinstein
Add the kptr_restrict setting of 3 which results in both
%p and %pK values being replaced by zeros.
Add an additional %pP value inspired by the Grsecurity
option which explicitly whitelists pointers for output.
This patch is based on work by William Roberts
Cc: William Ro
From: Dave Weinstein
Use the %pP functionality to explicitly allow kernel
pointers to be logged for stack traces
Cc: William Roberts
Cc: Chris Fries
Signed-off-by: Dave Weinstein
Signed-off-by: Greg Kroah-Hartman
---
arch/arm64/kernel/traps.c | 4 ++--
include/linux/kallsyms.h | 2 +-
kern
Here's a short patch series from Chris Fries and Dave Weinstein that
implement some new restrictions when printing out kernel pointers, as
well as the ability to whitelist kernel pointers where needed.
These patches are based on work from William Roberts, and also is
inspired by grsecurity's %pP t
On Fri, May 05, 2017 at 07:58:50PM -0600, Shuah Khan wrote:
> On 05/05/2017 12:32 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.67 release.
> > There are 20 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
> On Fri, May 5, 2017 at 3:44 PM, Kani, Toshimitsu
> wrote:
> > On Fri, 2017-05-05 at 15:25 -0700, Dan Williams wrote:
> >> On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu
> >> wrote:
> > :
> >> > > ---
> >> > > Changes since the initial RFC:
> >> > > * s/writethru/wt/ since we already have ior
Clang does not support this machine dependent option.
Older versions of GCC (pre 3.0) may not support this option, added in
2000, but it's unlikely they can still compile the kernel.
Signed-off-by: Nick Desaulniers
---
arch/x86/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
On Fri, May 5, 2017 at 3:44 PM, Kani, Toshimitsu wrote:
> On Fri, 2017-05-05 at 15:25 -0700, Dan Williams wrote:
>> On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu
>> wrote:
> :
>> > > ---
>> > > Changes since the initial RFC:
>> > > * s/writethru/wt/ since we already have ioremap_wt(),
>> > >
Subject is too long.
On Sat, May 06, 2017 at 04:04:50AM +0300, Gideon Sheril wrote:
> /* The atomisp uses type==0 for the end-of-list marker, so leave space. */
> @@ -152,13 +152,13 @@ const struct camera_af_platform_data
> *camera_get_af_platform_data(void)
> EXPORT_SYMBOL_GPL(camera_get_af_pl
On 05/05/2017 12:32 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.67 release.
> There are 20 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 sh
On 05/05/2017 12:31 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.52 release.
> There are 68 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 s
Please note the 4.11 and 4.10 log results in my email were
reversed - see correction below.
Performance regression is observed - FIO performance in 4.11 is
much less than 4.10 on ARM64 based platform.
On 17-05-05 06:37 PM, Scott Branden wrote:
I have updated the kernel to 4.11 and see significa
I have updated the kernel to 4.11 and see significant performance
drops using fio-2.9.
Using FIO the performanced drops from 281 KIOPS to 207 KIOPS using
single core and task.
Percent performance drop becomes even worse if multi-cores and multi-
threads are used.
Platform is ARM64 based A72. Ca
Some mailbox hardware doesn't have to perform any additional operations
on startup of shutdown, so make these optional.
Signed-off-by: Bjorn Andersson
---
Changes since v4:
- Inline the conditionals, rather than breaking them out into separate
functions
drivers/mailbox/mailbox.c | 16 +++
This implements a driver that exposes the IPC bits found in the APCS
Global block in various Qualcomm platforms. The bits are used to signal
inter-processor communication signals from the application CPU to other
masters.
Signed-off-by: Bjorn Andersson
---
Changes since v4:
- Updated commit mess
Introduce a binding for the Qualcomm APCS global block, exposing a
mailbox for invoking interrupts on remote processors in the system.
Signed-off-by: Bjorn Andersson
---
Changes since v4:
- None
.../bindings/mailbox/qcom,apcs-kpss-global.txt | 46 ++
1 file changed, 46
Thanks for feedback! This appears to be my internal issue.
2017-05-06 4:10 GMT+03:00 Randy Dunlap :
> On 05/05/17 17:45, as Bari wrote:
>> PCCARD entry has menuconfig type. This makes it invisible from, for
>> example, gconfig, and we get additional pcmcia modules in builtin
>> tree. This is unexp
On Fri, May 5, 2017 at 5:51 PM, wrote:
>> -Original Message-
>> From: Darren Hart [mailto:dvh...@infradead.org]
>> Sent: Friday, May 5, 2017 6:45 PM
>> To: Limonciello, Mario
>> Cc: pali.ro...@gmail.com; r...@rjwysocki.net; l...@amacapital.net;
>> len.br...@intel.com; corentin.ch...@gmai
Hi,
Here are release candidates 1 for LTTng kernel and user-space tracers 2.10.
This release is named "KeKriek", which is a sour mashed golden wheat ale
brewed by the Dunham microbrewery in Quebec.
The new features included are:
- A new "blocking" mode for LTTng-UST (it has been requested for a
On Fri 05 May 13:22 PDT 2017, Jassi Brar wrote:
> On Sat, May 6, 2017 at 1:23 AM, Jeffrey Hugo wrote:
> > On 5/5/2017 1:22 PM, Jassi Brar wrote:
> >>
> >> On Sat, May 6, 2017 at 12:07 AM, Bjorn Andersson
> >> wrote:
> >>>
> >
> > There is no way to determine if the remote processor has observed
On 05/05/17 17:45, as Bari wrote:
> PCCARD entry has menuconfig type. This makes it invisible from, for
> example, gconfig, and we get additional pcmcia modules in builtin
> tree. This is unexpected behaviour.
> Looks like the entry was improperly refactored since 2.6.24.
What kernel version are y
atomisp_gmin_platform.c:
Fix ERROR: spaces instead of tabs and comma/assignment padding error.
Signed-off-by: Gideon Sheril
---
.../platform/intel-mid/atomisp_gmin_platform.c | 166 ++---
1 file changed, 83 insertions(+), 83 deletions(-)
diff --git
a/drivers/staging/media/a
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, May 5, 2017 6:45 PM
> To: Limonciello, Mario
> Cc: pali.ro...@gmail.com; r...@rjwysocki.net; l...@amacapital.net;
> len.br...@intel.com; corentin.ch...@gmail.com; l...@kernel.org;
> andriy.shevche...@lin
PCCARD entry has menuconfig type. This makes it invisible from, for
example, gconfig, and we get additional pcmcia modules in builtin
tree. This is unexpected behaviour.
Looks like the entry was improperly refactored since 2.6.24.
I would like to hear others' opinion.
Announce of trace-cmd 2.6.1
It's been a while since I released any official version of trace-cmd, and
there's been lots of updates (although it took me a while to even push those up
to the repo). Here's a brief list of what's happened since 2.6:
trace-cmd record:
--max-graph-depth has been
On Fri, May 05, 2017 at 09:55:46PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Darren Hart [mailto:dvh...@infradead.org]
> > Sent: Thursday, April 20, 2017 3:45 PM
> > To: Pali Rohár
> > Cc: Limonciello, Mario ; r...@rjwysocki.net;
> > l...@amacapital.net; len
On Fri, May 05, 2017 at 09:42:14PM +0100, Matt Fleming wrote:
> (Including the folks from SGI since this was hit on a UV system)
Wasn't there a BIOS fix supplied at some point which obviated the need
to boot with efi=old_map on SGI boxes?
--
Regards/Gruss,
Boris.
Good mailing practices for
The driver now uses IRQ_POLL and needs to select it to avoid the following
build error.
ERROR: ".irq_poll_complete" [drivers/scsi/cxlflash/cxlflash.ko] undefined!
ERROR: ".irq_poll_sched" [drivers/scsi/cxlflash/cxlflash.ko] undefined!
ERROR: ".irq_poll_disable" [drivers/scsi/cxlflash/cxlflash.ko]
Joonas Lahtinen:
> Filing a bug in freedesktop.org with all the details is the fastest way
> of getting help. Without the bug (and with such little information as
> the previous e-mail) it's hard to estimate the extent and nature of the
> bug.
My original report was
http://marc.info/?l=linux-kerne
This patchset introduces the tiocsti_restrict sysctl, whose default is
controlled via CONFIG_SECURITY_TIOCSTI_RESTRICT. When activated, this
control restricts all TIOCSTI ioctl calls from non CAP_SYS_ADMIN users.
This patch was inspired from GRKERNSEC_HARDEN_TTY.
This patch would have prevented
h
This introduces the tiocsti_restrict sysctl, whose default is controlled via
CONFIG_SECURITY_TIOCSTI_RESTRICT. When activated, this control restricts
all TIOCSTI ioctl calls from non CAP_SYS_ADMIN users.
This patch depends on patch 1/2
This patch was inspired from GRKERNSEC_HARDEN_TTY.
This patc
This patch adds struct user_namespace *owner_user_ns to the tty_struct.
Then it is set to current_user_ns() in the alloc_tty_struct function.
This is done to facilitate capability checks against the original user
namespace that allocated the tty.
E.g. ns_capable(tty->owner_user_ns,CAP_SYS_ADMIN)
Linus Torvalds writes:
> On Fri, May 5, 2017 at 6:20 AM, Michael Ellerman wrote:
>>
>> Also due to a screw-up on my part, we need a hunk added when you merge
>> the powerpc tree with the KVM tree:
>>
>> diff --git a/arch/powerpc/kvm/book3s_xive.c b/arch/powerpc/kvm/book3s_xive.c
>> index 7807ee17
On Fri, May 5, 2017 at 4:01 PM, Bart Van Assche
wrote:
> On Fri, 2017-05-05 at 15:42 -0700, Kees Cook wrote:
>> diff --git a/drivers/scsi/qedf/qedf_main.c b/drivers/scsi/qedf/qedf_main.c
>> index cceddd995a4b..a5c97342fd5d 100644
>> --- a/drivers/scsi/qedf/qedf_main.c
>> +++ b/drivers/scsi/qedf/qe
On 05.05.17 17:38:05, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 SMMU implementation doesn't support page 1 register space
> and PAGE0_REGS_ONLY option will be enabled as an errata workaround.
>
> This option when turned on, replaces all page 1 offsets used for
> EVTQ_PROD/
On Fri, 2017-05-05 at 15:42 -0700, Kees Cook wrote:
> diff --git a/drivers/scsi/qedf/qedf_main.c b/drivers/scsi/qedf/qedf_main.c
> index cceddd995a4b..a5c97342fd5d 100644
> --- a/drivers/scsi/qedf/qedf_main.c
> +++ b/drivers/scsi/qedf/qedf_main.c
> @@ -2895,7 +2895,7 @@ static int __qedf_probe(stru
From: Andi Kleen
When looking at PT or brstackinsn traces with perf script
it can be very useful to see the source code. This adds a simple
facility to print them with perf script, if the information
is available through dwarf
% perf record ...
% perf script -F insn,ip,sym,srccode
...
* Peter Ujfalusi [170505 08:20]:
> On 2017-05-05 16:37, Peter Ujfalusi wrote:
> > On 2017-05-05 00:05, Tony Lindgren wrote:
> > > And this sync gpmc issue seems to be timing related. Setting
> > > DEBUG in tusb6010_omap.c makes it happen easily while without
> > > it it's much harder to trigger. S
Hello,
It seems thare are many places where code assumes iounmap(NULL) is safe.
Also there are several patches that state it explicitly:
ff6defa6a8fa ("ALSA: Deletion of checks before the function call "iounmap")
e24bb0ed8179 ("staging: dgnc: remove NULL test")
At the same time it seems PPC i
On Fri, 2017-05-05 at 15:25 -0700, Dan Williams wrote:
> On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu
> wrote:
:
> > > ---
> > > Changes since the initial RFC:
> > > * s/writethru/wt/ since we already have ioremap_wt(),
> > > set_memory_wt(), etc. (Ingo)
> >
> > Sorry I should have said earl
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from the kernel
rodata segment. Instead, use strncpy() which will fill the trailing bytes
with zeros.
This was found with the future CONFIG_FORTIFY_SOURCE feature.
In linux-next struct device dev; was added to struct iommu_device
this breaks calls to iommu_put/get_resv_regions function because
these functions expect struct device * instead.
Please review and consider this patch to fix this.
Thanks
Manoj Iyer
Argument to iommu_get/put_resv_regions function in
iommu_get_group_resv_regions function expects a struct device *
as first argument, struct device is passed instead.
Commit 39ab9555c241 ("iommu: Add sysfs bindings for struct iommu_device")
in linux-next adds struct device dev to struct iommu_devi
Using memcpy() from a buffer that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from the kernel
rodata segment. In this case, the source was made longer, since it did not
match the destination structure size. Additionally removes a needless cast.
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from the kernel
rodata segment. Instead, use strncpy() which will fill the trailing bytes
with zeros.
This was found with the future CONFIG_FORTIFY_SOURCE feature.
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from the kernel
rodata segment. Instead, use strncpy() which will fill the trailing bytes
with zeros.
This was found with the future CONFIG_FORTIFY_SOURCE feature.
On Thu, May 04, 2017 at 04:50:12PM +0800, Wei Wang wrote:
> Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables
> the transfer of the ballooned (i.e. inflated/deflated) pages in
> chunks to the host.
>
> The implementation of the previous virtio-balloon is not very
> efficient, because
On 05.05.17 17:38:05, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 SMMU implementation doesn't support page 1 register space
> and PAGE0_REGS_ONLY option will be enabled as an errata workaround.
>
> This option when turned on, replaces all page 1 offsets used for
> EVTQ_PROD/
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from the kernel
rodata segment. Instead, use strncpy() which will fill the trailing bytes
with zeros.
This was found with the future CONFIG_FORTIFY_SOURCE feature.
On Thu, Apr 27, 2017 at 02:31:49PM +0800, Wei Wang wrote:
> On 04/27/2017 07:20 AM, Michael S. Tsirkin wrote:
> > On Wed, Apr 26, 2017 at 11:03:34AM +, Wang, Wei W wrote:
> > > Hi Michael, could you please give some feedback?
> > I'm sorry, I'm not sure feedback on what you are requesting.
> Oh
On Fri, May 5, 2017 at 1:39 PM, Kani, Toshimitsu wrote:
> On Fri, 2017-04-28 at 12:39 -0700, Dan Williams wrote:
>> The pmem driver has a need to transfer data with a persistent memory
>> destination and be able to rely on the fact that the destination
>> writes are not cached. It is sufficient fo
On Sat, May 6, 2017 at 12:33 AM, Sudip Mukherjee
wrote:
> It is possible to update the backlight power and the brightness using
> the sysfs and on writing it either returns the count or if the callback
> function does not exist then returns the error code 'ENXIO'.
>
> We have a situation where the
On 05.05.17 17:38:04, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 SMMUv3 implementation has two Silicon Erratas.
> 1. Errata ID #74
>SMMU register alias Page 1 is not implemented
> 2. Errata ID #126
>SMMU doesnt support unique IRQ lines and also MSI for gerror,
>
On Sat, May 6, 2017 at 12:33 AM, Rafael J. Wysocki wrote:
> On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote:
>> Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state
>> selection")
>> Signed-off-by: Li, Fei
>> Tested-by: Shi, Feng
>> Reviewed-by: Andy Shevchenko
>> Reviewed-b
On Thu, Apr 27, 2017 at 02:33:44PM +0800, Wei Wang wrote:
> On 04/14/2017 01:08 AM, Michael S. Tsirkin wrote:
> > On Thu, Apr 13, 2017 at 05:35:08PM +0800, Wei Wang wrote:
> > > Add a new vq, miscq, to handle miscellaneous requests between the device
> > > and the driver.
> > >
> > > This patch im
On 05.05.17 17:38:09, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 implementation doesn't support second page in SMMU
> register space. Hence, resource size is set as 64k for this model.
>
> Signed-off-by: Linu Cherian
> Signed-off-by: Geetha Sowjanya
> ---
> drivers/acpi/
On 05.05.17 17:38:06, Geetha sowjanya wrote:
> From: Linu Cherian
>
> With implementations supporting only page 0 register space,
> resource size can be 64k as well and hence perform size checks
> based on SMMU option PAGE0_REGS_ONLY.
>
> For this, arm_smmu_device_dt_probe/acpi_probe has been mo
On Fri, Apr 28, 2017 at 8:32 AM, Thomas Garnier wrote:
> Ensure that a syscall does not return to user-mode with a kernel address
> limit. If that happens, a process can corrupt kernel-mode memory and
> elevate privileges [1].
>
> The CONFIG_ADDR_LIMIT_CHECK option disables the generic check so ea
e system]
>
> url:
> https://github.com/0day-ci/linux/commits/Wei-Wang/Extend-virtio-balloon-for-fast-de-inflating-fast-live-migration/20170505-052958
> reproduce: make htmldocs
>
> All warnings (new ones prefixed by >>):
>
>WARNING: convert(1) not found, for SVG
Bastien Nocera writes:
> On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote:
>> Ensure checkpatch compliance
>>
>> > Signed-off-by: Justin Vreeland
>> ---
>> v2:
>> - Added commit message
>> - Fixed overly long lines
>>
>> drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 18 ++
Hi Marc,
On 05/02/2017 11:16 AM, Marc Zyngier wrote:
> On Sun, Apr 30 2017 at 3:36:15 pm BST, Shanker Donthineni
> wrote:
>> We are always allocating extra 255Bytes of memory to handle ITE
>> physical address alignment requirement. The kmalloc() satisfies
>> the ITE alignment since the ITS dri
Bastien Nocera writes:
> On Mon, 2017-05-01 at 18:52 -0600, Justin Vreeland wrote:
>> Ensure checkpatch compliance
>>
>> > Signed-off-by: Justin Vreeland
>> ---
>> v2:
>> - Added commit message
>> - Fixed overly long lines
>>
>> drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 18 +++
From: Stephen Rothwell
This fixes the add/change_virtual-intf API change that happened in the
wifi tree in the rtl8723bs driver.
Signed-off-by: Stephen Rothwell
Signed-off-by: Greg Kroah-Hartman
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 4 ++--
1 file changed, 2 insertions(+), 2
From: Stephen Rothwell
Another fixup for the wifi changes that came from that tree for the
rtl8723bs driver.
Signed-off-by: Stephen Rothwell
Signed-off-by: Greg Kroah-Hartman
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 20
1 file changed, 12 insertions(+), 8 d
On Fri, 5 May 2017, Joonas Lahtinen wrote:
> On ma, 2017-05-01 at 11:05 +0900, J. R. Okajima wrote:
> > Thanx for the reply.
> >
> > Andrea Arcangeli:
> > >
> > > Yes I already reported this, my original fix was way more efficient
> > > (and also safer considering the above) than what landed upst
From: Stephen Rothwell
Fix up the rtl8723bs driver for the nl80211 api change that came in from
the wifi tree.
Signed-off-by: Stephen Rothwell
Signed-off-by: Greg Kroah-Hartman
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
On Thu, May 4, 2017 at 11:09 PM, Zheng, Lv wrote:
> Hi,
>
>> From: Jon Mason [mailto:jon.ma...@broadcom.com]
>> Sent: Thursday, May 4, 2017 11:06 PM
>> Subject: [PATCH] ACPI: SPCR: Use access width to determine mmio usage
>>
>> The current SPCR code does not check the access width of the mmio, and
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Thursday, April 20, 2017 3:45 PM
> To: Pali Rohár
> Cc: Limonciello, Mario ; r...@rjwysocki.net;
> l...@amacapital.net; len.br...@intel.com; corentin.ch...@gmail.com;
> l...@kernel.org; andriy.shevche...@linux.i
The current SPCR code does not check the access width of the mmio, and
uses a default of 8bit register accesses. This prevents devices that
only do 16 or 32bit register accesses from working. By simply checking
this field and setting the mmio string appropriately, this issue can be
corrected. To
Hello, Maxime.
On Fri, May 05, 2017 at 09:55:18PM +0200, Maxime Ripard wrote:
> > It doesn't make any sense to use the managed functions from the
> > release functions and if you're always matching devm_kmalloc() with
> > devm_kfree(), the only thing it'd do is confusing its readers.
>
> I wouldn
From: Rafael J. Wysocki
Add a document describing the current behavior and user space
interface of the intel_pstate driver in the RST format and
drop the existing outdated intel_pstate.txt document.
Also update admin-guide/pm/cpufreq.rst with proper RST references
to the new intel_pstate.rst doc
Hi Helmut,
On Fri, Mar 31, 2017 at 6:54 PM, Helmut Klein wrote:
> Add the documentation for the device tree binding of meson_uart
>
> Signed-off-by: Helmut Klein
> ---
> .../bindings/serial/amlogic,meson_uart.txt | 30
> ++
> 1 file changed, 30 insertions(+)
> crea
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-4.12
...to receive the libnvdimm update for 4.12. The bulk of this has been
in multiple -next releases. There were a few late breaking fixes and
small features that got added in the last
On Thursday, May 04, 2017 09:00:52 AM Li, Fei wrote:
> In case of there is no cpuidle devices registered, dev will be null, and
> panic will be triggered like below;
> In this patch, add checking of dev before usage, like that done in
> cpuidle_idle_call.
>
> Panic without fix:
> [ 184.961328] B
Hi,
El Fri, May 05, 2017 at 01:29:32PM -0700 Grant Grundler ha dit:
> On Fri, May 5, 2017 at 1:08 PM, Ville Syrjälä
> wrote:
> ...
> >> > I'm not convinced the patch is making things any better really. To
> >> > fix this really properly, I think we'd need to introduce a new enum
> >> > pch_trans
It is possible to update the backlight power and the brightness using
the sysfs and on writing it either returns the count or if the callback
function does not exist then returns the error code 'ENXIO'.
We have a situation where the userspace client is writing to the sysfs
to update the power and
Hi Peter,
El Fri, May 05, 2017 at 12:37:23PM -0700 h...@zytor.com ha dit:
> On May 5, 2017 11:44:05 AM PDT, Matthias Kaehlcke wrote:
> >El Fri, May 05, 2017 at 07:50:39PM +0200 Ingo Molnar ha dit:
> >
> >>
> >> * Peter Zijlstra wrote:
> >>
> >> > On Fri, May 05, 2017 at 01:11:47AM -0700, tip-
On Tue, 25 Apr, at 08:10:51PM, Fabian Frederick wrote:
> Remove NULL test on kmap()
>
> Signed-off-by: Fabian Frederick
> ---
> drivers/firmware/efi/capsule-loader.c | 5 -
> drivers/firmware/efi/capsule.c| 4
> 2 files changed, 9 deletions(-)
>
> diff --git a/drivers/firmware/
> Just to let you know, it's never a good idea to send new patches out
> during the merge window.
Thanks for such information.
> They are most likely to be missed and forgotten during this time.
This can happen then occasionally.
> Unless they are critical bug fixes, it's best to wait till af
From: Markus Elfring
Date: Fri, 5 May 2017 22:38:51 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: Possible unnecessary 'out of memory' message
Thus remove such a statement here.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Ref
From: Markus Elfring
Date: Fri, 5 May 2017 22:30:16 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The script “checkpatch.pl” pointed information out like the following.
Comparison to NULL could be written !…
Thus fix the affected source code pla
On 04/25/2017 05:56 PM, Florian Fainelli wrote:
> Changes in v3:
>
> - added check in usb_gadget_map_request_by_dev (Felipe), new patch
> - improved commit message description (Clemens)
> - added additiona checks for urb->setup_packet (Alan)
>
> Changes in v2:
>
> - moved the check from usb_star
On 05/01/2017 01:13 PM, Andres Galacho wrote:
> The device table is required to load modules based on
> modaliases. After adding MODULE_DEVICE_TABLE, below entries
> for example will be added to module.alias:
> alias: of:N*T*Cbrcm,bcm6328-hsspiC*
> alias: of:N*T*Cbrcm,bcm6328-hssp
On Tue, 02 May, at 08:51:47AM, Ocean HY1 He wrote:
> The commit 7efe665903d0 ("rtc: Disable EFI rtc for x86") turns off rtc-efi
> option completely for x86 in rtc/Kconfig, to avoid possible crash caused by
> buggy implementations of the time-related EFI runtime services.
>
> In fact, there are mor
On Fri, May 5, 2017 at 1:28 PM, Bob Peterson wrote:
>
> I asked around, but nobody could tell me what went wrong. Strangely,
> this command:
>
> git log --oneline --right-only origin/master...FETCH_HEAD --stat
>
> doesn't show this, but this one does:
>
> git diff --stat --right-only origin/master
1 - 100 of 650 matches
Mail list logo
