On Tuesday 02 May 2017 12:07 AM, Matthias Kaehlcke wrote:
Some regulators have different settling times for voltage increases and
decreases. Add DT properties to define separate settling times for up-
and downward voltage changes.
Signed-off-by: Matthias Kaehlcke
---
Acked-by: Laxman Dewanga
On 28 April 2017 at 18:14, Tejun Heo wrote:
> Hello, Vincent.
>
>>
>> The only interest of runnable_load_avg is to be null when a cfs_rq is
>> idle whereas load_avg is not but not to be higher than load_avg. The
>> root cause is that load_balance only looks at "load" but not number of
>> task cur
On Tuesday 02 May 2017 12:07 AM, Matthias Kaehlcke wrote:
Some regulators have different settling times for voltage increases and
decreases. To avoid a time penalty on the faster transition allow for
different settings for up- and downward transitions.
Signed-off-by: Matthias Kaehlcke
---
Ac
Hi all,
Please do not add any v4.13 destined material in your linux-next
included branches until after v4.12-rc1 has been released.
Changes since 20170501:
The tip tree gained a build failure due to an interaction with Linus'
tree for which I applied a merge fix patch.
The drivers-x86
Hello
When inserting sun4i_gpadc_iio I got the following error in dmesg:
[79961.039826] thermal thermal_zone0: failed to read out thermal zone (-110)
Then removing the module cause an oops:
[80105.370937] Unable to handle kernel paging request at virtual address
bf0ad1d0
[80105.370958] pgd = c00
On Mon, May 01, 2017 at 12:47:46PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> With perf script it is common that we just want to add or remove a field.
> Currently this requires figuring out the long list of default fields and
> specifying them first, and then adding/removing the new field.
Hi Will,
SMMU_IIDR register is broken on T99, that the reason we are using MIDR.
If using MIDR is not accepted, can we enable errata based on SMMU resource size?
some thing like below.
static bool page0_reg_only = false;
+static unsigned long arm_smmu_resource_size(void)
+{
+ if (page0_reg_
On Tue, Apr 11, 2017 at 5:16 AM, Christopher Bostic
wrote:
> From: Jeremy Kerr
>
> Implement fsi_slave_init: if we can read a chip ID, create fsi_slave
> devices and register with the driver core.
>
> Includes changes from Chris Bostic .
>
> Signed-off-by: Jeremy Kerr
> Signed-off-by: Chris Bost
> -Original Message-
> From: Felipe Balbi [mailto:ba...@kernel.org]
> Sent: Friday, March 10, 2017 7:27 PM
> To: Jerry Huang ; robh...@kernel.org;
> mark.rutl...@arm.com; catalin.mari...@arm.com
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org; li
We warn the user at driver probe time that debouncing is disabled.
However, if they request debouncing later on we print a confusing error
message:
gpio_aspeed 1e78.gpio: Failed to convert 5000us to cycles at 0Hz: -524
Instead bail out when the clock is not present.
Fixes: 5ae4cb94b3133 (gp
Minchan Kim writes:
> Hi Huang,
>
> On Tue, May 02, 2017 at 01:35:24PM +0800, Huang, Ying wrote:
>> Hi, Minchan,
>>
>> Minchan Kim writes:
>>
>> > On Fri, Apr 28, 2017 at 09:35:37PM +0800, Huang, Ying wrote:
>> >> In fact, during the test, I found the overhead of sort() is comparable
>> >> wit
Create mon_recv_decrypted_recv() to change rtl88eu_mon_recv_hook()
without affect to rtl88eu_mon_xmit_hook().
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/os_dep/mon.c | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8188
ieee80211_get_hdrlen is unused, remove it and all corresponding code.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_ieee80211.c | 27 --
drivers/staging/rtl8188eu/include/ieee80211.h | 13 -
2 files changed, 40 deletions(-)
diff --git a/
Remove unused RTW_IEEE80211_FCTL_*, RTW_IEEE80211_FTYPE_*,
RTW_IEEE80211_STYPE_*, IEEE80211_STATMASK_*, IEEE80211_DEFAULT_*,
BEACON_PROBE_SSID_ID_POSITION, MFIE_TYPE_*, IEEE80211_DTIM_*
and IEEE80211_PS_*.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/include/ieee80211.h | 91 ---
Hi all,
The linux-next build (powerpc allyesconfig) produced these warnings
(and have for a while):
arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_enter':
arch/powerpc/kvm/book3s_pr_papr.c:53:2: warning: ignoring return value of
'copy_from_user', declared with attribute warn_unused_
IV/ICV should be trimmed immediately after decoding
(this is a decryptor job).
Trim IV/ICV inside decrypt() for SW decrypted frames,
for HW decrypted - before rtl88eu_mon_recv_hook().
Adopt frames receive process to work without IV/ICV fields.
Signed-off-by: Ivan Safonov
---
drivers/staging/rt
It is useful to remove IV/ICV from rtl88eu_mon_recv_hook().
Also unprotect_frame() will be very short without skb_(pull|trim).
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/os_dep/mon.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/drivers/stagi
ieee80211_is_empty_essid() is unused, remove it.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_ieee80211.c | 17 -
drivers/staging/rtl8188eu/include/ieee80211.h | 3 ---
2 files changed, 20 deletions(-)
diff --git a/drivers/staging/rtl8188eu/core/rtw_ieee8
Length of IV/ICV fields calculated here, so trim these field here too.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_recv.c | 17 ++---
drivers/staging/rtl8188eu/os_dep/mon.c| 19 ---
2 files changed, 14 insertions(+), 22 deletions(-)
diff --
On 2017年04月30日 06:14, Colin King wrote:
From: Colin Ian King
trivial fix to spelling mistake in an error message.
Signed-off-by: Colin Ian King
---
tools/virtio/virtio_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/virtio/virtio_test.c b/tools/virtio/vir
On Tue, 2017-05-02 at 11:38 +0800, lixi...@cmss.chinamobile.com wrote:
> From: Xiubo Li
>
> Changed for V7:
> - #1 fix two issues.
> - #2 fix kbuild warning and some issues.
>
> Changed for V6:
> - Remove the tcmu_vma_close(). Since the unmap thread will do the same for it
> - The unmap thread
Around Mon 27 Mar 2017 15:35:56 +0200 or thereabout, Hans-Christian Noren
Egtvedt wrote:
> Around Mon 27 Mar 2017 15:26:04 +0200 or thereabout, Boris Brezillon wrote:
>> On Wed, 1 Mar 2017 21:44:26 +0100 Hans-Christian Noren Egtvedt
>> wrote:
>> Is this still planned for 4.12?
>
> Yes, I hav
On Fri, Apr 28, 2017 at 9:26 AM, Paul Moore wrote:
> On Fri, Apr 28, 2017 at 12:11 PM, Cong Wang wrote:
>> On Fri, Apr 28, 2017 at 8:30 AM, Paul Moore wrote:
>>> On Thu, Apr 27, 2017 at 8:47 PM, Paul Moore wrote:
In that case please send a proper inline patch to the audit mailing list
On 05/02/2017 10:34 AM, Guenter Roeck wrote:
> On 05/01/2017 09:35 PM, Shilpasri G Bhat wrote:
>> Hi Guenter,
>>
>> On 04/28/2017 06:59 PM, Guenter Roeck wrote:
>>> On 04/27/2017 10:59 PM, Shilpasri G Bhat wrote:
Add support for adding min/max values for the inband sensors copied by
OCC
Hi Huang,
On Tue, May 02, 2017 at 01:35:24PM +0800, Huang, Ying wrote:
> Hi, Minchan,
>
> Minchan Kim writes:
>
> > On Fri, Apr 28, 2017 at 09:35:37PM +0800, Huang, Ying wrote:
> >> In fact, during the test, I found the overhead of sort() is comparable
> >> with the performance difference of ad
Le 01/05/2017 à 23:46, Brian Norris a écrit :
On Fri, Feb 10, 2017 at 03:01:10PM +0100, Christophe Leroy wrote:
On some hardware, the nCE signal is wired to the ChipSelect associated
to bus address of the NAND, so it is automatically driven during the
memory access and it is not managed by a G
The adt7475 has had find_nearest() since it's creation in 2009. Since
then find_closest() has been introduced and several drivers have been
updated to use it. Update the adt7475 to use find_closest() and remove
the now unused find_nearest().
Signed-off-by: Chris Packham
---
drivers/hwmon/adt7475
By default adt7475 will stop the fans (pwm duty cycle 0%) when the
temperature drops past Tmin - hysteresis. Some systems want to keep the
fans moving even when the temperature drops so add new sysfs attributes
that configure the enhanced acoustics min 1-3 which allows the fans to
run at the minimu
When enabled temperature smoothing allows ramping the fan speed over a
configurable period of time instead of jumping to the new speed
instantaneously.
Signed-off-by: Chris Packham
---
Documentation/hwmon/adt7475 | 5 ++
drivers/hwmon/adt7475.c | 121 +++
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
drivers/nvdimm/pmem.c
between commit:
71389703839e ("mm, zone_device: Replace {get, put}_zone_device_page() with a
single reference to fix pmem crash")
from the tip tree and commit:
c1d6e828a35d ("pmem: add dax_oper
Hi, Minchan,
Minchan Kim writes:
> On Fri, Apr 28, 2017 at 09:35:37PM +0800, Huang, Ying wrote:
>> In fact, during the test, I found the overhead of sort() is comparable
>> with the performance difference of adding likely()/unlikely() to the
>> "if" in the function.
>
> Huang,
>
> This discussio
> On Apr 10, 2017, at 3:46 PM, Christopher Bostic
> wrote:
>
> From: Jeremy Kerr
>
> This change introduces the fsi device API: simple read, write and peek
> accessors for the devices' address spaces.
>
> Includes contributions from Chris Bostic
> and Edward A. James .
>
> Signed-off-by: Ed
On Thu, Apr 27, 2017 at 04:46:22PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> On (04/27/17 15:57), Joonsoo Kim wrote:
> [..]
> > I tested with your benchmark and found that contention happens
> > since the data page is perfectly the same. All the written data (2GB)
> > is de-duplicated.
>
> ye
On 04/28/2017 10:53 AM, Amir Goldstein wrote:
On Fri, Apr 28, 2017 at 1:03 AM, Richard Weinberger wrote:
Am 24.04.2017 um 17:47 schrieb Richard Weinberger:
So, if some flag should be implemented, who should do it? :)
I'll not do it for you. ;)
Please also see http://marc.info/?l=linux-fsde
On Mon, 2017-05-01 at 13:40 -0500, Mike Christie wrote:
> On 04/30/2017 06:29 AM, Xiubo Li wrote:
> > [...]
> >> To avoid starvation, I think you want a second list/fifo that holds the
> >> watiers. In tcmu_get_empty_block if the list is not empty, record how
> >> many pages we needed and then a
Hi Xiubo & Co,
On Wed, 2017-04-26 at 14:25 +0800, lixi...@cmss.chinamobile.com wrote:
> From: Xiubo Li
>
> Changed for V6:
> - Remove the tcmu_vma_close(). Since the unmap thread will do the same for it
> - The unmap thread will skip the busy devices.
> - Using and testing the V5 version 3 week
Oops, forgot to add lkml and linux-mm.
Sorry for that.
Send it again.
>From 8ddf1c8aa15baf085bc6e8c62ce705459d57ea4c Mon Sep 17 00:00:00 2001
From: Minchan Kim
Date: Tue, 2 May 2017 12:34:05 +0900
Subject: [PATCH] vmscan: scan pages until it founds eligible pages
On Tue, May 02, 2017 at 01:40:38
On 05/01/2017 09:35 PM, Shilpasri G Bhat wrote:
Hi Guenter,
On 04/28/2017 06:59 PM, Guenter Roeck wrote:
On 04/27/2017 10:59 PM, Shilpasri G Bhat wrote:
Add support for adding min/max values for the inband sensors copied by
OCC to main memory. And also add current(mA) sensors to the list.
Sig
On Fri, Apr 28, 2017 at 09:35:37PM +0800, Huang, Ying wrote:
> In fact, during the test, I found the overhead of sort() is comparable
> with the performance difference of adding likely()/unlikely() to the
> "if" in the function.
Huang,
This discussion is started from your optimization code:
On Monday 01 May 2017 10:50 AM, Keerthy wrote:
>
>
> On Thursday 27 April 2017 09:50 PM, Eduardo Valentin wrote:
>> On Wed, Apr 26, 2017 at 05:33:10PM +0200, SF Markus Elfring wrote:
>>> From: Markus Elfring
>>> Date: Wed, 26 Apr 2017 17:24:56 +0200
>>>
>>> Three update suggestions were taken
Hi Guenter,
On 04/28/2017 06:59 PM, Guenter Roeck wrote:
> On 04/27/2017 10:59 PM, Shilpasri G Bhat wrote:
>> Add support for adding min/max values for the inband sensors copied by
>> OCC to main memory. And also add current(mA) sensors to the list.
>>
>> Signed-off-by: Shilpasri G Bhat
>> ---
>>
Howdy,
Well, sadly, the problem is more or less back is 4.11.0. The system doesn't
really
crash but it goes into an infinite loop with
[34776.826800] BUG: workqueue lockup - pool cpus=6 node=0 flags=0x0 nice=0
stuck for 33s!
More logs: https://pastebin.com/YqE4riw0
(I upgraded from 4.8 with cu
On Mon, May 1, 2017 at 5:40 PM, Greg KH wrote:
> On Mon, May 01, 2017 at 04:19:48PM +0530, Adheer Chandravanshi wrote:
>> Fix style issues as reported by checkpatch.pl
>
> That's really vague, you need to be specific, and only fix one type of
> thing per patch.
>
> thanks,
>
> greg k-h
Thanks for
On Mon, May 01, 2017 at 09:11:05PM -0700, Linus Torvalds wrote:
> On Mon, May 1, 2017 at 9:02 PM, Paul E. McKenney
> wrote:
> >
> > I will get rid of the unused rcu_segcblist_extract_all() function
> > and create a kernel/rcu/segcblist.c for the functions that are either
> > non-trivial or perform
Hello Rui,
Please pull the following changes to get the Thermal SoC updates
for 4.12-rc1. Here we have:
- Removal of non-DT booting on TI-SoC driver. Also, support to
fetching coefficients from DT.
- Refactoring of RCAR Gen3.
- New driver: support for BCM 2835.
- New driver: support for Broadcom N
On Mon, May 1, 2017 at 9:02 PM, Paul E. McKenney
wrote:
>
> I will get rid of the unused rcu_segcblist_extract_all() function
> and create a kernel/rcu/segcblist.c for the functions that are either
> non-trivial or performance-insensitive.
>
> Does that cover it, or am I missing something?
That's
Hi all,
Today's linux-next merge of the drivers-x86 tree got a conflict in:
drivers/watchdog/iTCO_wdt.c
between commit:
38a700fa1df9 ("watchdog: iTCO_wdt: cleanup set/unset no_reboot_bit functions")
(which also appears in the drivers-x86 tree as commit f583a884afec)
from the watchdog tree
Add null check before dereferencing dev->regs pointer inside
net2280_led_shutdown() function.
Addresses-Coverity-ID: 101783
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/udc/net2280.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/gadget/udc/n
On Thu, Apr 27, 2017 at 05:06:36PM +0200, Michal Hocko wrote:
> On Tue 25-04-17 12:42:57, Joonsoo Kim wrote:
> > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote:
> > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote:
> > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote:
> >
On Mon, May 01, 2017 at 06:19:44PM -0700, Linus Torvalds wrote:
> On Mon, May 1, 2017 at 2:59 AM, Ingo Molnar wrote:
> > Linus,
> >
> > Please pull the latest core-rcu-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > core-rcu-for-linus
>
> I pulle
On Wednesday 26 April 2017 09:04 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 26 Apr 2017 16:45:25 +0200
>
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function
On Wednesday 26 April 2017 09:07 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 26 Apr 2017 17:03:07 +0200
>
> The script "checkpatch.pl" pointed information out like the following.
>
> WARNING: Possible unnecessary 'out of memory' message
>
> Thus remove such statements her
On Wednesday 26 April 2017 09:09 PM, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 26 Apr 2017 17:11:28 +0200
>
> Add a missing character in this description for a function.
Reviewed-by: Keerthy
>
> Signed-off-by: Markus Elfring
> ---
> drivers/thermal/ti-soc-thermal/ti-ban
Since commit 23688bf4f830 ("block: ensure to split after potentially
bouncing a bio") blk_queue_bounce() is called *before*
blk_queue_split().
This means that:
1/ the comments blk_queue_split() about bounce buffers are
irrelevant, and
2/ a very large bio (more than BIO_MAX_PAGES) will no long
This function allocates a bio, then a collection
of pages. It copes with failure.
It currently uses a mempool() to allocate the bio,
but alloc_page() to allocate the pages. These fail
in different ways, so the usage is inconsistent.
Change the bio_clone() to bio_clone_kmalloc()
so that no pool
bio_clone() is no longer used.
Only bio_clone_bioset() or bio_clone_fast().
This is for the best, as bio_clone() used fs_bio_set,
and filesystems are unlikely to want to use bio_clone().
So remove bio_clone() and all references.
This includes a fix to some incorrect documentation.
Reviewed-by: Ch
blk_bio_segment_split() makes sure bios have no more than
BIO_MAX_PAGES entries in the bi_io_vec.
This was done because bio_clone_bioset() (when given a
mempool bioset) could not handle larger io_vecs.
No driver uses bio_clone_bioset() any more, they all
use bio_clone_fast() if anything, and bio_c
This patch converts bioset_create() and
bioset_create_nobvec() to not create a workqueue so
alloctions will never trigger punt_bios_to_rescuer(). It
also introduces bioset_create_rescued() and
bioset_create_nobvec_rescued() which preserve the old
behaviour.
All callers of bioset_create() and bios
bios that are re-submitted will pass through blk_queue_split() when
blk_queue_bio() is called, and this will split the bio if necessary.
There is no longer any need to do this splitting in xen-blkfront.
Acked-by: Roger Pau Monné
Signed-off-by: NeilBrown
---
drivers/block/xen-blkfront.c | 54 +
bio_clone() makes a copy of the bi_io_vec, but rbd never changes that,
so there is no need for a copy.
bio_clone_fast() can be used instead, which avoids making the copy.
This requires that we provide a bio_set. bio_clone() uses fs_bio_set,
but it isn't, in general, safe to use the same bio_set a
A rescuing bioset is only useful if there might be bios from
that same bioset on the bio_list_on_stack queue at a time
when bio_alloc_bioset() is called. This never applies to
q->bio_split.
Allocations from q->bio_split are only ever made from
blk_queue_split() which is only ever called early in
"flags" arguments are often seen as good API design as they allow
easy extensibility.
bioset_create_nobvec() is implemented internally as a variation in
flags passed to __bioset_create().
To support future extension, make the internal structure part of the
API.
i.e. add a 'flags' argument to biose
drbd does not modify the bi_io_vec of the cloned bio,
so there is no need to clone that part. So bio_clone_fast()
is the better choice.
For bio_clone_fast() we need to specify a bio_set.
We could use fs_bio_set, which bio_clone() uses, or
drbd_md_io_bio_set, which drbd uses for metadata, but it is
pktcdvd doesn't change the bi_io_vec of the clone bio,
so it is more efficient to use bio_clone_fast(), and not clone
the bi_io_vec.
This requires providing a bio_set, and it is safest to
provide a dedicated bio_set rather than sharing
fs_bio_set, which filesytems use.
This new bio_set, pkt_bio_set
pblk_submit_read() uses bio_clone_bioset() but doesn't change the
io_vec, so bio_clone_fast() is a better choice.
It also uses fs_bio_set which is intended for filesystems. Using it
in a device driver can deadlock.
So allocate a new bioset, and and use bio_clone_fast().
Signed-off-by: NeilBrown
This is a revision of my series of patches working
towards removing the bioset work queues.
This set is based on Linus' tree as for today (2nd May) plus
the for-linus branch from Shaohua's md/raid tree.
This series adds a fix for the new lightnvm/pblk-read code
and discards bioset_create_nobvec()
blk_queue_split() is always called with the last arg being q->bio_split,
where 'q' is the first arg.
Also blk_queue_split() sometimes uses the passed-in 'bs' and sometimes uses
q->bio_split.
This is inconsistent and unnecessary. Remove the last arg and always use
q->bio_split inside blk_queue_sp
On Tuesday 18 April 2017 11:48 AM, Keerthy wrote:
>
>
> On Tuesday 18 April 2017 11:45 AM, Ravikumar wrote:
>>
>>
>> On Tuesday 18 April 2017 09:59 AM, Keerthy wrote:
>>> orderly_poweroff is triggered when a graceful shutdown
>>> of system is desired. This may be used in many critical states of
On Tuesday 18 April 2017 09:59 AM, Keerthy wrote:
> thermal_zone_device_check --> thermal_zone_device_update -->
> handle_thermal_trip --> handle_critical_trips --> orderly_poweroff
>
> The above sequence happens every 250/500 mS based on the configuration.
> The orderly_poweroff function is get
From: Xiubo Li
Currently for the TCMU, the ring buffer size is fixed to 64K cmd
area + 1M data area, and this will be bottlenecks for high iops.
The struct tcmu_cmd_entry {} size is fixed about 112 bytes with
iovec[N] & N <= 4, and the size of struct iovec is about 16 bytes.
If N == 0, the rati
From: Xiubo Li
For each target there will be one ring, when the target number
grows larger and larger, it could eventually runs out of the
system memories.
In this patch for each target ring, currently for the cmd area
the size will be fixed to 8MB and for the data area the size
will grow from 0
From: Xiubo Li
Changed for V7:
- #1 fix two issues.
- #2 fix kbuild warning and some issues.
Changed for V6:
- Remove the tcmu_vma_close(). Since the unmap thread will do the same for it
- The unmap thread will skip the busy devices.
- Using and testing the V5 version 3 weeks and the V6 for abo
Hi Markus,
Apologies for the delayed follow-up here as well.
On Sun, 2017-04-09 at 21:43 +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 9 Apr 2017 21:33:21 +0200
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (5)
On Mon, May 01 2017, Jens Axboe wrote:
> On 04/30/2017 11:00 PM, NeilBrown wrote:
>> On Mon, Apr 24 2017, Christoph Hellwig wrote:
>>
>>> On Mon, Apr 24, 2017 at 11:51:01AM +1000, NeilBrown wrote:
I was following the existing practice exemplified by
bioset_create_nobvec().
>>>
>>>
Hi all,
After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/nvdimm/pmem.c: In function 'pmem_freeze_queue':
drivers/nvdimm/pmem.c:237:2: error: implicit declaration of function
'blk_mq_freeze_queue_start' [-Werror=implicit-function-declaration]
On Mon, May 01, 2017 at 11:21:52PM +, Linux Kernel wrote:
> Web:
> https://git.kernel.org/torvalds/c/e7ea7c9806a2681807257ea89085339d33f7fa0b
> Commit: e7ea7c9806a2681807257ea89085339d33f7fa0b
> Parent: 4495c08e84729385774601b5146d51d9e5849f81
> Refname:refs/heads/maste
On Sun, Apr 30, 2017 at 7:32 PM, Jonathan Cameron wrote:
> On 29/04/17 08:49, Eva Rachel Retuya wrote:
>> The ADXL345 provides a DATA_READY interrupt function to signal
>> availability of new data. This interrupt function is latched and can be
>> cleared by reading the data registers. The polarity
Hi Dave,
On Tue, 2 May 2017 12:36:35 +1000 Dave Airlie wrote:
>
> We've had register header files like this on a number of occasions
> before, not sure why it warrants a mention now.
Linus expressed suprise once before when we had a large number of new
lines appear in another subsystem ...
> It
hns_get_sset_count() returns HNS_NET_STATS_CNT and the data space allocated
is not enough for ethtool_get_strings(), which will cause random memory
corruption.
When SLAB and DEBUG_SLAB are both enabled, memory corruptions like the
the following can be observed without this patch:
[ 43.115200] Sl
From: Frank Rowand
Remove "phandle", "linux,phandle", and "ibm,phandle" properties from
the internal device tree. The phandle will still be in the struct
device_node phandle field.
This is to resolve the issue found by Stephen Boyd [1] when he changed
the type of struct property.value from void
From: Frank Rowand
Overlays are not allowed to modify phandle values of previously existing
nodes because there is no information available to allow fixup up
properties that use the previously existing phandle.
Signed-off-by: Frank Rowand
---
drivers/of/overlay.c | 4
1 file changed, 4 in
From: Frank Rowand
checkpatch whined about using S_IRUGO instead of octal equivalent
when adding phandle sysfs code, so used octal in that patch.
Change other instances of the S_* constants in the same file to
the octal form.
Signed-off-by: Frank Rowand
---
drivers/of/base.c | 2 +-
1 file cha
From: Frank Rowand
__of_attach_node() is not used outside of drivers/of/dynamic.c. Make
it static and remove it from drivers/of/of_private.h.
Signed-off-by: Frank Rowand
---
drivers/of/dynamic.c| 2 +-
drivers/of/of_private.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --
From: Frank Rowand
Remove "phandle" and "linux,phandle" properties from the internal
device tree. The phandle will still be in the struct device_node
phandle field.
This is to resolve the issue found by Stephen Boyd [1] when he changed
the type of struct property.value from void * to const void
On 4/26/17 9:15 AM, Andrey Konovalov wrote:
> +David
>
> I've enabled CONFIG_DEBUG_OBJECTS_RCU_HEAD and this is what I get.
>
> Apparently the rcu warning is related to the fib6_del_route bug I've
> been trying to reproduce:
> https://groups.google.com/forum/#!msg/syzkaller/3SS80JbVPKA/2tfIAcW7Dw
On 04/27/2017 07:42 PM, Kees Cook wrote:
> On Thu, Apr 27, 2017 at 3:17 PM, Tyler Hicks wrote:
>> Quick update... I finished the move from the high-water mark
>> log_max_action sysctl to the bitmask based actions_logged sysctl.
>
> Awesome!
>
>> Unfortunately, I've just realized that SECCOMP_SET
On 5/1/2017 9:54 PM, Lukas Wunner wrote:
> (b) ASPM L1 enabled on boot, but disabled after powering off and back on
> => I believe Sinan is working on this (+cc).
The decision was made not to touch ASPM registers following hotplug insertion
unless pcie_aspm.policy=powersave is specified.
The
On 2 May 2017 at 11:31, Stephen Rothwell wrote:
> Hi Linus,
>
> Just so you don't get a large suprise:
>
> $ git diff --dirstat v4.11..next-20170501
>3.9% arch/
> 13.5% drivers/gpu/drm/amd/include/asic_reg/vega10/DC/
>6.0% drivers/gpu/drm/amd/include
Hi, Peter,
Peter Zijlstra writes:
> On Tue, Mar 07, 2017 at 11:18:36AM +0800, kernel test robot wrote:
>> Greeting,
>>
>> FYI, we noticed a -14.4% regression of hackbench.throughput due to commit:
>
> Yeah, I know ... this patch is a mixed bag, some like it, some hate it.
>
> But given it was f
Hi Greg K-H,
On 2017-04-25 19:36, Greg Kroah-Hartman wrote:
On Tue, Apr 25, 2017 at 04:43:33PM +0800, we...@codeaurora.org wrote:
Hi Greg K-H,
On 2017-04-24 16:46, Greg Kroah-Hartman wrote:
> And does it really reduce boot time? What are the numbers?
Yes, it really reduce boot time. After m
On 2 May 2017 at 11:22, Dmitry Torokhov wrote:
> On May 1, 2017 6:14:54 PM PDT, Ed Bordin wrote:
>>On 2 May 2017 at 07:35, Greg Kroah-Hartman
>>wrote:
>>> 4.10-stable review patch. If anyone has any objections, please let
>>me know.
>>
>>Minor query (that I probably should have raised earlier):
On Tue, May 2, 2017 at 6:45 AM, Eduardo Molinas wrote:
> If the driver is built as a module, it won't be autloaded if the devices
> are registered via PLATFORM code because the PLATFORM device table
> entries are not exported as aliases
>
> Before the patch:
> $ modinfo drivers/iio/adc/sun4i-gpadc
SNIP
~
$ perf report --stdio --inline --no-children
Failed to open [ext4], continuing without symbols
# To display the perf.data header info, please use --header/--header-only
options.
#
#
# Total Lost Samples: 0
#
# Samples: 499 of event 'cycles'
# Event count (approx.): 329354953
#
# Ove
On Tue, May 2, 2017 at 6:45 AM, Eduardo Molinas wrote:
> If the driver is built as a module, it won't be autloaded if the devices
> are registered via OF code because the OF device table
> entries are not exported as aliases
>
> Before the patch:
> $ modinfo drivers/iio/adc/sun4i-gpadc-iio.ko | gr
On Mon, May 1, 2017 at 3:47 PM, Matthias Kaehlcke wrote:
> The constraint "rm" allows the compiler to put mix_const into memory.
> When the input operand is a memory location mul needs an operand size
> suffix, since it can't infer the multiplication width from the operand.
>
> Add and use the _AS
This patch adds an entry in f2fs/status to show # of available nids.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/debug.c | 5 +++--
fs/f2fs/f2fs.h | 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c
index 6102737473d4..87f449845f5f 100644
--- a/f
This patch flushes dirty nats in order to acquire available nids by writing
checkpoint. Otherwise, we can have no chance to get freed nids.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
i
Hi Ashok,
sorry for the delay, I was swamped with work in the first quarter and am
in the process of slowly going through my backlog...
On Thu, Feb 09, 2017 at 10:46:13AM -0800, Raj, Ashok wrote:
> I did a lspci and captured after a fresh reboot on the slot before
> attempting a power off via s
ping
anyone has any objections.
On 2017/4/27 19:49, zhongjiang wrote:
> From: zhong jiang
>
> Recently, I found the following issue, it will result in the panic.
>
> [ 168.739152] mmap1: Corrupted page table at address 7f3e6275a002
> [ 168.745039] PGD 61f4a1067
> [ 168.745040] PUD 61ab190
On May 1, 2017, at 7:37 PM, Stephen Rothwell wrote:
>
> Hi Jens,
>
>> On Mon, 1 May 2017 19:09:34 -0600 Jens Axboe wrote:
>>
>> Indeed, I have warned Linus about it. Thanks Stephen.
>
> Thanks.
>
> BTW, (unusually) I did not see your pull request(s) ...
I CC'ed linux-block, so they showed
1 - 100 of 636 matches
Mail list logo
