No idea if this is a problem. Maybe trace_afs_call is just using the
address?
julia
-- Forwarded message --
Date: Thu, 23 Feb 2017 23:18:26 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: fs/afs/rxrpc.c:187:17-21: ERROR: reference preceded by free on l
If device_add() fails, cleanup the cdev. Otherwise, we leak a kobj_map()
with a stale device number.
Fixes: ba09c01d2fa8 ("dax: convert to the cdev api")
Cc:
Cc: Logan Gunthorpe
Reported-by: Jason Gunthorpe
Signed-off-by: Dan Williams
---
drivers/dax/dax.c |1 +
1 file changed, 1 insertio
On 02/23, Chao Yu wrote:
> On 2017/2/18 2:39, Jaegeuk Kim wrote:
> > Hi Yunlong,
> >
> > I already started to test this since a couple of days ago. :)
> >
> > http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev-test&id=908b5f463c82eaf972b149a26bb310f5e25064fd
>
> Hi, Jaege
On Thu, Feb 23, 2017 at 01:22:06PM -0500, Johannes Weiner wrote:
> On Thu, Feb 23, 2017 at 08:26:03AM -0800, Shaohua Li wrote:
> > On Thu, Feb 23, 2017 at 10:58:27AM -0500, Johannes Weiner wrote:
> > > Hi Shaohua,
> > >
> > > On Wed, Feb 22, 2017 at 10:50:41AM -0800, Shaohua Li wrote:
> > > > @@ -
On Thu, Feb 23, 2017 at 8:45 AM, Will Deacon wrote:
>
> Whilst I'm pleased that you've sent a fix (and I'll pick it up), I have
> to ask... did anybody actually test the original patch? If so, why wasn't
> this found earlier?
First, Shanker's going to post a V2 with an improved patch description.
On Thu, Feb 23, 2017 at 10:15 AM, Bjorn Helgaas wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git c4d052ce970e
Ok, so this is just strange.
I do not generally pull the random SHA1's directly, I want a branch
name or a tag-name.
(Honesty in advertising: I *have* pulled t
On Thu, Feb 23, 2017 at 2:59 AM, Jani Nikula
wrote:
> On Mon, 20 Feb 2017, Jim Davis wrote:
>> For the Sphinx targets, htmldocs, pdfdocs, epubdocs, and cleandocs
>> failed. cleandocs works without the O= argument, and arguably the O=
>> thing isn't very useful with any of these targets, but it i
cat /sys/devices/virtual/iommu/dmar0/intel-iommu/version
Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
CPU: 2 PID: 1488 Comm: cat Not tainted 4.10.0-think+ #5
task: 8804ee440040 task.stack: c9d48000
RIP: 0010:intel_iommu_show_version+0x13/0x40
RSP: 0018:c9d4bcf0 EFLAGS: 00010286
On Thu, Feb 23, 2017 at 11:35:46AM -0800, Linus Torvalds wrote:
> On Thu, Feb 23, 2017 at 10:15 AM, Bjorn Helgaas wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git c4d052ce970e
>
> Ok, so this is just strange.
>
> I do not generally pull the random SHA1's directly, I
> -Original Message-
> From: Colin King [mailto:colin.k...@canonical.com]
> Sent: Thursday, February 23, 2017 2:57 AM
> To: qla2xxx-upstr...@qlogic.com; James E . J . Bottomley
> ; Martin K . Petersen
> ; linux-s...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Subject: [PATCH] qla
On 02/13/17 18:50, Stephen Boyd wrote:
> The 'blob' we pass into populate_properties() is marked as const,
> but we cast that const away when we assign the result of
> fdt_getprop_by_offset() to pp->value. Let's mark value as const
> instead, so that code can't mistakenly write to the value of the
The commit 38fd94b0275c 'arm64: Work around Falkor erratum 1003' has
been added to fix the hardware bug but causing a system crash. The
value of the register x1 which contains 'struct mm_struct *' should
be preserved inside macro pre_ttbr0_update_workaround.
Macro pre_ttbr0_update_workaround expec
Hi!
> > > > Somehow, startup_32_smp() is on the stack twice. The stack unwind led
> > > > to the startup_32_smp() frame at 0xf50cdf9c rather than the one at
> > > > 0xf50cdfa8 (which is where it should normally be). So the question is
> > > > how startup_32_smp() got executed the second time, w
On Thu, Feb 23, 2017 at 11:22:03AM -0800, Dan Williams wrote:
> If device_add() fails, cleanup the cdev. Otherwise, we leak a kobj_map()
> with a stale device number.
>
> Fixes: ba09c01d2fa8 ("dax: convert to the cdev api")
> Cc:
> Cc: Logan Gunthorpe
> Reported-by: Jason Gunthorpe
> Signed-off
Hi!
> > Ok, and this is where the problems start. You are not supposed to
> > control keyboard backlight like that. (In the same way you can't
> > control display backlight like that.)
> >
> > There are numerous problems with the shell script:
> >
> > 1) how to identify the keyboard backlight LE
On Wed, Feb 22, 2017 at 4:01 AM, Michal Hocko wrote:
> From: Michal Hocko
>
> Lowmemory killer is sitting in the staging tree since 2008 without any
> serious interest for fixing issues brought up by the MM folks. The main
> objection is that the implementation is basically broken by design:
>
Bjorn complained some strange print out for pending interrupts.
Actually that is caused that have cmd print out after write_cmd.
Adjust the sequence to get right order for debug print out.
Signed-off-by: Yinghai Lu
diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.
On Thu, Feb 23, 2017 at 12:20 PM, Jason Gunthorpe
wrote:
> On Thu, Feb 23, 2017 at 11:22:03AM -0800, Dan Williams wrote:
>> If device_add() fails, cleanup the cdev. Otherwise, we leak a kobj_map()
>> with a stale device number.
>>
>> Fixes: ba09c01d2fa8 ("dax: convert to the cdev api")
>> Cc:
>>
On Wed, 1 Feb 2017, Laura Abbott wrote:
> That's the main one where debugging was happening. There may be a couple
> of others floating around that I hadn't had time to fully investigate.
> I'll dupe them to the above if I find them.
[ adding Joey and Gary to CC ]
Laura,
have you by any chanc
On Thu, Feb 23, 2017 at 9:24 PM, John Stultz wrote:
>
> So, just for context, Android does have a userland LMK daemon (using
> the mempressure notifiers) as you mentioned, but unfortunately I'm
> unaware of any devices that ship with that implementation.
I've previously worked on enabling userspa
Hello,
We're still waiting on any kind of response from Bjorn. (If you're
listening please say something!)
Does anyone have any suggestions for dealing with an unresponsive
maintainer? Or a way for us to move forward with this quickly and get it
merged?
ie. Can anyone else pick this up through a
On Thursday 23 February 2017 21:23:33 Pavel Machek wrote:
> Hi!
>
> > > Ok, and this is where the problems start. You are not supposed to
> > > control keyboard backlight like that. (In the same way you can't
> > > control display backlight like that.)
> > >
> > > There are numerous problems with
If device_add() fails, cleanup the cdev. Otherwise, we leak a kobj_map()
with a stale device number.
As Jason points out, there is a small possibility that userspace has
opened and mapped the device in the time between cdev_add() and the
device_add() failure. We need a new kill_dax_dev() helper to
On 02/23/2017 02:02 PM, Shanker Donthineni wrote:
The commit 38fd94b0275c 'arm64: Work around Falkor erratum 1003' has
been added to fix the hardware bug but causing a system crash. The
"causes"
value of the register x1 which contains 'struct mm_struct *' should
be preserved inside macro pre_
On 2/23/2017 3:36 PM, Logan Gunthorpe wrote:
> We're still waiting on any kind of response from Bjorn. (If you're
> listening please say something!)
>
> Does anyone have any suggestions for dealing with an unresponsive
> maintainer? Or a way for us to move forward with this quickly and get it
> me
On Thu, Feb 23, 2017 at 05:49:28AM +0300, Dmitry V. Levin wrote:
> linux/netfilter.h is the last uapi header file that includes
> linux/sysctl.h but it does not depend on definitions provided
> by this essentially dead header file.
Applied, thanks.
On 02/23/2017 01:36 PM, Logan Gunthorpe wrote:
> Hello,
>
> We're still waiting on any kind of response from Bjorn. (If you're
> listening please say something!)
>
> Does anyone have any suggestions for dealing with an unresponsive
> maintainer? Or a way for us to move forward with this quickly a
On Thu, Feb 23, 2017 at 01:36:51PM -0700, Logan Gunthorpe wrote:
> Hello,
>
> We're still waiting on any kind of response from Bjorn. (If you're
> listening please say something!)
>
> Does anyone have any suggestions for dealing with an unresponsive
> maintainer? Or a way for us to move forward w
On 02/23/17 11:54, Frank Rowand wrote:
> On 02/13/17 18:50, Stephen Boyd wrote:
>> The 'blob' we pass into populate_properties() is marked as const,
>> but we cast that const away when we assign the result of
>> fdt_getprop_by_offset() to pp->value. Let's mark value as const
>> instead, so that cod
On 02/23/2017 02:46 PM, Timur Tabi wrote:
On 02/23/2017 02:02 PM, Shanker Donthineni wrote:
The commit 38fd94b0275c 'arm64: Work around Falkor erratum 1003' has
been added to fix the hardware bug but causing a system crash. The
"causes"
value of the register x1 which contains 'struct mm_st
On 02/23/2017 03:05 PM, Shanker Donthineni wrote:
Why do you want keep 'pre_ttbr0_update_workaround' in subject, nothing
wrong with macro definition itself. Problem with the caller, not passing
the right arguments.
Ok, how about this:
arm64: qcom: do not use x1 when calling pre_ttbr0_update_wo
Hi!
> > > > 2) there may be more then one
> > >
> > > Yes and script can be adjusted to use specific one (config option
> > > for script).
> >
> > No, you should autoconfigure it,
>
> Why? Because you prefer autoconfiguration and all other people must use
> it only? Does not seems a good argum
Most system have port link enabled by default, and should not
have confusing printout.
Also move printout before actully write, so could make debug print in order.
Signed-off-by: Yinghai Lu
---
drivers/pci/hotplug/pciehp_hpc.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
I
Hi Timur,
On 02/23/2017 03:11 PM, Timur Tabi wrote:
On 02/23/2017 03:05 PM, Shanker Donthineni wrote:
Why do you want keep 'pre_ttbr0_update_workaround' in subject, nothing
wrong with macro definition itself. Problem with the caller, not passing
the right arguments.
Ok, how about this:
arm6
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/realtek/r8169.c | 41 ---
On 2/21/2017 9:06 AM, Borislav Petkov wrote:
On Thu, Feb 16, 2017 at 09:45:09AM -0600, Tom Lendacky wrote:
Boot data (such as EFI related data) is not encrypted when the system is
booted and needs to be mapped decrypted. Add support to apply the proper
attributes to the EFI page tables and to t
On 02/23/2017 01:51 PM, Sinan Kaya wrote:
> On 2/23/2017 3:36 PM, Logan Gunthorpe wrote:
>> We're still waiting on any kind of response from Bjorn. (If you're
>> listening please say something!)
>>
>> Does anyone have any suggestions for dealing with an unresponsive
>> maintainer? Or a way for us t
Most system have port link enabled by default, and should not
have confusing printout.
Also move printout before actully write, so could make debug print in order.
-v2: inline __pciehp_link_set into pciehp_link_enable
Signed-off-by: Yinghai Lu
---
drivers/pci/hotplug/pciehp_hpc.c | 19 +
On 23/02/17 01:51 PM, Sinan Kaya wrote:
> You'll want to be careful during the merge window (these days) as the
> maintainer is usually busy with code delivery. You can't rush your code in at
> the last minute.
Thanks for the advice, we will continue to wait.
However, I would say we've been ver
The s5p-cec driver has a few places that touch hdmicec clk:
static int s5p_cec_probe(struct platform_device *pdev)
{
...
cec->clk = devm_clk_get(dev, "hdmicec");
if (IS_ERR(cec->clk))
return PTR_ERR(cec->clk);
...
}
static int __maybe_unused s5p_cec
On 02/23/17 11:54, Frank Rowand wrote:
> On 02/13/17 18:50, Stephen Boyd wrote:
>> The 'blob' we pass into populate_properties() is marked as const,
>> but we cast that const away when we assign the result of
>> fdt_getprop_by_offset() to pp->value. Let's mark value as const
>> instead, so that cod
The Kconfig currently controlling compilation of this code is:
drivers/phy/Kconfig:config PHY_EXYNOS_PCIE
drivers/phy/Kconfig:bool "Exynos PCIe PHY driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so t
So, the issue is that you could get the following sequence -
write command
print out in ISR for pending interrupt
ctrl_dbg message for write command
and this makes it look like the write command occurred after the pending
interrupt message?
On 02/23/2017 03:28 PM, Yinghai Lu wrote:
Bjorn c
yes.
On 02/23/2017 01:55 PM, James Puthukattukaran wrote:
So, the issue is that you could get the following sequence -
write command
print out in ISR for pending interrupt
ctrl_dbg message for write command
and this makes it look like the write command occurred after the
pending interrupt me
On 02/23/2017 12:30 PM, Colin King wrote:
> From: Colin Ian King
>
> trivial fix to spelling mistake in NS_ERR error message
>
> Signed-off-by: Colin Ian King
Acked-by: Marek Vasut
Thanks
> ---
> drivers/mtd/nand/nandsim.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -
The commit 38fd94b0275c 'arm64: Work around Falkor erratum 1003' has
been added to fix the hardware bug but causes a system crash. The
value of the register x1 which contains 'struct mm_struct *' should
be preserved inside macro pre_ttbr0_update_workaround.
Macro pre_ttbr0_update_workaround expect
On Thu, Feb 9, 2017 at 2:05 AM, Brian Norris wrote:
> The following code snippet:
>
> module_param(writeable, bool, 0);
>
> yields this warning:
>
> ERROR: Use 4 digit octal (0777) not decimal permissions
> #390: FILE: drivers/mtd/spi-nor/intel-spi.c:143:
> +module_param(writeable,
On Thu, Feb 23, 2017 at 2:58 PM, Frank Rowand wrote:
> On 02/23/17 11:54, Frank Rowand wrote:
>> On 02/13/17 18:50, Stephen Boyd wrote:
>>> The 'blob' we pass into populate_properties() is marked as const,
>>> but we cast that const away when we assign the result of
>>> fdt_getprop_by_offset() to
On 22/02/2017 02:26, Mickaël Salaün wrote:
> Add a basic sandbox tool to create a process isolated from some part of
> the system. This sandbox create a read-only environment. It is only
> allowed to write to a character device such as a TTY:
>
> # :> X
> # echo $?
> 0
> # ./samples/bpf/l
On Thu, Feb 23, 2017 at 01:36:51PM -0700, Logan Gunthorpe wrote:
> Hello,
>
> We're still waiting on any kind of response from Bjorn. (If you're
> listening please say something!)
>
> Does anyone have any suggestions for dealing with an unresponsive
> maintainer? Or a way for us to move forward w
On 23.02.2017 20:44, Jim Davis wrote:
On Thu, Feb 23, 2017 at 2:59 AM, Jani Nikula
wrote:
On Mon, 20 Feb 2017, Jim Davis wrote:
For the Sphinx targets, htmldocs, pdfdocs, epubdocs, and cleandocs
failed. cleandocs works without the O= argument, and arguably the O=
thing isn't very useful wi
On Thu, 2017-02-23 at 10:27 +0100, Peter Zijlstra wrote:
> On Wed, Feb 22, 2017 at 10:37:04PM -0800, Ricardo Neri wrote:
> > @@ -492,6 +493,9 @@ do_general_protection(struct pt_regs *regs, long
> > error_code)
> > RCU_LOCKDEP_WARN(!rcu_is_watching(), "entry code didn't wake RCU");
> > cond
On Tue 2017-02-21 16:12:01, Arjan van de Ven wrote:
> is NX enabled in the bios?
Yes. (Plus, read-only should work even without NX, right?)
Pavel
> On Tue, Feb 21, 2017 at 2:14 PM, Pavel Machek wrote:
>
> > Hi!
> >
> > I'm gettin
On Thu, 2017-02-23 at 08:24 +0100, Peter Zijlstra wrote:
> On Wed, Feb 22, 2017 at 10:36:50PM -0800, Ricardo Neri wrote:
> > + /*
> > +* A negative offset generally means a error, except
> > +* -EDOM, which means that the contents of the reg
Thanks Bjorn! I understand your busy and we appreciate your time in this
matter.
I'll prepare a v3 with a collected set of tags shortly. We're more than
happy to clean this up to make your job as easy as possible. We were
just looking for direction in how to move this forward.
Logan
On 23/02/17
On Thu, 2017-02-23 at 18:54 +0800, kbuild test robot wrote:
> >> arch/x86/lib/insn-eval.c:106:21: error: static declaration of
> 'insn_get_addr_ref' follows non-static declaration
> static void __user *insn_get_addr_ref(struct insn *insn, struct
> pt_regs *regs)
> ^~
On Fri, 2017-02-24 at 00:10 +0200, Andy Shevchenko wrote:
> On Thu, Feb 9, 2017 at 2:05 AM, Brian Norris wrote:
> > The following code snippet:
> >
> > module_param(writeable, bool, 0);
> >
> > yields this warning:
> >
> > ERROR: Use 4 digit octal (0777) not decimal permissions
> >
From: Dave Hansen
Kirill got a warning from UBSAN about undefined behavior when using
protection keys. He is running on hardware that actually has support
for it, which is not widely available.
The warning was because we did some very large shifts of integers when
doing a pkey_free() of a larg
Shuah, I assume you'll take this patch in through the selftests tree.
--
From: Dave Hansen
The kernel pkeys code had a minor bug where it did some large shifts
to an integer which is undefined behavior in C. It didn't cause any
real harm, but it is screwy behavior that the kernel should have
On Thursday, February 23, 2017 08:33:11 PM David Wu wrote:
> From: "david.wu"
>
> This adds the necessary data for handling io voltage domains on the rk3328.
> As interesting tidbit, the rk3328 only contains one iodomain area in the
> regular General Register Files (GRF).
>
> Signed-off-by: davi
On 02/23/2017 03:26 PM, Dave Hansen wrote:
> Shuah, I assume you'll take this patch in through the selftests tree.
Yes I can do that.
-- Shuah
>
> --
> From: Dave Hansen
>
> The kernel pkeys code had a minor bug where it did some large shifts
> to an integer which is undefined behavior in C.
On Thursday, February 23, 2017 09:55:17 PM Alex Shi wrote:
>
> On 02/23/2017 08:15 PM, Rafael J. Wysocki wrote:
> > On Wednesday, February 22, 2017 10:55:04 PM Alex Shi wrote:
> >>>
> >>> Its not hard; spinlock_t ends up being a mutex, and this is ran from the
> >>> idle thread. What thread do you
On Mon, Feb 20, 2017 at 4:20 PM, Jonathan Corbet wrote:
>> Exception occurred:
>> File "/usr/lib/python3.5/site-packages/docutils/writers/_html_base.py",
>> line
>> 671, in depart_document
>> assert not self.context, 'len(context) = %s' % len(self.context)
>> AssertionError: len(context) =
Hi!
On Tue 2017-02-21 13:11:04, Sakari Ailus wrote:
> On Tue, Feb 21, 2017 at 12:07:21PM +0100, Pavel Machek wrote:
> > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrote:
> > > > I've tested ACPI, will test DT soon...
> > >
> > > DT
On 02/23, Chao Yu wrote:
> On 2017/2/14 10:06, Jaegeuk Kim wrote:
> > This patches adds bitmaps to represent empty or full NAT blocks containing
> > free nid entries.
> >
> > If we can find valid crc|cp_ver in the last block of checkpoint pack, we'll
> > use these bitmaps when building free nids.
On Thu, Feb 02, 2017 at 11:06:02AM -0700, Logan Gunthorpe wrote:
> This patch adds a few read-only sysfs attributes which provide
> some device information that is exposed from the devices. Primarily
> component and device names and versions. These are documented in
> Documentation/ABI/testing/sysf
On 23/02/17 03:43 PM, Bjorn Helgaas wrote:
> This path seems a little generic. I don't see other cases where a
> product brand name ("Switchtec") appears at the top level of
> /sys/class/...
Ok, well we are certainly open to suggestions, but there isn't really a
generic version of this device a
On 02/23/2017 12:34 PM, Jiri Kosina wrote:
> On Wed, 1 Feb 2017, Laura Abbott wrote:
>
>> That's the main one where debugging was happening. There may be a couple
>> of others floating around that I hadn't had time to fully investigate.
>> I'll dupe them to the above if I find them.
>
> [ addin
On Mon, Feb 20, 2017 at 01:35:50PM +0100, Michal Hocko wrote:
> On Mon 13-02-17 14:44:16, Maxime Ripard wrote:
> > Hi Michal,
> >
> > On Thu, Feb 09, 2017 at 08:20:47PM +0100, Michal Hocko wrote:
> > > [CC CMA people]
> > >
> > > On Thu 09-02-17 17:39:17, Maxime Ripard wrote:
> > > > Modules migh
Change log from v1:
- modified some condition checks suggested by Chao
This patches adds bitmaps to represent empty or full NAT blocks containing
free nid entries.
If we can find valid crc|cp_ver in the last block of checkpoint pack, we'll
use these bitmaps when building free nids. In order to a
On 02/13/17 18:50, Stephen Boyd wrote:
> The 'blob' we pass into populate_properties() is marked as const,
> but we cast that const away when we assign the result of
> fdt_getprop_by_offset() to pp->value. Let's mark value as const
> instead, so that code can't mistakenly write to the value of the
On 2/22/2017 12:13 PM, Dave Hansen wrote:
On 02/16/2017 07:43 AM, Tom Lendacky wrote:
static inline unsigned long pte_pfn(pte_t pte)
{
- return (pte_val(pte) & PTE_PFN_MASK) >> PAGE_SHIFT;
+ return (pte_val(pte) & ~sme_me_mask & PTE_PFN_MASK) >> PAGE_SHIFT;
}
static inline unsig
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-defconfig
for you to fetch changes up to ddf5cf02b981e32
On 02/23/2017 03:10 PM, Arnd Bergmann wrote:
> The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
>
> Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> tags/arm
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-dt
for you to fetch changes up to a25996e733db057a27a5f90
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-drivers
for you to fetch changes up to db27dd05b1da6e658
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-soc
for you to fetch changes up to af1d09eefa72089300ddde
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-dt64
for you to fetch changes up to cbab31977008a9eb9eb24
The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes-nc
for you to fetch changes up to 92f3e6ebf6e43fdd
Hi Linus,
This seems to be a rather quiet merge window for us, with no invasive
changes made, or major platforms added. These are the first seven pull
requests for the merge window, we have one 'late' branch that we may
send in a few days, and there are some pending bugfixes as well.
Some statist
The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-arm64
for you to fetch changes up to 971d33cb422b3109fe3
Mark Brown writes:
> > > The obvious question here, especially in the case of
> > > mod_delayed_work(), is why not fix the existing functions to have
> > > the expected behaviour?
>
> > AFAICS the existing functions behave as documented. I don't feel
> > to be an authority to decide that the docum
On 02/23/17 14:09, Rob Herring wrote:
> On Thu, Feb 23, 2017 at 2:58 PM, Frank Rowand wrote:
>> On 02/23/17 11:54, Frank Rowand wrote:
>>> On 02/13/17 18:50, Stephen Boyd wrote:
The 'blob' we pass into populate_properties() is marked as const,
but we cast that const away when we assign t
On Wed, Feb 22, 2017 at 03:53:16PM +0100, Michal Hocko wrote:
> On Wed 22-02-17 23:35:17, Minchan Kim wrote:
> > On Wed, Feb 22, 2017 at 01:11:00PM +0100, Michal Hocko wrote:
> > > On Wed 22-02-17 14:39:24, Minchan Kim wrote:
> > > > With rw_page, page_endio is used for completing IO on a page
> >
acklight)
^
Caused by commit
9f69eb5c36a6 ("drm/tinydrm: Add helper functions")
I have used the drm tree from next-20170223 for today.
--
Cheers,
Stephen Rothwell
On 02/23/17 15:08, Frank Rowand wrote:
> On 02/13/17 18:50, Stephen Boyd wrote:
>> The 'blob' we pass into populate_properties() is marked as const,
>> but we cast that const away when we assign the result of
>> fdt_getprop_by_offset() to pp->value. Let's mark value as const
>> instead, so that cod
Hi Dave,
After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:
/next/include/drm/drm_gem_cma_helper.h:4:0,
from include/drm/tinydrm/tinydrm.h:13,
from include/drm/tinydrm/mipi-dbi.h:15,
from drivers/g
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
lib/Kconfig
between commit:
44091d29f207 ("lib: Introduce priority array area manager")
from Linus' tree and commit:
cf4a7207b1cb ("lib: Add a simple prime number generator")
from the drm tree.
I fixed it up (see bel
On Thu, Feb 23, 2017 at 3:05 PM, Arnd Bergmann wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> tags/armsoc-fixes-nc
Interesting. So I'm pulling this, and I get to pull request 3/7, and
that's when I notice that the email is sent by Arnd, but the tag is
signed by Olof
> "Finn" == Finn Thain writes:
Finn> The mac_scsi driver still gets disabled when SCSI=m. This should
Finn> have been fixed back when I enabled the tristate but I didn't see
Finn> the bug.
Applied to 4.11/scsi-fixes.
--
Martin K. Petersen Oracle Linux Engineering
On Tue, Feb 21, 2017 at 5:45 AM, Viresh Kumar wrote:
> The rate_limit_us tunable is intended to reduce the possible overhead
> from running the schedutil governor. However, that overhead can be
> divided into two separate parts: the governor computations and the
> invocation of the scaling driver
From: Rafael J. Wysocki
Define a pr_fmt() for hibernate.c and convert all of the explicit
printk() calls into corresponding pr_*() so that they use the
pr_fmt() format.
Signed-off-by: Rafael J. Wysocki
---
kernel/power/hibernate.c | 60 ++-
1 file
From: Rafael J. Wysocki
The power_down() routine in the core hibernation code is not exactly
straightforward (to put it lightly), so clean it up to make it avoid
invoking itself recursively, among other things.
Signed-off-by: Rafael J. Wysocki
---
kernel/power/hibernate.c | 35 ++
Hi,
These are two cleanups for hibernate.c, one to untangle power_down() and the
other related to printing messages.
Thanks,
Rafael
On Thu, Feb 23, 2017 at 5:08 PM, Frank Rowand wrote:
> On 02/13/17 18:50, Stephen Boyd wrote:
>> The 'blob' we pass into populate_properties() is marked as const,
>> but we cast that const away when we assign the result of
>> fdt_getprop_by_offset() to pp->value. Let's mark value as const
>> inste
Hi Dave,
On Thu, Feb 23, 2017 at 02:44:06PM -0500, Dave Jones wrote:
> cat /sys/devices/virtual/iommu/dmar0/intel-iommu/version
>
> Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
Thanks for the report, the problem reproduces easily here. The diff
below fixes the issue on Intel, AMD has the same pro
> "Colin" == Colin King writes:
Colin> trivial fix to spelling mistake in pr_err message
Applied to 4.11/scsi-fixes.
--
Martin K. Petersen Oracle Linux Engineering
Hi,
Please pull this usercopy fix for v4.11-rc1. Arnd noticed a corner case.
Thanks!
-Kees
The following changes since commit 4c5d7bc63775b40631b75f6c59a3a3005455262d:
usercopy: Add tests for all get_user() sizes (2017-02-21 11:59:38 -0800)
are available in the git repository at:
git://g
On Thu, Feb 23, 2017 at 1:43 PM, John Stultz wrote:
> Hey folks,
>I've not been able to figure out why yet, but I wanted to raise the
> issue that last night I found I couldn't boot Android on my Hikey
> board with Linus' HEAD kernel. It seems to cause logd to crash
> repeatedly so I'm not abl
On Tue, Feb 21, 2017 at 12:55 AM, Chunyan Zhang
wrote:
> From: Orson Zhai
>
> SC9860G is a 8 cores of A53 SoC with 4G LTE support SoC from Spreadtrum.
>
> According to regular hierarchy of sprd dts, whale2.dtsi contains SoC
> peripherals IP nodes, sc9860.dtsi contains stuff related to ARM core st
401 - 500 of 647 matches
Mail list logo
