From: Peng Li
HNS3 Hardware can support up to two VLAN tags in transmit leg, the PPP
module can handle the packets based on the tag1 and tag2 config. This
patch adds support for tag2 config for vlan handling
Signed-off-by: Peng Li
Signed-off-by: Salil Mehta
---
.../net/ethernet/hisilicon/hns3
On 05/25/2018 01:27 PM, Steve deRosier wrote:
On Fri, May 25, 2018 at 11:23 AM Gustavo A. R. Silva
wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
Changes in v2:
- Place code co
Hi!
> > On 05/25/2018 12:08 AM, Tomas Hlavacek wrote:
> >> But I also have good news: The FW of the MCU is also OSS (see the repo
> >> in the link (1)). There is a method for flashing the MCU over I2C from
> >> Linux and there is JTAG connector for the MCU, in case un-bricking is
> >> needed. Ther
On Fri, 25 May 2018 09:27:09 -0600
Mathieu Poirier wrote:
> On 24 May 2018 at 17:30, Kim Phillips wrote:
> > On Thu, 24 May 2018 09:32:48 -0600
> > Mathieu Poirier wrote:
> >
> >> On 23 May 2018 at 13:51, Kim Phillips wrote:
> >> > On Tue, 22 May 2018 11:31:40 -0600
> >> > Mathieu Poirier wro
From: YueHaibing
Date: Thu, 24 May 2018 19:27:07 +0800
> This comment is outdated as fec_ptp_ioctl has been replaced by
> fec_ptp_set/fec_ptp_get
> since commit 1d5244d0e43b ("fec: Implement the SIOCGHWTSTAMP ioctl")
>
> Signed-off-by: YueHaibing
Applied, thank you.
Based on several conditions the kernel can decide to force charge an
allocation for a memcg i.e. overcharge memcg->memory and memcg->memsw
counters. Do the same for memcg->kmem counter too. In cgroup-v1, this
bug can cause a __GFP_NOFAIL kmem allocation fail if an explicit limit
on kmem counter is
On 05/16/2018 9:06 AM, Stuart Hayes wrote:
> If the WSMT ACPI table is present and indicates that a fixed communication
> buffer should be used, use the firmware-specified buffer instead of
> allocating a buffer in memory for communications between the dcdbas driver
> and firmare.
>
> Signed-off-
This commit documents the scheme used to generate the names for the
litmus tests.
Signed-off-by: Paul E. McKenney
---
README | 136 -
1 file changed, 135 insertions(+), 1 deletion(-)
diff --git a/tools/memory-model/litmus-tests/RE
The driver does not cope with the fact that probe can fail in a number
of cases after enabling pm_runtime on the device, this results in
warnings about "Unbalanced pm_runtime_enable". Further more if probe
fails after invoking host_init the power-domain will be left referenced.
As it's not possibl
On 25 May 2018 at 12:52, Kim Phillips wrote:
> On Fri, 25 May 2018 09:27:09 -0600
> Mathieu Poirier wrote:
>
>> On 24 May 2018 at 17:30, Kim Phillips wrote:
>> > On Thu, 24 May 2018 09:32:48 -0600
>> > Mathieu Poirier wrote:
>> >
>> >> On 23 May 2018 at 13:51, Kim Phillips wrote:
>> >> > On Tu
usuarios de webmail
Tenga en cuenta que el 95% de sus correos electrónicos recibidos después de
actualizar el servidor webmail recientemente en nuestra base de datos se han
suspendido. Reciba su mensaje regularmente. Nuestro personal técnico
actualizará su cuenta dentro de los tres días hábiles
Hi Arnd,
On Fri, May 25, 2018 at 6:10 PM, Arnd Bergmann wrote:
> The secure_cntvoff_init() function is not available without CONFIG_SMP,
> leading to a link error on shmobile:
>
> arch/arm/mach-shmobile/setup-rcar-gen2.o: In function `rcar_gen2_timer_init':
> setup-rcar-gen2.c:(.init.text+0x18):
The x86/mtrr code does horrific things because hardware. It uses
stop_machine_from_inactive_cpu(), which does a wakeup (of the stopper
thread on another CPU), which uses RCU, all before the CPU is onlined.
RCU complains about this, because wakeups use RCU and RCU does
(rightfully) not consider off
On Fri, 25 May 2018 12:18:02 -0700
"Paul E. McKenney" wrote:
> [ paulmck: Add !SMP support, per 0day Test Robot report. ]
Somehow I read this as:
[ paulmck: Add NR_CPUS=0 support ]
no idea why.
-- Steve
On Tue, May 22, 2018 at 5:08 AM Ulf Hansson wrote:
> First, I thought I preferred this option, as it becomes clear of what
> goes on. However I then realize, that it may not be worth it, because
> in the end I guess the caller (sdhci), will not be able to deal with
> error codes. For example, wha
On Fri, May 25, 2018 at 09:42:29AM -0600, Ross Zwisler wrote:
> On Thu, May 24, 2018 at 10:02:18PM -0700, Darrick J. Wong wrote:
> > On Thu, May 24, 2018 at 08:55:12PM -0600, Ross Zwisler wrote:
> > > From: "Darrick J. Wong"
> > >
> > > Remove __bdev_dax_supported and change to bdev_dax_supported
Hi Sudeep,
> -Original Message-
> From: Sudeep Holla [mailto:sudeep.ho...@arm.com]
> Sent: Tuesday, May 15, 2018 1:58 AM
> To: Jolly Shah ; ard.biesheu...@linaro.org;
> mi...@kernel.org; gre...@linuxfoundation.org; m...@codeblueprint.co.uk;
> hkallwe...@gmail.com; keesc...@chromium.org;
>
This change uses the appropriate _cansleep or non-sleeping API for
reading GPIO card detect state. This allows users with GPIOs that
never sleep to avoid a warning when certain quirks are present.
The sdhci controller has an SDHCI_QUIRK_NO_CARD_NO_RESET, which
indicates that a controller will not
The msm8996 PCIe sits behind the "agnoc0", which is represented as a
simple-pm-bus, so enable support for this. Then enable the QMP phy
driver.
Also enable the atl1c ethernet driver and ath10k wlan driver to support
these components on the DragonBoard820c.
Signed-off-by: Bjorn Andersson
---
arc
On Tue 22 May 12:57 PDT 2018, Niklas Cassel wrote:
> The property name vddpe-supply is not included in
> Documentation/devicetree/bindings/pci/qcom,pcie.txt
> nor in the pcie-qcom PCIe Root Complex driver.
>
> This property name was used in an initial patchset for pcie-qcom,
> but was renamed in
On Thu 24 May 11:01 PDT 2018, Thierry Escande wrote:
> This patch removes the unused bt-en-1-8v regulator and moves the
> bt_en_gios claim to the pm8994_gpios node.
>
> This bt_en_gpio could have been moved to the bluetooth serial node but
> instead this node declares an 'enable' gpio addressing
On Fri, 25 May 2018, Michal Hocko wrote:
> > The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if
> > it cannot reap an mm. This can happen for a variety of reasons,
> > including:
> >
> > - the inability to grab mm->mmap_sem in a sufficient amount of time,
> >
> > - when
This adds a new binding for Ilitek ILI9341 display panels. It includes
a compatible string for one display (more can be added in the future).
The vendor prefix "noname" is used because the vendor is not known.
The YX240QV29-T panel[1] is found, for example, in an Adafruit breakout
board[2] and in
This fixes the path to the ilitek,ili9225 device tree binding file.
Signed-off-by: David Lechner
Reviewed-by: Noralf Trønnes
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 334a00350922..bc219de9cbee 100644
--- a/MAINTAINERS
++
This adds a new driver for display panels that use the Ilitek ILI9341
controller. It currently supports a single display panel, namely
the YX240QV29-T (e.g. Adafruit 2.4" TFT).
The init sequence is from the Adafruit Python library for the ILI9341
controller. https://github.com/adafruit/Adafruit_Py
This adds a device tree vendor prefix for Adafruit Industries, LLC.
Signed-off-by: David Lechner
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/binding
This series adds a new tinydrm driver for the Ilitek ILI9341 controller and
a 2.4" display panel that uses this controller.
A few things to note here:
* The datasheet for this display[1] doesn't have a vendor mentioned on it
anywhere, so I have used "adafruit" as the vendor prefix. If someone ha
On Fri, 25 May 2018 15:08:53 +0200 Vlastimil Babka wrote:
> we might consider this for 4.17 although I don't know if there's anything
> currently broken. Stable backports should be more important, but will have to
> be reviewed carefully, as the code went through many changes.
> BTW I think that
On Fri, May 25, 2018 at 03:19:33PM -0400, Steven Rostedt wrote:
> On Fri, 25 May 2018 12:18:02 -0700
> "Paul E. McKenney" wrote:
>
> > [ paulmck: Add !SMP support, per 0day Test Robot report. ]
>
> Somehow I read this as:
>
> [ paulmck: Add NR_CPUS=0 support ]
>
> no idea why.
;-) ;-) ;-)
On Fri, 25 May 2018, Tetsuo Handa wrote:
> > The oom reaper ensures forward progress by setting MMF_OOM_SKIP itself if
> > it cannot reap an mm. This can happen for a variety of reasons,
> > including:
> >
> > - the inability to grab mm->mmap_sem in a sufficient amount of time,
> >
> > - when
On Fri, May 25, 2018 at 06:50:09PM +0200, Eugene Syromiatnikov wrote:
> On Thu, May 24, 2018 at 04:34:51PM -0700, Alexei Starovoitov wrote:
> > On Thu, May 24, 2018 at 09:41:08AM +0200, Jesper Dangaard Brouer wrote:
> > > On Wed, 23 May 2018 15:02:45 -0700
> > > Alexei Starovoitov wrote:
> > >
>
On Fri, 25 May 2018, ufo19890607 wrote:
> From: yuzhoujian
>
> The dump_header does not print the memcg's name when the system
> oom happened, so users cannot locate the certain container which
> contains the task that has been killed by the oom killer.
>
> I follow the advices of David Rientje
The fstrim gathers huge number of large discard commands, and tries to issue
without IO awareness, which results in long user-perceive IO latencies on
READ, WRITE, and FLUSH in UFS. We've observed some of commands take several
seconds due to long discard latency.
This patch limits the maximum size
2018-05-25 13:16-0400, Waiman Long:
> As the SSBD bit in kvm_cpuid_7_0_edx_x86_features has been renamed to
> SPEC_CTRL_SSBD in the commit 52817587e706 ("x86/cpufeatures: Disentangle
> SSBD enumeration"). The corresponding name change needed to be made in
> the KVM code as well.
>
> Fixes: 5281758
James Morris writes:
> On Thu, 24 May 2018, Eric W. Biederman wrote:
>
>> Below is where I suggest you start on sorting out these security hooks.
>> - Adding a security_kernel_arg to catch when you want to allow/deny the
>> use of an argument to a syscall. What security_kernel_file_read and
>>
> -Original Message-
> From: Dexuan Cui
> Sent: Tuesday, May 22, 2018 8:18 PM
> To: Lorenzo Pieralisi ; Bjorn Helgaas
> ; linux-...@vger.kernel.org; KY Srinivasan
> ; Stephen Hemminger ;
> o...@aepfle.de; a...@canonical.com; jasow...@redhat.com
> Cc: linux-kernel@vger.kernel.org; driverde
On Thu, May 24 2018 at 10:55pm -0400,
Ross Zwisler wrote:
> Currently the code in dm_dax_direct_access() only checks whether the target
> type has a direct_access() operation defined, not whether the underlying
> block devices all support DAX. This latter property can be seen by looking
> at whe
As what former drcmr -1 value meant, add a this as a default to each
channel, ie. that by default no requestor line is used.
This is specifically used for network drivers smc91x and smc911x, and
needed for their port to slave maps.
Cc: Arnd Bergmann
Signed-off-by: Robert Jarzmik
---
drivers/dm
Petr Tesarik writes:
> V Thu, 24 May 2018 11:34:05 -0500
> ebied...@xmission.com (Eric W. Biederman) napsáno:
>
>> Petr Tesarik writes:
>>
>> 2> On Thu, 24 May 2018 09:49:05 +0800
>> > Dave Young wrote:
>> >
>> >> Hi Petr,
>> >>
>> >> On 05/23/18 at 10:22pm, Petr Tesarik wrote:
>> >>[...]
Anna-Maria Gleixner writes:
> Since commit b4abf91047cf ("rtmutex: Make wait_lock irq safe") the rtmutex
> wait_lock is irq safe. Therefore the irqsave/restore in kernel/signal is no
> longer required (see Patch 2/2). During discussions about v1 of this patch,
> Eric Biederman noticed, that there
On Thu, May 24, 2018 at 06:49:46PM -0400, Steven Rostedt wrote:
>
> From: Steven Rostedt (VMware)
>
> Joel Fernandes found that the synchronize_rcu_tasks() was taking a
> significant amount of time. He demonstrated it with the following test:
>
> # cd /sys/kernel/tracing
> # while [ 1 ]; do x
Hi,
We are seeing something probably related.
We run ethtool on a system with Broadcom NIC to increase number of
combined queues.
[root@ ~]# ethtool -l eth0
Channel parameters for eth0:
Pre-set maximums:
RX: 9
TX: 8
Other: 0
Combined:
"dirver"?
On 05/25/2018 02:36 PM, David Lechner wrote:
This adds a new binding for Ilitek ILI9341 display panels. It includes
a compatible string for one display (more can be added in the future).
The vendor prefix "noname" is used because the vendor is not known.
Looks like I forgot to update "noname"
On Fri, May 25, 2018 at 6:53 PM, Eric Sandeen wrote:
> On 5/25/18 10:14 AM, Arnd Bergmann wrote:
>>
>> gcc-8 reports two warnings for the newly added getlabel/setlabel code:
>
>
> Thanks for catching these.
>
> The patch summary confuses me, what does "mark sb_fname as nonstring"
> mean in the con
When charging to a hugetlb_cgroup fails, alloc_huge_page() returns
ERR_PTR(-ENOSPC) which will cause VM_FAULT_SIGBUS to be returned to the
page fault handler.
Instead, return the proper error code, ERR_PTR(-ENOMEM), so VM_FAULT_OOM
is handled correctly. This is consistent with failing mem cgroup
On Fri, May 25, 2018 at 6:52 PM, Christoph Hellwig wrote:
>> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
>> index 84fbf164cbc3..eb79f2bc4dcc 100644
>> --- a/fs/xfs/xfs_ioctl.c
>> +++ b/fs/xfs/xfs_ioctl.c
>> @@ -1819,12 +1819,12 @@ xfs_ioc_getlabel(
>> BUILD_BUG_ON(sizeof(sbp->sb_fna
On 5/25/18 3:16 PM, Arnd Bergmann wrote:
On Fri, May 25, 2018 at 6:53 PM, Eric Sandeen wrote:
On 5/25/18 10:14 AM, Arnd Bergmann wrote:
...
@@ -1860,7 +1860,7 @@ xfs_ioc_setlabel(
spin_lock(&mp->m_sb_lock);
memset(sbp->sb_fname, 0, sizeof(sbp->sb_fname));
- strncpy(s
Hello
I urgently need a partner to retain and invest 14 six zero USD figures
currently in America, I'm willing to give 35 percent of the total as
compensation to you for your assistance.
Sincerely,
Richard.
This patchset adds two new SEV commands, introduced in SEV API v0.15
and v0.16 respectively.
* DOWNLOAD_FIRMWARE allows the SEV firmware to be updated if a blob newer
than or similar to the exisiting build is available.
* GET_ID allows to query for a unique ID that can be used to retrieve the
The GET_ID command, added as of SEV API v0.16, allows the SEV firmware
to be queried about a unique CPU ID. This unique ID can then be used
to obtain the public certificate containing the Chip Endorsement Key
(CEK) public key signed by the AMD SEV Signing Key (ASK).
For more information please ref
The DOWNLOAD_FIRMWARE command, added as of SEV API v0.15, allows the OS
to install SEV firmware newer than the currently active SEV firmware.
For the new SEV firmware to be applied it must:
* Pass the validation test performed by the existing firmware.
* Be of the same build or a newer build compa
From: Song Liu
Date: Thu, 24 May 2018 17:44:46 +
> We should also rename __entry->length to __entry->data_len, so that whoever
> using this field will notice the change.
Agreed.
Policy notifiers are called before a frequency change and may narrow
the min/max frequency range in devfreq_policy, which is used to adjust
the target frequency if it is beyond this range.
Also add a few helpers:
- devfreq_verify_within_[dev_]limits()
- should be used by the notifiers for pol
Currently update_devfreq() is only visible to devfreq governors outside
of devfreq.c. Make it public to allow drivers that adjust devfreq policies
to cause a re-evaluation of the frequency after a policy change.
Signed-off-by: Matthias Kaehlcke
---
drivers/devfreq/governor.h | 3 ---
include/lin
Signed-off-by: Matthias Kaehlcke
---
.../devicetree/bindings/misc/throttler.txt| 41 +++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/misc/throttler.txt
diff --git a/Documentation/devicetree/bindings/misc/throttler.txt
b/Documentatio
The driver subscribes to throttling events from the Chrome OS
embedded controller and enables/disables system throttling based
on these events.
Signed-off-by: Matthias Kaehlcke
---
drivers/misc/throttler/Kconfig | 15 +++
drivers/misc/throttler/Makefile| 1 +
drivers/m
The performance, powersave and simpleondemand governors can return
df->min/max_freq, which are the user defined frequency limits.
update_devfreq() already takes care of adjusting the target frequency
with the user limits if necessary, therefore we can return
df->scaling_min/max_freq instead, which
Move variables related with devfreq policy changes from struct devfreq
to the new struct devfreq_policy and add a policy field to struct devfreq.
The following variables are moved:
df->min/max_freq => p->user.min/max_freq
df->scaling_min/max_freq => p->devinfo.min/max_freq
df->gov
The purpose of the throttler is to provide support for non-thermal
throttling. Throttling is triggered by external event, e.g. the
detection of a high battery discharge current, close to the OCP limit
of the battery. The throttler is only in charge of the throttling, not
the monitoring, which is do
The userspace and simpleondemand governor determine a target frequency and
then adjust it according to the df->min/max_freq limits that might have
been set by user space. This adjustment is redundant, it is done in
update_devfreq() for any governor, right after returning from
governor->get_target_f
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
devfreq device") initializes df->min/max_freq with the min/max OPP when
the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the
available min/max frequency") adds df->scaling_min/max_freq and the
following to the fr
This series adds the throttler driver, for non-thermal throttling of
CPUs and devfreq devices. A use case for non-thermal throttling could
be the detection of a high battery discharge voltage, close to the
over-current protection (OCP) limit of the battery.
To support throttling of devfreq devices
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding
the devfreq device") introduced the initialization of the user
limits min/max_freq from the lowest/highest available OPPs. Later
commit f1d981eaecf8 ("PM / devfreq: Use the available min/max
frequency") added scaling_min/max_freq, whi
Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that
df->max_freq is not 0, remove unnecessary checks.
Signed-off-by: Matthias Kaehlcke
---
drivers/devfreq/governor_performance.c| 5 +
drivers/devfreq/governor_simpleondemand.c | 7 +++
2 files changed, 4 insertions(+
From: Bo Chen
Date: Thu, 24 May 2018 12:48:35 -0700
> The call to free_netdev() in __rtl8139_cleanup_dev() clears the network device
> napi list, and explicit calls to netif_napi_del() are unnecessary.
>
> Signed-off-by: Bo Chen
Since this is just unnecessary work and not a bug, applied to net
On Fri, May 25, 2018 at 10:56 AM wrote:
> You need the extern inline in the .h file and the out-of-line .S file
both.
But the out-of-line .S file looks like:
...
10 ENTRY(native_save_fl)
11 pushf
12 pop %_ASM_AX
13 ret
14 ENDPROC(native_save_fl)
15 EXPORT_SYMBO
On Thu 24 May 2018 at 23:34, Cong Wang wrote:
> On Mon, May 14, 2018 at 7:27 AM, Vlad Buslov wrote:
>> Currently, all netlink protocol handlers for updating rules, actions and
>> qdiscs are protected with single global rtnl lock which removes any
>> possibility for parallelism. This patch set is
From: Jon Maxwell
Date: Fri, 25 May 2018 07:38:29 +1000
> Fixup the checksum for CHECKSUM_COMPLETE when pulling skbs on RX path.
> Otherwise we get splats when tc mirred is used to redirect packets to ifb.
>
> Before fix:
>
> nic: hw csum failure
>
> Signed-off-by: Jon Maxwell
This definite
On Fri, 25 May 2018 13:16:45 -0700 (PDT) David Rientjes
wrote:
> When charging to a hugetlb_cgroup fails, alloc_huge_page() returns
> ERR_PTR(-ENOSPC) which will cause VM_FAULT_SIGBUS to be returned to the
> page fault handler.
>
> Instead, return the proper error code, ERR_PTR(-ENOMEM), so VM_
On Fri, May 18, 2018 at 03:07:29PM +0100, Sean Young wrote:
> Add support for BPF_PROG_LIRC_MODE2. This type of BPF program can call
> rc_keydown() to reported decoded IR scancodes, or rc_repeat() to report
> that the last key should be repeated.
>
> The bpf program can be attached to using the bp
On Thu, May 24, 2018 at 5:35 AM Vijay Viswanath
wrote:
> On 5/22/2018 11:40 PM, Evan Green wrote:
> > On Thu, May 17, 2018 at 3:30 AM Vijay Viswanath > wrote:
> >
> >> In addition to offsets of certain registers changing, the registers in
> >> core_mem have been shifted to HC mem as well. To a
On Thu, May 24, 2018 at 6:01 AM Vijay Viswanath
wrote:
> On 5/22/2018 11:42 PM, Evan Green wrote:
> > Hi Vijay. Thanks for this patch.
> >
> > On Thu, May 17, 2018 at 3:30 AM Vijay Viswanath > wrote:
> >
> >> From: Sayali Lokhande
> >
...
> > Nit: host->ioaddr + msm_offset->core_dll_config mi
On 05/25/2018 09:43 PM, Andrew Morton wrote:
> On Fri, 25 May 2018 15:08:53 +0200 Vlastimil Babka wrote:
>
>> we might consider this for 4.17 although I don't know if there's anything
>> currently broken. Stable backports should be more important, but will have to
>> be reviewed carefully, as the
From: Florian Fainelli
Date: Thu, 24 May 2018 20:52:14 -0700
> Remove redundant debug prints from phy_read/write since we can trace those
> calls through trace events. Enhance dynamic debug prints to print arguments
> which helps figuring how what is going on at the driver level with higher
> le
On Fri, 25 May 2018 08:45:36 +
Shameerali Kolothum Thodi wrote:
> Yes, the above changes related to list empty cases looks fine to me.
Thanks Shameer, applied to my next branch with the discussed fixes for
v4.18 (modulo patch 4/7 which Joerg already pushed for v4.17). Thanks,
Alex
On Mon, 21 May 2018 19:57:45 +0800
Yisheng Xie wrote:
> match_string() returns the index of an array for a matching string,
> which can be used intead of open coded variant.
>
> Cc: Alex Williamson
> Cc: k...@vger.kernel.org
> Signed-off-by: Yisheng Xie
> ---
> drivers/vfio/vfio.c | 11 +++---
Let's begin the holiday weekend with some networking fixes:
1) Whoops need to restrict cfg80211 wiphy names even more to 64
bytes. From Eric Biggers.
2) Fix flags being ignored when using kernel_connect() with SCTP, from
Xin Long.
3) Use after free in DCCP, from Alexey Kodanev.
4) Need
On Fri, 25 May 2018, Andrew Morton wrote:
> On Fri, 25 May 2018 13:16:45 -0700 (PDT) David Rientjes
> wrote:
>
> > When charging to a hugetlb_cgroup fails, alloc_huge_page() returns
> > ERR_PTR(-ENOSPC) which will cause VM_FAULT_SIGBUS to be returned to the
> > page fault handler.
> >
> > Inst
On 5/25/2018 12:27 AM, George Cherian wrote:
> Hi Prashanth,
>
> On 05/25/2018 12:55 AM, Prakash, Prashanth wrote:
>> Hi George,
>>
>> On 5/22/2018 5:42 AM, George Cherian wrote:
>>> Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides performance
>>> feedback via set of performance counters.
On 05/25/18 13:36, Nick Desaulniers wrote:
> On Fri, May 25, 2018 at 10:56 AM wrote:
>> You need the extern inline in the .h file and the out-of-line .S file
> both.
>
> But the out-of-line .S file looks like:
>
> ...
> 10 ENTRY(native_save_fl)
>
> 11 pushf
>
> 12 pop %_ASM_AX
The newly added runtime-pm functions cause a harmless warning
when CONFIG_PM is disabled:
drivers/mmc/host/sunxi-mmc.c:1452:12: error: 'sunxi_mmc_runtime_suspend'
defined but not used [-Werror=unused-function]
static int sunxi_mmc_runtime_suspend(struct device *dev)
^
Without dmaengine support, we get a harmless warning about an
unused function:
drivers/pwm/pwm-stm32.c:166:12: error: 'stm32_pwm_capture' defined but not used
[-Werror=unused-function]
Changing the #ifdef to an IS_ENABLED() check shuts up that warning
and is slightly nicer to read.
Fixes: 53e38
On Fri, 25 May 2018 13:59:40 -0700 (PDT) David Rientjes
wrote:
> > > --- a/mm/hugetlb.c
> > > +++ b/mm/hugetlb.c
> > > @@ -2006,8 +2006,10 @@ struct page *alloc_huge_page(struct vm_area_struct
> > > *vma,
> > >* code of zero indicates a reservation exists (no change).
> > >*/
> > > ma
Changing from UNIVERSAL_DEV_PM_OPS to SIMPLE_DEV_PM_OPS caused a harmless
warning in configurations without CONFIG_PM_SLEEP:
drivers/i2c/busses/i2c-i801.c:1723:12: error: 'i801_resume' defined but not
used [-Werror=unused-function]
static int i801_resume(struct device *dev)
^
The newly added code in this file causes a build error unless
we include linux/spinlock.h, at least in some configurations:
In file included from drivers/memory/tegra/mc.h:15,
from drivers/memory/tegra/tegra20.c:11:
include/soc/tegra/mc.h:159:2: error: unknown type name 'spinlock_
On Fri, 25 May 2018 14:07:31 -0400
Steven Rostedt wrote:
> >
> > BTW, would you plan to add simplar test case for the marker?
> > (like just write a marker and read trace log, and run a simple
> > trigger, like taking a snapshot by marker)
>
> I wasn't planning to, but I could.
Like someth
On Fri, 25 May 2018 17:12:29 -0400
Steven Rostedt wrote:
> #!/bin/sh
Hmm, I think I need to make this #!/bin/bash
> test_trace() {
> file=$1
> x=$2
>
> cat $file | while read line; do
> if [ "$line" != "${line/\#/}" ]; then
> continue
> fi
> echo "test
On 26.05.2018 00:11, Arnd Bergmann wrote:
> The newly added code in this file causes a build error unless
> we include linux/spinlock.h, at least in some configurations:
>
> In file included from drivers/memory/tegra/mc.h:15,
> from drivers/memory/tegra/tegra20.c:11:
> include/soc
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/wireless/ath/ath9k/ar5008_phy.c | 2 ++
drivers/net/wireless/ath/ath9k/ar9002_phy.c | 1 +
drivers/net/wireless/ath/ath9k/main.c |
Adding Broadcom developers to the thread.
Hi Michael, Vasundhara, and Andy,
Could you please help look into the case I found? ethtool crashes the system
for both net/master and net-next/master.
Thanks,
Song
On Fri, May 25, 2018 at 1:10 PM, Song Liu wrote:
> Hi,
>
> We are seeing something prob
Several subsystems depend on INFINIBAND_ADDR_TRANS, which in turn depends
on INFINIBAND. However, when with CONFIG_INIFIBAND=m, this leads to a
link error when another driver using it is built-in. The
INFINIBAND_ADDR_TRANS dependency is insufficient here as this is
a 'bool' symbol that does not for
gcc warns about a noreturn function possibly returning in
some configurations:
kernel/bpf/btf.c: In function 'env_type_is_resolve_sink':
kernel/bpf/btf.c:729:1: error: control reaches end of non-void function
[-Werror=return-type]
Using BUG() instead of BUG_ON() avoids that warning and otherwise
The stack_map_get_build_id_offset() function is too long for gcc to track
whether 'work' may or may not be initialized at the end of it, leading
to a false-positive warning:
kernel/bpf/stackmap.c: In function 'stack_map_get_build_id_offset':
kernel/bpf/stackmap.c:334:13: error: 'work' may be used
On Fri, May 25, 2018 at 11:10:01AM +0530, Viresh Kumar wrote:
> The cooling device properties, like "#cooling-cells" and
> "dynamic-power-coefficient", should either be present for all the CPUs
> of a cluster or none. If these are present only for a subset of CPUs of
> a cluster then things will st
Without CONFIG_MMU, we get a build warning:
fs/proc/vmcore.c:228:12: error: 'vmcoredd_mmap_dumps' defined but not used
[-Werror=unused-function]
static int vmcoredd_mmap_dumps(struct vm_area_struct *vma, unsigned long dst,
The function is only referenced from an #ifdef'ed caller, so
this uses t
On Tue, May 22, 2018 at 11:37:39PM -0500, Andy Gross wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux
With CONFIG_TLS=m and MLX5_CORE_EN=y, we get a link failure:
drivers/net/ethernet/mellanox/mlx5/core/en_accel/tls_rxtx.o: In function
`mlx5e_tls_handle_ooo':
tls_rxtx.c:(.text+0x24c): undefined reference to `tls_get_record'
drivers/net/ethernet/mellanox/mlx5/core/en_accel/tls_rxtx.o: In function
On Tue, May 22, 2018 at 11:37:41PM -0500, Andy Gross wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux
On Fri, May 25, 2018 at 03:54:10PM -0400, Mike Snitzer wrote:
> On Thu, May 24 2018 at 10:55pm -0400,
> Ross Zwisler wrote:
>
> > Currently the code in dm_dax_direct_access() only checks whether the target
> > type has a direct_access() operation defined, not whether the underlying
> > block devi
601 - 700 of 800 matches
Mail list logo
