Currently mtty sample driver uses mdev state and UUID in convoluated way to
generate an interrupt.
It uses several translations from mdev_state to mdev_device to mdev uuid.
After which it does linear search of long uuid comparision to
find out mdev_state in mtty_trigger_interrupt().
mdev_state is a
There is no single production driver who is interested in mdev device
name.
Additionally mdev device name is already available using core kernel
API dev_name().
Hence removed unused exported symbol.
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c | 6 --
include/linux/mdev.h
While generating interrupt, mdev_state is already available for which
interrupt is generated.
Instead of doing indirect way from state->device->uuid-> to searching
state linearly in linked list on every interrupt generation,
directly use the available state.
Hence, simplify the code to use mdev_st
On 8/2/2019 12:03 PM, Vinod Koul wrote:
On 02-08-19, 09:45, Rajendra Nayak wrote:
From: Jitendra Sharma
Add the binding for the TLMM pinctrl block found in the SC7180 platform
Signed-off-by: Jitendra Sharma
Signed-off-by: Vivek Gautam
[rnayak: Fix some copy-paste issues, sort and fix fun
> >
> > Cc: Ingo Molnar
> > Cc: Peter Zijlstra
> > Cc: Andrew Morton
> > Suggested-by/Acked-by: Dave Hansen
>
> Though I am not sure, should the above be two separate lines instead ?
Sure! Will split them in V2.
>
> > Signed-off-by: Sai Praneeth Prakhya
> > ---
> > include/linux/mm_types_
On Fri, Aug 02, 2019 at 09:44:43AM +0300, Ard Biesheuvel wrote:
>
> OK. I will adopt this mechanism [0] after all and resubmit, once I get
> confirmation from either Voldis or Heiko that this makes the issue go
> away (given that my local GCC does not reproduce the issue)
>
> [0]
> https://lore.k
On Tue, Jul 09, 2019 at 09:56:54PM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> The struct chip_select array that's used for saving chip select bases
> and masks is fixed at length of two. There should be one struct
> chip_select for each controller, so this array should be increased to
On 01/08/19 2:31 PM, Michael Ira Krufky wrote:
> Sean,
>
> Please pardon the late reply. See my responses inline below:
>
> On Wed, Jul 24, 2019 at 1:36 AM Sean Young wrote:
>> On Sat, Jul 20, 2019 at 11:43:02AM +0530, Vandana BN wrote:
>>> Syzbot reported global-out-of-bounds Read in dvb_pll_
On Fri, Aug 02, 2019 at 02:48:44PM +1000, Stephen Rothwell wrote:
> Hi Herbert,
>
> On Fri, 2 Aug 2019 13:14:14 +1000 Herbert Xu
> wrote:
> >
> > For now I'm going to back out those two specific patches as the
> > rest seem to be valid by themselves.
>
> I have applied the top commit from your
On Fri, 2 Aug 2019 at 09:46, Heiko Carstens wrote:
>
> On Thu, Aug 01, 2019 at 08:28:56PM +0300, Ard Biesheuvel wrote:
> > On Thu, 1 Aug 2019 at 15:28, Heiko Carstens
> > wrote:
> > > Still not... with linux-next as of today I get this (s390 defconfig):
> > >
> > > ERROR: "crypto_aegis128_decryp
On Fri, 2 Aug 2019 at 03:20, Stephen Rothwell wrote:
>
> Hi Herbert,
>
> On Thu, 1 Aug 2019 20:28:56 +0300 Ard Biesheuvel
> wrote:
> >
> > On Thu, 1 Aug 2019 at 15:28, Heiko Carstens
> > wrote:
> > >
> > > On Wed, Jul 31, 2019 at 01:44:54PM +0200, Heiko Carstens wrote:
> > > > On Wed, Jul 31,
> > > > +static const char * const resident_page_types[NR_MM_COUNTERS] = {
> > > > + "MM_FILEPAGES",
> > > > + "MM_ANONPAGES",
> > > > + "MM_SWAPENTS",
> > > > + "MM_SHMEMPAGES",
> > > > +};
> > >
> > > But please let's not put this in a header file. We're asking the
> > >
On Thu, Aug 01, 2019 at 08:28:56PM +0300, Ard Biesheuvel wrote:
> On Thu, 1 Aug 2019 at 15:28, Heiko Carstens wrote:
> > Still not... with linux-next as of today I get this (s390 defconfig):
> >
> > ERROR: "crypto_aegis128_decrypt_chunk_simd" [crypto/aegis128.ko] undefined!
> > ERROR: "crypto_aegi
On Fri, 2 Aug 2019 at 06:14, Herbert Xu wrote:
>
> Hi Stephen:
>
> On Fri, Aug 02, 2019 at 10:20:19AM +1000, Stephen Rothwell wrote:
> >
> > It might be time to revert all this series and try again. The
> > implementation seems to have not been well thought through from a kernel
> > building poin
On Friday 02 August 2019, Mark Balantzyan wrote:
> This patch rewrites the alim1535_wdt driver to use the watchdog subsystem.
> By virtue of this, it also fixes a (theoretical) race condition between the
> formerly arranged ali_timeout_bits and ali_settimer() interoperation.
Please don't rewrite d
On Thu, Aug 01, 2019 at 12:59:25PM -0700, Frank Rowand wrote:
> On 8/1/19 12:32 PM, Greg Kroah-Hartman wrote:
> > On Thu, Aug 01, 2019 at 12:28:13PM -0700, Frank Rowand wrote:
> >> Hi Greg,
> >>
> >> On 7/31/19 11:12 PM, Greg Kroah-Hartman wrote:
> >>> On Wed, Jul 31, 2019 at 03:17:13PM -0700, Sara
On 02-08-19, 09:45, Rajendra Nayak wrote:
> From: Jitendra Sharma
>
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for SC7180
Reviewed-by: Vinod Koul
--
~Vinod
On 02-08-19, 09:45, Rajendra Nayak wrote:
> From: Jitendra Sharma
>
> Add the binding for the TLMM pinctrl block found in the SC7180 platform
>
> Signed-off-by: Jitendra Sharma
> Signed-off-by: Vivek Gautam
> [rnayak: Fix some copy-paste issues, sort and fix functions]
> Signed-off-by: Rajendr
On Thu, Aug 01, 2019 at 11:53:53PM +, Michael Kelley wrote:
> If alloc_descs fails before irq_sysfs_init has run, free_desc in the
> cleanup path will call kobject_del even though the kobject has not
> been added with kobject_add. Fix this by making the call to
> kobject_del conditional on whet
Add pxe1610 as a trivial device
On Tue, 23 Jul 2019 at 17:14, Vijay Khemka wrote:
>
> On 7/23/19, 7:53 AM, "Rob Herring" wrote:
>
> On Tue, Jul 23, 2019 at 8:50 AM Rob Herring wrote:
> >
> > On Mon, Jul 22, 2019 at 6:46 PM Vijay Khemka wrote:
> > >
> > > The pxe1610 is a
On 30. 07. 19, 17:08, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 6789f873 Merge tag 'pm-5.3-rc2' of
> git://git.kernel.org/pu..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1696897c60
> kernel config: https://
Hi all,
According to the reviews from Johoannes, I've changed the old patch and
then submitted the version 2 patch a few days ago.
Please let me know if all this sounds good, or if there are any issues.
Thanks,
Jason
On 2019/7/30 下午1:16, Jason Xing wrote:
Only when calling the poll syscall
On Thu, Aug 01, 2019 at 03:35:56PM -0700, Hridya Valsaraju wrote:
> If CONFIG_ANDROID_BINDERFS is set, the default binder devices
> specified by CONFIG_ANDROID_BINDER_DEVICES are created in each
> binderfs instance instead of global devices being created by
> the binder driver.
>
> Co-developed-by
On Thu, 1 Aug 2019 at 05:45, Andrew Jeffery wrote:
>
>
>
> On Tue, 30 Jul 2019, at 10:27, Andrew Jeffery wrote:
> >
> >
> > On Tue, 30 Jul 2019, at 07:23, Linus Walleij wrote:
> > > On Wed, Jul 24, 2019 at 10:13 AM Andrew Jeffery wrote:
> > >
> > > > It's probably best if we push the three patche
On Thu, Jul 18, 2019 at 6:33 PM Vivek Gautam
wrote:
>
> To better support future versions of llcc, consolidating the
> driver to llcc-qcom driver file, and taking care of the dependencies.
> v1 series is availale at:
> https://lore.kernel.org/patchwork/patch/1099573/
>
> Changes since v1:
> Addres
On Tue, 30 Jul 2019 at 08:19, Avi Fishman wrote:
>
> Similar to w25q256 (besides not supporting QPI mode) but with different ID.
> The "JVM" suffix is in the datasheet.
> The datasheet indicates DUAL and QUAD are supported.
> https://www.winbond.com/resource-files/w25q256jv%20spi%20revi%2010232018
Hello Wolfram,
On Fri, Aug 02, 2019 at 01:21:23PM +1000, Stephen Rothwell wrote:
> After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/i2c/busses/i2c-designware-master.c: In function
> 'i2c_dw_init_recovery_info':
> drivers/i2c/busses/i
Hi all,
In commit
1b82feb6c5e1 ("crypto: qat - Silence smp_processor_id() warning")
Fixes tag
Fixes: ed8ccaef52 ("crypto: qat - Add support for SRIOV")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.1
Hi all,
Changes since 20190801:
My fixes tree is empty again
The jc_docs tree gained a conflict against the cifs tree.
The drm-misc tree lost its build failure.
The tip tree lost its build failure.
Non-merge commits (relative to Linus' tree): 3729
4234 files changed, 221424 inser
On Fri, 02 Aug 2019 05:04:08 +0200,
Tony W Wang-oc wrote:
>
> Add the new PCI ID 0x1d17 0x3288 Zhaoxin controller support
>
> Signed-off-by: Tony W Wang-oc
Applied, thanks.
Takashi
On Thu, 01 Aug 2019 18:28:24 +0200,
Colin King wrote:
>
> From: Colin Ian King
>
> The pointer bptr is being assigned a value that is never read
> and it is being updated in the next statement with a new value.
> The initialization is redundant and can be removed.
>
> Addresses-Coverity: ("Unus
Intel pstate driver exposes min_perf_pct and max_perf_pct sysfs files,
which can be used to force a limit on the min/max P state of the driver.
Though these files eventually control the min/max frequencies that the
CPUs will run at, they don't make a change to policy->min/max values.
When the valu
To avoid reducing the frequency of a CPU prematurely, we skip reducing
the frequency if the CPU had been busy recently.
This should not be done when the limits of the policy are changed, for
example due to thermal throttling. We should always get the frequency
within the new limits as soon as poss
Hi all,
I’m currently using Ftrace with tracepoints to trace several events in
kernel. But I found the tracing overhead is a little high.
I found the major overhead comes from
“local_dec(&cpu_buffer->committing);” in rb_end_commit() function.
local_dec() will invoke atomic_long_dec(), which final
On 8/1/19, 10:26 PM, "Joel Stanley" wrote:
> I've applied both of these to the aspeed tree for 5.4.
Thank you Joel.
Cheers,
Tao
On Fri, 2 Aug 2019 at 05:20, Tao Ren wrote:
>
> On 8/1/19, 9:21 PM, "Joel Stanley" wrote:
>
> > On Fri, 2 Aug 2019 at 04:10, Tao Ren wrote:
> >>
> >> Add initial version of device tree for Facebook Wedge100 AST2400 BMC
> >> platform.
> >>
> >> Signed-off-by: Tao Ren
> >> Reviewed-by: Andrew Je
On 8/1/2019 8:58 AM, Masanari Iida wrote:
This patch fix a spelling typo in Makefile.
Signed-off-by: Masanari Iida
Reviewed-by: Mukesh Ojha
-Mukesh
---
tools/perf/Documentation/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Documentation/Makef
On 01. 07. 19 7:37, Manish Narani wrote:
> Add the new compatible string for ZynqMP SD Host Controller for its use
> in the Arasan SDHCI driver for some of the ZynqMP specific operations.
> Add required properties for the same.
>
> Signed-off-by: Manish Narani
> ---
> This patch depends on the be
On 8/1/19, 9:21 PM, "Joel Stanley" wrote:
> On Fri, 2 Aug 2019 at 04:10, Tao Ren wrote:
>>
>> Add initial version of device tree for Facebook Wedge100 AST2400 BMC
>> platform.
>>
>> Signed-off-by: Tao Ren
>> Reviewed-by: Andrew Jeffery
>> ---
>> Changes in v2:
>> - remove "debug" from boota
Le 02/08/2019 à 07:02, Chris Packham a écrit :
Since commit cbe46bd4f510 ("powerpc: remove CONFIG_CMDLINE #ifdef mess")
CONFIG_CMDLINE has always had a value regardless of CONNIG_CMDLINE_BOOL.
s/CONNIG/CONFIG/
For example:
$ make ARCH=powerpc defconfig
$ cat .config
# CONFIG_CMDLIN
On 02. 08. 19 6:59, Nishka Dasgupta wrote:
> On 31/07/19 7:51 PM, Michal Simek wrote:
>> On 31. 07. 19 15:06, Nishka Dasgupta wrote:
>>> On 31/07/19 2:01 PM, Michal Simek wrote:
On 09. 07. 19 19:28, Nishka Dasgupta wrote:
> Each iteration of for_each_available_child_of_node puts the previo
On Mon, 2019-07-29 at 09:04 +1200, Chris Packham wrote:
> On Fri, 2019-07-26 at 13:31 +, Jon Maloy wrote:
> >
> >
> > >
> > >
> > > -Original Message-
> > > From: netdev-ow...@vger.kernel.org
> > > On
> > > Behalf Of Chris Packham
> > > Sent: 25-Jul-19 19:37
> > > To: tipc-discuss.
On Thu, Aug 01, 2019 at 08:22:48PM -0500, Gustavo A. R. Silva wrote:
> Mark switch cases where we are expecting to fall through.
>
> This patch fixes the following warning (Building: allmodconfig i386):
>
> drivers/pci/hotplug/ibmphp_res.c: In function ‘update_bridge_ranges’:
> drivers/pci/hotplu
Please see: https://lkml.org/lkml/2019/8/2/6
Thank you.
Since commit cbe46bd4f510 ("powerpc: remove CONFIG_CMDLINE #ifdef mess")
CONFIG_CMDLINE has always had a value regardless of CONNIG_CMDLINE_BOOL.
For example:
$ make ARCH=powerpc defconfig
$ cat .config
# CONFIG_CMDLINE_BOOL is not set
CONFIG_CMDLINE=""
When enabling CONNIG_CMDLINE_BOOL this
On 31/07/19 7:51 PM, Michal Simek wrote:
On 31. 07. 19 15:06, Nishka Dasgupta wrote:
On 31/07/19 2:01 PM, Michal Simek wrote:
On 09. 07. 19 19:28, Nishka Dasgupta wrote:
Each iteration of for_each_available_child_of_node puts the previous
node, but in the case of a goto from the middle of the
On 1/08/19 6:16 PM, Raul Rangel wrote:
> On Wed, Jun 19, 2019 at 08:56:25AM -0600, Raul Rangel wrote:
>> Your patch looks good. I tried it out and got over 57k insertion/removal
>> iterations. Do you want me to send out your patch, or do you want to do
>> it?
>>
>> Just to recap, the patch you prop
On Thu, 2019-08-01 at 21:23 -0700, Joe Perches wrote:
> If any feels like it, here are some more typos from:
>
> $ git grep -P '\b\w+itons?' | grep -ohP '\b\w+itons?' | sort | uniq -c | sort
> -rn
> 7 additon
> 6 definitons
> 5 Prediciton
> 5 instruciton
> 4 conditon
Hi Herbert,
On Fri, 2 Aug 2019 13:14:14 +1000 Herbert Xu
wrote:
>
> For now I'm going to back out those two specific patches as the
> rest seem to be valid by themselves.
I have applied the top commit from your tree to linux-next today just
to help with building and testing over the weekend (I
Le 02/08/2019 à 00:50, Chris Packham a écrit :
Bring powerpc in line with other architectures that support extending or
overriding the bootloader provided command line.
The current behaviour is most like CMDLINE_FROM_BOOTLOADER where the
bootloader command line is preferred but the kernel con
Le 02/08/2019 à 00:32, Chris Packham a écrit :
On Thu, 2019-08-01 at 08:14 +0200, Christophe Leroy wrote:
Le 01/08/2019 à 04:12, Chris Packham a écrit :
Bring powerpc in line with other architectures that support
extending or
overriding the bootloader provided command line.
The current be
On Fri, Aug 02, 2019 at 06:54:27AM +0300, Daniel Baluta wrote:
> One more thing. See below:
>
> On Wed, Jul 31, 2019 at 12:14 PM Richard Zhu wrote:
>
>
>
> > -/* Control Register */
> > -#define IMX_MU_xCR 0x24
> > /* General Purpose Interrupt Enable */
> > #define IMX_MU_xCR_GIE
If any feels like it, here are some more typos from:
$ git grep -P '\b\w+itons?' | grep -ohP '\b\w+itons?' | sort | uniq -c | sort
-rn
7 additon
6 definitons
5 Prediciton
5 instruciton
4 conditon
3 partititon
3 notificaiton
3 implementaiton
3
On Fri, 2 Aug 2019 at 04:10, Tao Ren wrote:
>
> Add initial version of device tree for Facebook Wedge100 AST2400 BMC
> platform.
>
> Signed-off-by: Tao Ren
> Reviewed-by: Andrew Jeffery
> ---
> Changes in v2:
> - remove "debug" from bootargs.
Thanks. I applied wedge40 and then this one fails
From: Jitendra Sharma
Add initial pinctrl driver to support pin configuration with
pinctrl framework for SC7180
Signed-off-by: Jitendra Sharma
Signed-off-by: Vivek Gautam
[rnayak: modify to use upstream tile support
sort and squash some functions]
Signed-off-by: Rajendra Nayak
Review
There was some sort of filesystem error that cause the wrong file to be
saved. Hence, yes, possibly there was no difference betwee the v2 and the
'v4' (which should have been the 'v3'). Since the last one, though
unchanged from v2, was a changelog-less 'v3', THIS is an actual 'v4'.
Thank you,
From: Jitendra Sharma
Add the binding for the TLMM pinctrl block found in the SC7180 platform
Signed-off-by: Jitendra Sharma
Signed-off-by: Vivek Gautam
[rnayak: Fix some copy-paste issues, sort and fix functions]
Signed-off-by: Rajendra Nayak
Reviewed-by: Bjorn Andersson
---
.../bindings/p
This patch rewrites the alim1535_wdt driver to use the watchdog subsystem.
By virtue of this, it also fixes a (theoretical) race condition between the
formerly arranged ali_timeout_bits and ali_settimer() interoperation.
Signed-off-by: Mark Balantzyan
---
drivers/watchdog/Kconfig| 1 +
Add initial version of device tree for Facebook Wedge100 AST2400 BMC
platform.
Signed-off-by: Tao Ren
Reviewed-by: Andrew Jeffery
---
Changes in v2:
- remove "debug" from bootargs.
arch/arm/boot/dts/Makefile| 1 +
.../boot/dts/aspeed-bmc-facebook-wedge100.dts | 149
Add initial version of device tree for Facebook Wedge40 AST2400 BMC
platform.
Signed-off-by: Tao Ren
Reviewed-by: Andrew Jeffery
---
Changes in v2:
- remove "debug" from bootargs.
arch/arm/boot/dts/Makefile| 1 +
.../boot/dts/aspeed-bmc-facebook-wedge40.dts | 141 +
On 2019年08月01日 17:41, Will Deacon wrote:
On Thu, Aug 01, 2019 at 04:33:40PM +0800, Jiping Ma wrote:
In arm64, the PC of the frame is matched to the last frame function,
rather than the function of his frame. For the following example, the
stack size of occupy_stack_init function should be 337
On Tue, Jul 30, 2019 at 7:38 PM Paolo Bonzini wrote:
>
> On 30/07/19 15:35, Anup Patel wrote:
> > On Tue, Jul 30, 2019 at 6:48 PM Paolo Bonzini wrote:
> >>
> >> On 30/07/19 14:45, Anup Patel wrote:
> >>> Here's some text from RISC-V spec regarding SIP CSR:
> >>> "software interrupt-pending (SSIP)
On 8/1/19, 7:56 PM, "Andrew Jeffery" wrote:
>On Fri, 2 Aug 2019, at 10:24, Tao Ren wrote:
>> Add initial version of device tree for Facebook Wedge40 AST2400 BMC
>> platform.
>>
>> Signed-off-by: Tao Ren
>
> Reviewed-by: Andrew Jeffery
Thank you Andrew for the quick review (on both pat
On 8/1/19, 8:02 PM, "Joel Stanley" wrote:
> On Fri, 2 Aug 2019 at 01:02, Tao Ren wrote:
>> +
>> + chosen {
>> + stdout-path = &uart3;
>> + bootargs = "debug console=ttyS2,9600n8 root=/dev/ram rw";
>
> Are you sure you want 'debug' in your boot arguments?
>
One more thing. See below:
On Wed, Jul 31, 2019 at 12:14 PM Richard Zhu wrote:
> -/* Control Register */
> -#define IMX_MU_xCR 0x24
> /* General Purpose Interrupt Enable */
> #define IMX_MU_xCR_GIEn(x) BIT(28 + (3 - (x)))
> /* Receive Interrupt Enable */
> @@ -44,6 +36,13 @@
On 01-08-19, 10:57, Doug Smythies wrote:
> On 2019.07.31 23:17 Viresh Kumar wrote:
> > On 31-07-19, 17:20, Doug Smythies wrote:
> >> Summary:
> >>
> >> The old way, using UINT_MAX had two purposes: first,
> >> as a "need to do a frequency update" flag; but also second, to
> >> force any subsequent
On 31-07-19, 14:10, Sowjanya Komatineni wrote:
> This patch adds suspend and resume pm ops for cpufreq driver.
>
> PLLP is the safe clock source for CPU during system suspend and
> resume as PLLP rate is below the CPU Fmax at Vmin.
>
> CPUFreq driver suspend switches the CPU clock source to PLLP
Take a second look. It is different. And I had to amend the title hence
the second send to include the subsystem, as you so duly tend to remind
me. It just so happened that I mistyped and skipped a version by...1.
Mark
On Thu, 1 Aug 2019, Guenter Roeck wrote:
On 8/1/19 8:26 PM, Mark Balantzy
Hi Stephen:
On Fri, Aug 02, 2019 at 10:20:19AM +1000, Stephen Rothwell wrote:
>
> It might be time to revert all this series and try again. The
> implementation seems to have not been well thought through from a kernel
> building point of view. For a start the two commits
>
> 7cdc0ddbf74a ("c
On 08/01/2019 11:58 AM, Mike Rapoport wrote:
> The madvise_behavior() function converts -ENOMEM to -EAGAIN in several
> places using identical code.
>
> Move that code to a common error handling path.
>
> No functional changes.
>
> Signed-off-by: Mike Rapoport
Reviewed-by: Anshuman Khandual
On 8/1/19 8:26 PM, Mark Balantzyan wrote:
This patch rewrites the alim1535_wdt driver to use the watchdog subsystem.
By virtue of this, it also fixes a (theoretical) race condition between the
formerly arranged ali_timeout_bits and ali_settimer() interoperation.
Signed-off-by: Mark Balantzyan
There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
and raw_sock_no_ioctlcmd as static.
net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not declared.
Should it be static?
net/can/raw.c:840:5: warning: symbol 'raw_sock_no_ioctlcmd' was not declared.
Should
This patch rewrites the alim1535_wdt driver to use the watchdog subsystem.
By virtue of this, it also fixes a (theoretical) race condition between the
formerly arranged ali_timeout_bits and ali_settimer() interoperation.
Signed-off-by: Mark Balantzyan
---
drivers/watchdog/Kconfig| 1
On Fri, Aug 2, 2019 at 12:14 PM Joe Perches wrote:
>
> On Fri, 2019-08-02 at 10:40 +0900, Masahiro Yamada wrote:
> > On Thu, Aug 1, 2019 at 4:27 AM Joe Perches wrote:
> > > On Wed, 2019-07-31 at 21:03 +0200, Rikard Falkeborn wrote:
> > > > GENMASK() and GENMASK_ULL() are supposed to be called wit
> -Original Message-
> From: Daniel Baluta
> Sent: 2019年8月1日 22:47
> To: Richard Zhu
> Cc: jassisinghb...@gmail.com; Oleksij Rempel ;
> Aisheng Dong ; Linux Kernel Mailing List
> ; linux-arm-kernel
> ; dl-linux-imx
> Subject: [EXT] Re: [PATCH v3] mailbox: imx: add support for imx v1 mu
>
This patch rewrites the alim1535_wdt driver to use the watchdog subsystem.
By virtue of this, it also fixes a (theoretical) race condition between the
formerly arranged ali_timeout_bits and ali_settimer() interoperation.
Signed-off-by: Mark Balantzyan
---
drivers/watchdog/Kconfig| 1
Hi all,
After merging the i2c tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/i2c/busses/i2c-designware-master.c: In function
'i2c_dw_init_recovery_info':
drivers/i2c/busses/i2c-designware-master.c:658:6: warning: unused variable 'r'
[-Wunused-variable]
int
Add the new PCI ID 0x1d17 0x3288 Zhaoxin controller support
Signed-off-by: Tony W Wang-oc
---
sound/pci/hda/hda_intel.c | 4
1 file changed, 4 insertions(+)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 324a4b2..d08da0e 100644
--- a/sound/pci/hda/hda_intel.c
+++
On Fri, 2019-08-02 at 10:40 +0900, Masahiro Yamada wrote:
> On Thu, Aug 1, 2019 at 4:27 AM Joe Perches wrote:
> > On Wed, 2019-07-31 at 21:03 +0200, Rikard Falkeborn wrote:
> > > GENMASK() and GENMASK_ULL() are supposed to be called with the high bit
> > > as the first argument and the low bit as
On Fri, 2019-08-02 at 09:47 +0800, Chuhong Yuan wrote:
> strncmp(str, const, len) is error-prone because len
> is easy to have typo.
> The example is the hard-coded len has counting error
> or sizeof(const) forgets - 1.
> So we prefer using newly introduced str_has_prefix
> to substitute such strnc
Same as the commit 01766229533f ("perf record: Support s390 random
socket_id assignment"), aarch64 also have this problem.
Without this fix:
[root@localhost perf]# ./perf report --header -I -v
...
socket_id number is too big.You may need to upgrade the perf tool.
#
# captured o
On Wed, 2019-07-31 at 20:04 +0300, Andrey Ryabinin wrote:
>
> On 7/26/19 4:19 PM, Walter Wu wrote:
> > On Fri, 2019-07-26 at 15:52 +0300, Andrey Ryabinin wrote:
> >>
> >> On 7/26/19 3:28 PM, Walter Wu wrote:
> >>> On Fri, 2019-07-26 at 15:00 +0300, Andrey Ryabinin wrote:
>
> >>>
> >
> >>>
On Thu, 1 Aug 2019, at 19:48, Ben Pai wrote:
> The Mihawk BMC is an ASPEED ast2500 based BMC that is part of an
> OpenPower Power9 server.
>
> Signed-off-by: Ben Pai
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/aspeed-bmc-opp-mihawk.dts | 902 ++
On Fri, 2 Aug 2019 at 01:02, Tao Ren wrote:
> +
> + chosen {
> + stdout-path = &uart3;
> + bootargs = "debug console=ttyS2,9600n8 root=/dev/ram rw";
Are you sure you want 'debug' in your boot arguments?
The rest lgtm. I can remove debug when applying, or leave i
On Fri, 2 Aug 2019, at 10:24, Tao Ren wrote:
> Add initial version of device tree for Facebook Wedge40 AST2400 BMC
> platform.
>
> Signed-off-by: Tao Ren
Reviewed-by: Andrew Jeffery
> ---
> arch/arm/boot/dts/Makefile| 1 +
> .../boot/dts/aspeed-bmc-facebook-wedge40.dt
On Fri, 2 Aug 2019, at 10:32, Tao Ren wrote:
> Add initial version of device tree for Facebook Wedge100 AST2400 BMC
> platform.
>
> Signed-off-by: Tao Ren
Reviewed-by: Andrew Jeffery
> ---
> arch/arm/boot/dts/Makefile| 1 +
> .../boot/dts/aspeed-bmc-facebook-wedge100.
Hello,
syzbot found the following crash on:
HEAD commit:a9815a4f Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12a6dbf060
kernel config: https://syzkaller.appspot.com/x/.config?x=37c48fb52e3789e6
da
On 8/1/2019 8:06 PM, Bjorn Andersson wrote:
On Thu 01 Aug 03:07 PDT 2019, Rajendra Nayak wrote:
[..]
+static const struct msm_pingroup sc7180_groups[] = {
+ [0] = PINGROUP(0, SOUTH, qup01, cri_trng, _, phase_flag, _, _, _, _, _),
+ [1] = PINGROUP(1, SOUTH, qup01, cri_trng, _, pha
On Tue, 2019-07-30 at 04:37:04 UTC, Stephen Rothwell wrote:
> Mark switch cases where we are expecting to fall through.
>
> This patch fixes the following warning (Building: powerpc):
>
> drivers/macintosh/smu.c: In function 'smu_queue_i2c':
> drivers/macintosh/smu.c:854:21: warning: this stateme
On Wed, 2019-07-31 at 06:01:42 UTC, Christophe Leroy wrote:
> Due to commit 4a6d8cf90017 ("powerpc/mm: don't use pte_alloc_kernel()
> until slab is available on PPC32"), pte_alloc_kernel() cannot be used
> during early KASAN init.
>
> Fix it by using memblock_alloc() instead.
>
> Reported-by: Erh
From: John Hubbard
Hi,
These are best characterized as miscellaneous conversions: many (not all)
call sites that don't involve biovec or iov_iter, nor mm/. It also leaves
out a few call sites that require some more work. These are mostly pretty
simple ones.
It's probably best to send all of the
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder versions").
Cc: Joe
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
On Tue, Jul 30, 2019 at 12:36 AM Arnd Bergmann wrote:
>
> On Tue, Jul 30, 2019 at 6:31 AM Kees Cook wrote:
> >
> > On Mon, Jul 29, 2019 at 06:49:23PM -0700, Deepa Dinamani wrote:
> > > Also update the gran since pstore has microsecond granularity.
> >
> > So, I'm fine with this, but technically t
From: John Hubbard
Provide more capable variation of put_user_pages_dirty_lock(),
and delete put_user_pages_dirty(). This is based on the
following:
1. Lots of call sites become simpler if a bool is passed
into put_user_page*(), instead of making the call site
choose which put_user_page*() varia
From: John Hubbard
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page() or
release_pages().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder v
On Thu, Aug 01, 2019 at 01:58:34PM -0700, Mark Balantzyan wrote:
> This patch rewrites the alim1535_wdt driver to use the watchdog subsystem. By
> virtue of this, it also fixes a potential race condition between
> ali_timeout_bits and ali_settimer().
>
There is no such race condition, as I expla
1 - 100 of 1028 matches
Mail list logo
