>
> On Sat, Feb 24, 2018 at 05:43:16PM +0200, Tomas Winkler wrote:
> > The correct sequence is to first request locality and only after that
> > perform cmd_ready handshake, otherwise the hardware will drop the
> > subsequent message as from the device point of view the cmd_ready
> > handshake
diff --git a/Documentation/devicetree/bindings/dma/snps-dma.txt
b/Documentation/devicetree/bindings/dma/snps-dma.txt
index d58675ea1abf..f4bdc9d62130 100644
--- a/Documentation/devicetree/bindings/dma/snps-dma.txt
+++ b/Documentation/devicetree/bindings/dma/snps-dma.txt
@@ -58,6 +58,6 @@ Example:
I'm announcing the release of the 4.9.84 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.4.118 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.22 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web
From: Or Idgar
This patch is a driver which expose the Virtual Machine Generation ID
via sysfs. The ID is a UUID value used to differentiate between virtual
machines.
The VM-Generation ID is a feature defined by Microsoft (paper:
http://go.microsoft.com/fwlink/?LinkId=260709)
On Sat, Feb 24, 2018 at 4:08 PM, Daniel Axtens wrote:
> Miguel Ojeda writes:
>
>> Hi Daniel,
>>
>> On Sun, Nov 26, 2017 at 3:53 AM, Daniel Axtens wrote:
>>> This matches the header at the top of the file and squashes:
>>>
>>>
Since do_undefinstr() uses get_user to get the undefined
instruction, it can be called before kprobes processes
recursive check. This can cause an infinit recursive
exception.
Prohibit probing on get_user functions.
Fixes: 24ba613c9d6c ("ARM kprobes: core code")
Signed-off-by: Masami Hiramatsu
Prohibit kprobes on do_undefinstr because kprobes on
arm is implemented by undefined instruction. This means
if we probe do_undefinstr(), it can cause infinit
recursive exception.
Fixes: 24ba613c9d6c ("ARM kprobes: core code")
Signed-off-by: Masami Hiramatsu
---
So pointer rings work fine, but they have a problem: make them too small
and not enough entries fit. Make them too large and you start flushing
your cache and running out of memory.
This is a new idea of mine: a ring backed by a linked list. Once you run
out of ring entries, instead of a drop
On Sat, Feb 24, 2018 at 09:59:56AM +0800, Dave Young wrote:
> On 02/23/18 at 11:01am, Philipp Rudo wrote:
> > Hi Dave
> >
> > On Fri, 23 Feb 2018 16:34:05 +0800
> > Dave Young wrote:
> >
> > > On 02/14/18 at 10:54am, Philipp Rudo wrote:
> > > > Hi Dave,
> > > >
> > > > I
On 2018/2/24 10:47, jiangyiwen wrote:
> On 2018/2/9 14:13, jiangyiwen wrote:
>> User use some syscall, for example mmap(v9fs_file_mmap), it will not
>> update atime even if user's mnt_flags have MNT_NOATIME, because
>> v9fs default set SB_NOATIME in v9fs_set_super.
>>
>> For supporting access time
Hi Sebastian,
I love your patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.16-rc2 next-20180223]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
On 24 February 2018 at 21:06, kbuild test robot wrote:
> Hi Baolin,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on power-supply/for-next]
> [also build test ERROR on v4.16-rc2 next-20180223]
> [if your patch is applied to the wrong git
On Sat, Feb 24, 2018 at 02:35:40PM +0900, Masami Hiramatsu wrote:
> Add array type support for probe events.
> This allows user to get arraied types from memory address.
> The array type syntax is
>
> TYPE[N]
>
> Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> x8/16/32/64, symbol,
Alot of folks have been wondering: why are things they way that they
are? Many have been pondering this notion. All things have roots: you,
me, we all do, but when we are cut from those roots we feel adrift in
this world. Like this world is not our own. In the past many of us have
been
On Sun, Feb 25, 2018 at 06:09:53PM -0700, Tycho Andersen wrote:
> Hi Tobin,
>
> On Mon, Feb 19, 2018 at 01:50:49PM +1100, Tobin C. Harding wrote:
> > +sub already_scanned
> > +{
> > + my ($filename) = @_;
> > + state %seen;
> > +
> > + foreach (@once_only) {
> > + if
On Sun, Feb 25, 2018 at 06:26:31PM -0700, Tycho Andersen wrote:
> Hi Tobin,
>
> On Mon, Feb 19, 2018 at 01:50:47PM +1100, Tobin C. Harding wrote:
> > -# Do not parse these files under any subdirectory.
> > -my @skip_parse_files_any = ('0',
> > - '1',
> > -
On 02/24/2018 01:16 AM, Andy Shevchenko wrote:
> On Fri, Feb 23, 2018 at 4:19 PM, Shawn Lin wrote:
>> On 2018/2/23 21:27, Andy Shevchenko wrote:
>>> On Fri, Feb 23, 2018 at 8:41 AM, Jaehoon Chung
>>> wrote:
'clock-freq-min-max' property
I dun kno what the fucc yall is saying. Vacume cleaners on skin n WT.
Skin lightening creams are bullshit japanese use to white wash them.
On 2018-02-26 00:46, Arnt Karlsen wrote:
On Sun, 25 Feb 2018 16:13:05 +, thetruthstandsb...@firemail.cc
wrote in message
How about you white folks stop trying to silence any that have something
other than your whitewashed opinions. Your culture sterile.
Truth:
https://www.liveleak.com/view?i=c34_1519605684
On 2018-02-25 22:24, Antony Stone wrote:
On Sunday 25 February 2018 at 23:17:40, info at smallinnovations
There's real men and then there's you mther fuckers. Men don't talk in
lawyer bullshit or programmer babble. Real men fuck real women.
You lawyers and programmers don't do none of it. White fag bullshit.
On 2018-02-25 21:43, taii...@gmx.com wrote:
Looks like someone took the brown acid.
From: Frank Rowand
In preparation for fixing __of_node_dup(), clean up the unittest
function that calls it.
Devicetree nodes created from a flattened device tree have a name
property. Follow this convention for nodes added by a changeset.
For node added by changeset,
From: Frank Rowand
struct device_node full_name has been changed to include the
basename instead of the full path. kbasename() is no longer
needed to extract the basename from full_name.
Signed-off-by: Frank Rowand
---
drivers/of/kobj.c | 2 +-
1
Hi all,
Today's linux-next merge of the kvms390 tree got a conflict in:
drivers/video/console/Kconfig
between commit:
2312dbf7462b ("drivers/video/concole: add negative dependency for VGA_CONSOLE
on nds32")
from the nds32 tree and commits:
8da93aca3729 ("Kconfig : Remove HAS_IOMEM
From: Corey Minyard
Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
KCS controller, but whatever it is, it's not one. Ignore it if seen.
Reported-by: Chris Chiu
Signed-off-by: Corey Minyard
---
I haven't heard
Hi Andy,
On 25 February 2018 at 20:19, Andy Shevchenko wrote:
> On Sat, Feb 24, 2018 at 12:44 PM, Baolin Wang wrote:
>> The Spreadtrum PMIC EIC controller contains only one bank of debounce EIC,
>> and this bank contains 16 EICs. Each EIC can
We're on the normal schedule for 4.16 and everything still looks very regular.
rc3 is larger than rc2 was, but as mentioned last week, that's
expected - rc2 really was tiny. People have started finding things to
fix, but there's nothing that really stands out as particularly scary
here.
"Small
On 2018年02月26日 09:17, Michael S. Tsirkin wrote:
So pointer rings work fine, but they have a problem: make them too small
and not enough entries fit. Make them too large and you start flushing
your cache and running out of memory.
This is a new idea of mine: a ring backed by a linked list.
SUN8I_I2S_TX_CHAN_OFFSET_MASK should be GENMASK(13, 12).
And offset tune of RX should also be updated.
Fixes: 7d2993811a1e ("ASoC: sun4i-i2s: Add support for H3")
Signed-off-by: Yong Deng
---
sound/soc/sunxi/sun4i-i2s.c | 8 +++-
1 file changed, 7 insertions(+), 1
== v5 ==
Patch numbers changing due to squash and reorder.
Using Prior (v4) Patch number noting *new* patch numbers as bullet item.
Patch 0001 & 0004 Merged into: Update-Module-info-and-copyright
1) New Patch 0001
Patch 0002 Remove legacy NMI sourcing
1) Unmodified
Patch 0003 Update nmi_panic
Gen8 and prior Proliant systems supported the "CRU" interface
to firmware. This interfaces allows linux to "call back" into firmware
to source the cause of an NMI. This feature isn't fully utilized
as the actual source of the NMI isn't printed, the driver only
indicates that the source couldn't
Add a few dynamic debug messages to aid in module level debug.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index b8205c6e61c1..b82bbeed0e43
The intent of this parameter is unclear and it sets up a
race between the reset of the system by ASR and crashdump.
The length of time between receipt of the pretimeout NMI
and the ASR reset of the system is fixed by hardware.
Turning the parameter off doesn't necessairly prevent a crash dump.
Update driver version number to reflect changes.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index b82bbeed0e43..a43ab2cecca2 100644
---
Make whether or not the hpwdt watchdog delivers a pretimeout NMI
programable by the user.
The underlying iLO hardware is programmable as to whether or not
a pre-timeout NMI is delivered to the system before the iLO resets
the system. However, the iLO does not allow for programming the
length of
Include the nmistat in the nmi_panic message to give support
an indication why the NMI was called (e.g. a timeout or generate
nmi button.)
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
Follow Documentation/watchdog/convert_drivers_to_kernel_api.txt to
convert hpwdt from legacy watchdog driver to use the watchdog core.
Removed functions: hpwdt_open, hpwdt_release, hpwdt_write, hpwdt_ioctl
Removed data structures: hpwdt_fops, hpwdt_miscdev, watchdog_device
Modified functions:
Update Copyright and Module description to reflect branding changes.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index
Linus,
please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
A single commit removing a bunch of bogus double semicolons all over the
tree.
Thanks,
tglx
-->
Ingo Molnar (1):
Hi!
On Sun, Feb 25, 2018 at 06:22:16PM +0100, Mathieu Malaterre wrote:
> When neither CONFIG_ALTIVEC, nor CONFIG_VSX or CONFIG_PPC64 is defined, the
> array feature_properties is defined as an empty array, which in turn
> triggers the following warning (treated as error on W=1):
> - for (i =
On Sun, Feb 25, 2018 at 7:13 PM, Randy Dunlap wrote:
> On 02/25/2018 04:46 AM, Miguel Ojeda wrote:
>> There was a missing first line and a missing member,
>> which gave a warning under W=1:
>>
>> CC drivers/auxdisplay/arm-charlcd.o
>>
On 23.02.2018 01:15, Eric W. Biederman wrote:
> Helge Deller writes:
>
>> * Eric W. Biederman :
>>> Setting si_code to 0 results in a userspace seeing an si_code of 0.
>>> This is the same si_code as SI_USER. Posix and common sense requires
>>> that SI_USER
The IRQ is requested before the struct rtc is allocated and registered, but
this struct is used in the IRQ handler, leading to:
Unable to handle kernel NULL pointer dereference at virtual address 017c
pgd = a38a2f9b
[017c] *pgd=
Internal error: Oops: 5 [#1] ARM
Modules linked in:
On Sun, Feb 25, 2018 at 7:05 AM, kernel test robot
wrote:
>
> FYI, we noticed a -18.0% regression of aim7.jobs-per-min due to commit:
>
> commit: c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e ("iversion: make
> inode_cmp_iversion{+raw} return bool instead of s64")
That looks
Hi Andy,
At 02/23/2018 08:40 PM, Andy Shevchenko wrote:
On Fri, Feb 23, 2018 at 9:54 AM, Dou Liyang wrote:
The pending interrupt check code is old, update the following code.
-Replace for() with for_each_set_bit()
- for (j = 31; j >= 0;
Hi, all
I sent the patch series of Sony CXD2880 DVB-T2/T tuner + demodulator driver
version 5 on 18th/Jan.
I'd like to get better understanding of current review status for our drivers.
Are there any comments, advices and review results for them?
Thanks,
Takiguchi
On Fri, Feb 16, 2018 at 04:32:05PM -0500, David Miller wrote:
> From: "Michael S. Tsirkin"
> Date: Fri, 16 Feb 2018 09:40:54 +0200
>
> > So pointer rings work fine, but they have a problem:
> > make them too small and not enough entries fit.
> > Make them too large and you start
Hi Tobin,
On Mon, Feb 19, 2018 at 01:50:49PM +1100, Tobin C. Harding wrote:
> +sub already_scanned
> +{
> + my ($filename) = @_;
> + state %seen;
> +
> + foreach (@once_only) {
> + if (/^$filename$/) {
> + if ($seen{$_} == 1) {
This should be something
CPU is active when have running tasks on it and CPUFreq governor can
select different operating points (OPP) according to different workload;
we use 'pstate' to present CPU state which have running tasks with one
specific OPP. On the other hand, CPU is idle which only idle task on
it, CPUIdle
Hi Tobin,
On Mon, Feb 19, 2018 at 01:50:47PM +1100, Tobin C. Harding wrote:
> -# Do not parse these files under any subdirectory.
> -my @skip_parse_files_any = ('0',
> - '1',
> - '2',
> - 'pagemap',
> -
BTW. This is truth so you best much less listen.
On 2018-02-26 01:56, thetruthbefor...@firemail.cc wrote:
Alot of folks have been wondering: why are things they way that they
are? Many have been pondering this notion. All things have roots: you,
me, we all do, but when we are cut from those
Media don't care none about the truth about white people.
They befriend and protect them. That's how it is.
Millions of black men in jail. Media don't give a shit.
http://www.liveleak.com/view?i=c34_1519605684
On 2018-02-26 00:46, Bruce Perens wrote:
GNU Mailman should be able to exclude
Hi test robot,
2018-02-24 14:00 GMT+09:00 kbuild test robot :
> Hi Masahiro,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on linus/master]
> [also build test WARNING on v4.16-rc2 next-20180223]
> [if your patch is applied to the wrong git
On Spreadtrum platform, we need power off system through external SC27xx
series PMICs including the SC2720, SC2721, SC2723, SC2730 and SC2731 chips.
Thus this patch adds SC27xx series PMICs power-off support.
Signed-off-by: Baolin Wang
---
Changes since v3:
- Add
From: Frank Rowand
Struct device_node full_name no longer includes the full path
name. The overlay node creation code was not modified to
reflect this change. Fix the node names generate by overlay
code to contain only the basename.
Unittests call an overlay internal
From: Frank Rowand
struct device_node full_name has been changed to include the
basename instead of the full path. kbasename() is no longer
needed to extract the basename from full_name.
Signed-off-by: Frank Rowand
---
drivers/of/platform.c | 2
From: Frank Rowand
struct device_node full_name has been changed to include the
basename instead of the full path. kbasename() is no longer
needed to extract the basename from full_name.
Signed-off-by: Frank Rowand
---
drivers/of/base.c | 4 ++--
From: Frank Rowand
Struct device_node full_name no longer includes the full path
name.
Fix some broken overlay code that was not updated to reflect this.
Clean up the unittest changeset test that calls into this
overlay code.
kbasename(->full_name) is no longer needed,
From: Frank Rowand
struct device_node full_name has been changed to include the
basename instead of the full path. kbasename() is no longer
needed to extract the basename from full_name.
Signed-off-by: Frank Rowand
---
Alex reported the following race condition:
/* link goes up... interrupt... schedule watchdog */
\ e1000_watchdog_task
\ e1000e_has_link
\ hw->mac.ops.check_for_link() === e1000e_check_for_copper_link
\ e1000e_phy_has_link_generic(..., )
the pending interrupt check code is mixed with the local APIC setup code,
that looks messy.
Extract the related code, move it into a new function named
apic_pending_intr_clear().
Signed-off-by: Dou Liyang
---
arch/x86/kernel/apic/apic.c | 98
The pending interrupt check code is old, update the following.
-Replace for-if pair with for_each_set_bit()
-Replace printk() with pr_err()
Also merge the printk's code in one line and make curly braces balanced
Signed-off-by: Dou Liyang
---
changlog:
v3 --> v4:
Hi Waiman,
What's happened to this patchset? Any plans to repost a more recent
version?
FYI, I just ran a workload that hit 60% CPU usage on sb inode list
lock contention - a multithreaded bulkstat scan of an XFS filesystem
with millions of inodes on SSDs. last time I ran this (about 18
months
I2S's RX slot number of SUN8I should be shifted 4 bit to left.
Fixes: 7d2993811a1e ("ASoC: sun4i-i2s: Add support for H3")
Signed-off-by: Yong Deng
---
sound/soc/sunxi/sun4i-i2s.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Feb 26, 2018 at 10:43 AM, Yong Deng wrote:
> I2S's RX slot number of SUN8I should be shifted 4 bit to left.
>
> Fixes: 7d2993811a1e ("ASoC: sun4i-i2s: Add support for H3")
>
> Signed-off-by: Yong Deng
Reviewed-by: Chen-Yu Tsai
Hi, Shakeel
On 02/25, Shakeel Butt wrote:
>On Sun, Feb 25, 2018 at 6:44 AM, kernel test robot
> wrote:
>>
>> Greeting,
>>
>> FYI, we noticed a -7.9% regression of stress-ng.hdd.ops_per_sec due to
>> commit:
>>
>>
>> commit: 9c4e6b1a7027f102990c0395296015a812525f4d ("mm,
In some platforms (such as arm), high memory is used, then the
decrypting filename will cause panic, the reason see commit
569cf1876a32e574ba8a7fb825cd91bafd003882 ("f2fs crypto: allocate buffer
for decrypting filename"):
We got dentry pages from high_mem, and its address space directly goes
Hi, Eric,
Thanks for your review, I have removed the symlink part and use
kmemdup instead. As for directory pages restricted to lowmem, I am
not sure whether it is proper for f2fs, since the directory structures
of f2fs are different from ext4. So I just keep its old kmap.
On 2018/2/25 2:32,
From: "leilei.lin"
Do not install cgroup event into the CPU context and schedule it
if the cgroup is not running on this CPU
While there is no task of cgroup running specified CPU, current
kernel still install cgroup event into CPU context that causes
another cgroup
Hardware-realized virtio-pci devices can implement SR-IOV, so this
patch enables its use. The device in question is an upcoming Intel
NIC that implements both a virtio-net PF and virtio-net VFs. These
are hardware realizations of what has been up to now been a software
interface.
The device in
You all know that you're working with white and japanese mthr fuckers
right? you just fine with that? After what they did to your people? Ok
then. You be you. You be you.
Here's some real talk about the while mother fuckers:
https://www.liveleak.com/view?i=c34_1519605684
On 2018-02-26 02:07,
Modify prior change to not claim an NMI unless originated
from iLO to apply only to iLO5 and later going forward.
This restores hpwdt traditional behavior of calling panic
if the NMI is NMI_IO_CHECK, NMI_SERR, or NMI_UNKNOWN for
legacy hardware.
Signed-off-by: Jerry Hoemann
You know you are hitting something when white people,
like you linux kernel programmers, attack and constanly
squelch and masking-tape and silence your words.
It means these are words of truth.
Harsh, real, unvarnished truth. Real talk. Not some
lawyer bullshit or programmer babble. Real talk
On Sun, Feb 25, 2018 at 10:17:30AM -0800, Paul E. McKenney wrote:
> On Sun, Feb 25, 2018 at 09:49:27AM -0800, Paul E. McKenney wrote:
> > On Sat, Feb 24, 2018 at 03:12:40PM -0500, Steven Rostedt wrote:
> > > On Fri, 1 Dec 2017 11:21:40 -0800
> > > "Paul E. McKenney"
There are two ways to connect the Steam Controller: directly to the USB
or with the USB wireless adapter. Both methods are similar, but the
wireless adapter can connect up to 4 devices at the same time.
The wired device will appear as 3 interfaces: a virtual mouse, a virtual
keyboard and a
This device has a feature report to send and receive commands.
Use it to get the serial number and set the device's uniq value.
Signed-off-by: Rodrigo Rivas Costa
---
drivers/hid/hid-steam.c | 105 ++--
1 file changed, 102
The wireless Steam Controller is battery operated, so add the battery
device and power information.
Signed-off-by: Rodrigo Rivas Costa
---
drivers/hid/hid-steam.c | 141 +++-
1 file changed, 140 insertions(+), 1
On 02/25/2018 07:24 AM, Hans de Goede wrote:
> From: Heikki Krogerus
>
> Several frameworks - clk, gpio, phy, pmw, etc. - maintain
> lookup tables for describing connections and provide custom
> API for handling them. This introduces a single generic
> lookup
On 02/25/2018 07:25 AM, Hans de Goede wrote:
> From: Heikki Krogerus
>
> ---
> Documentation/driver-api/usb/typec.rst | 73 +++--
> drivers/usb/typec/Makefile | 1 +
> drivers/usb/typec/{typec.c => class.c} | 70
>
On Sat, Feb 24, 2018 at 11:43:28PM +0100, Tobias Jordan wrote:
> pm_runtime_get_sync() increases the device's usage count even when
> reporting an error, so add a call to pm_runtime_put_noidle() in the
> related error branches.
>
> Fixes: 588eb93ea49f ("i2c: imx: add runtime pm support to improve
Hello, Greg.
2018-02-23 19:52 GMT+09:00 Greg Kroah-Hartman :
> On Fri, Feb 23, 2018 at 07:13:50PM +0900, Seunghun Han wrote:
>> I am Seunghun Han and a senior security researcher at National Security
>> Research Institute of South Korea.
>>
>> I found a critical
> FWIW, alpha and m68k are known boot with qemu (even though m68k
> generates a warning traceback with the mainline kernel).
M68K works - people actively use it. Crazy people true 8). Alpha I
believe one or two people boot. I just need to track down some discs for
my Alpha 8)
Alan
Gen8 and prior Proliant systems supported the "CRU" interface
to firmware. This interfaces allows linux to "call back" into firmware
to source the cause of an NMI. This feature isn't fully utilized
as the actual source of the NMI isn't printed, the driver only
indicates that the source couldn't
== v4 ==
Modifications from prior version:
Manual merging and patch reordering has caused minor white
space and diff changes. Such change shouldn't have effected
the logic and are omitted below:
Patch 001 Remove legacy NMI sourcing.
1) Updated patch documentation to reflect Spectre concerns.
Add a few dynamic debug messages to aid in module level debug.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index be7b3edac56c..b5fb2663c2a1
Update Module description to reflect branding changes.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index 2a6f3be22c98..44c3038cc531 100644
Include the nmistat in the nmi_panic message to give support
an indication why the NMI was called (e.g. a timeout or generate
nmi button.)
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
On 02/25/2018 07:25 AM, Hans de Goede wrote:
Remove the unused (not implemented anywhere) tcpc_mux_dev abstraction
and replace it with calling the new typec_set_orientation,
usb_role_switch_set and typec_set_mode functions.
Reviewed-by: Heikki Krogerus
On Sun, Feb 25, 2018 at 09:49:27AM -0800, Paul E. McKenney wrote:
> On Sat, Feb 24, 2018 at 03:12:40PM -0500, Steven Rostedt wrote:
> > On Fri, 1 Dec 2017 11:21:40 -0800
> > "Paul E. McKenney" wrote:
> >
> > > Now that cond_resched() also provides RCU quiescent
Signed-off-by: Mike Rapoport
---
mm/cma.c| 5 +
mm/compaction.c | 1 +
mm/kmemleak.c | 10 ++
mm/memory_hotplug.c | 6 ++
mm/oom_kill.c | 2 ++
mm/pagewalk.c | 3 +++
mm/rmap.c | 1 +
mm/zsmalloc.c |
The alloc_mm_area in nommu is a stub, but it's description states it
allocates kernel address space.
Remove the description to make the code and the documentation agree.
Signed-off-by: Mike Rapoport
---
mm/nommu.c | 12
1 file changed, 12 deletions(-)
diff
Hi,
Here's another set of (mostly) trivial updates for kernel-doc descriptions
in the mm code.
Mike Rapoport (3):
mm/nommu: remove description of alloc_vm_area
mm/swap: remove @cold parameter description for release_pages
mm: kernel-doc: add missing parameter descriptions
mm/cma.c
The 'cold' parameter was removed from release_pages function by the commit
c6f92f9fbe7db ("mm: remove cold parameter for release_pages").
Update the description to match the code.
Signed-off-by: Mike Rapoport
---
mm/swap.c | 1 -
1 file changed, 1 deletion(-)
diff
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
Three patches to fix memory ordering issues on ALPHA and a comment to
clarify the usage scope of a mutex internal function.
Thanks,
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
A single commit which shuts up a bogus GCC-8 warning.
Thanks,
tglx
-->
Arnd Bergmann (1):
x86/oprofile: Fix
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 small set of fixes:
- UAPI data type correction for hyperv
- Correct the cpu cores field in /proc/cpuinfo on CPU hotplug
- Return
Make whether or not the hpwdt watchdog delivers a pretimeout NMI
programable by the user.
The underlying iLO hardware is programmable as to whether or not
a pre-timeout NMI is delivered to the system before the iLO resets
the system. However, the iLO does not allow for programming the
length of
On 02/25/2018 07:25 AM, Hans de Goede wrote:
Setting the mux to MUX_NONE and the switch to USB_SWITCH_DISCONNECT when
the data-role is device is not correct. Plenty of devices support
operating as USB device through a (separate) USB device controller.
We really need 2 different versions of
The intent of this parameter is unclear and it sets up a
race between the reset of the system by ASR and crashdump.
The length of time between receipt of the pretimeout NMI
and the ASR reset of the system is fixed by hardware.
Turning the parameter off doesn't necessairly prevent a crash dump.
1 - 100 of 682 matches
Mail list logo