On Tue, Oct 09, 2018 at 11:24:26AM +0200, Juri Lelli wrote:
> The main concerns I have with the current approach is that, being based
> on mutex.c, it's both
>
> - not linked with futexes
> - not involving "legacy" priority inheritance (rt_mutex.c)
>
> I believe one of the main reasons Peter st
On Mon, Oct 08, 2018 at 01:41:09PM -0700, David Rientjes wrote:
> On Fri, 5 Oct 2018, Andrea Arcangeli wrote:
>
> > I tried to add just __GFP_NORETRY but it changes nothing. Try it
> > yourself if you think that can resolve the swap storm and excessive
> > reclaim CPU overhead... and see if it wor
> -Original Message-
> From: Boris Brezillon
> Sent: 2018年9月28日 15:19
> To: Chuanhua Han
> Cc: broo...@kernel.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; e...@deif.com
> Subject: Re: [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw function
>
> On Fri, 28 Sep 2018
/linux/commits/john-hubbard-gmail-com/get_user_pages-and-RDMA-first-steps/20181009-152159
config: x86_64-randconfig-s4-10091707 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new
Start populating /sys/hypervisor with KVM entries when we're running on
KVM. This is to replicate functionality that's available when we're
running on Xen.
Let's start with /sys/hypervisor/uuid, which users prefer over
/sys/devices/virtual/dmi/id/product_uuid as a way to recognize a virtual
machin
On Thu, 27 Sep 2018, Amelie Delaunay wrote:
> STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
> using I2C for communication with the main MCU. Main features are:
> - 16 fast GPIOs individually configurable in input/output
> - 8 alternate GPIOs individually configurable in
On Thu, 27 Sep 2018, Amelie Delaunay wrote:
> This patch adds documentation of device tree bindings for the
> STMicroelectronics Multi-Function eXpander (STMFX) MFD core.
>
> Signed-off-by: Amelie Delaunay
> Reviewed-by: Linus Walleij
> ---
> Documentation/devicetree/bindings/mfd/stmfx.txt | 2
On 09/10/18 11:44, Peter Zijlstra wrote:
> On Tue, Oct 09, 2018 at 11:24:26AM +0200, Juri Lelli wrote:
> > The main concerns I have with the current approach is that, being based
> > on mutex.c, it's both
> >
> > - not linked with futexes
> > - not involving "legacy" priority inheritance (rt_mut
ping
thanks,
jirka
On Wed, Oct 03, 2018 at 09:20:46AM +0200, Jiri Olsa wrote:
> This reverts commit ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7.
>
> Michael reported an issue with oversized terms values assignment
> and I noticed there was actually a misunderstanding of the max
> value check in the
On Thu, Oct 04, 2018 at 10:20:39AM +0100, John Garry wrote:
SNIP
> > We synthesize an update event that needs to touch the evsel
> > id array, which is not defined at that time. Fixing this by
> > forcing the id allocation for events with theeir own cpus.
> >
> > Reported-by: John Garry
> > Lin
On 2018/10/09 16:50, Michal Hocko wrote:
> On Tue 09-10-18 08:35:41, Michal Hocko wrote:
>> [I have only now noticed that the patch has been reposted]
>>
>> On Mon 08-10-18 18:27:39, Tetsuo Handa wrote:
>>> On 2018/10/08 17:38, Yong-Taek Lee wrote:
> [...]
Thank you for your suggestion. But i
On Wed, Oct 03, 2018 at 07:45:50AM -0700, Andi Kleen wrote:
> > note there's couple of changes that actually changed
> > the number completely, like:
> >
> > -"Filter": "edge=1,filter_band2=4000",
> > +"Filter": "edge=1,filter_band2=30",
>
> Thanks. Looks good. I'll fix the script
Hi Kishon,
>-Original Message-
>From: Kishon Vijay Abraham I [mailto:kis...@ti.com]
>Sent: Tuesday, October 09, 2018 1:18 PM
>To: Anurag Kumar Vulisha ; robh...@kernel.org;
>mark.rutl...@arm.com; Michal Simek ;
>vivek.gau...@codeaurora.org
>Cc: v.anuragku...@gmail.com; Ajay Yugalkishore Pa
Randy Dunlap writes:
> On 10/8/18 3:03 AM, Punit Agrawal wrote:
>> Arm v8 architecture supports multiple page sizes - 4k, 16k and
>> 64k. Based on the active page size, the Linux port supports
>> corresponding hugepage sizes at PMD and PUD(4k only) levels.
>>
>> In addition, the architecture als
On 2018-10-08 9:21 p.m., Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/sched/cls_u32.c
between commit:
6d4c407744dd ("net: sched: cls_u32: fix hnode refcounting")
from the net tree and commit:
a030598690c6 ("net: sched: cls_u32
On Tue, 9 Oct 2018 09:52:23 +
Chuanhua Han wrote:
> 1. In the dspi driver (spi controller), bits_per_word
> (dspi->bits_per_word = transfer->bits_per_word) passed from the upper
> layer (spi-mem.c) is used. In this way, I can only assign the
> appropriate value of transfer->bits_per_word befo
On Thu, 27 Sep 2018, Nathan Chancellor wrote:
> On Wed, Sep 26, 2018 at 08:33:17PM -0700, Nathan Chancellor wrote:
> > Clang warns:
> >
> > drivers/mfd/cros_ec_dev.c:509:40: warning: variable 'cros_ec_id' is not
> > needed and will not be emitted [-Wunneeded-internal-declaration]
> > static const
On Thu, 27 Sep 2018, Emil Karlson wrote:
> Commit 57e94c8b974db2d83c60e1139c89a70806abbea0 caused cros-ec keyboard events
> be truncated on many chromebooks so that Left and Right keys on Column 12 were
> always 0. This commit fixes the issue by restoring the old semantics when the
> protocol vers
Hi Shawn,
> On Fri, Sep 28, 2018 at 12:26:55AM +0200, Lukasz Majewski wrote:
> > Add Device Tree binding document for Liebherr's BK4 external SPI
> > bus.
> >
> > Signed-off-by: Lukasz Majewski
>
> There should really be a patch series consisting of this one and
> spidev change [1].
>
> Sinc
> -Original Message-
> From: Boris Brezillon
> Sent: 2018年10月9日 18:05
> To: Chuanhua Han
> Cc: broo...@kernel.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; e...@deif.com
> Subject: Re: [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw function
>
> On Tue, 9 Oct 2018
On Sat, 30 Jun 2018, Vignesh R wrote:
> Currently tscadc MFD is marked as wakeup capable which incorrect
> because, its actually touch event by child TSC device that wakes up the
> system. Therefore, remove device_init_wakeup() call that marks TSCADC
> device as wakeup capable in favor of moving t
On Sat, 30 Jun 2018, Vignesh R wrote:
> If a child device like touchscreen is wakeup capable, then keep ADC
> interface on, so that a touching resistive screen will generate wakeup
> event to the system.
>
> Signed-off-by: Vignesh R
> ---
> drivers/mfd/ti_am335x_tscadc.c | 13 +
> 1
On Sat, 30 Jun 2018, Vignesh R wrote:
> Instead of TSCADC MFD device, mark TSC as wakeup source and change all
> wakeup related PM calls to operate on TSC device.
>
> Signed-off-by: Vignesh R
> ---
> drivers/input/touchscreen/ti_am335x_tsc.c | 16 +++-
> 1 file changed, 11 insertion
On Sat, 30 Jun 2018, Vignesh R wrote:
> Parent MFD device takes care of enabling ADC interface whenever
> touchscreen is marked wakeup capable. Therefore, unconditionally disable
> ADC interface during system suspend to save power in case of system with
> just ADC and no TSC.
>
> Signed-off-by: V
On Sat, 30 Jun 2018, Vignesh R wrote:
> On AM335x, ti_am335x_tsc can wake up the system from suspend, mark the
> IRQ as wakeup capable, so that device irq is not disabled during system
> suspend.
>
> Signed-off-by: Vignesh R
> ---
> drivers/input/touchscreen/ti_am335x_tsc.c | 6 ++
> 1 file
On Tue, Oct 9, 2018 at 6:24 AM Colin King wrote:
>
> From: Colin Ian King
>
> Currently the range check on the port index is off-by-one and a potential
> out of bounds write can occur on priv->ports[i]. Fix this by checking the
> maximum port using >= INNO_PHY_PORT_NUM rather than > INNO_PHY_PORT
Commit-ID: cf089611f4c446285046fcd426d90c18f37d2905
Gitweb: https://git.kernel.org/tip/cf089611f4c446285046fcd426d90c18f37d2905
Author: Borislav Petkov
AuthorDate: Mon, 8 Oct 2018 10:05:20 +0200
Committer: Borislav Petkov
CommitDate: Tue, 9 Oct 2018 11:57:28 +0200
proc/vmcore: Fix i386
On 31.8.2018 15:30, Lothar Waßmann wrote:
> Michal Vokáč wrote:
>
>> On 31.8.2018 14:45, Lothar Waßmann wrote:
>>> Rob Herring wrote:
>>>
On Tue, Aug 21, 2018 at 04:38:52PM +0200, Michal Vokáč wrote:
> Output of the PWM block of i.MX SoCs is always zero volts when the block
On Tue, Oct 09, 2018 at 12:05:22PM +0200, Boris Brezillon wrote:
> On Tue, 9 Oct 2018 09:52:23 +
> Chuanhua Han wrote:
> > 1. In the dspi driver (spi controller), bits_per_word
> > (dspi->bits_per_word = transfer->bits_per_word) passed from the upper
> > layer (spi-mem.c) is used. In this way
Enjoy!
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git
ib-mfd-iio-input-v4.20
for you to fetch changes up to 7a39915b72
On Tue, Oct 09, 2018 at 06:11:03PM +0800, Chunhui Li wrote:
> From: "chunhui.li"
>
>kasan detect unwind_frame out-of-bounds error when one task
> dump another, log as below
> BUG: KASAN: out-of-bounds in unwind_frame+0x140/0x20c Read of
> size 8 at addr ffea1e2378e0 by task AnrMonitorThre
v5: Use READ_ONCE()/WRITE_ONCE()
move mount pointer struct init to bm_fill_super() and add smp_wmb()
remove useless NULL value init
add WARN_ON_ONCE()
v4: first user namespace is initialized with &init_binfmt_ns,
all new user namespaces are initialized with a NULL and use
the o
This patch allows to have a different binfmt_misc configuration
for each new user namespace. By default, the binfmt_misc configuration
is the one of the previous level, but if the binfmt_misc filesystem is
mounted in the new namespace a new empty binfmt instance is created and
used in this namespac
Commit-ID: 9d94e8b1d4f94a3c4cee5ad11a1be460cd070839
Gitweb: https://git.kernel.org/tip/9d94e8b1d4f94a3c4cee5ad11a1be460cd070839
Author: Peter Zijlstra (Intel)
AuthorDate: Wed, 3 Oct 2018 14:41:27 +0200
Committer: Borislav Petkov
CommitDate: Tue, 9 Oct 2018 12:30:25 +0200
x86/kaslr, ACP
On 10/09/2018 11:54 AM, Filippo Sironi wrote:
> Start populating /sys/hypervisor with KVM entries when we're running on
> KVM. This is to replicate functionality that's available when we're
> running on Xen.
>
> Let's start with /sys/hypervisor/uuid, which users prefer over
> /sys/devices/virtu
Hi Morimoto-san
Thanks for your feedback
On 2018/10/09 16:47, Kuninori Morimoto wrote:
Hi Jiada
Thanks for your feedback
1ch: (tdm_slots < 4) Basic mode, (tdm_slots >= 4) TDM Split mode
2ch: (2 <= tdm_slots < 8) Basic mode, (tdm_slots >= 8) TDM Ex-Split mode
4ch: (4 <= tdm_slots < 8) Basic
On Tuesday, October 9, 2018 12:26:48 AM CEST Rafael J. Wysocki wrote:
> On Tue, Oct 9, 2018 at 12:14 AM Doug Smythies wrote:
> >
> > On 2018.10.08 00:51 Rafael J. Wysocki wrote:
> > > On Mon, Oct 8, 2018 at 8:02 AM Doug Smythies wrote:
> > >>
> > >> On 2018.10.03 23:56 Rafael J. Wysocki wrote:
>
This commit adds DTS support for BK4 device from Liebherr. It
uses vf610 SoC from NXP.
Signed-off-by: Lukasz Majewski
---
Changes for v3:
- Rename regulator-vcc_3v3_mcu -> regulator-vcc3v3mcu
- Add a blank line between properties and node @ mdio
- Rename rtc and eeprom node's labels and names
-
On 2018-10-09 11:24:26 [+0200], Juri Lelli wrote:
> The main concerns I have with the current approach is that, being based
> on mutex.c, it's both
>
> - not linked with futexes
> - not involving "legacy" priority inheritance (rt_mutex.c)
>
> I believe one of the main reasons Peter started this
Chuanhua Han writes:
> 1. In the dspi driver (spi controller), bits_per_word (dspi->bits_per_word =
> transfer->bits_per_word) passed from the upper layer (spi-mem.c) is used.
> In this way, I can only assign the appropriate value of
> transfer->bits_per_word before passing to the controller, tha
* Yi Sun wrote:
> Follow PV spinlock mechanism to implement the callback functions
> to allow the CPU idling and kicking operations on Hyper-V.
> +#if defined(CONFIG_SMP)
> + smp_ops.smp_prepare_boot_cpu = hv_smp_prepare_boot_cpu;
> +#endif
What's wrong with using the common pattern of:
Xen PVH guests receive the address of the RSDP table from Xen. In order
to support booting a Xen PVH guest via Grub2 using the standard x86
boot entry we need a way for Grub2 to pass the RSDP address to the
kernel.
For this purpose expand the struct setup_header to hold the physical
address of the
In case the rsdp address in struct boot_params is specified don't try
to find the table by searching, but take the address directly as set
by the boot loader.
Signed-off-by: Juergen Gross
---
V3: use a generic retrieval function with a __weak annotated default
function (Ingo Molnar)
V4: chec
In the non-EFI boot path the ACPI RSDP table is currently found via
either EBDA or by searching through low memory for the RSDP magic.
This requires the RSDP to be located in the first 1MB of physical
memory. Xen PVH guests, however, get the RSDP address via the start of
day information block.
In
Commit-ID: 8ca2b56cd7da98fc8f8d787bb706b9d6c8674a3b
Gitweb: https://git.kernel.org/tip/8ca2b56cd7da98fc8f8d787bb706b9d6c8674a3b
Author: Waiman Long
AuthorDate: Wed, 3 Oct 2018 13:07:18 -0400
Committer: Ingo Molnar
CommitDate: Tue, 9 Oct 2018 09:56:33 +0200
locking/lockdep: Make class->
On Mon, Oct 08, 2018 at 12:57:51PM -0700, Josh Triplett wrote:
> On Mon, Oct 08, 2018 at 04:23:57PM -0300, Mauro Carvalho Chehab wrote:
> > Fully agreed on that. The same argument that we use for GPL 2 only
> > applies here: we should stick with an specific version of this it, in
> > a way that we
On 2018-10-05 20:10:35 [+0200], Andrea Parri wrote:
>
> Clearly not my topic..., but out of curiosity: What do you mean by
> "well-bounded" and "minimal"? Can you maybe point me to some doc.?
it means that the lock is not held for an arbitrary amount of time like
by processing a list with thous
On 23.8.2018 14:36, Lukasz Majewski wrote:
> Hi Michal,
>
>> On 23.8.2018 12:40, Lukasz Majewski wrote:
>>
>> Hi Lukasz, thanks for the reply!
>>> Hi Michal,
>>>
Output of the PWM block of i.MX SoCs is always zero volts when the
block is disabled. This can caue issues when inverted P
USLUGI REPETITORA 1-7 klass.
Nizkie ceni
2:07:54 PM
On Tue, Oct 9, 2018 at 7:50 AM Lukasz Majewski wrote:
>
> This commit adds DTS support for BK4 device from Liebherr. It
> uses vf610 SoC from NXP.
>
> Signed-off-by: Lukasz Majewski
Reviewed-by: Fabio Estevam
On Tue 09-10-18 19:00:44, Tetsuo Handa wrote:
> On 2018/10/09 16:50, Michal Hocko wrote:
[...]
> > Well, that is unfortunate indeed and it
> > breaks the OOM_SCORE_ADJ_MIN contract. There are basically two ways here
> > 1) do not care and encourage users to use a saner
On Thu 04-10-18 09:51:37, Dan Williams wrote:
> On Thu, Oct 4, 2018 at 12:48 AM Michal Hocko wrote:
> >
> > On Wed 03-10-18 19:15:24, Dan Williams wrote:
> > > Some data exfiltration and return-oriented-programming attacks rely on
> > > the ability to infer the location of sensitive data objects.
On 9 October 2018 at 09:54, Ludovic BARRE wrote:
> hi Ulf
>
> On 10/09/2018 09:30 AM, Ulf Hansson wrote:
>>
>> Applied for next, thanks!
>>
>> FYI, I made little fixup of the help text in the Kconfig for the last
>> patch.
>
>
> Thanks for your review.
> Did you had a feedback on Qcom platform tes
pr_debug_ratelimited tests the dynamic debug descriptor the old-fashioned
way, and doesn't utilize the static key/jump label implementation on
architectures that HAVE_JUMP_LABEL. Use the DYNAMIC_DEBUG_BRANCH which
is defined appropriately.
Acked-by: Petr Mladek
Acked-by: Jason Baron
Cc: Steven R
For built-in modules, we're already reusing the passed-in string via
kstrdup_const(). But for actual modules (i.e. when we're called from
dynamic_debug_setup in module.c), the passed-in string (which points
at the name[] array inside struct module) is also
guaranteed to live at least as long as the
For symmetry with ddebug_remove_module, and to avoid a bit of ifdeffery
in module.c, move the declaration of ddebug_add_module inside #if
defined(CONFIG_DYNAMIC_DEBUG) and add a corresponding no-op stub in the
#else branch.
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
---
include/linux
This serves two purposes: First, we get a diagnostic if (though
extremely unlikely), any of the calls of ddebug_add_module for built-in
code fails, effectively disabling dynamic_debug. Second, I want to make
struct _ddebug opaque, and avoid accessing any of its members outside
dynamic_debug.[ch].
From: Dinh Nguyen
Turn on these ARM and PL310 errata for SoCFPGA:
ARM_ERRATA_754322
ARM_ERRATA_764369
ARM_ERRATA_775420
PL310_ERRATA_588369
PL310_ERRATA_727915
PL310_ERRATA_753970
PL310_ERRATA_769419
Signed-off-by: Dinh Nguyen
Signed-off-by: Clément Péron
---
v2:
- Remove fixes ta
v2: Added various acks/reviews. I'll follow up with rewriting the x86
part as asm macros once that work is in mainline.
Patches 15, 16 are in next-20181009; in hindsight I should probably
have asked Rafael not to pick those. Patch 17 textually depend on
those, and patch 19 removes the .
With coming changes on x86-64, all dynamic debug descriptors in a
translation unit must have distinct names. The macro _dynamic_func_call
takes care of that. No functional change.
Cc: linux-a...@vger.kernel.org
Acked-by: Rafael J. Wysocki
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
--
Most invocations of DEFINE_DYNAMIC_DEBUG_METADATA happen through
"public" macros such as pr_debug or netdev_dbg, which have been updated
to ensure they pass a unique identifier to use as the name for the
struct _ddebug instance. But it is still possible that someone invokes
DEFINE_DYNAMIC_DEBUG_MET
When we introduce compact versions of these pointers (a la
CONFIG_GENERIC_BUG_RELATIVE_POINTERS), all access to these members must
go via appropriate accessors. This just mass-converts dynamic_debug.c to
use the new accessors.
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
---
lib/dynami
Similar to how x86_64 uses bug_entry-relative pointers to reduce
sizeof(struct bug_entry), the same thing can now be done for struct
_ddebug, saving 16 bytes for each of those (i.e., each pr_debug, dev_dbg
etc. in a CONFIG_DYNAMIC_DEBUG kernel).
Note the use of .ifndef/.endif in asm to avoid
fs/a
From: Dinh Nguyen
When doing a software reboot, all peripheral clocks must get turned on for the
L3 interconnect to work.
This code is needed when doing a "reboot" from user-space and a peripheral
clock as been gated off. Why would a peripheral clock get gated? An example
use case would be a .ko
These will be useful when defining the contents of (a struct containing)
a static key in inline assembly.
Cc: x...@kernel.org
Reviewed-by: Ingo Molnar
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
---
arch/x86/include/asm/jump_label.h | 18 ++
include/linux/jump_label.h
Based on the same idea for struct bug_entry, an architecture can opt-in
to use relative pointers in struct _ddebug. It only makes sense for 64
bit architectures, where one saves 16 bytes per entry (out of 40 or 56,
depending on CONFIG_JUMP_LABEL). The architecture is responsible for
providing a sui
Properly initializing a struct containing bitfields in assembly is
hard. Instead, merge lineno and flags to a single unsigned int, which we
mask manually. This should not cause any worse code than what gcc would
need to generate for accessing the bitfields anyway.
Actually, on 64 bit, there is a f
Chuanhua Han writes:
>> -Original Message-
>> From: Boris Brezillon
>> Sent: 2018年10月9日 18:05
>> To: Chuanhua Han
>> Cc: broo...@kernel.org; linux-...@vger.kernel.org;
>> linux-kernel@vger.kernel.org; e...@deif.com
>> Subject: Re: [PATCH 1/2] spi: spi-mem: Add the spi_set_xfer_bpw funct
First, the btrfs_debug macros open-code (one possible definition of)
DYNAMIC_DEBUG_BRANCH, so they don't benefit from the HAVE_JUMP_LABEL
optimization.
Second, changes on x86-64 later in this series require that all struct
_ddebug descriptors in a translation unit use distinct identifiers.
Using
If CONFIG_DYNAMIC_DEBUG is not set, acpi_handle_debug directly invokes
acpi_handle_printk (if DEBUG) or does a no-printk (if !DEBUG). So this
macro is never used.
Cc: linux-a...@vger.kernel.org
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
---
include/linux/acpi.h | 3 ---
1 file change
dynamic debug may be implemented via static keys, but ACPI is missing
out on that runtime benefit since it open-codes one possible definition
of DYNAMIC_DEBUG_BRANCH.
Cc: linux-a...@vger.kernel.org
Acked-by: Jason Baron
Signed-off-by: Rasmus Villemoes
---
include/linux/acpi.h | 2 +-
1 file cha
These functions are unused externally, removed them and declare
the one used locally as static.
Signed-off-by: Clément Péron
---
arch/arm/mach-socfpga/core.h| 2 --
arch/arm/mach-socfpga/socfpga.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/mach-socfpga/cor
The only caller of ddebug_{add,remove}_module outside dynamic_debug.c is
kernel/module.c, which is obviously not itself modular (though it would
be an interesting exercise to make that happen...). I also fail to see
how these interfaces can be used by modules, in-tree or not.
Acked-by: Jason Baron
Commit-ID: 4de1a293a08bdf8ec1530e02163930ac86f80ea2
Gitweb: https://git.kernel.org/tip/4de1a293a08bdf8ec1530e02163930ac86f80ea2
Author: Lance Roy
AuthorDate: Tue, 2 Oct 2018 22:38:57 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 9 Oct 2018 13:19:28 +0200
futex: Replace spin_is_lock
For the upcoming 'define the _ddebug descriptor in assembly', we need
all the descriptors in a translation unit to have distinct
names (because asm does not understand C scope). The easiest way to
achieve that is as usual with an extra level of macros, passing the
identifier to use to the innermost
On Thu 04-10-18 09:44:35, Dan Williams wrote:
> Hi Michal,
>
> On Thu, Oct 4, 2018 at 12:53 AM Michal Hocko wrote:
> >
> > On Wed 03-10-18 19:15:18, Dan Williams wrote:
> > > Changes since v1:
> > > * Add support for shuffling hot-added memory (Andrew)
> > > * Update cover letter and commit messa
Changes on x86-64 later in this series require that all struct _ddebug
descriptors in a translation unit uses distinct identifiers. Realize
that for pr_debug_ratelimited by generating such an identifier via
__UNIQUE_ID and pass that to an extra level of macros.
No functional change.
Acked-by: Pet
Now that we store the passed-in string directly in ddebug_add_module, we
can use pointer equality instead of strcmp. This is a little more
efficient, but more importantly, this also makes the code somewhat more
correct:
Currently, if one loads and then unloads a module whose name happens to
match
Instead of defining DEFINE_DYNAMIC_DEBUG_METADATA in terms of a helper
DEFINE_DYNAMIC_DEBUG_METADATA_KEY, that needs another helper
dd_key_init to be properly defined, just make the various #ifdef
branches define a _DPRINTK_KEY_INIT that can be used directly, similar
to _DPRINTK_FLAGS_DEFAULT.
Ack
Changes on x86-64 later in this series require that all struct _ddebug
descriptors in a translation unit uses distinct identifiers. Realize
that for dev_dbg_ratelimited by generating such an identifier via
__UNIQUE_ID and pass that to an extra level of macros.
No functional change.
Reviewed-by: G
dev_dbg_ratelimited tests the dynamic debug descriptor the old-fashioned
way, and doesn't utilize the static key/jump label implementation on
architectures that HAVE_JUMP_LABEL. Use the DYNAMIC_DEBUG_BRANCH which
is defined appropriately.
Reviewed-by: Greg Kroah-Hartman
Acked-by: Jason Baron
Sig
Cyclone5 and Arria10 doesn't have the same memory map for UART1.
Split the SOCFPGA_UART1 into 2 options to allow debugging on UART1 for Cylone5.
Signed-off-by: Clément Péron
---
arch/arm/Kconfig.debug | 23 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/a
On Mon, Oct 08, 2018 at 01:45:13PM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 08, 2018 at 06:15:22PM +0200, Dmitry Vyukov wrote:
> > On Mon, Oct 8, 2018 at 6:12 PM, syzbot
> > wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:ae16eea39a86 Add linux-n
On 8.10.2018 20:21, Jolly Shah wrote:
> This patchset adds CCF compliant clock driver for ZynqMP.Clock driver queries
> supported clock information from firmware and regiters pll and output clocks
> with CCF.
>
> This patch series is earlier reveiwed as part of FW patchset
> (https://patchwork.
On Thu, 27 Sep 2018, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in hid_err error message
>
> Signed-off-by: Colin Ian King
> ---
> drivers/hid/hid-elan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hid/hid-elan.c b/driver
On 09. okt. 2018 11:21, Greg Kroah-Hartman wrote:
On Tue, Oct 09, 2018 at 05:21:31AM +0200, Andre Tomt wrote:
On 08. okt. 2018 20:29, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.13 release.
There are 168 patches in this series, all will be posted as a res
On Mon, Oct 8, 2018 at 5:44 PM Rajneesh Bhardwaj
wrote:
>
> Add myself and David as the new maintainers for Intel Telemetry driver.
>
There is no explanation why.
(Like previous one left the company, and / or you are doing set of the
drivers related to PMC where telemetry is part of, etc)
> Sign
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
Pu
On 10/9/18 12:51 PM, Sebastian Andrzej Siewior wrote:
>> The main concerns I have with the current approach is that, being based
>> on mutex.c, it's both
>>
>> - not linked with futexes
>> - not involving "legacy" priority inheritance (rt_mutex.c)
>>
>> I believe one of the main reasons Peter sta
Hi Jacek and Pavel,
On 5 October 2018 at 04:00, Jacek Anaszewski wrote:
> Hi Baolin,
>
> On 10/03/2018 03:21 AM, Baolin Wang wrote:
>> Hi Jacek,
>>
>> On 3 October 2018 at 04:25, Jacek Anaszewski
>> wrote:
>>> Hi Baolin,
>>>
>>> Thank you for the v14. We'll probably need v15, though :-)
>>>
>>>
- Original Message -
> Hi all,
>
> Commit
>
> b7f5a2cd27b7 ("GFS2: Flush the GFS2 delete workqueue before stopping the
> kernel threads")
>
> is missing a Signed-off-by from its committer.
>
> --
> Cheers,
> Stephen Rothwell
Fixed now. Sorry about that.
Regards,
Bob Peterson
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
Pu
On Tue, Oct 02, 2018 at 10:38:58PM -0700, Lance Roy wrote:
> lockdep_assert_held() is better suited to checking locking requirements,
> since it won't get confused when someone else holds the lock. This is
> also a step towards possibly removing spin_is_locked().
>
> Signed-off-by: Lance Roy
> Cc
[Sorry for being slow in responding but I was mostly offline last few
days]
On Tue 09-10-18 10:48:25, Mel Gorman wrote:
[...]
> This goes back to my point that the MADV_HUGEPAGE hint should not make
> promises about locality and that introducing MADV_LOCAL for specialised
> libraries may be more
Commit-ID: f726c4620df39055f060537a8ed183c18a2c504b
Gitweb: https://git.kernel.org/tip/f726c4620df39055f060537a8ed183c18a2c504b
Author: Yi Sun
AuthorDate: Thu, 27 Sep 2018 14:01:43 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 9 Oct 2018 14:14:49 +0200
x86/hyperv: Add GUEST_IDLE_MS
Commit-ID: 3a025de64bf89c84a79909069e3c24ad9e710d27
Gitweb: https://git.kernel.org/tip/3a025de64bf89c84a79909069e3c24ad9e710d27
Author: Yi Sun
AuthorDate: Mon, 8 Oct 2018 16:29:34 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 9 Oct 2018 14:21:39 +0200
x86/hyperv: Enable PV qspinloc
On 07.10.2018 21:36, Chris Clayton wrote:
> Hi again,
>
> I didn't think there was anything in 4.19-rc7 to fix this regression, but
> tried it anyway. I can confirm that the
> regression is still present and my network still fails when, after a resume
> from suspend (to ram or disk), I open my
>
On (10/09/18 10:42), Petr Mladek wrote:
> On Tue 2018-10-02 11:38:36, Sergey Senozhatsky wrote:
> > We have a proper 'overflow' check which tells us that we need to
> > split up existing cont buffer in separate records:
> >
> > if (cont.len + len > sizeof(cont.buf))
> > cont_flush(
On (10/09/18 10:39), Petr Mladek wrote:
> >
> > Signed-off-by: Sergey Senozhatsky
> > ---
> > kernel/printk/printk.c | 10 +++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
>
> The patch makes perfect sense. It looks a bit hacky but I can't
> think about any less hacky one.
>
> I w
On 09/10/18 13:56, Daniel Bristot de Oliveira wrote:
> On 10/9/18 12:51 PM, Sebastian Andrzej Siewior wrote:
> >> The main concerns I have with the current approach is that, being based
> >> on mutex.c, it's both
> >>
> >> - not linked with futexes
> >> - not involving "legacy" priority inheritan
101 - 200 of 710 matches
Mail list logo
