There has been a lurking "TBD" in the machine check poll routine ever
since it was first split out from the machine check handler. The potential
issue is that the poll routine may have just begun a read from the STATUS
register in a machine check bank when the hardware logs an error in that
bank
Hi,
On 11/03/19 10:02 AM, Naga Sureshkumar Relli wrote:
> Hi Vignesh,
>
>> -Original Message-
>> From: linux-spi-ow...@vger.kernel.org On
>> Behalf Of
>> Vignesh Raghavendra
>> Sent: Friday, March 8, 2019 10:20 AM
>> To: Naga Sureshkumar Relli ; broo...@kernel.org;
>>
On Mon, 2019-03-11 at 16:54 -0700, Calvin Owens wrote:
> We're having lots of problems with TPM commands timing out, and we're
> seeing these problems across lots of different hardware (both v1/v2).
>
> I instrumented the driver to collect latency data, but I wasn't able to
> find any specific
The pull request you sent on Mon, 11 Mar 2019 21:39:08 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
> tags/tag-chrome-platform-for-v5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f47d633134f7033e3d0c667419d9f8afd69e308d
Thank
+DT folks
Please add them in future versions (script/scripts/get_maintainer.pl
should have listed them)
On Tue, Mar 12, 2019 at 05:52:59PM +0530, Harish Bandi wrote:
> This patch enables regulators for the Qualcomm Bluetooth wcn3998
> controller.
No, it doesn't.
The next version should
On Tue, 2019-03-12 at 07:42 -0700, James Bottomley wrote:
> On Tue, 2019-03-12 at 14:50 +0200, Jarkko Sakkinen wrote:
> > On Mon, Mar 11, 2019 at 05:27:43PM -0700, James Bottomley wrote:
> > > On Mon, 2019-03-11 at 16:54 -0700, Calvin Owens wrote:
> > > > e're having lots of problems with TPM
On Tue 12-03-19 09:37:41, Sultan Alsawaf wrote:
> I have not had a chance to look at PSI yet, but
> unless a PSI-enabled solution allows allocations to reach the same point as
> when
> the OOM killer is invoked (which is contradictory to what it sets out to do),
> then it cannot take advantage of
Two auto corrections:
On 3/10/19 7:28 PM, Jacek Anaszewski wrote:
Add public led_compose_name() API for composing LED class device
name basing on fwnode_handle data. The function composes device name
according to either a new pattern or the legacy
pattern. The decision on using the
particular
On Tue, 2019-03-12 at 14:36 +0200, Jarkko Sakkinen wrote:
> On Mon, Mar 11, 2019 at 04:54:04PM -0700, Calvin Owens wrote:
> > We're having lots of problems with TPM commands timing out, and we're
> > seeing these problems across lots of different hardware (both v1/v2).
> >
> > I instrumented the
On Mon, Mar 11, 2019 at 9:39 PM Benson Leung wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
> tags/tag-chrome-platform-for-v5.1
No diffstat in the pull request? And the shortlog looks truncated too,
with Nick Crews being reported as having four commits, but
Hi Masami,
On Wed, 2019-03-13 at 00:46 +0900, Masami Hiramatsu wrote:
> On Mon, 4 Mar 2019 17:36:46 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > Replace hist_err() and hist_err_event() with tracing_log_err() from
> > the new tracing error_log mechanism.
> >
> > Also add a
Hi Masami,
On Tue, 2019-03-12 at 15:26 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Tue, 5 Mar 2019 23:06:46 +0900
> Masami Hiramatsu wrote:
>
> > On Mon, 4 Mar 2019 17:36:43 -0600
> > > Changes from v2:
> > >
> > > - Added [n] numbering as suggested by Masami
>
> Hmm, this seems a bit
On Tue 12-03-19 09:37:41, Sultan Alsawaf wrote:
> On Tue, Mar 12, 2019 at 09:05:32AM +0100, Michal Hocko wrote:
> > The only way to control the OOM behavior pro-actively is to throttle
> > allocation speed. We have memcg high limit for that purpose. Along with
> > PSI, I can imagine a reasonably
On Wed, Mar 13, 2019 at 12:44 AM Michal Hocko wrote:
>
> On Wed 13-03-19 00:29:57, Yafang Shao wrote:
> > On Wed, Mar 13, 2019 at 12:18 AM Michal Hocko wrote:
> > >
> > > On Sat 02-03-19 12:38:58, Yafang Shao wrote:
> > > > Only mm_compaction_isolate_{free, migrate}pages may be used when
> > > >
On 2019-03-07 23:12, Li RongQing wrote:
From: Li Rongqing
msgctl10 of ltp triggers the following lockup When CONFIG_KASAN
is enabled on large memory SMP systems, the pages initialization
can take a long time, if msgctl10 requests a huge block memory,
and it will block rcu scheduler, so release
On Wed 13-03-19 00:29:57, Yafang Shao wrote:
> On Wed, Mar 13, 2019 at 12:18 AM Michal Hocko wrote:
> >
> > On Sat 02-03-19 12:38:58, Yafang Shao wrote:
> > > Only mm_compaction_isolate_{free, migrate}pages may be used when
> > > CONFIG_COMPACTION is not set.
> > > All others are used only when
> that line goes forever now, please provide some formating
> into multiple lines
Here's an updated patch with line wrapping.
---
perf report: Show all sort keys in help output
Show all the supported sort keys in the command line help output,
so that it's not needed to refer to the manpage.
On 3/11/19 6:24 PM, Jacek Anaszewski wrote:
Dan,
On 3/11/19 1:26 PM, Dan Murphy wrote:
On 3/10/19 1:28 PM, Jacek Anaszewski wrote:
Introduce dedicated properties for conveying information about
LED function and color. Mark old "label" property as deprecated.
Signed-off-by: Jacek Anaszewski
Hi Linus,
Please pull Kconfig updates for v5.1.
Thanks.
The following changes since commit f17b5f06cb92ef2250513a1e154c47b78df07d40:
Linux 5.0-rc4 (2019-01-27 15:18:05 -0800)
are available in the git repository at:
On Sat, Mar 02, 2019 at 06:26:39PM +, Jonathan Cameron wrote:
> On Fri, 1 Mar 2019 14:42:27 +0100
> Andreas Klinger wrote:
>
> > Add doc for dt binding maxbotix,i2cxl. This binding is for MaxBotix
> > I2CXL-MaxSonar ultrasonic rangers which share a common i2c interface.
>
> I'm a bit
On Mon, Mar 11 2019 at 04:42 -0600, Marc Zyngier wrote:
On 22/02/2019 22:18, Lina Iyer wrote:
Introduce a new domain for wakeup capable GPIOs. The domain can be
requested using the bus token DOMAIN_BUS_WAKEUP. In the following
patches, we will specify PDC as the wakeup-parent for the TLMM GPIO
On Tue, Mar 12, 2019 at 09:05:32AM +0100, Michal Hocko wrote:
> The only way to control the OOM behavior pro-actively is to throttle
> allocation speed. We have memcg high limit for that purpose. Along with
> PSI, I can imagine a reasonably working user space early oom
> notifications and
On Mon, Mar 11 2019 at 04:55 -0600, Marc Zyngier wrote:
On 22/02/2019 22:18, Lina Iyer wrote:
To allow GPIOs to wakeup the system from suspend or deep idle, the
wakeup capable GPIOs are setup in hierarchy with interrupts from the
wakeup-parent irqchip.
In older SoC's, the TLMM will handover
.set_current_limit callback should select the current closest to max_uA.
Signed-off-by: Axel Lin
---
drivers/regulator/wm831x-isink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/wm831x-isink.c b/drivers/regulator/wm831x-isink.c
index
.set_current_limit callback should select the current closest to max_uA.
Signed-off-by: Axel Lin
---
drivers/regulator/wm8350-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/wm8350-regulator.c
b/drivers/regulator/wm8350-regulator.c
index
Use regulator_set/get_current_limit_regmap helpers to save some code.
Signed-off-by: Axel Lin
---
drivers/regulator/wm8350-regulator.c | 81
1 file changed, 11 insertions(+), 70 deletions(-)
diff --git a/drivers/regulator/wm8350-regulator.c
Use regulator_set/get_current_limit_regmap helpers to save some code.
Signed-off-by: Axel Lin
---
drivers/mfd/wm831x-core.c| 2 +-
drivers/regulator/wm831x-isink.c | 45 +---
include/linux/mfd/wm831x/regulator.h | 2 +-
3 files changed, 9 insertions(+),
On Tue, Mar 12, 2019 at 03:57:33PM +0100, Enrico Weigelt, metux IT consult
wrote:
> ---
> drivers/tty/serial/8250/8250_bcm2835aux.c | 12
> 1 file changed, 4 insertions(+), 8 deletions(-)
No changelog or signed-off-by, sorry, please fix up the series and
resend.
thanks,
greg k-h
On Tue, Mar 12, 2019 at 03:41:57PM +0100, Matthias Brugger wrote:
>
>
> On 11/03/2019 09:54, Erin Lo wrote:
> > This adds dt-binding documentation of uart for Mediatek MT8183 SoC
> > Platform.
> >
> > Signed-off-by: Erin Lo
> > Acked-by: Rob Herring
> > ---
> >
Hello Yash,
On Tue, 12 Mar 2019, Yash Shah wrote:
> This patch series adds a L2 Cache EDAC driver and DT documentation
> for HiFive Unleashed board.
This should also reference the "FU540-C000 chip" since there isn't
anything board-specific about it.
Also - could you please describe in your
Hello Yash,
On Tue, 12 Mar 2019, Yash Shah wrote:
> Add driver for the SiFive L2 cache controller
> on the HiFive Unleashed board
This should read "for the SiFive FU540-C000 chip" or something similar.
The L2 cache controller is not specific to the HiFive Unleashed board.
Could you also
Gautham R Shenoy writes:
>> Signed-off-by: Thiago Jung Bauermann
>
> Thanks for this version. I have tested the patch and we no longer see
> the "Querying DEAD? cpu X (Y) shows 2" message.
>
>
> Tested-and-Reviewed-by: Gautham R. Shenoy
Thanks for reviewing and testing the patch!
--
Document the ast2400, ast2500 PCI-to-AHB bridge control driver bindings.
Signed-off-by: Patrick Venture
---
Changes for v7:
- Moved node under the syscon node it requires
Changes for v6:
- None
Changes for v5:
- None
Changes for v4:
- None
Changes for v3:
- None
Changes for v2:
- Added comment
The ASPEED AST2400, and AST2500 in some configurations include a
PCI-to-AHB MMIO bridge. This bridge allows a server to read and write
in the BMC's physical address space. This feature is especially useful
when using this bridge to send large files to the BMC.
The host may use this to send down
On Wed, Mar 13, 2019 at 12:18 AM Michal Hocko wrote:
>
> On Sat 02-03-19 12:38:58, Yafang Shao wrote:
> > Only mm_compaction_isolate_{free, migrate}pages may be used when
> > CONFIG_COMPACTION is not set.
> > All others are used only when CONFIG_COMPACTION is set.
>
> Why is this an improvement?
Hi Harish,
On Tue, Mar 12, 2019 at 05:52:58PM +0530, Harish Bandi wrote:
> Added new compatible for wcn3998 and corresponding voltage
> and current values to wcn3998 compatible.
> Changed driver code to support wcn3998
>
> Signed-off-by: Harish Bandi
> ---
> changes in v3:
> - updated to latest
Le 12/03/2019 à 15:58, Michal Hocko a écrit :
On Mon 11-03-19 20:17:01, Laurent Dufour wrote:
The commit 95402b382901 ("cpu-hotplug: replace per-subsystem mutexes with
get_online_cpus()") remove the CPU_LOCK_ACQUIRE operation which was use to
grap the cache_chain_mutex lock which was protecting
On Sat 02-03-19 12:38:58, Yafang Shao wrote:
> Only mm_compaction_isolate_{free, migrate}pages may be used when
> CONFIG_COMPACTION is not set.
> All others are used only when CONFIG_COMPACTION is set.
Why is this an improvement?
> Signed-off-by: Yafang Shao
> ---
>
On Sat 02-03-19 12:38:57, Yafang Shao wrote:
> show the gfp flag names instead of the gfp_mask could make the trace
> more convenient.
Agreed
> Signed-off-by: Yafang Shao
Acked-by: Michal Hocko
> ---
> include/trace/events/compaction.h | 4 ++--
> 1 file changed, 2 insertions(+), 2
We have a good example of deadlock when using an XFS filesystem on an
nbd loopback device regardless of mlockall and MCL_FUTURE. Below I'll
paste the hung task traces but I'll try to summarize the steps that
caused the problem.
The setup is an nbd loopback device with an XFS filesystem that is
On Fri, 1 Mar 2019 14:41:57 +0100, Andreas Klinger wrote:
> Add MaxBotix, which is a vendor of ultrasonic rangers in different
> varieties and interfaces.
>
> Signed-off-by: Andreas Klinger
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
>
On Fri, 1 Mar 2019 05:23:40 +0100, =?UTF-8?q?Marek=20Beh=C3=BAn?= wrote:
> This adds device tree binding documentation for the rWTM BIU mailbox
> driver on the Armada 37xx SOC (EspressoBin, Turris Mox).
>
> Signed-off-by: Marek Behún
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> ---
>
Hello Dear,
Please forgive me for stressing you with my predicaments as I know
that this letter may come to you as big surprise. Actually, I came
across your E-mail from my personal search afterward I decided to
email you directly believing that you will be honest to fulfill my
final wish before
On Thu, 28 Feb 2019 11:19:51 +0100, Fabrice Gasnier wrote:
> Add documentation for STMicroelectronics STM32 Factory-programmed
> read only memory area.
>
> Signed-off-by: Fabrice Gasnier
> ---
> Changes in v2:
> - update "st,stm32f4-otp" compatible as discussed with Rob
> ---
>
Add DT nodes for
- Two xHCI host controllers
- Two BDC Broadcom USB device controller
- Five USB PHY controllers
[xHCI0] [BDC0][xHCI1][BDC1]
| | | |
--- ---
|
USB PHY driver supports two types of stingray USB PHYs
- Type 1 is a combo PHY contains two PHYs, one SS and one HS.
- Type 2 is a single HS PHY.
These two PHY versons support both Generic xHCI host controller driver
and BDC Broadcom device controller driver.
Signed-off-by: Srinath Mannam
---
These patches add Stingray USB PHY driver and its corresponding
DT nodes with documentation.
This patch set is based on Linux-5.0-rc2.
Changes from v4:
- Addressed Rob Herring review comments
- Removed child nodes and added #phy-cells 1
- Added xlate function to get phy using phandle
Add DT binding document for Stingray USB PHY.
Signed-off-by: Srinath Mannam
---
.../bindings/phy/brcm,stingray-usb-phy.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt
diff --git
On Tue, Mar 12, 2019 at 8:26 AM Jerome Glisse wrote:
>
> On Mon, Mar 11, 2019 at 08:13:53PM -0700, Dan Williams wrote:
> > On Thu, Mar 7, 2019 at 10:56 AM Jerome Glisse wrote:
> > >
> > > On Thu, Mar 07, 2019 at 09:46:54AM -0800, Andrew Morton wrote:
> > > > On Tue, 5 Mar 2019 20:20:10 -0800 Dan
> > > Some Wilco devices do not support a keyboard backlight. This
> > > is checked in probe(), and in this case the sysfs entry will
> > > not appear, and everything will behave normally.
> >
> > It would be even better if we did not register platform device if EC
> > does not support backlight.
On Wed, Feb 27, 2019 at 11:27:22AM -0600, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add peripheral bindings for Stratix10 EDAC to capture
> the differences between the ARM64 and ARM32 architecture.
What's the difference? Sounds like 2 different chips, so Stratix10 or
s10 is
Hi,
I hit the following issue when running syzkaller in arm64. It is hardly to
reproduce the issue by the attached log.
[ 206.633857] Injecting memory failure for pfn 0x38c7e0 at process virtual
address 0x201e
[ 206.766875] WARNING: CPU: 1 PID: 738 at mm/rmap.c:1571
On 3/12/2019 8:42 AM, Enrico Weigelt, metux IT consult wrote:
> On 12.03.19 12:37, Thierry Reding wrote:
>
>> The driver currently doesn't request the memory described in the
>> resource, so technically you're changing behaviour here and with your
>> change the driver could now fail if
On Tue, 12 Mar 2019 01:16:28 -0500
Kangjie Lu wrote:
> create_singlethread_workqueue may fail and return NULL. The fix
> checks if it is NULL to avoid NULL pointer dereference.
> Also, the fix moves the call of create_singlethread_workqueue
> earlier to avoid resource-release issues.
>
>
On Wed, Feb 27, 2019 at 11:27:21AM -0600, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Fix Stratix10 ECC bindings to specify only the single
> bit error. On Stratix10 double bit errors are handled
> as SErrors instead of interrupts.
> Indicate the differences between the ARM64 and
On Tue 12-03-19 16:35:06, Oscar Salvador wrote:
[...]
> One thing I noticed when looking at start_isolate_page_range and
> undo_isolate_page_range functions, is that start_isolate_page_range increments
> the number of isolated pageblocks, while undo_isolate_page_range does the
> counter
> part.
On Tue, Mar 12, 2019 at 11:35:29AM -0400, Jerome Glisse wrote:
> > > > Yes you now have the filesystem as well as the GUP pinner claiming
> > > > authority over the contents of a single memory segment. Maybe better not
> > > > allow that?
> > >
> > > This goes back to regressing existing driver
Hi Rocky,
On Tue, Mar 12, 2019 at 05:01:59PM +0800, rjl...@codeaurora.org wrote:
> 在 2019-03-09 02:52，Matthias Kaehlcke 写道：
> > On Fri, Mar 08, 2019 at 10:43:14AM +0530, Balakrishna Godavarthi wrote:
> > > Hi Matthias,
> > >
> > > On 2019-03-08 02:12, Matthias Kaehlcke wrote:
> > > > Hi
This driver has been converted to use regulator core's simplified DT
parsing code. So the match_init_data/match_of_node functions are not
necessary now, remove them.
Signed-off-by: Axel Lin
---
drivers/regulator/max14577-regulator.c | 55 --
1 file changed, 55
Hi,
On Mon, Mar 11, 2019 at 09:43:36PM +0300, Sergey Suloev wrote:
> according to MIPI DSI spec chapter 8.8.2 the EoTp packet can be enabled or
> disabled on the protocol level.
> It seems like that it might be required for the panel I am working on (Himax
> HX8379A-based panel).
> Here is some
On 12-Mar 16:20, Peter Zijlstra wrote:
> On Fri, Feb 08, 2019 at 10:05:40AM +, Patrick Bellasi wrote:
> > +/* Integer ceil-rounded range for each bucket */
> > +#define UCLAMP_BUCKET_DELTA ((SCHED_CAPACITY_SCALE / UCLAMP_BUCKETS) + 1)
>
> Uhm, should that not me ((x+y-1)/y), aka.
On Tue, 26 Feb 2019 16:04:36 +0100, Artur Rojek wrote:
> Add documentation for the "status-gpios" property.
> Update the "gpios" property with a valid example.
>
> Signed-off-by: Artur Rojek
> ---
>
> Changes:
>
> v2: - add a better description for the "status-gpios" property,
> - add
Nianyao,
Please do not send patches as HTML. Or any email as HTML. Please make
sure that you only send plain text emails on any mailing list (see point
#6 in Documentation/process/submitting-patches.rst).
On 12/03/2019 12:22, Tangnianyao (ICT) wrote:
> In gicv4, direct vlpi may be forward to PE
Use regulator core's simplified DT parsing code to simply the driver
implementation.
Signed-off-by: Axel Lin
---
drivers/regulator/da9055-regulator.c | 67 +++-
1 file changed, 6 insertions(+), 61 deletions(-)
diff --git a/drivers/regulator/da9055-regulator.c
Use regulator core's simplified DT parsing code to simply the driver
implementation.
Signed-off-by: Axel Lin
---
Hi,
I don't have this h/w, so please help testing it.
Thanks,
Axel
drivers/regulator/da9052-regulator.c | 33 +---
1 file changed, 6 insertions(+), 27
Andy Shevchenko writes:
> On Fri, Mar 1, 2019 at 9:14 PM Mans Rullgard wrote:
>>
>> The charlcd driver currently flashes the backlight once on init.
>> This may not be desirable. Thus, add options for turning the
>> backlight off or on as well.
>>
>> Signed-off-by: Mans Rullgard
>> ---
>>
On Tue, Mar 12, 2019 at 04:11:36PM +0100, Miguel Ojeda wrote:
> On Tue, Mar 12, 2019 at 3:44 PM Andy Shevchenko
> wrote:
> >
> > I have found a memory leak in hd44780 and it becomes that we have no
> > counterpart to charlcd_alloc() that developers can easily miss.
>
> Side-note now that I see
On Mon, 4 Mar 2019 17:36:46 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> Replace hist_err() and hist_err_event() with tracing_log_err() from
> the new tracing error_log mechanism.
>
> Also add a couple related helper functions and remove most of the old
> hist_err()-related code.
>
>
On Fri, Mar 1, 2019 at 9:14 PM Mans Rullgard wrote:
>
> The charlcd driver currently flashes the backlight once on init.
> This may not be desirable. Thus, add options for turning the
> backlight off or on as well.
>
> Signed-off-by: Mans Rullgard
> ---
> drivers/auxdisplay/Kconfig | 21
On 12.03.19 12:37, Thierry Reding wrote:
> The driver currently doesn't request the memory described in the
> resource, so technically you're changing behaviour here and with your
> change the driver could now fail if somebody else has already claimed
> the memory.
hmm, using w/o
--
Goedendag,
Het is ons een genoegen u te schrijven met betrekking tot het
verstrekken van leningen per postadvertentie. Simple Federal Credit
Union, We opereren onder een korte, duidelijke en begrijpelijke algemene
voorwaarden. We verstrekken leningen tegen een lage rente van 3%.
On Tue, Mar 12, 2019 at 07:42:46AM -0700, James Bottomley wrote:
> On Tue, 2019-03-12 at 14:50 +0200, Jarkko Sakkinen wrote:
> > On Mon, Mar 11, 2019 at 05:27:43PM -0700, James Bottomley wrote:
> > > On Mon, 2019-03-11 at 16:54 -0700, Calvin Owens wrote:
> > > > e're having lots of problems with
On Tue 12-03-19 16:33:15, Michal Hocko wrote:
> On Tue 12-03-19 08:25:41, Matthew Wilcox wrote:
> > On Tue, Mar 12, 2019 at 09:05:32AM +0100, Michal Hocko wrote:
> > > On Mon 11-03-19 15:15:35, Suren Baghdasaryan wrote:
> > > > Yeah, killing speed is a well-known problem which we are considering
>
On Tue, Mar 12, 2019 at 10:05:52AM -0500, Aditya Pakki wrote:
> saved-context in byt_gpio_probe is allocated via devm_kcalloc and is
> used without checking for NULL in later functions. This patch avoids
> such a scenario.
>
Thanks.
I take it to our branch after merge window will be finished.
>
On Tue, Mar 12, 2019 at 11:22:46PM +0800, Icenowy Zheng wrote:
> Introduce the GPIO pins that is only available on V3 (not on V3s) to the
> V3 pinctrl driver.
>
> Signed-off-by: Icenowy Zheng
> ---
> drivers/pinctrl/sunxi/pinctrl-sun8i-v3.c | 291 +--
>
On Tue, Mar 12, 2019 at 10:56:08AM -0400, Steven Rostedt wrote:
> On Tue, 12 Mar 2019 07:09:23 -0700
> "Paul E. McKenney" wrote:
>
> > On Tue, Mar 12, 2019 at 05:25:28PM +0530, Neeraj Upadhyay wrote:
> > > On 3/12/19 7:20 AM, Steven Rostedt wrote:
> > > >On Fri, 8 Mar 2019 15:16:18 +0530
> >
>Subject: [PATCH] infiniband: i40iw: fix potential NULL pointer dereferences
>
>alloc_ordered_workqueue may fail and return NULL. Let's check its return value
>to ensure it is not NULL so as to avoid potential NULL pointer dereferences.
>
>Signed-off-by: Kangjie Lu
>---
>
On Tue, Mar 12, 2019 at 04:52:07AM +, Christopher Lameter wrote:
> On Fri, 8 Mar 2019, Jerome Glisse wrote:
>
> > >
> > > It would good if that understanding would be enforced somehow given the
> > > problems
> > > that we see.
> >
> > This has been discuss extensively already. GUP usage is
On Sun, Mar 10, 2019 at 04:01:02PM -0400, Qian Cai wrote:
> The commit f1dd2cd13c4b ("mm, memory_hotplug: do not associate hotadded
> memory to zones until online") introduced move_pfn_range_to_zone() which
> calls memmap_init_zone() during onlining a memory block.
> memmap_init_zone() will reset
On Tue 12-03-19 08:25:41, Matthew Wilcox wrote:
> On Tue, Mar 12, 2019 at 09:05:32AM +0100, Michal Hocko wrote:
> > On Mon 11-03-19 15:15:35, Suren Baghdasaryan wrote:
> > > Yeah, killing speed is a well-known problem which we are considering
> > > in LMKD. For example the recent LMKD change to
The Allwinner V3/V3s/S3L/SoChip S3 Ethernet MAC and internal PHY is quite
similar to the ones on Allwinner H3, except for V3s the external MII is
not wired out.
Add ethernet support to V3/V3s/S3/S3L.
Signed-off-by: Icenowy Zheng
---
arch/arm/boot/dts/sun8i-v3.dtsi | 13
On Tue, Mar 12, 2019 at 04:07:37PM +0100, Geert Uytterhoeven wrote:
> Hi Andy,
>
> On Tue, Mar 12, 2019 at 3:44 PM Andy Shevchenko
> wrote:
> > In order to be more particular in names, rename to_priv() macro
> > to charlcd_to_priv().
>
> As this is a macro, not a function, the name doesn't end
On 12/03/2019 14:25, Sameer Pujar wrote:
> Enable aconnect, adma and agic for Tegra Jetson TX1.
>
> Signed-off-by: Sameer Pujar
> ---
> arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts | 12
> 1 file changed, 12 insertions(+)
>
> diff --git
On 12/03/2019 14:34, Sameer Pujar wrote:
> aconnect bus driver is using pm_clk_*() for managing required clocks. With
> this, clocks seem to be always ON. This happens because, the clock prepare
> count is incremented in pm_clock_acquire() which is called during device
> probe(). The count is
On Mon, Mar 11, 2019 at 08:13:53PM -0700, Dan Williams wrote:
> On Thu, Mar 7, 2019 at 10:56 AM Jerome Glisse wrote:
> >
> > On Thu, Mar 07, 2019 at 09:46:54AM -0800, Andrew Morton wrote:
> > > On Tue, 5 Mar 2019 20:20:10 -0800 Dan Williams
> > > wrote:
> > >
> > > > My hesitation would be
On Tue, Mar 12, 2019 at 09:05:32AM +0100, Michal Hocko wrote:
> On Mon 11-03-19 15:15:35, Suren Baghdasaryan wrote:
> > Yeah, killing speed is a well-known problem which we are considering
> > in LMKD. For example the recent LMKD change to assign process being
> > killed to a cpuset cgroup
Hi Enrico,
On Mon, Mar 11, 2019 at 2:21 PM Enrico Weigelt, metux IT consult
wrote:
>
> Formatting of Kconfig files doesn't look so pretty, so let the
> Great White Handkerchief come around and clean it up.
I am all for humor in the right places, but this does not even explain
why this is being
On 12/03/2019 14:35, Sameer Pujar wrote:
> Usage of pm_clk_*() results in non-zero prepare_count for clocks and hence
> module clocks remain ON always. This is not desired as it will leak power
> unncessarily. This patch replaces pm_clk_*() with devm_clk_*() interface.
Technically, this is not
On Tue, 12 Mar 2019 05:08:30 -0400
valdis.kletni...@vt.edu wrote:
> On Tue, 12 Mar 2019 04:58:32 -0400, "Valdis Klētnieks" said:
> >
> > CC kernel/trace/trace_kprobe.o
> > kernel/trace/trace_kprobe.c:41: warning: cannot understand function
> > prototype: 'struct trace_kprobe '
> >
> >
On Tue, 12 Mar 2019 08:14:52 -0700
Randy Dunlap wrote:
> > NACK.
> >
> > This isn't a kernel doc comment, and I don't want to make it one when
> > it is not. Just ignore that warning.
> >
> > -- Steve
>
> Huh? The patch doesn't do that -- it does the opposite of that.
> I.e., begin a
On Tue, Mar 12, 2019 at 11:05:14AM -0400, Joel Fernandes wrote:
> On Mon, Mar 11, 2019 at 03:29:03PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 11, 2019 at 09:39:39AM -0400, Joel Fernandes wrote:
> > > On Wed, Aug 29, 2018 at 03:20:34PM -0700, Paul E. McKenney wrote:
> > > > RCU's dyntick-idle
On Fri, Feb 08, 2019 at 10:05:40AM +, Patrick Bellasi wrote:
> +/* Integer ceil-rounded range for each bucket */
> +#define UCLAMP_BUCKET_DELTA ((SCHED_CAPACITY_SCALE / UCLAMP_BUCKETS) + 1)
Uhm, should that not me ((x+y-1)/y), aka. DIV_ROUND_UP(x,y) ?
The above would give 4 for 9/3, which is
axp20x_build_funcs_groups allocates groups via devm_kcalloc and tries to
dereference without checking for NULL. This patch avoids such a
scenario.
Signed-off-by: Aditya Pakki
---
drivers/pinctrl/pinctrl-axp209.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 2019-03-12, Petr Mladek wrote:
> Per-console kthread sounds interesting but there is the problem with
> reliability. I mean that kthread need not get scheduled.
>
> Some of these problems might get solved by the per-console loglevel
> patchset.
>
> Sigh, any feature might be useful in some
No problem. In a previous patch I had one for each item, but I thought
it could be packed in a single one - and avoid '[PATCH n/m]'.
Thanks.
On 3/12/19, Dan Carpenter wrote:
> On Tue, Mar 12, 2019 at 11:39:13AM -0300, Guilherme T Maeoka wrote:
>> From: Guilherme T Maeoka
>>
>> Fix coding style
Hi Geert,
On 3/11/19 4:03 AM, Geert Uytterhoeven wrote:
[ snip ]
OK.
Now about the actual solution: what is your opinion on embedding e.g.
a squashfs image in the kernel instead, which would be a more generic
solution, not adding more ABI to /proc?
I'm not familiar enough with the
On 3/12/19 8:01 AM, Steven Rostedt wrote:
> On Tue, 12 Mar 2019 04:58:32 -0400
> "Valdis Klētnieks" wrote:
>
>> CC kernel/trace/trace_kprobe.o
>> kernel/trace/trace_kprobe.c:41: warning: cannot understand function
>> prototype: 'struct trace_kprobe '
>>
>> The real problem is that a
Linus,
The following changes since commit a3b22b9f11d9fbc48b0291ea92259a5a810e9438:
Linux 5.0-rc7 (2019-02-17 18:46:40 -0800)
are available in the Git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-5.1-rc1
for you to fetch changes up to
Em Mon, Mar 11, 2019 at 10:30:45PM -0700, Song Liu escreveu:
> This patch enables perf-record to save btf information as headers to
> perf.data A new header type HEADER_BPF_BTF is introduced for this data.
>
> Signed-off-by: Song Liu
> ---
> tools/perf/util/header.c | 101
Linus,
The following changes since commit 1c163f4c7b3f621efff9b28a47abb36f7378d783:
Linux 5.0 (2019-03-03 15:21:29 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-5.1-rc1
for you to fetch changes up to
801 - 900 of 1231 matches
Mail list logo
