alpha:allmodconfig fails to build as follows.
drivers/gpu/drm/amd/amdgpu/amdgpu.h:1006:2: error:
expected identifier before '(' token
drivers/gpu/drm/amd/amdgpu/amdgpu.h:1011:28: error:
'NGG_BUF_MAX' undeclared here
The problem is not really the enum definition of NGG_BUF_MAX but
On 05/03/2017 11:29 PM, Dmitry Torokhov wrote:
Before trying to properly initialize the touchpad and generate bunch of
errors, let's first see it there is anything at the given address. If we
get error, fail silently with -ENXIO.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/elan_i2c_
Hi,
> Things still work, but when it starts warning, it generates a *lot*
> of noise (I got 36 of these within about ten minutes).
Yeah, that's kinda dumb - I just sent a patch to make that just warn
once and actually report the configuration.
> I have no idea what triggered it, because when I r
On 3 May 2017 at 22:47, Goel, Sameer wrote:
>
>
> On 5/3/2017 2:18 PM, Leif Lindholm wrote:
>> On Wed, May 03, 2017 at 11:07:45AM -0600, Goel, Sameer wrote:
>>> On 5/3/2017 5:26 AM, Will Deacon wrote:
[adding some /dev/mem fans to cc]
On Tue, May 02, 2017 at 02:28:05PM -0600, Sameer
On 03/05/17 22:20, Boris Ostrovsky wrote:
> Routines that are set by xen_init_time_ops() use shared_info's
> pvclock_vcpu_time_info area. This area is not properly available until
> shared_info is mapped in xen_setup_shared_info().
>
> This became especially problematic due to commit dd759d93f4dd
If the driver is built as a module, autoload won't work because the module
alias information is not filled. So user-space can't match the registered
device with the corresponding module.
Export the OF and I2C device ID table entries as module aliases, using the
MODULE_DEVICE_TABLE() macro.
Before
Before trying to properly initialize the touchpad and generate bunch of
errors, let's first see it there is anything at the given address. If we
get error, fail silently with -ENXIO.
Signed-off-by: Dmitry Torokhov
---
drivers/input/mouse/elan_i2c_core.c | 9 +
1 file changed, 9 insertion
On Wed, 3 May 2017, Joe Perches wrote:
> (adding Julia Lawall and cocci)
>
> On Wed, 2017-05-03 at 13:38 -0700, Matthew Wilcox wrote:
> > On Wed, May 03, 2017 at 11:26:38AM -0700, Joe Perches wrote:
> > > On Wed, 2017-05-03 at 14:13 -0400, Jeff Layton wrote:
> > > > On Wed, 2017-05-03 at 17:04 +
Masahiro Yamada writes:
> Hi Robert,
>
> 2017-04-26 5:07 GMT+09:00 Robert Jarzmik :
>> Masahiro Yamada writes:
>>
>>> Hi Robert,
diff --git a/scripts/tags.sh b/scripts/tags.sh
index a2ff3388e5ea..35cb64d5211c 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -106,7 +
Otherwise other compilers, like Clang, are prevented from compiling the
kernel. This flag was introduced in
3f135e57a4f76d24ae8d8a490314331f0ced40c5.
Signed-off-by: Nick Desaulniers
---
arch/x86/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/Makefile b/arch
On Thu, May 04, 2017 at 07:51:29AM +0200, Peter Zijlstra wrote:
> Urgh, and my numbers were so pretty :/
Just to clarify on how to run schbench, I limited to a single socket (as
that is what you have) and set -t to the number of cores in the socket
(not the number of threads).
Furthermore, my ma
From: Matt Ranostay
Add entries for microwatt-hours and microamp-hours.
Cc: Rob Herring
Cc: Mark Rutland
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Matt Ranostay
Signed-off-by: Liam Breck
Acked-by: Sebastian Reichel
Acked-by: Rob Herring
---
Documentati
On 04/07/2017 02:38 AM, Joonsoo Kim wrote:
> On Wed, Mar 29, 2017 at 06:06:41PM +0200, Vlastimil Babka wrote:
>> On 03/16/2017 03:14 AM, Joonsoo Kim wrote:
>>> On Tue, Mar 07, 2017 at 02:15:44PM +0100, Vlastimil Babka wrote:
The migrate scanner in async compaction is currently limited to
On Thu, 2017-05-04 at 07:35 +0300, Kalle Valo wrote:
> Linus Torvalds writes:
>
> > So my Dell XPS 13 seems to have grown a new warning as of the
> > networking merge yesterday.
> >
> > Things still work, but when it starts warning, it generates a *lot* of
> > noise (I got 36 of these within abo
On Wed, May 3, 2017 at 7:43 PM, Linux Kernel Mailing List
wrote:
> Web:
> https://git.kernel.org/torvalds/c/7eada909bfd7ac90a4522e56aa3179d1fd68cd14
> Commit: 7eada909bfd7ac90a4522e56aa3179d1fd68cd14
> Parent: 400a0befc96240f7bb2a53b9622deffd55d385fe
> Refname:refs/heads/master
On Wed, May 03, 2017 at 05:45:46PM -0400, Tejun Heo wrote:
> FUDGE2: Changes things a lot (load values go wild) but only because
> it's missing scale_load_down(). After adding
> scale_load_down(), it doesn't do much. For this to work, it
> needs to be always propagated, w
On Wed 03 May 02:55 PDT 2017, Jassi Brar wrote:
> Loic, thanks for adding me.
>
> On Wed, May 3, 2017 at 2:58 PM, Loic PALLARDY wrote:
> >
> >
> >> -Original Message-
> >> From: linux-remoteproc-ow...@vger.kernel.org [mailto:linux-remoteproc-
> >> ow...@vger.kernel.org] On Behalf Of Bjor
On Wed, May 3, 2017 at 6:17 PM, Eric Anholt wrote:
> Laurent Pinchart writes:
>
>> Hi Daniel,
>>
>> On Wednesday 03 May 2017 16:28:56 Daniel Vetter wrote:
>>> On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote:
>>> > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote:
>>> >> On W
On Wed, May 03, 2017 at 04:21:01PM -0700, Linus Torvalds wrote:
> This is from last merge window, and the reason I react now is that
> nobody noticed or cared until we had a release..
>
> On Mon, Feb 27, 2017 at 11:57 PM, Ingo Molnar wrote:
> >
> > Peter Zijlstra (1):
> > locking/refcounts:
There are Device Tree source files defining a device node for the
tps61050/61052 I2C chip but there isn't a binding document for it.
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Tony Lindgren
---
Changes in v6: None
Changes in v5:
- Add Rob Herring's Acked-by tag.
-
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
The tps61052 device node doesn't have a vendor prefix
in its compatible string, fix it by adding one.
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Tony Lindgren
---
Changes in v6: None
Changes in v5:
- Add Rob Herring's Acked-by tag.
- Add Acked-by: Tony Lindgren 's
There are Device Tree source files defining a device node for the
retu/tahvo I2C chip, but there isn't a DT binding document for it.
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Aaro Koskinen
Acked-by: Tony Lindgren
Acked-by: Lee Jones
---
Changes in v6:
- Mention
The example contains a device node for a retu device, but
its compatible string doesn't have a vendor prefix.
While being there, drop the -mfd suffix since isn't correct.
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Aaro Koskinen
Acked-by: Tony Lindgren
Reviewed-by:
The retu device node doesn't have a vendor prefix
in its compatible string, fix it by adding one.
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Aaro Koskinen
Acked-by: Tony Lindgren
Reviewed-by: Wolfram Sang
---
Changes in v6:
- Add Wolfram Sang's Reviewed-by tag.
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
It's not correct to encode the subsystem in the I2C device name, so
drop the -mfd suffix. To maintain bisect-ability, change driver and
platform code / DTS users in the same patch.
Suggested-by: Lee Jones
Signed-off-by: Javier Martinez Canillas
Acked-by: Rob Herring
Acked-by: Aaro Koskinen
Ack
Hello,
This series add OF device ID tables to mfd I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a MODALIA
Avoid stuck and hacking jiffies for a long time and using msleep()
for certatin numeber of cylces without the factor of safety
but using the the long delay considering the factor of safety
with the while loop such that after msleep for a short period
of time we check the msg if it's OK, breaking t
On 05/03, Paul E. McKenney wrote:
>On Thu, May 04, 2017 at 10:59:26AM +0800, kernel test robot wrote:
>>
>> FYI, we noticed the following commit:
>>
>> commit: 87c458e6304c6a1b37bf856e88c70fc37f08851f ("rcuperf: Set more
>> user-friendly defaults")
>> https://git.kernel.org/cgit/linux/kernel/git
On Wed, May 03, 2017 at 01:19:41PM -0700, Kees Cook wrote:
> On Wed, May 3, 2017 at 1:02 PM, Matt Brown wrote:
> > On 05/03/2017 03:45 PM, Greg KH wrote:
> >>
> >> On Wed, May 03, 2017 at 12:32:07PM -0700, Kees Cook wrote:
> >>>
> >>> On Mon, Apr 24, 2017 at 6:57 AM, Serge E. Hallyn
> >>> wrote:
On Tue, 2 May 2017, at 08:42 AM, Dave Jones wrote:
> On Mon, May 01, 2017 at 11:21:52PM +, Linux Kernel wrote:
> > Web:
> https://git.kernel.org/torvalds/c/e7ea7c9806a2681807257ea89085339d33f7fa0b
> > Commit: e7ea7c9806a2681807257ea89085339d33f7fa0b
> > Parent: 4495c08e847293
The Samsung email address will stop working soon, so use my personal
email address instead.
Also, there used to be a MFD and RTC drivers for max77802 but now these
have been merged with the max77686 MFD and RTC drivers. The only driver
that's still max77802 specific is the regulator one since ther
Linus Torvalds writes:
> So my Dell XPS 13 seems to have grown a new warning as of the
> networking merge yesterday.
>
> Things still work, but when it starts warning, it generates a *lot* of
> noise (I got 36 of these within about ten minutes).
>
> I have no idea what triggered it, because when
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 20170503:
The f2fs tree gained a conflict against the fscrypt tree.
The spi-nor tree gained a build failure so I used the version from
next-20170503
On 5/3/17 9:55 PM, Cong Wang wrote:
> Why not add a printk and play with my patch to see the difference?
I have other things to do. If you believe your patch fixes the problem,
send it and let Andrey verify.
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The generic connectors such as hdmi-connector doesn't have any driver in,
> so if they are added to the component list, we will be waiting forever for
> a non-existing driver to probe.
>
> Add a list of the connectors we want to ignore when bu
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> It appears that the total vertical resolution needs to be doubled when
> we're not in interlaced. Make sure that is the case.
I think the total vertical resolution needs to be doubled in all cases.
It just happens that you should've been usin
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> Both TCON channels need to have the resolution doubled, since the size the
> hardware is going to use is whatever we put in the register divided by two.
>
> However, we handle it differently for the two channels: in the channel 0,
> our regist
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> Even though that mux is undocumented, it seems like it needs to be set to 1
> when using composite, and 0 when using HDMI.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Wed, May 3, 2017 at 7:43 PM, David Ahern wrote:
> On 5/3/17 5:35 PM, Cong Wang wrote:
>> Ah, we need:
>>
>> @@ -4024,7 +4027,7 @@ static struct pernet_operations ip6_route_net_late_ops
>> = {
>>
>> static struct notifier_block ip6_route_dev_notifier = {
>> .notifier_call = ip6_route_d
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The muxing can actually happen on both channels on some SoCs, so it makes
> more sense to just move it out of the sun4i_tcon1_mode_set function and
> create a separate function that needs to be called by the encoders.
>
> Let's do that and con
On Wed, May 3, 2017 at 8:40 AM, Olliver Schinagl wrote:
> Hey Tim,
>
> Ok, so as far as I understand (from the datasheet) the intended way to do
> this would be to check for the BUSY IRQ & USR[0] IRQ and if it is busy,
> (re-write) the LCR. We no longer do this because it did not work due to the
On Wed, May 03, 2017 at 10:19:55PM +0100, Ben Hutchings wrote:
> On Wed, 2017-05-03 at 21:00 +, alexander.le...@verizon.com wrote:
> > On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote:
> > > liblockdep hasn't been buildable since (I think) Linux 4.6. I sent
> > > Sasha fixes for t
On 05/03/2017 10:57 PM, Paolo Bonzini wrote:
On 03/05/2017 16:50, Xiao Guangrong wrote:
Furthermore, userspace has no knowledge about if PML is enable (it
can be required from sysfs, but it is a good way in QEMU), so it is
difficult for the usespace to know when to use write-protect-all.
May
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The video PLLs are used directly by the HDMI controller. Export them so
> that we can use them in our DT node.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> Currently, the parent rate given back to the clock framework in our
> request is the original parent rate we calculated before trying to round
> the rate of our clock.
>
> This works fine unless our clock also changes its parent rate, in which
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The current function name is a bit confusing, and doesn't really allow to
> create an explicit function to reverse the operation.
>
> We also for now change the parent rate through a pointer, while we don't
> return anything.
>
> In order to b
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The pre-divider retrieval code was merged into the function to apply the
> current pre-divider onto the parent clock rate so that we can use that
> adjusted value to do our factors computation.
>
> However, since we'll need to do the reverse o
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The current code only rely on the parent to change its rate in the case
> where CLK_SET_RATE_PARENT is set.
>
> However, some clock rates might be obtained only through a modification of
> the parent and the clock divider. Just rely on the rou
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> divider_round_rate already evaluates changing the parent rate if
^^^ Might want to update this, as you are now using the new function
you added in patch 1.
> CLK_SET_RATE_PARENT is set. Now that we can do that on muxes too, let's
> j
On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard
wrote:
> The clocks might need to modify their parent clocks. In order to make that
> possible, give them access to the parent clock being evaluated, and to a
> pointer to the parent rate so that they can modify it if needed.
>
> Signed-off-by: Maxime
On Thu, May 04, 2017 at 10:59:26AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: 87c458e6304c6a1b37bf856e88c70fc37f08851f ("rcuperf: Set more
> user-friendly defaults")
> https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git
> dev.2017.04.21a
Hi Chis, do you have any comments for this problem?
>> +static struct sg_table *
>> +intel_vgpu_create_sg_pages(struct drm_device *dev, u32 start, u32
>> +num_pages) {
>> +struct drm_i915_private *dev_priv = dev->dev_private;
>> +struct sg_table *st;
>> +struct scatterlist *sg;
>> +
Hi Alex, do you have any comments for this interface?
>-Original Message-
>From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
>Behalf Of Chen, Xiaoguang
>Sent: Wednesday, May 03, 2017 9:39 AM
>To: Gerd Hoffmann
>Cc: Tian, Kevin ; intel-...@lists.freedesktop.org; l
Hi,
On Thu, May 4, 2017 at 4:34 AM, Maxime Ripard
wrote:
> Hi,
>
> On Wed, May 03, 2017 at 11:16:53AM +0800, Chen-Yu Tsai wrote:
>> The MMC clocks on newer SoCs, such as the A83T and H3, support the
>> "new timing mode". Under this mode, the output of the clock is divided
>> by 2, and the clock d
FYI, we noticed the following commit:
commit: 87c458e6304c6a1b37bf856e88c70fc37f08851f ("rcuperf: Set more
user-friendly defaults")
https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git
dev.2017.04.21a
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu host -s
On 5/3/17 5:35 PM, Cong Wang wrote:
> Ah, we need:
>
> @@ -4024,7 +4027,7 @@ static struct pernet_operations ip6_route_net_late_ops
> = {
>
> static struct notifier_block ip6_route_dev_notifier = {
> .notifier_call = ip6_route_dev_notify,
> - .priority = 0,
> + .priority = -
FYI, we noticed the following commit:
commit: 9f0f3ea31419e56d861441b2d863e992d13f19d7 ("fw_cfg: do DMA read
operation")
url:
https://github.com/0day-ci/linux/commits/marcandre-lureau-redhat-com/fw_cfg-add-DMA-operations/20170429-202925
in testcase: boot
on test machine: qemu-system-x86_64 -
Hi all,
I am working on a platform, which is using the Linux version 4.4. I have
observed a DEADLOCK between couple of threads and looking for
suggestions/comments.
Here is my understanding from the call stacks of these blocked tasks.
0) CPU3 is getting hot plugged from a kthread and which is
It is assumed that the head of cache_groups always has valid RMID,
which isn't true.
When we deallocate RMID from conflicting events currently we don't
move them to the tail, and one of those events can happen to be in
the head. Another case is we allocate RMIDs for all the events except
the head
On Wed, May 3, 2017 at 7:25 PM, Baoquan He wrote:
> Jeff Moyer reported that on his system with two memory regions 0~64G and
> 1T~1T+192G, and kernel option "memmap=192G!1024G" added, enabling kaslr
> will make system hang intermittently during boot. While adding 'nokaslr'
> won't.
>
> This is bec
2017-05-03 8:58 GMT-06:00 Joerg Roedel :
> On Wed, May 03, 2017 at 08:35:47AM -0600, Alex Henrie wrote:
>> 2017-05-03 5:58 GMT-06:00 Greg KH :
>> > On Tue, May 02, 2017 at 10:55:09PM -0600, Alex Henrie wrote:
>> >> Today I ran a regression test to determine which commit made the
>> >> keyboard stop
On Wed, May 03, 2017 at 07:02:07PM -0700, Alexander Kappner wrote:
> Some buggy NVMe controllers support APST (autonomous power
> state transitions), but do not report APSTA=1. On these controllers, the NVMe
> driver does not enable APST support. I have verified this problem occurring
> on
>
On 2017/5/4 2:46, Rik van Riel wrote:
> On Tue, 2017-05-02 at 13:54 -0700, David Rientjes wrote:
>
>>> diff --git a/drivers/char/mem.c b/drivers/char/mem.c
>>> index 7e4a9d1..3a765e02 100644
>>> --- a/drivers/char/mem.c
>>> +++ b/drivers/char/mem.c
>>> @@ -55,7 +55,7 @@ static inline int
>> valid_p
So my Dell XPS 13 seems to have grown a new warning as of the
networking merge yesterday.
Things still work, but when it starts warning, it generates a *lot* of
noise (I got 36 of these within about ten minutes).
I have no idea what triggered it, because when I rebooted (not because
of this issue
On Wed, May 03, 2017 at 09:02:20PM +0200, Arend Van Spriel wrote:
> On 3-1-2017 18:59, Luis R. Rodriguez wrote:
> > On Mon, Dec 26, 2016 at 05:35:59PM +0100, Pavel Machek wrote:
> >>
> >> Right question is "should we solve it without user-space help"?
> >>
> >> Answer is no, too. Way too complex. Y
Jeff Moyer reported that on his system with two memory regions 0~64G and
1T~1T+192G, and kernel option "memmap=192G!1024G" added, enabling kaslr
will make system hang intermittently during boot. While adding 'nokaslr'
won't.
This is because the for loop count calculation in sync_global_pgds is
not
Some buggy NVMe controllers support APST (autonomous power
state transitions), but do not report APSTA=1. On these controllers, the NVMe
driver does not enable APST support. I have verified this problem occurring
on
- Samsung 960 Pro 2TB (Firmware 2B6QCXP7, current as of 5/4/17)
-
On Wed, 3 May 2017 18:59:05 -0700
Linus Torvalds wrote:
> On Tue, May 2, 2017 at 4:41 PM, Steven Rostedt wrote:
> >
> > This will conflict with changes I have already sent to you. They may
> > not be so trivial to fix. I merged my urgent branch when pushing to
> > linux-next. You can look at
On Wed, May 3, 2017 at 4:36 PM, Kani, Toshimitsu wrote:
> On Wed, 2017-05-03 at 17:25 -0600, Toshi Kani wrote:
>> On Wed, 2017-05-03 at 16:08 -0700, Dan Williams wrote:
>> > On Wed, May 3, 2017 at 3:51 PM, Dan Williams > > co
>> > m> wrote:
>> > > On Wed, May 3, 2017 at 3:41 PM, Kani, Toshimitsu >
On Tue, May 2, 2017 at 4:41 PM, Steven Rostedt wrote:
>
> This will conflict with changes I have already sent to you. They may
> not be so trivial to fix. I merged my urgent branch when pushing to
> linux-next. You can look at how I resolved the conflicts in my
> "for-next" branch, specificall
Hi Guenter:
>> Change boot mode trigger parameter of Raydium firmware update.
>>
>That is a bit vague. What is changed to what, and why ?
>In other words, what prevents someone else from changing it back to
>the old value, using the same description ?
This bit control erase type as doing firmwar
Hi Jeffy,
On Thu, 4 May 2017 09:18:12 +0800 "Jeffy" wrote:
>
> it should be fixed by "Arnd Bergmann"(thanks a lot by the way)
> in:
>
> 4a85aae multi_v7_defconfig: make Rockchip DRM drivers built-in
Thanks for the heads up, I will await the arm-soc merges.
--
Cheers,
Stephen Rothwell
Kexec setups all identity mappings before booting into the new
kernel, and this will cause extra memory consumption for paging
structures which is quite considerable on modern machines with
huge number of memory.
E.g. On one 32TB machine, in kdump case, it could waste around
128MB (around 4MB/TB)
The current kernel_ident_mapping_init() creates the identity
mapping always using 2MB page(PMD level), this patch adds the
1GB page(PUD level) support.
The primary advantage would be better TLB coverage/performance,
because we'd utilize 1GB TLBs instead of 2MB ones.
It is also useful for machines
Use __print_flags in show_bio_op_flags and show_cpreason instead of
__print_symbolic, it enables tracer function traverses and shows all
bits in the flag.
Additionally, add missing REQ_FUA into F2FS_OP_FLAGS.
Signed-off-by: Chao Yu
---
v2:
update patch as Jaegeuk's suggestion.
- remove useless
Hi All,
This is regarding the usage of gic_write_grpen1 API usage in irq-gic-v3
driver.
Here my understanding about ICC_IGRPEN1_EL1.
ICC_IGRPEN1_EL1 is banked between secure and non-secure states. If two
secure states are implemented, Secure side Group bit is set by the
platform firmware (PS
On 04/05/17 04:30, Guenter Roeck wrote:
> On Wed, May 03, 2017 at 12:40:09PM +1200, Chris Packham wrote:
>> 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 Packha
On Wed, May 03 2017, Mikulas Patocka wrote:
> On Mon, 24 Apr 2017, NeilBrown wrote:
>>
>> I had a look at how the allocation 'dm_region' objects are used,
>> and it would take a bit of work to make it really safe.
>> My guess is __rh_find() should be allowed to fail, and the various
>> callers ne
> @@ -5527,7 +5527,7 @@ static void uncharge_list(struct list_head *page_list)
> next = page->lru.next;
>
> VM_BUG_ON_PAGE(PageLRU(page), page);
> - VM_BUG_ON_PAGE(page_count(page), page);
> + VM_BUG_ON_PAGE(!PageHWPoison(page) && page_count(pag
Hi Jaegeuk,
On 2017/5/4 2:47, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 05/03, Chao Yu wrote:
>> From: Chao Yu
>>
>> Use __print_flags in show_bio_op_flags and show_cpreason instead of
>> __print_symbolic, it enables tracer function traverses and shows all
>> bits in the flag.
>>
>> Additionally, add
Since commit 5399eb9b3908 ("dtbsinstall: don't move target directory
out of the way"), the target __dtbs_install_prep is invoked just for
creating the install directory, but all the necessary directories
are automatically created by:
cmd_dtb_install = mkdir -p $(2); cp $< $(2)
Signed-off-by: Ma
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: 901e798bdc9249ffd86a4d4cb002a6772660e41d
commit: e3f53ab9491c1c4b321bde579c906a630fab4da8 [57/76] rcu: Move docbook
comments out of rcupdate.h
reproduce: make htmldocs
All warnings (new ones prefixed by
);
^
drivers/mtd/spi-nor/stm32-quadspi.c:110:33: note: in definition of macro
'FSIZE_VAL'
#define FSIZE_VAL(size) (__fls(size) - 1)
^
Exposed by commit
7a754f2016a0 ("mtd: spi-nor: stm32-quadspi: allow building with COMPILE_TEST")
I have used the spi-nor tree from next-20170503 for today.
--
Cheers,
Stephen Rothwell
Linus,
Please pull below to receive a few minor modules updates for the 4.12 merge
window.
Thanks,
Jessica
---
The following changes since commit 4495c08e84729385774601b5146d51d9e5849f81:
Linux 4.11-rc2 (2017-03-12 14:47:08 -0700)
are available in the git repository at:
git://git.kernel.
On Wed, May 03, 2017 at 02:21:36PM -0600, Mathieu Poirier wrote:
> Hi Leo,
>
> On Tue, May 02, 2017 at 04:15:03PM +0800, Leo Yan wrote:
> > Almost low level functions from open firmware have used const to
> > qualify device_node structures, so add const for device_node
> > parameters in of_coresig
* Sebastian Reichel [170503 04:14]:
> Provide a simple driver for PWM controllable vibrators. It
> will be used by Motorola Droid 4.
>
> Signed-off-by: Sebastian Reichel
> ---
> Changes since PATCHv1:
> - move driver removal code to input->close function
> - mark PM functions __maybe_unused an
Almost low level functions from open firmware have used const to
qualify device_node structures, so add const for device_node
parameters in of_coresight related functions.
Reviewed-by: Stephen Boyd
Signed-off-by: Leo Yan
---
drivers/hwtracing/coresight/of_coresight.c | 7 ---
include/linux/
perf record -b -g
perf report --branch-history
This merges the LBRs with the callgraphs.
However it would be nice if it also works without callgraphs (-g)
set in perf record, so that only the LBRs are displayed.
But currently perf report errors in this case. For example,
perf record -b
perf re
+Cc: Greg KH
On Sun, Apr 30, 2017 at 2:36 PM, David Lin wrote:
> Hi,
>
> These patch series add the LED_BRIGHTNESS_FAST flag support for
> ledtrig-transient to use hrtimer so that platforms with high-resolution timer
> support can have better accuracy in the trigger duration timing. The need for
On Wed, 2017-05-03 at 22:30 +0100, Russell King - ARM Linux wrote:
> On Wed, May 03, 2017 at 12:44:11PM -0700, Joe Perches wrote:
> > On Wed, 2017-05-03 at 20:23 +0100, Russell King - ARM Linux wrote:
> > > On Wed, Apr 26, 2017 at 10:39:49AM -0700, Joe Perches wrote:
> > > > Multiple line formats a
We've encountered zombies that are waiting for a thread to exit that are
looping in ep_poll() almost endlessly although there is a pending SIGKILL
as a result of a group exit.
This happens because we always find ep_events_available() and fetch more
events and never are able to check for signal_pen
* Sebastian Reichel [170503 09:11]:
> Hi,
>
> On Wed, May 03, 2017 at 05:02:13PM +0200, Marcel Holtmann wrote:
> > >> Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This
> > >> fixes the DT file to use correct compatible for the wifi node
> > >> and adds the bluetooth node.
> > >>
>
This patch implements Direct Access (DAX) in F2FS, including:
- a mount option to enable DAX
- read/write and mmap of regular files in the DAX way
- zero-out of non-aligned partial blocks in the DAX way
- garbage collection of DAX files
- incompatibility of DAX with inline data, atomic or vola
Export interfaces of dax_map/unmap_atomic() for usage in moving data
pages of DAX files in garbage collection of F2FS.
Signed-off-by: Qiuyang Sun
---
fs/dax.c| 6 --
include/linux/dax.h | 3 +++
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
i
Currently in F2FS, page faults and fallocate operations, like punch_hole
and collapse/insert/zero_range, are completely unsynchronized. This can
result in page fault faulting in a page into a range that we are changing
after truncating pagecache, and thus we can end up with a page mapped to
dis
Initialize scalar variables _pid_ and _ver_ to avoid a possible misbehavior.
Addresses-Coverity-ID: 1324239
Addresses-Coverity-ID: 1324240
Signed-off-by: Gustavo A. R. Silva
---
drivers/media/i2c/ov2659.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/ov2
When a pinctrl driver gets interrupted during its probe process
(returning -EPROBE_DEFER), the devres system cleans up all allocated
resources. During this process it calls pinmux_generic_free_functions()
and pinctrl_generic_free_groups(), which in turn use managed kmalloc
calls for temporarily all
The Marvell Armada 3700 UART uses "ar3700_uart" for its earlycon name.
Adjust documentation to match the code.
Signed-off-by: Andre Przywara
---
Documentation/admin-guide/kernel-parameters.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/kernel-pa
1 - 100 of 696 matches
Mail list logo
