On 7/13/2018 1:33 PM, Wolfram Sang wrote:
BTW, to whom should I ask applying this patch? Should I send v2 after
adding your reviewed-by tag?
Not needed, thanks. I use 'patchwork' and this tool collects all the
tags for me. If I see a patch reviewed by a driver maintainer, I'll pick
it up in t
On Fri, 13 Jul 2018 12:26:05 +0900 Naoya Horiguchi
wrote:
> There's a race condition between soft offline and hugetlb_fault which
> causes unexpected process killing and/or hugetlb allocation failure.
>
> The process killing is caused by the following flow:
>
> CPU 0 CPU 1
Linus,
I2C has for you:
- one I2C core bugfix regarding bus recovery
- one driver bugfix for the tegra driver
- one typo correction
Please pull.
Thanks,
Wolfram
The following changes since commit 021c91791a5e7e85c567452f1be3e4c2c6cb6063:
Linux 4.18-rc3 (2018-07-01 16:04:53 -0700)
are
> BTW, to whom should I ask applying this patch? Should I send v2 after
> adding your reviewed-by tag?
Not needed, thanks. I use 'patchwork' and this tool collects all the
tags for me. If I see a patch reviewed by a driver maintainer, I'll pick
it up in the next queue.
signature.asc
Descriptio
On Fri, Jul 13, 2018 at 07:36:36AM +0800, Huang, Ying wrote:
> From: Huang Ying
>
> In this patch, locking related code is shared between huge/normal code
> path in put_swap_page() to reduce code duplication. And `free_entries
> == 0` case is merged into more general `free_entries !=
> SWAPFILE_
On Fri, Jul 13, 2018 at 07:36:33AM +0800, Huang, Ying wrote:
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 75c84aa763a3..160f78072667 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -270,7 +270,10 @@ static inline void cluster_set_null(struct
> swap_cluster_info *info)
>
> static
To clear a checkpatch issue removed the typedef of the enumeration TR_SELECT
this should not impact runtime code as it's only a coding style change.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/ieee80211.h | 4 ++--
drivers/staging/rtl8192u/ieee80211/rtl819x_BAProc.c
In struct TS_COMMON_INFO rename the member List to list. This clears the
checkpatch issue concerning CamelCase naming of variables.
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
.../rtl8192u/ieee80211/rtl819x_TSProc.c | 64 +--
2 fi
Rename the struct TS_COMMON_INFO member SetupTimer to setup_timer. This
clears the checkpatch issue with CamelCase variable names.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c | 8
2 file
Rename the struct TS_COMMON_INFO member variable TClasProc to
t_clas_proc. This change clears the checkpatch issue with CamelCase variable
names. There should be no impact on runtime execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
drivers/s
Rename the struct TS_COMMON_INFO member variable TClasNum to t_clas_num. This
change clears the checkpatch issue with CamelCase naming. There should be no
impact on runtime execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
drivers/staging/rtl
Rename the TS_COMMON_INFO structure's member TSpec to t_spec. This change
clears the checkpatch issue with CamelCase naming of variables. There should
be no impact on runtime execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_BAProc.c | 2 +-
drivers/staging/r
Rename the struct TS_COMMON_INFO member variable from TClass to t_class. This
change clears the checkpatch issue with CamelCase Variable names. There should
be no impact on runtime execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
drivers/sta
To clear a checkpatch issue removed the typedef of the structure
TS_COMMON_INFO.
This change removes the previous declaration, which defined two types, both
TS_COMMON_INFO and a pointer type PTS_COMMON_INFO:
typedef struct _TS_COMMON_INFO {
...
} TS_COMMON_INFO, *PTS_COMMON_INFO;
The poi
Attached C repro code as well as its kernel config. It takes about 10-30
seconds to reproduce.
C repro:
https://kiwi.cs.purdue.edu/static/race-fuzzer/null-ptr-deref-smc_ioctl.c
kernel config (v4.18-rc3):
https://kiwi.cs.purdue.edu/static/race-fuzzer/null-ptr-deref-smc_ioctl.c
[ 172.890255]
Rename the TX_COMMON_INFO structure's member Addr to addr. This change
clears the checkpatch issue with CamelCase naming. This is a coding style
change only and should not impact runtime execution.
Signed-off-by: John Whitmore
---
.../staging/rtl8192u/ieee80211/rtl819x_BAProc.c| 10 +
Rename the struct TS_COMMON_INFO member InactTimer to inact_timer.
This change clears the checkpatch issue with CamelCase naming. The change
should not have any impact on runtime execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/ieee80211/rtl819x_TS.h | 2 +-
drivers/stag
All coding style changes, but the second [2/10] is a bit more hairy then
most. The original code combined two typedef declarations into one with both
the structure and a pointer to the structure defined. I've totally removed the
pointer to the structure type since it uses Hungarian notation, which
pxrc_probe() calls usb_get_dev(), but there is no usb_put_dev()
anywhere in the driver.
The patch adds one to error handling code and to pxrc_disconnect().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/input/joystick/pxrc.c | 2 ++
Hi Baolin,
Thank you for the update.
On 07/13/2018 08:21 AM, Baolin Wang wrote:
From: Bjorn Andersson
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This adds a new optional operator that LED class dri
On Fri, 13 Jul 2018 09:24:44 -0400 Pavel Tatashin
wrote:
> On 07/13/2018 09:17 AM, Oscar Salvador wrote:
> > On Thu, Jul 12, 2018 at 04:37:26PM -0400, Pavel Tatashin wrote:
> >> +static void *sparsemap_buf __meminitdata;
> >> +static void *sparsemap_buf_end __meminitdata;
> >> +
> >> +void __ini
Linus,
Please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
# HEAD: 5e18e412973d6bb1804de1d4d30a891c774b006e clocksource:
arm_arch_timer: Set arch_mem_timer cpumask to cpu_possible_mask
A clocksou
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
# HEAD: 6e1d33b24a2b4aebcb05782e937ebc9a7a4a3f50 Merge tag
'perf-urgent-for-mingo-4.18-20180711' of
git://git.kernel.org/pub/scm/linux/kerne
On Fri, Jul 13, 2018 at 12:21 PM, Laura Abbott wrote:
> On 07/13/2018 08:30 AM, Olof Johansson wrote:
>>
>> Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
>> in particular. So, probe for whether it's available and use the previous
>> (linux) targets if it isn't.
>>
>
>
> For
Linus,
Please pull the latest efi-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
efi-urgent-for-linus
# HEAD: e296701800f30d260a66f8aa1971b5b1bc3d2f81 efi/x86: Fix mixed mode
reboot loop by removing pointless call to PciIo->Attributes()
Fix a U
On Fri, Jul 13, 2018 at 06:42:39PM +0200, Peter Zijlstra wrote:
>
> Hi Michael,
>
> On Fri, Jul 13, 2018 at 11:15:26PM +1000, Michael Ellerman wrote:
> > I reran some numbers today with some slightly updated tests.
> >
> > It varies quite a bit across machines and CPU revisions.
> >
> > On one
On 07/13/2018 12:40 PM, Arjan van de Ven wrote:
> On 7/13/2018 12:19 PM, patrickg wrote:
>> This RFC patch is intended to allow bypass CPUID, MSR and QuickPIT
>> calibration methods should the user desire to.
>>
>> The current ordering in ML x86 tsc is to calibrate in the order listed
>> above
On 07/13/2018 12:40 PM, Arjan van de Ven wrote:
> On 7/13/2018 12:19 PM, patrickg wrote:
>> This RFC patch is intended to allow bypass CPUID, MSR and QuickPIT
>> calibration methods should the user desire to.
>>
>> The current ordering in ML x86 tsc is to calibrate in the order listed
>> above
This RFC patch is intended to allow bypass CPUID, MSR and QuickPIT calibration
methods should the user desire to.
The current ordering in ML x86 tsc is to calibrate in the order listed above;
returning whenever there's a successful calibration. However there are certain
BIOS/HW Designs for ove
On 7/13/2018 12:19 PM, patrickg wrote:
This RFC patch is intended to allow bypass CPUID, MSR and QuickPIT calibration
methods should the user desire to.
The current ordering in ML x86 tsc is to calibrate in the order listed above;
returning whenever there's a successful calibration. However t
On 7/12/2018 1:41 AM, Brendan Higgins wrote:
On Mon, Jul 2, 2018 at 2:40 PM Jae Hyun Yoo
wrote:
This patch adjusts spinlock scope to make it wrap the whole irq
handler using a single lock/unlock which covers both master and
slave handlers.
Signed-off-by: Jae Hyun Yoo
---
drivers/i2c/busses
On 07/13/2018 08:30 AM, Olof Johansson wrote:
Not all toolchains have the baremetal elf targets, RedHat/Fedora ones
in particular. So, probe for whether it's available and use the previous
(linux) targets if it isn't.
For the Fedora toolchains:
Tested-by: Laura Abbott
Reported-by: Laura A
>> Dell - Internal Use - Confidential
>Really? To a public mailing list? odd...
Ha yea sorry - I was so excited to show my support, that I jumped the gun :)
On Fri, Jul 13, 2018 at 10:16:48AM -0700, Linus Torvalds wrote:
> On Fri, Jul 13, 2018 at 2:34 AM Will Deacon wrote:
> >
> > And, since we're stating preferences, I'll reiterate my preference towards:
> >
> > * RCsc unlock/lock
> > * RCpc release/acquire
>
> Yes, I think this woul
On Fri, Jul 13, 2018 at 06:49:04PM +, eugene@dell.com wrote:
> Dell - Internal Use - Confidential
Really? To a public mailing list? odd...
On Wed, Jul 11, 2018 at 4:29 AM, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Warn the user in case the performance can be significantly
> improved by switching to a 64-bit kernel.
...
> +#ifdef CONFIG_X86_32
> + if (boot_cpu_has(X86_FEATURE_PCID)) {
I'm a bit confused. Wouldn't the setu
On Fri, Jul 13, 2018 at 11:38:19AM -0700, Daniel Jordan wrote:
> On Fri, Jul 13, 2018 at 07:36:32AM +0800, Huang, Ying wrote:
> > @@ -1260,7 +1257,6 @@ static void swapcache_free(swp_entry_t entry)
> > }
> > }
> >
> > -#ifdef CONFIG_THP_SWAP
> > static void swapcache_free_cluster(swp_entry_
On 7/13/2018 11:12 AM, Brendan Higgins wrote:
On Fri, Jul 13, 2018 at 10:22 AM Jae Hyun Yoo
wrote:
On 7/12/2018 11:21 AM, Jae Hyun Yoo wrote:
On 7/12/2018 2:33 AM, Brendan Higgins wrote:
On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
wrote:
+ for (;;) {
+ if (!(readl
On Fri, Jul 13, 2018 at 6:13 AM Will Deacon wrote:
>
> Catalin's out enjoying the sunshine, so I'm sending the fixes for a couple
> of weeks (although there hopefully won't be any more!).
Never fear, I'm sure there won't be more than a couple of weeks of
sunshine in the UK this summer.
That's wh
On Fri, Jul 06, 2018 at 03:14:28PM -0700, Joe Perches wrote:
> On Fri, 2018-07-06 at 15:09 -0700, Joe Perches wrote:
> > On Fri, 2018-07-06 at 17:58 -0400, Don Zickus wrote:
> > > We have an internal use case of multiple MAINTAINER files, some folks have
> > > more rights to patches than others so
On 7/13/2018 11:02 AM, Brendan Higgins wrote:
On Thu, Jul 12, 2018 at 11:21 AM Jae Hyun Yoo
wrote:
On 7/12/2018 2:33 AM, Brendan Higgins wrote:
On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
wrote:
+/* Timeout for bus busy checking */
+#define BUS_BUSY_CHECK_TIMEOUT
Dell - Internal Use - Confidential
+1 from someone using Nuvoton's BMC SoC
-Original Message-
From: Alexander Amelkin [mailto:a.amel...@yadro.com]
Sent: Friday, July 13, 2018 10:14 AM
To: Andrew Jeffery; Benjamin Herrenschmidt; Rob Herring
Cc: Mark Rutland; devicet...@vger.kernel.org;
Dear Sir/Madam,
How are you doing today? My name is Billy Wilfred. I am California, United
States of America. I am a broker of Project Financing Firm who has cutting edge
and group capital fund, they can finance any lucrative project and help you to
enhance your business plan. Are you in need of
On Fri, Jul 13, 2018 at 07:36:32AM +0800, Huang, Ying wrote:
> @@ -1260,7 +1257,6 @@ static void swapcache_free(swp_entry_t entry)
> }
> }
>
> -#ifdef CONFIG_THP_SWAP
> static void swapcache_free_cluster(swp_entry_t entry)
> {
> unsigned long offset = swp_offset(entry);
> @@ -1271,
> We bail out during patch registration for architectures, those don't
> support reliable stack trace.
Does anybody know if that change was intentional? I thought the plan
was to allow non-consistency-model arches to still use livepatch, and
that they'd just have to 'force' patches to completion
Hi Anson,
On Tue, Jul 10, 2018 at 4:48 AM, Anson Huang wrote:
> GPIO registers could lose context on some i.MX SoCs,
> like on i.MX7D, when enter LPSR mode, the whole SoC
After further reviewing this patchI have a question: here you say that
i.MX7D needs to save some registers.
> will be powere
On 07/13/2018 06:02 AM, Will Deacon wrote:
> On Tue, Jul 10, 2018 at 02:31:30PM -0400, Waiman Long wrote:
>> It was found that a constant stream of readers might cause the count to
>> go negative most of the time after an initial trigger by a writer even
>> if no writer was present afterward. As a
On Fri, 13 Jul 2018, Metzger, Markus T wrote:
> Hello Hugh,
>
> > A little "optimization" crept into alloc_bts_buffer() along the way, which
> > now
> > places bts_interrupt_threshold not on a record boundary.
> > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This
> > addr
It was discovered that a constant stream of readers might cause the
count to go negative most of the time after an initial trigger by a
writer even if no writer was present afterward. As a result, most of the
readers would have to go through the slowpath reducing their performance.
To avoid that f
This patch adds optional regulators, which can be used to power
up touchscreen. After enabling regulators, we need to wait 150msec.
This value is taken from official driver.
It was tested on Samsung Galaxy i9000 (based on Samsung S5PV210 SOC).
Signed-off-by: Paweł Chmiel
---
drivers/input/touch
Document new optional voltage regulators, which can be used
to power down/up touchscreen.
Signed-off-by: Paweł Chmiel
---
Documentation/devicetree/bindings/input/atmel,maxtouch.txt | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/atmel,maxtouch.
This two patches add optional regulator support to atmel_mxt_ts.
First patch adds regulators to driver.
Second patch updates documentation.
Paweł Chmiel (2):
Input: atmel_mxt_ts: Add support for optional regulators.
Input: atmel_mxt_ts: Document optional voltage regulators
.../devicetree/bi
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
# HEAD: 8a46580128a02bdc18d7dcc0cba19d3cea4fb9c4 rseq/selftests: cleanup:
Update comment above rseq_prepare_unload
Various rseq ABI fixes an
Hi Jisheng,
I love your patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on v4.18-rc4 next-20180713]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Fri, Jul 13, 2018 at 10:22 AM Jae Hyun Yoo
wrote:
>
> On 7/12/2018 11:21 AM, Jae Hyun Yoo wrote:
> > On 7/12/2018 2:33 AM, Brendan Higgins wrote:
> >> On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
> >> wrote:
> >>
> > + for (;;) {
> > + if (!(readl(bus->base + ASP
Remove custom is_multicast_mac_addr() and is_broadcast_mac_addr().
Use is_multicast_ether_addr() instead.
By definition the broadcast address is also a multicast address.
is_multicast_ether_addr() returns true for broadcast addresses.
Hence checking for multicast in the conditional is sufficient.
On Thu, Jul 12, 2018 at 11:21 AM Jae Hyun Yoo
wrote:
>
> On 7/12/2018 2:33 AM, Brendan Higgins wrote:
> > On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
> > wrote:
> >>
> >
> +/* Timeout for bus busy checking */
> +#define BUS_BUSY_CHECK_TIMEOUT 25 /* 250ms
On Fri, Jul 13, 2018 at 4:58 AM, Anson Huang wrote:
> Enable SEIKO 43WVF1G lcdif panel for DRM driver,
> add necessary properties according to SEIKO 43WVF1G
> driver's requirement, such as "dvdd-supply", "avdd-supply"
> and "backlight" etc..
>
> Signed-off-by: Anson Huang
Reviewed-by: Fabio Este
On Fri, Jul 13, 2018 at 4:58 AM, Anson Huang wrote:
> On i.MX6SLL EVK board, lcd regulator is controlled
> by GPIO4 IO03 using MX6SLL_PAD_KEY_ROW5__GPIO4_IO03 pin,
> NOT MX6SLL_PAD_ECSPI1_SCLK__GPIO4_IO08, correct it.
>
> Signed-off-by: Anson Huang
Reviewed-by: Fabio Estevam
Hi Anson,
On Fri, Jul 13, 2018 at 4:55 AM, Anson Huang wrote:
> On i.MX6SL EVK board, the MX6SL_PAD_KEY_ROW5 pin is
> used as lcd 3v3 regulator control pin, need to make
> sure MX6SL_PAD_KEY_ROW5 is muxed as GPIO function
> for controlling lcd 3v3 regulator.
>
> Signed-off-by: Anson Huang
> ---
On Fri, Jul 13, 2018 at 4:58 AM, Anson Huang wrote:
> Enable pwm1 module on i.MX6SLL EVK board to make
> backlight driver really work with LCD panel connected.
>
> Signed-off-by: Anson Huang
Reviewed-by: Fabio Estevam
On Fri, Jul 13, 2018 at 4:11 AM, Linus Walleij wrote:
> On Tue, Jul 10, 2018 at 9:53 AM Anson Huang wrote:
>
>> GPIO registers could lose context on some i.MX SoCs,
>> like on i.MX7D, when enter LPSR mode, the whole SoC
>> will be powered off except LPSR domain, GPIO banks
>> will lose context in
On Fri, Jul 13, 2018 at 2:30 PM, Andrey Smirnov
wrote:
> It looks like I made a nasty typo in the original patch which resulted
> in missing watchdog device. Fix it.
>
> Cc: Fabio Estevam
> Cc: Nikita Yushchenko
> Cc: Lucas Stach
> Cc: cphe...@gmail.com
> Cc: Shawn Guo
> Cc: Rob Herring
> Cc:
On Fri, Jul 13, 2018 at 2:30 PM, Andrey Smirnov
wrote:
> Instead of relying on default values, configure PAD_AUD3_BB_CK to be a
> GPIO explicitly. While at, it change the pad configuration to enable
> a 100K pull-down (the pin is used as IRQ_TYPE_LEVEL_HIGH).
>
> Cc: Fabio Estevam
> Cc: Nikita Yu
For the ARM64 simd locking it would be easier to have local_lock_bh()
which grabs a local_lock with BH disabled and turns into a
local_bh_disable() on !RT.
Signed-off-by: Sebastian Andrzej Siewior
---
obviously required by the previous one…
include/linux/locallock.h | 33 +++
In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The
code disables BH and expects that it is not preemptible. On -RT the
task remains preemptible but remains the same CPU. This may corrupt the
content of the SIMD registers if the task is preempted during
saving/restoring those re
For now, that's arch/x86/boot/compressed/vmlinux.bin.zst but probably more
will come, thus let's be consistent with all other compressors.
Signed-off-by: Adam Borowski
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 97ba6b79834c..0d09cf1c053c 1006
Shawn:
Here's a couple of fixes for things I missed in the
[original-submission]. Sorry about the inconvenience.
Changes since [v1]:
- Reword commit message for patch 2/2
Thanks,
Andrey Smirnov
[v1] lkml.kernel.org/r/20180712023337.30112-1-andrew.smir...@gmail.com
[original-submission]
l
Instead of relying on default values, configure PAD_AUD3_BB_CK to be a
GPIO explicitly. While at, it change the pad configuration to enable
a 100K pull-down (the pin is used as IRQ_TYPE_LEVEL_HIGH).
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc:
It looks like I made a nasty typo in the original patch which resulted
in missing watchdog device. Fix it.
Cc: Fabio Estevam
Cc: Nikita Yushchenko
Cc: Lucas Stach
Cc: cphe...@gmail.com
Cc: Shawn Guo
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-arm-ker...@lists.infradead.org
Cc: devicet...@vger
On Wed, Jul 11, 2018 at 4:29 AM, Joerg Roedel wrote:
> From: Joerg Roedel
>
> It marks the end of the address-space range reserved for the
> LDT. The LDT-code will use it when unmapping the LDT for
> user-space.
>
Reviewed-by: Andy Lutomirski
On Wed, Jul 11, 2018 at 4:29 AM, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Add a config option that enabled code to check that we enter
> and leave the kernel with the correct cr3. This is needed
> because we have no NX protection of user-addresses in the
> kernel-cr3 on x86-32 and wouldn't no
On Fri, Jul 13, 2018 at 3:05 AM, Joerg Roedel wrote:
> On Thu, Jul 12, 2018 at 01:53:19PM -0700, Andy Lutomirski wrote:
>> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
>> > NMI will no longer use most of the shared return path,
>> > because NMI needs special handling when the CR3 switches f
On Fri, Jul 13, 2018 at 5:06 AM, Ondrej Mosnacek wrote:
> The 'ts' argument of process_adj_status() and process_adjtimex_modes()
> is unused and can be safely removed.
>
> Signed-off-by: Ondrej Mosnacek
Thanks for sending this set along. I'll queue them up for closer
review and testing.
thanks
On Fri, Jul 13, 2018 at 3:56 AM, Joerg Roedel wrote:
> Hi Andy,
>
> thanks for you valuable feedback.
>
> On Thu, Jul 12, 2018 at 02:09:45PM -0700, Andy Lutomirski wrote:
>> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
>> > -.macro SAVE_ALL pt_regs_ax=%eax
>> > +.macro SAVE_ALL pt_regs_ax=%
On 7/12/2018 11:21 AM, Jae Hyun Yoo wrote:
On 7/12/2018 2:33 AM, Brendan Higgins wrote:
On Wed, Jun 27, 2018 at 10:55 AM Jae Hyun Yoo
wrote:
+/* Timeout for bus busy checking */
+#define BUS_BUSY_CHECK_TIMEOUT 25 /*
250ms */
+#define BUS_BUSY_CHECK_INTERVAL
On Fri, Jul 13, 2018 at 12:13 AM, Mukesh Ojha wrote:
> Hi John,
>
> Thanks for your response
> Please find my comments inline.
>
>
> On 7/11/2018 1:43 AM, John Stultz wrote:
>>
>> On Fri, Jul 6, 2018 at 6:17 AM, Mukesh Ojha wrote:
>>>
>>> Currently, there exists a corner case assuming when there
On Fri, Jul 13, 2018 at 2:48 AM, Joerg Roedel wrote:
> On Thu, Jul 12, 2018 at 01:49:13PM -0700, Andy Lutomirski wrote:
>> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
>> >/* Offset from the sysenter stack to tss.sp0 */
>> > -DEFINE(TSS_entry_stack, offsetof(struct cpu_entry_area,
find_regset() goes through regsets sequentially. Empty slots
in regset arrays causes mismatch. Add comments to x86_regset
enum.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/ptrace.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/x86/kernel/ptrace.c b/arch/x86/kernel/ptrace.c
i
On Fri, Jul 13, 2018 at 2:34 AM Will Deacon wrote:
>
> And, since we're stating preferences, I'll reiterate my preference towards:
>
> * RCsc unlock/lock
> * RCpc release/acquire
Yes, I think this would be best. We *used* to have pretty heavy-weight
locking rules for various reaso
On Fri, Jul 13, 2018 at 8:40 AM, David Howells wrote:
> Andy Lutomirski wrote:
>
>> > Whilst I'm at it, do we want the option of doing the equivalent of
>> > mountat()? I.e. offering the option to open all the device files used by
>> > a superblock with dfd and AT_* flags in combination with the
Hi Linus,
Second pull request for -rc
Things have been quite slow, only 6 RC patches have been sent to the
list. Lots of stuff in for-next already though.
The following changes since commit 6f0d349d922ba44e4348a17a78ea51b7135965b1:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
Sean Christopherson writes:
> On Wed, Jul 11, 2018 at 07:37:18PM +0200, Vitaly Kuznetsov wrote:
>> When we switched from doing rdmsr() to reading FS/GS base values from
>> current->thread we completely forgot about legacy 32-bit userspaces which
>> we still support in KVM (why?). task->thread.{fs
On Wed, Jul 11, 2018 at 05:10:50PM -0700, David Collins wrote:
> Hello Doug,
>
> On 07/11/2018 03:43 PM, Doug Anderson wrote:
> > On Wed, Jul 11, 2018 at 3:36 PM, David Collins
> > wrote:
> >>> On Tue, Jul 10, 2018 at 10:45 AM, David Collins
> >>> wrote:
> On 06/29/2018 04:54 PM, Matthias
On Tue, Jun 19, 2018 at 10:26 AM, Souptick Joarder wrote:
> On Mon, Jun 4, 2018 at 10:47 PM, Souptick Joarder
> wrote:
>> Use new return type vm_fault_t for fault handler. For
>> now, this is just documenting that the function returns
>> a VM_FAULT value rather than an errno. Once all instances
Hello,
This is the second version of driver. I added a mfd driver which by
default probes atmel_serial driver and if in dt is specified to probe
the spi driver, then the spi-at91-usart driver will be probed. The
compatible for atmel_serial is now the compatible for at91-usart mfd
driver and compat
On Wed, Jul 11, 2018 at 07:37:18PM +0200, Vitaly Kuznetsov wrote:
> When we switched from doing rdmsr() to reading FS/GS base values from
> current->thread we completely forgot about legacy 32-bit userspaces which
> we still support in KVM (why?). task->thread.{fsbase,gsbase} are only
> synced for
This patch modifies the place where resources and device tree properties
are searched.
Signed-off-by: Radu Pirea
Reviewed-by: Andy Shevchenko
Acked-by: Richard Genoud
Acked-by: Nicolas Ferre
---
drivers/tty/serial/Kconfig| 1 +
drivers/tty/serial/atmel_serial.c | 42 +
This patch moves the bindings for serial from serial/atmel-usart.txt to
mfd/atmel-usart.txt and adds bindings for USART in SPI mode.
Signed-off-by: Radu Pirea
Reviewed-by: Rob Herring
Acked-for-MFD-by: Lee Jones
Acked-by: Nicolas Ferre
---
.../bindings/{serial => mfd}/atmel-usart.txt | 25 ++
Added entry for at91 usart mfd driver.
Signed-off-by: Radu Pirea
Acked-by: Nicolas Ferre
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7ac6e6af5292..f849cc4acbf6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9362,6 +9362,13 @@ F:
This mfd driver is just a wrapper over atmel_serial driver and
spi-at91-usart driver. Selection of one of the drivers is based on a
property from device tree. If the property is not specified, the default
driver is atmel_serial.
Signed-off-by: Radu Pirea
Reviewed-by: Andy Shevchenko
Acked-by: Ro
This is the driver for at91-usart in spi mode. The USART IP can be configured
to work in many modes and one of them is SPI.
The driver was tested on sama5d3-xplained and sama5d4-xplained boards with
enc28j60 ethernet controller as slave.
Signed-off-by: Radu Pirea
Reviewed-by: Andy Shevchenko
Re
Added entry for at91 usart mfd driver.
Signed-off-by: Radu Pirea
Acked-by: Nicolas Ferre
Acked-for-MFD-by: Lee Jones
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9d5eeff51b5f..7ac6e6af5292 100644
--- a/MAINTAINERS
+++ b/MAINTAINER
-
Problem located with experimental coccinelle script
looks like cut&past error from imx6ul (or vice versa)
Patch was compile tested with: imx_v6_v7_defconfig (implies
CONFIG_SOC_IMX6SLL=y)
Patch is against 4.18-rc4 (localversion-next is next-20180713)
drivers/clk/imx/clk-imx6sll.c | 1 +
On Fri, Jul 13, 2018 at 09:27:30AM -0700, Stephen Boyd wrote:
> Quoting Nicholas Mc Guire (2018-07-13 04:13:20)
> > of_find_compatible_node() is returning a device node with refcount
> > incremented and must be explicitly decremented after the last use
> > which is right after the us in of_iomap()
Hi Michael,
On Fri, Jul 13, 2018 at 11:15:26PM +1000, Michael Ellerman wrote:
> I reran some numbers today with some slightly updated tests.
>
> It varies quite a bit across machines and CPU revisions.
>
> On one I get:
>
> Lock/UnlockTime Time %Total Cycles Cycles Cy
On 07/13/2018 02:24 PM, Tony Krowiak wrote:
On 07/09/2018 04:38 PM, Pierre Morel wrote:
On 09/07/2018 14:20, Pierre Morel wrote:
On 29/06/2018 23:11, Tony Krowiak wrote:
Provides a sysfs interface to view the AP matrix configured for the
mediated matrix device.
The relevant sysfs structure
On Fri, Jul 13, 2018 at 09:00:19AM -0700, Stephen Boyd wrote:
> Quoting Matthias Kaehlcke (2018-07-09 14:25:21)
> > diff --git a/arch/arm64/boot/dts/qcom/pm8998.dtsi
> > b/arch/arm64/boot/dts/qcom/pm8998.dtsi
> > index 92bed1e7d4bb..7eea94701b23 100644
> > --- a/arch/arm64/boot/dts/qcom/pm8998.dts
Hi Linus,
The following changes since commit 1e4b044d22517cae7047c99038abb23243ca:
Linux 4.18-rc4 (2018-07-08 16:34:02 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.18-rc5
for you to fetch changes up to 498e8bf51c633cc4496343e6113f
Inherit the tracing on/off setting on ring_buffer to next
trace buffer when taking a snapshot.
Taking a snapshot is done by swapping with backup ring buffer
(max_tr_buffer). But since the tracing on/off setting is set
in the ring buffer, when swapping it, tracing on/off setting
can also be changed
101 - 200 of 470 matches
Mail list logo
