Linus,
Please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
# HEAD: c5b635203032462603c503ecce91a7021c1ad44a irqchip/mxs: Add missing
set_handle_irq()
Mostly driver fixes, but also an irq core crash
在 2016年01月30日 00:28, Rob Herring 写道:
On Thu, Jan 28, 2016 at 04:43:35PM +0800, Caesar Wang wrote:
This patch add the mclk property for the CODEC driver,
since sometime the CODEC driver needs the clock enabled.
s/add/adds/
s/sometime/sometimes/
Done, thanks for pointing out that.
The
This patch adds the mclk property for the CODEC driver,
since sometimes the CODEC driver needs the clock enabled.
The system clock of ALC5616 can be selected from MCLK,
That also makes the codec the master clock provider
Signed-off-by: Caesar Wang
---
Changes in v4 -> v4.1:
- Fix the wrong
Am 29.01.2016 um 15:31 schrieb Nicolai Stange:
>>> Question 1: now that ->pte_high will be gone, do you want to have
>>> ->pte_low renamed to e.g. ->pte_val?
>>
>> So, with a freshly booted brain the story looks a bit different.
>> All this code needs a cleanup and we need to check
Doug,
On 01/29/2016 10:20 AM, Douglas Anderson wrote:
According to the most up to date version of the dwc2 databook, the FRINT
field of the HFIR register should be programmed to:
* 125 us * (PHY clock freq for HS) - 1
* 1000 us * (PHY clock freq for FS/LS) - 1
I got 3 version of dwc_otg
Doug,
Reviewed-by: Kever Yang
Thanks,
- Kever
On 01/29/2016 10:20 AM, Douglas Anderson wrote:
I find that when I plug a full speed (NOT high speed) hub into a dwc2
port and then I plug a bunch of devices into that full speed hub that
dwc2 goes bat guano crazy. Specifically, it just spews
Use the current logging styles. And convert printk(KERN_ERR ...)
to pr_err(...) for threshold.c.
Signed-off-by: Chen Yucong
---
arch/x86/kernel/cpu/mcheck/threshold.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/mcheck/threshold.c
Doug,
On 01/29/2016 10:20 AM, Douglas Anderson wrote:
In dwc2_hcd_qh_deactivate() we will put some things on the
periodic_sched_ready list. These things won't be taken off the ready
list until the next SOF, which might be a little late. Let's put them
on right away.
Signed-off-by: Douglas
Hi,
On 01/29/2016 06:21 PM, Chen-Yu Tsai wrote:
Hi everyone,
This was "mmc: sunxi: Support vqmmc regulator and eMMC DDR modes". vqmmc
support and DT patches were merged even though it was an RFC series, to
my suprise.
These are the remaining patches that add eMMC HS-DDR support to sunxi.
On Sun, Jan 31, 2016 at 10:05:09AM +0530, Parav Pandit wrote:
> Changes from v4:
> * Fixed compilation errors for lockdep_assert_held reported by kbuild
>test robot
> * Fixed compilation warning reported by coccinelle for extra semicolon.
> * Fixed compilation error for inclusion of
On Sun, Jan 31, 2016 at 3:16 PM, Tejun Heo wrote:
> On Sun, Jan 31, 2016 at 10:05:09AM +0530, Parav Pandit wrote:
>> Changes from v4:
>> * Fixed compilation errors for lockdep_assert_held reported by kbuild
>>test robot
>> * Fixed compilation warning reported by coccinelle for extra
Hello, Parav.
On Sun, Jan 31, 2016 at 02:14:13AM +0530, Parav Pandit wrote:
...
> V1 patch had IB resources defined in the header file of rdmacg, which
> I believe is very restrictive model with evolving rdma stack and
> features.
Wasn't this the model that we agreed upon? Besides, even if the
On Sun, Jan 31, 2016 at 09:51:55AM +0100, Richard Weinberger wrote:
> On Sun, Jan 31, 2016 at 7:07 AM, Sina Hamedian wrote:
> > The URL to the book IA-64 and Elementary Functions in idiv32.S and
> > idiv64.S just led to a 404 page, so I updated them with a known good link
> > that others can
On Sat, Jan 30, 2016 at 11:54:03AM +0800, Li Bin wrote:
> The file cgroup-debug.c had been removed from commit fe6934354f8e
> (cgroups: move the cgroup debug subsys into cgroup.c to access internal
> state).
> Remain the CFLAGS_REMOVE_cgroup-debug.o = $(CC_FLAGS_FTRACE)
> useless in
On Sun, Jan 31, 2016 at 3:32 PM, Tejun Heo wrote:
> Hello, Parav.
>
> On Sun, Jan 31, 2016 at 02:14:13AM +0530, Parav Pandit wrote:
> ...
>> V1 patch had IB resources defined in the header file of rdmacg, which
>> I believe is very restrictive model with evolving rdma stack and
>> features.
>
>
Am Donnerstag, 28. Januar 2016, 16:43:30 schrieb Caesar Wang:
> As the kylin schematic drawing, add the needed work led for
> kylin board.
>
> Run:
> echo 0 > /sys/class/leds/kylin:red:led/brightness
> echo 1 > /sys/class/leds/kylin:red:led/brightness
>
> The led can normal on/off on kylin
On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:
> > I did probably 70% of the work needed to switch the radix tree over to
> > storing PFNs instead of sectors. It seems viable, though it's a big
> > change from where we are today:
>
> At one point I had kaddrs in the radix tree, so
On 26/01/16 05:12, Yong Wu wrote:
This patch add SMI(Smart Multimedia Interface) driver. This driver
is responsible to enable/disable iommu and control the power domain
and clocks of each local arbiter.
Signed-off-by: Yong Wu
Tested-by: Philipp Zabel
---
Signed-off-by: Matthias Brugger
On 29/01/2016 23:21, Andrew Vagin wrote:
> On Thu, Jan 28, 2016 at 02:42:25PM -0800, Andrey Wagin wrote:
>> On Thu, Jan 28, 2016 at 10:33:28PM +0100, Paolo Bonzini wrote:
>>>
>>>
>>> On 28/01/2016 09:31, Andrey Wagin wrote:
I tried to print drX registers after a break-point. Looks like they
Hello, Parav.
On Sun, Jan 31, 2016 at 04:11:54PM +0530, Parav Pandit wrote:
> No. We agreed that let IB stack define in the header file that rdmacg
> can include.
> However when I started with that I realized that, such design has
> basic flaw that IB stack is compiled as loadable modules.
>
Hi Caesar,
Am Donnerstag, 28. Januar 2016, 16:43:38 schrieb Caesar Wang:
> You have to use the 4 bus to work if someone wants to support
> the spi devices, since the the pin is re-used by data[5-8] and spi.
> If support the spi making the happy work, that will waste the
> emmc performance.
>
>
On Sun, 24 Jan 2016 11:10:33 +0100,
Dmitry Vyukov wrote:
>
> Hello,
>
> The following program causes use-after-free in snd_timer_notify1:
>
> ==
> BUG: KASAN: use-after-free in snd_timer_notify1+0x411/0x460 at addr
>
On Wed, 27 Jan 2016 13:31:05 +0100,
Dmitry Vyukov wrote:
>
> On Tue, Jan 26, 2016 at 3:51 PM, Takashi Iwai wrote:
> > On Sun, 24 Jan 2016 17:29:12 +0100,
> > Dmitry Vyukov wrote:
> >>
> >> Hello,
> >>
> >> The following program triggers WARNING in snd_rawmidi_transmit_ack:
> >>
> >>
On Sat, 30 Jan 2016 21:28:27 +0100,
Dmitry Vyukov wrote:
>
> Hello,
>
> I've got the following deadlock report while running syzkaller fuzzer:
>
> [ INFO: possible circular locking dependency detected ]
> 4.5.0-rc1+ #305 Not tainted
> ---
>
On Sunday 31 January 2016 02:19:46 Sebastian Reichel wrote:
> Disabled power management means, that the driver can only be
> used together with further out-of-tree kernel patches. There
> is no reason to support this in the mainline kernel and not
> having support for it means, that userspace can
Hi,
On 26/01/2016 at 17:00:31 +0100, Alexandre Belloni wrote :
> On 26/01/2016 at 06:56:40 -0800, Joshua Clayton wrote :
> > Ping?
> >
> > On Monday, January 04, 2016 10:31:18 AM Joshua Clayton wrote:
> > > Alexandre,
> > > this is the second version of apatch set to be able to adjust the
> > >
Hi,
On 04/01/2016 at 10:31:25 -0800, Joshua Clayton wrote :
> The file is called "offset", and may be set and read in decimal.
> For rtcs that do not have read_offset or set_offset implemented,
> read always returns zero and write will return -EINVAL.
>
Can you expand rtc_attr_is_visible()
On 20/01/16 07:08, James Liao wrote:
Refine scpsys driver common code to support multiple SoC / platform.
Signed-off-by: James Liao
---
drivers/soc/mediatek/mtk-scpsys.c | 418 --
drivers/soc/mediatek/mtk-scpsys.h | 55 +
2 files changed, 270
Hi,
On 27/01/2016 at 00:36:36 -0300, Javier Martinez Canillas wrote :
> Hello,
>
> On a recent disussion [0] with Krzysztof Kozlowski and Laxman Dewangan,
> we came to the conclusion that the max77686 and max77802 RTC are almost
> the same with only a few differences so there shouldn't be two
On 27/01/2016 at 15:46:11 +0900, Krzysztof Kozlowski wrote :
> Cleanup of entire driver of its dmesg output:
> 1. Remove printing of the function name, because printing device name is
>sufficient. This also makes the dev_err()-like functions more compact
>and readable (not need of line
From: Matthew Wilcox
In preparation for adding the ability to handle PUD pages, convert
->pmd_fault to ->huge_fault. huge_fault() takes a vm_fault structure
instead of separate (address, pmd, flags) parameters. The vm_fault
structure is extended to include a union of the different page table
From: Matthew Wilcox
We don't actually care about the contents of the PUD, as long as it's
present (which is checked by the pagewalk code), so just set the bits
to indicate presence and return.
Signed-off-by: Matthew Wilcox
---
mm/mincore.c | 13 +
1 file changed, 13 insertions(+)
From: Matthew Wilcox
ext4 needs to reserve enough space in the journal to allocate a PUD-sized
page.
Signed-off-by: Matthew Wilcox
---
fs/ext4/file.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index 71859ed..ec6664a 100644
--- a/fs/ext4/file.c
+++
From: Matthew Wilcox
Because there's no 'struct page' for DAX THPs, a lot of this code is
simpler than the PMD code it mimics. Extra code would need to be added
to support PUDs of anonymous or page-cache THPs.
Signed-off-by: Matthew Wilcox
---
fs/proc/task_mmu.c | 109
From: Matthew Wilcox
The DAX support for transparent huge PUD pages
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 185 +++
1 file changed, 185 insertions(+)
diff --git a/fs/dax.c b/fs/dax.c
index b2ad0ce..2f9bb89 100644
---
W dniu 31.01.2016 o 21:05, Alexandre Belloni pisze:
> Hi,
>
> On 27/01/2016 at 00:36:36 -0300, Javier Martinez Canillas wrote :
>> Hello,
>>
>> On a recent disussion [0] with Krzysztof Kozlowski and Laxman Dewangan,
>> we came to the conclusion that the max77686 and max77802 RTC are almost
>> the
From: Matthew Wilcox
Spotted during PUD support review.
Reported-by: Kirill A. Shutemov
Signed-off-by: Matthew Wilcox
---
mm/memory.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index a2eaeef..324b40b 100644
--- a/mm/memory.c
+++
From: Matthew Wilcox
The x86-specific code needed to support the PUD uses in the transparent
hugepages code.
Signed-off-by: Matthew Wilcox
---
arch/x86/Kconfig | 1 +
arch/x86/include/asm/paravirt.h | 11 +++
arch/x86/include/asm/paravirt_types.h | 2 +
We have customer demand to use 1GB pages to map DAX files. Unlike the 2MB
page support, the Linux MM does not currently support PUD pages, so I have
attempted to add support for the necessary pieces for DAX huge PUD pages.
Filesystems still need work to allocate 1GB pages. With ext4, I can
only
Be informed that Muthoot Finance give out Guarantee Business Loans, Automobile
Purchase Loans, House Purchase Loans, Personal Loans at 3% interest rate, for
more info email: muthootfinancceh...@gmail.com
Estar informado de que Muthoot Finanzas Dar a conocer Garanta de negocios
Prstamos,
do_fault assumes that PAGE_SIZE is the same as PAGE_CACHE_SIZE.
Use linear_page_index() to calculate pgoff in the correct units.
Signed-off-by: Matthew Wilcox
---
mm/memory.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index 554816b..5224c06
From: Matthew Wilcox
The current transparent hugepage code only supports PMDs. This patch
adds support for transparent use of PUDs with DAX. It does not include
support for anonymous pages.
Most of this patch simply parallels the work that was done for huge PMDs.
The only major difference is
Now that the PMD and PUD fault handlers are passed pgoff, there's no
need to calculate it themselves.
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 26 --
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index 696ff90..d0e1334 100644
---
We were a little sloppy about using PAGE_SIZE instead of PAGE_CACHE_SIZE.
The important thing to remember is that the VM is gicing us a pgoff_t
and asking us to populate that. If PAGE_CACHE_SIZE were larger than
PAGE_SIZE, then we would not successfully fill in the PTEs for faults
that occurred
We were assuming that it was OK to do a GFP_KERNEL allocation in page
fault context. That appears to be largely true, but filesystems are
permitted to override that in their setting of mapping->gfp_flags, which
the VM then massages into vmf->gfp_flags. No practical difference for
now, but there
These two functios are still large, but they're no longer quite so
ludicrously large
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 153 +--
1 file changed, 80 insertions(+), 73 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index
Very little exciting in here. This is all based on the PUD support code
that I just sent, mostly addressing things that came up during review
of the PUD code but weren't really justifiable as being mixed into the
adding of PUD support.
Matthew Wilcox (6):
dax: Use vmf->gfp_mask
dax: Remove
When i_mmap_lock (or the page lock) was the only protection against
truncate, we checked i_size at the beginning of the fault handler,
then rechecked it after acquiring the lock. Since the fliesystems now
exclude truncate from racing with the fault handler, we no longer need
to recheck i_size.
Follow the factoring done for dax_pmd_fault.
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 100 +--
1 file changed, 53 insertions(+), 47 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index ec31e6e..e9701d6 100644
--- a/fs/dax.c
+++
On (01/29/16 15:37), Sergey Senozhatsky wrote:
>
> panic()->console_panic_mode()->{for_each_console()->reset(),
> zap_locks()}->console_trelock()->console_unlock().
Hello,
This is not a final submission, just a RFC, so we can settle a better
plan. the patches are not signed off, have known
Console driver(-s) can be in any state when CPU stop IPI
arrives from panic() issued on another CPU, so
console_flush_on_panic()->console_unlock() can call
con->write() callback on a locked console driver.
Introduce reset_console_drivers() that attempts to reset()
every console in via a console
CPU stop IPI issued from panic() on CPUA, can leave console_sem locked
on CPUB if that cpu was holding the console_sem lock at the time when
IPI arrived. console_flush_on_panic() is trying to workaround it by
ignoring the return status of console_trylock() and unconditionally
executing
spin_dump() calls printk() which can attempt to reacquire the
'buggy' lock (one of printk's lock, or console device driver lock,
etc.) and thus spin_dump() will recursive into itself. Steal most
significant bit of spin_lock->owner_cpu to keep there a mark
that spin_dump() is in progress for that
Linus,
please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
A single commit, which makes the rtmutex.wait_lock an irq safe lock. This
prevents a potential deadlock which can be triggered by the rcu
On (01/29/16 21:54), Byungchul Park wrote:
> Hello, Andrew
>
> Please take this v5 patch instead of v2 patch, which you took. Or give your
> opinion.
>
> > It causes an infinite recursive cycle when using CONFIG_DEBUG_SPINLOCK,
> > in the spin_dump(). Backtrace prints printk() ->
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
This is much bigger than typical fixes, but Peter found a category of races
that spurred more fixes and more debugging enhancements. Work
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
Three small fixes in the scheduler/core
- Use after free in the numa code
- Crash in the numa init code
- A simple spelling
-Senozhatsky/printk-introduce-console_reset_on_panic-function/20160131-203605
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/printk/printk.c: In fu
-Senozhatsky/printk-introduce-console_reset_on_panic-function/20160131-203605
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/printk/printk.c: In fu
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
The timer departement delivers:
- A regression fix for the NTP code along with a proper selftest
- Prevent a spurious timer interrupt
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A bit on the largish side due to a series of fixes for a regression in the x86
vector management which was introduced in 4.3. This work was
This patch adds support for Si-En SN3218 18 Channel LED Driver.
Signed-off-by: Stefan Wahren
---
drivers/leds/Kconfig | 12 ++
drivers/leds/Makefile |1 +
drivers/leds/leds-sn3218.c | 297
3 files changed, 310 insertions(+)
create
Si-En Technology is a fabless design house which offers
audio amplifiers, LED drivers and sensors.
Signed-off-by: Stefan Wahren
Acked-by: Rob Herring
---
.../devicetree/bindings/vendor-prefixes.txt|1 +
1 file changed, 1 insertion(+)
diff --git
This patch series implements support for the Si-En SN3218
18 Channel LED Driver connected through I2C. The SN3218
doesn't support reading so the LED states are cached in a
regmap.
The driver has been tested on a Raspberry Pi B.
Changes since RFC:
* using regmap instead of direct I2C
* add
This patch adds the binding for Si-En Technology SN3218
18-Channel LED driver.
Signed-off-by: Stefan Wahren
Acked-by: Rob Herring
---
.../devicetree/bindings/leds/leds-sn3218.txt | 42
1 file changed, 42 insertions(+)
create mode 100644
Am Samstag, 30. Januar 2016, 17:38:28 schrieb Dan Carpenter:
Hi Dan,
> We're clearing the wrong memory. The memory corruption is likely
> harmless because we weren't going to use that stack memory again but not
> zeroing is a potential information leak.
>
> Fixes: e28facde3c39 ('crypto:
Hello!
In current linux-mips master branch from
git://git.linux-mips.org/pub/scm/ralf/linux
there are two commits
commit 76654c7be21c1704607e9ed22cf5d18d430fd828
Author: Alban Bedel
Date: Mon Nov 16 22:22:04 2015 +0100
MIPS: ath79: Enable the USB port on the TL-WR1043ND
After rename file dentry still holds reference to lower dentry from
previous location. This doesn't matter for data access because data
cames from upper dentry. But this stale lower dentry taints dentry
at new location and turns it into non-pure upper. Such file leaves
visible whiteout entry after
This fixes some cases of missing atime update for overlayfs.
Signed-off-by: Konstantin Khlebnikov
---
fs/inode.c | 15 +--
include/linux/fs.h |6 +-
2 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/fs/inode.c b/fs/inode.c
index
Overlayfs must update uid/gid after chown, otherwise functions
like inode_owner_or_capable() will check user against stale uid.
Catched by xfstests generic/087, it chowns file and calls utimes.
Signed-off-by: Konstantin Khlebnikov
---
fs/overlayfs/inode.c |2 ++
1 file changed, 2
Catched by xfstests generic/319
Signed-off-by: Konstantin Khlebnikov
---
fs/overlayfs/super.c |4
1 file changed, 4 insertions(+)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index ba28b007005e..e6ae59c7119c 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@
This adds missing .d_select_inode into alternative dentry_operations.
Signed-off-by: Konstantin Khlebnikov
Fixes: 7c03b5d45b8e ("ovl: allow distributed fs as lower layer")
Fixes: 4bacc9c9234c ("overlayfs: Make f_path always point to the overlay and
f_inode to the underlay")
---
For example fuse root dentry has no dentry operations.
Signed-off-by: Konstantin Khlebnikov
Fixes: 7c03b5d45b8e ("ovl: allow distributed fs as lower layer")
---
fs/overlayfs/super.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/fs/overlayfs/super.c
On Tue, Jan 26, 2016 at 9:01 AM, Felipe Ferreri Tonello
wrote:
> Actually yes, thanks! I didn't know about the existence of fsl-asoc-card.
>
> I get some errors but I don't think they actually matter:
> [ 19.734494] fsl-asrc 2034000.asrc: driver registered
> [ 19.738707] fsl-asoc-card sound:
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/i2c/busses/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 0299dfa..a2e456a 100644
---
Add COMPILE_TEST for the compilation test coverage.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/uniphier/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/uniphier/Kconfig b/drivers/pinctrl/uniphier/Kconfig
index 7abd614..43f689f 100644
---
Hi Eric, Alex, Antonios;
On 1/29/2016 5:35 PM, Sinan Kaya wrote:
> The code is using the compatible DT string to associate a reset driver with
> the actual device itself. The compatible string does not exist on ACPI
> based systems. HID is the unique identifier for a device driver instead.
> The
Julian Calaby writes:
> Hi Bhaktipriya,
>
> On Sat, Jan 30, 2016 at 5:00 AM, Jes Sorensen wrote:
>> Bhaktipriya Shridhar writes:
>> If you insist on pushing this rather unncessary change, please do it
>> properly, and remove the blank line before the return statement as well.
>
> As Jes said,
Bhaktipriya Shridhar writes:
> This patch fixes checkpatch.pl warning in rtw_mlme_ext.c file.
> WARNING: void function return statements are not generally useful
>
> Signed-off-by: Bhaktipriya Shridhar
> ---
> Changes in v2:
>- Removed the unnecessary blank lines.
>
Commit 7bc5a2bad0b8 ("ACPI: Support _OSI("Darwin") correctly") always
reports positive value when Apple hardware queries _OSI("Darwin").
But sometimes the users might want to tell the hardware they don't
need the Darwin feature, for example, users may leverage the hardware
to power off the
On Sat, 30 Jan 2016, Maciej W. Rozycki wrote:
> > % echo 2.24.51.20140217 | ld-version.sh
> > 22451000
>
> So the above version is a non-release snapshot from the development tree
> as the repository trunk is switched to x.y+1.51 once a release branch for
> x.y has been made. Then the
Commit 16da306849d0 ("um: kill pfn_t")
introduced a compile warning for defconfig (SUBARCH=i386):
arch/um/kernel/skas/mmu.c:38:206:
warning: right shift count >= width of type [-Wshift-count-overflow]
Aforementioned patch changes the definition of the phys_to_pfn() macro from
((pfn_t)
Hi Linus,
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.5-rc2
for you to fetch changes up to
Some I2C devices have multiple addresses assigned, for example each address
corresponding to a different internal register map page of the device.
So far drivers which need support for this have handled this with a driver
specific and non-generic implementation, e.g. passing the additional address
On Sun, Jan 31, 2016 at 12:00:41PM +0100, Matthias Brugger wrote:
>
>
> On 26/01/16 05:12, Yong Wu wrote:
> >This patch add SMI(Smart Multimedia Interface) driver. This driver
> >is responsible to enable/disable iommu and control the power domain
> >and clocks of each local arbiter.
> >
>
Use list_for_each_entry*() instead of list_for_each*() to simplify
the code. Fix coding style by the way.
Signed-off-by: Geliang Tang
---
drivers/staging/rtl8723au/core/rtw_ap.c | 166 --
drivers/staging/rtl8723au/core/rtw_mlme.c | 38 ++---
BUFFER_TRACE info "call ext4_handle_dirty_metadata" doesn't match the
code, so drop it.
Signed-off-by: Geliang Tang
---
fs/ext4/inline.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c
index dfe3b9b..cbcb907 100644
--- a/fs/ext4/inline.c
+++
-when-acpi_osi-Darwin-provided/20160131-224855
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
config: i386-randconfig-s0-201605 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new
Use list_for_each_entry() instead of list_for_each() to simplify the code.
Signed-off-by: Geliang Tang
---
init/main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/init/main.c b/init/main.c
index 68ec07b..3cf30ec 100644
--- a/init/main.c
+++ b/init/main.c
@@ -728,7
Hi,
On Sun, Jan 31, 2016 at 12:24:34PM +0100, Pali Rohár wrote:
> On Sunday 31 January 2016 02:19:46 Sebastian Reichel wrote:
> > Disabled power management means, that the driver can only be
> > used together with further out-of-tree kernel patches. There
> > is no reason to support this in the
The following patches add the self-test for
sigaltstack(SS_DISABLE) inside the signal handler,
and allow an app to temporarily disable and re-enable
the sigaltstack within a sighandler.
This is needed to make sigaltstack() compatible with
swapcontext(): before using swapcontext() inside
the
sigaltstack needs to be disabled before the signal handler can
safely use swapcontext(). Unfortunately linux implementation of
sigaltstack() returns EPERM in that case.
Re-enabling is also needed and tested.
CC: Shuah Khan
CC: linux-kernel@vger.kernel.org
CC: linux-...@vger.kernel.org
CC: Andy
Currently get_sigframe() checks only
(ka->sa.sa_flags & SA_ONSTACK) && (!on_sig_stack(sp))
to determine whether the switch to sigaltstack is needed.
It forgets to checks whether the sigaltstack was previously set.
This patch replaces the !on_sig_stack(sp) with the standard check
Currently x86's get_sigframe() checks for "current->sas_ss_size"
to determine whether there is a need to switch to sigaltstack.
The common practice used by all other arches is to check for
sas_ss_flags(sp) == 0
This patch makes the code consistent with other arches and also
allows for the
linux implements the sigaltstack() in a way that makes it impossible to
use with swapcontext(). Per the man page, sigaltstack is allowed to return
EPERM if the process is altering its sigaltstack while running on
sigaltstack.
This is likely needed to consistently return oss->ss_flags, that
On Sun, Jan 31, 2016 at 2:55 AM, Matthew Wilcox wrote:
> On Sat, Jan 30, 2016 at 11:12:12PM -0700, Ross Zwisler wrote:
>> > I did probably 70% of the work needed to switch the radix tree over to
>> > storing PFNs instead of sectors. It seems viable, though it's a big
>> > change from where we
Rule r is only used in org or report mode, so only execute it in those
cases.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/api/pm_runtime.cocci |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccinelle/api/pm_runtime.cocci
On Sun, Jan 31, 2016 at 8:24 AM, Stas Sergeev wrote:
>
> Currently x86's get_sigframe() checks for "current->sas_ss_size"
> to determine whether there is a need to switch to sigaltstack.
> The common practice used by all other arches is to check for
> sas_ss_flags(sp) == 0
>
> This patch makes
On Mon, Jan 25, 2016 at 8:15 AM, Chen-Yu Tsai wrote:
> sun6i's AR100 clock is a classic factors clk case:
>
> AR100 = ((parent mux) >> p) / (m + 1)
>
> Signed-off-by: Chen-Yu Tsai
This patch adds a ".remove" function to a driver that is controlled by
a bool Kconfig, and hence the remove code
On Sun, Jan 31, 2016 at 8:28 AM, Stas Sergeev wrote:
>
> linux implements the sigaltstack() in a way that makes it impossible to
> use with swapcontext(). Per the man page, sigaltstack is allowed to return
> EPERM if the process is altering its sigaltstack while running on
> sigaltstack.
> This
301 - 400 of 596 matches
Mail list logo
