On Thu, Mar 07, 2019 at 07:49:11AM +, Tony Chuang wrote:
>
>
> > -Original Message-
> > From: kernel test robot [mailto:rong.a.c...@intel.com]
> > Sent: Thursday, March 07, 2019 3:05 PM
> > To: Tony Chuang
> > Cc: Johannes Berg; Larry Finger; LKML; Linus Torvalds; l...@01.org
> >
On 2019/3/7 2:29, Andrea Arcangeli wrote:
> Hello Zhong,
>
> On Wed, Mar 06, 2019 at 09:07:00PM +0800, zhong jiang wrote:
>> The patch use call_rcu to delay free the task_struct, but It is possible to
>> free the task_struct
>> ahead of get_mem_cgroup_from_mm. is it right?
> Yes it is possible to
Clang warns about a tentative array definition without a length:
kernel/locking/lockdep.c:845:12: error: tentative array definition assumed to
have one element [-Werror]
There is no real reason to do this here, so just set the same length as
in the real definition later in the same file. It
Hi Zack,
> On Tue, Mar 5, 2019 at 10:24 AM Lukasz Majewski wrote:
> > From other discussion [4] - regarding the following system calls:
> > time, stime, gettimeofday, settimeofday, adjtimex, nanosleep,
> > alarm, getitimer, setitimer, select, utime, utimes, futimesat, and
> >
ARM64 randdconfig builds regularly run into a build error, especially
when NUMA_BALANCING and SPARSEMEM are enabled but not SPARSEMEM_VMEMMAP:
#error "KASAN: not enough bits in page flags for tag"
The last-cpuid bits are already contitional on the available space,
so the result of the
On Wed, Mar 6, 2019 at 8:53 PM Yafang Shao wrote:
>
> On Wed, Mar 6, 2019 at 8:38 PM Peter Zijlstra wrote:
> >
> > On Wed, Mar 06, 2019 at 07:49:36PM +0800, Yafang Shao wrote:
> >
> >
> > $ grep SCHEDSTAT defconfig-build/.config
> > # CONFIG_SCHEDSTATS is not set
> > $ obbjdump -dr
> -Original Message-
> From: kernel test robot [mailto:rong.a.c...@intel.com]
> Sent: Thursday, March 07, 2019 3:05 PM
> To: Tony Chuang
> Cc: Johannes Berg; Larry Finger; LKML; Linus Torvalds; l...@01.org
> Subject: [LKP] [mac80211] c752cac9db:
>
; be Y2038 aware (as for example clock_settime{64}() is).
>
> Correct. FWIW, this is now merged into the mainline kernel.
>
The arch/arm/tools/syscall.tbl
linux-next 20190306
SHA1: cf08baa29613dd899954089e7cc7dba1d478b365
Has now:
403 common clock_gettime64 sys_clock_gettime
404
Hello Dinh,
Just a short ping on this patch - do yo think you can accept this
patch and have it merged? I'd like to know whether it is planned to be
integrated, as it might be beneficial for a lot of socfpga users...
Thanks a lot!
--
Regards,
Andrey.
On Wed, Feb 27, 2019 at 5:50 PM Andrey
On Thu, Mar 7, 2019 at 12:48 AM Linus Torvalds
wrote:
> On Wed, Mar 6, 2019 at 2:33 AM Greg KH wrote:
>
> I wonder why this wasn't seen in linux-next? Yes, the connection is
> odd, and maybe it's very compiler version dependent, but I do hope
> people react to new warnings. The kernel is
On Thu, 7 Mar 2019 at 08:13, kernelci.org bot wrote:
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation
On Mon, Feb 11, 2019 at 08:42:51PM +0100, Borislav Petkov wrote:
> On Mon, Feb 11, 2019 at 11:27:03AM -0800, Nadav Amit wrote:
> > Is there any comment over static_cpu_has()? ;-)
>
> Almost:
>
> /*
> * Static testing of CPU features. Used the same as boot_cpu_has().
> * These will statically
On (02/12/19 15:29), John Ogness wrote:
[..]
> +static bool console_can_emergency(int level)
> +{
> + struct console *con;
> +
> + for_each_console(con) {
> + if (!(con->flags & CON_ENABLED))
> + continue;
> + if (con->write_atomic && level <
On Thu, Mar 7, 2019 at 2:21 AM Luis Henriques wrote:
>
> "Yan, Zheng" writes:
>
> > On Sat, Mar 2, 2019 at 3:13 AM Luis Henriques wrote:
> >>
> >> The CephFS kernel client doesn't enforce quotas that are set in a
> >> directory that isn't visible in the mount point. For example, given the
> >>
Hi,
On 06/03/19 20:57, Lingutla Chandrasekhar wrote:
> If user updates any cpu's cpu_capacity, then the new value is going to
> be applied to all its online sibling cpus. But this need not to be correct
> always, as sibling cpus (in ARM, same micro architecture cpus) would have
> different
On Wed, Mar 06, 2019 at 06:14:09PM -0800, Bart Van Assche wrote:
> On 3/6/19 5:24 PM, Jason Gunthorpe wrote:
> > On Wed, Mar 06, 2019 at 05:01:53PM -0800, Bart Van Assche wrote:
> > > This patch avoids that the following warning is reported when building
> > > the mlx5 driver with W=1:
> > >
> > >
On 07/03/2019 03.14, Bart Van Assche wrote:
> On 3/6/19 5:24 PM, Jason Gunthorpe wrote:
>>>
>>> diff --git a/include/linux/overflow.h b/include/linux/overflow.h
>>> index 40b48e2133cb..8afe0c0ada6f 100644
>>> +++ b/include/linux/overflow.h
>>> @@ -202,6 +202,24 @@
>>> #endif /*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
The spi-pxa2xx can't read and write data correctly on our board.
The pxa_ssp_type is LPSS_BXT_SSP in our case.
With more debug we find that it's related to restart the SPP
during pxa2xx_spi_transfer_one().
In the normal case the spi_transfer_one_message() calls spi-pxa2xx
cs_assert before
Hi,
>Hi,
>
>On 21/02/2019 09:14, Felipe Balbi wrote:
>>
>> Hi,
>>
>> (please break your emails at 80-columns)
>>
>> Pawel Laszczak writes:
> One more thing. Workaround has implemented algorithm that decide for which
> endpoint it should be enabled. e.g for composite device MSC+NCM+ACM
On Wed, Mar 06, 2019 at 09:50:32PM -0800, Darren Hart (VMware) wrote:
> Avoid conflicts from other subsystems by including the header with the
> rest of the driver files.
>
Acked-by: Andy Shevchenko
> Cc: Andy Shevchenko
> Cc: Vadim Pasternak
> Signed-off-by: Darren Hart (VMware)
> ---
>
On Thu, Mar 07, 2019 at 01:10:13AM +0100, Enrico Weigelt, metux IT consult
wrote:
> On 05.03.19 14:56, Andy Shevchenko wrote:
> >
> > Darren gave a talk about merging kernel configs to get something like
> > you want to.
> > This tool is quite long already lying around. merge_config.sh in your
>
在 2019-03-07 14:49，Balakrishna Godavarthi 写道：
Hi Stepen,
On 2019-03-07 04:03, Stephen Boyd wrote:
Quoting Balakrishna Godavarthi (2019-03-06 08:21:13)
This patch enables enough time to ROME controller to bootup
after we bring the enable ping out of reset.
Signed-off-by: Balakrishna
On (03/07/19 15:41), Sergey Senozhatsky wrote:
> This sounds concerning. IMHO, netconsole is too important to rely
> on preemptible printk and scheduler. Especially those netcons which
> run in "report only when oops_in_progress" mode. Sometimes netconsole
> is the fastest console available, but
Hi Stepen,
On 2019-03-07 04:03, Stephen Boyd wrote:
Quoting Balakrishna Godavarthi (2019-03-06 08:21:13)
This patch enables enough time to ROME controller to bootup
after we bring the enable ping out of reset.
Signed-off-by: Balakrishna Godavarthi
---
Any Fixes tag? And maybe some more
Hi Jarkko,
On 3/6/2019 3:52 PM, Jarkko Nikula wrote:
Hi
On 3/6/19 5:05 AM, xiao jin wrote:
From: "he, bo"
We find spi can't work on board. More debug shows it's related
to the following patch that changed the chip selection assert and
deassert timing.
^^ timing caught my attention. More
On Feb 17, 2019, "Maciej W. Rozycki" wrote:
> Is there an MMIO completion barrier missing there somewhere by any chance
> causing an IRQ that has been handled already to be redelivered because an
> MMIO write meant to clear the IRQ at its origin at handler's completion
> has not reached its
On (03/06/19 23:22), John Ogness wrote:
> On 2019-03-06, Petr Mladek wrote:
> >> _Both_ categories are important for the user, but their requirements
> >> are different:
> >>
> >>informational: non-disturbing
> >>emergency: reliable
> >
> > Isn't this already handled by the
On Thu, 2019-03-07 at 13:03 +0900, Masahiro Yamada wrote:
[...]
> If make-kpkg will still be included in the future Debian releases,
> I'd like to change make-kpkg to make it work more reliably.
>
>
> The git URL in the control file
>
Hi James,
On 3/7/19 2:08 AM, James Sewart wrote:
- /*
-* For each rmrr
-* for each dev attached to rmrr
-* do
-* locate drhd for dev, alloc domain for dev
-* allocate free domain
-* allocate page table entries for rmrr
-
On 03/07/2019 03:48 AM, Qian Cai wrote:
pte_unmap() compiles away on some powerpc platforms, so silence the
warnings below by using the argument to pte_unmap() as a nop. Also, fix
checkpatch.pl warnings "Single statement macros should not use a do {}
while (0) loop".
mm/memory.c: In function
This is mostly update of the usual drivers: arcmsr, qla2xxx, lpfc,
hisi_sas, target/iscsi and target/core. Additionally Christoph
refactored gdth as part of the dma changes. The major mid-layer change
this time is the removal of bidi commands and with them the whole of
the osd/exofs driver and
Hi Darren,
On Thu, Mar 7, 2019 at 3:17 PM Darren Hart wrote:
>
> On Wed, Mar 06, 2019 at 10:09:26PM -0800, Darren Hart wrote:
> > On Sat, Feb 23, 2019 at 08:57:50PM +0100, Mattias Jacobsson wrote:
> > > On 2019-02-20, Masahiro Yamada wrote:
> >
> > > > > > If you want all the patches to go
On Tue, Feb 19, 2019 at 08:59:48PM +0100, Mattias Jacobsson wrote:
> The kernel provides the macro MODULE_DEVICE_TABLE() which can help
> driver authors to generate the appropriate MODULE_ALIAS() output. The
> WMI device type is currently not supported by MODULE_DEVICE_TABLE().
Thanks Mattias. I
Hi Jiada
> two issues were found due to linux-next commit
> 7674bec4fc09 ("ASoC: rsnd: update BSDSR/BSDISR handling")
> this patch-set address these two issues
>
> ---
> v2: Update rsnd_of_match table instead of set priv->flags in probe
>
> v1: initial version
>
> Jiada Wang (2):
> ASoC:
Hi Daniel,
On 03/04/2019 05:26 AM, Daniel Axtens wrote:
Hi Christophe,
diff --git a/arch/powerpc/include/asm/kasan.h b/arch/powerpc/include/asm/kasan.h
new file mode 100644
index ..c3161b8fc017
--- /dev/null
+++ b/arch/powerpc/include/asm/kasan.h
@@ -0,0 +1,15 @@
+/*
On Wed, Mar 06, 2019 at 10:09:26PM -0800, Darren Hart wrote:
> On Sat, Feb 23, 2019 at 08:57:50PM +0100, Mattias Jacobsson wrote:
> > On 2019-02-20, Masahiro Yamada wrote:
>
> > > > > If you want all the patches to go through x86 platform-driver tree,
> > > > > I am fine with that too.
> > > >
>
two issues were found due to linux-next commit
7674bec4fc09 ("ASoC: rsnd: update BSDSR/BSDISR handling")
this patch-set address these two issues
---
v2: Update rsnd_of_match table instead of set priv->flags in probe
v1: initial version
Jiada Wang (2):
ASoC: rsnd: src: Avoid a potential
compiler complains about following declarations
sound/soc/sh/rcar/src.c:174:1: warning: 'static' is not at beginning of
declaration [-Wold-style-declaration]
const static u32 bsdsr_table_pattern1[] = {
^
sound/soc/sh/rcar/src.c:183:1: warning: 'static' is not at beginning of
declaration
lockdep warns us that priv->lock and k->k_lock can cause a
deadlock when after acquire of k->k_lock, process is interrupted
by src, while in another routine of src .init, k->k_lock is
acquired with priv->lock held.
This patch avoids a potential deadlock by not calling soc_device_match()
in SRC
On Sat, Feb 23, 2019 at 08:57:50PM +0100, Mattias Jacobsson wrote:
> On 2019-02-20, Masahiro Yamada wrote:
> > > > If you want all the patches to go through x86 platform-driver tree,
> > > > I am fine with that too.
> > >
> > > I don't mind either way, however I've asked the x86 platform-driver
>
commit af692e117cb8cd9d3d844d413095775abc1217f9 upstream.
This patch resolves the following page use-after-free issue,
z_erofs_vle_unzip:
...
for (i = 0; i < nr_pages; ++i) {
...
z_erofs_onlinepage_endio(page); (1)
}
for (i = 0; i < clusterpages; ++i) {
On Thu, Mar 7, 2019 at 1:03 AM Jiri Bohac wrote:
>
> Hi,
>
> On Wed, Mar 06, 2019 at 07:38:59PM +0800, Kairui Song wrote:
> > +int register_mem_pfn_is_ram(int (*fn)(unsigned long pfn))
> > +{
> > + if (mem_pfn_is_ram)
> > + return -EBUSY;
> > + mem_pfn_is_ram = fn;
> > +
Avoid conflicts from other subsystems by including the header with the
rest of the driver files.
Cc: Andy Shevchenko
Cc: Vadim Pasternak
Signed-off-by: Darren Hart (VMware)
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
On Thu, 7 Mar 2019, Dominique Martinet wrote:
> > >
> > > addr = 4095
> > > vma->vm_end = 4096
> > > pages = 1000
> > >
> > > then `end' is 4096 and `(end - addr) << PAGE_SHIFT' is zero, but it
> > > should have been 1.
> >
> > Good catch! It should rather be something like
> >
> >
On Thu, Mar 7, 2019 at 5:46 AM Kees Cook wrote:
>
> On Sat, Mar 2, 2019 at 1:43 AM Oded Gabbay wrote:
> >
> > When parsing the address of an internal command buffer, the driver prints
> > an error if the buffer's address is not in the range of the device's DRAM
> > or SRAM memory address space.
On Wed, Mar 06, 2019 at 09:27:01PM -0800, Darren Hart wrote:
> On Mon, Mar 04, 2019 at 02:37:35PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the drivers-x86 tree got a conflict in:
> >
> > include/linux/platform_data/mlxreg.h
> >
> > between commit:
> >
>
commit af692e117cb8cd9d3d844d413095775abc1217f9 upstream.
This patch resolves the following page use-after-free issue,
z_erofs_vle_unzip:
...
for (i = 0; i < nr_pages; ++i) {
...
z_erofs_onlinepage_endio(page); (1)
}
for (i = 0; i < clusterpages; ++i) {
Hi,
>Pawel,
>
>On 14/02/2019 21:45, Pawel Laszczak wrote:
>> This patch introduce new Cadence USBSS DRD driver to linux kernel.
>>
>> The Cadence USBSS DRD Driver is a highly configurable IP Core whichi
>> can be instantiated as Dual-Role Device (DRD), Peripheral Only and
>> Host Only
commit a112152f6f3a2a88caa6f414d540bd49e406af60 upstream.
EROFS has an optimized path called TAIL merging, which is designed
to merge multiple reads and the corresponding decompressions into
one if these requests read continuous pages almost at the same time.
In general, it behaves as follows:
On Mon, Mar 04, 2019 at 02:37:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the drivers-x86 tree got a conflict in:
>
> include/linux/platform_data/mlxreg.h
>
> between commit:
>
> 9f03161a1bd8 ("platform_data/mlxreg: additions for Mellanox watchdog
>
From: Shile Zhang
Read /sys/fs/bcache//cacheN/priority_stats can take very long
time with huge cache after long run.
Signed-off-by: Shile Zhang
---
drivers/md/bcache/sysfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/md/bcache/sysfs.c b/drivers/md/bcache/sysfs.c
index
Hi all.
As you may have noticed, recently I've been working on a reworked version
of sm712fb, and planned to convert it to a DRM/KMS driver. Besides using
it on embedded/non-x86 systems, I thought it would be a good idea to support
histrocial x86 laptops with this VGA chipset as well, so I've
Hi John,
On (03/05/19 22:00), John Ogness wrote:
> Hi Sergey,
>
[..]
> Console printing is a convenient feature to allow a kernel to
> communicate information to a user without any reliance on
> userspace. IMHO there are 2 categories of messages that the kernel will
> communicate. The first is
On Wed, Mar 06, 2019 at 02:37:21PM +0100, Arnd Bergmann wrote:
>
> There is also y2070 (many RTCs), y2100 (some other RTCs, especially
> those that assume it's a leap year), and y2106.
That's okay, Arnd. When the time comes you can come out of retirement
and cash in, doing Y2.07, Y2.1, and
hi Matthias,
On 2019-03-07 06:10, Matthias Kaehlcke wrote:
Firmware download to the WCN3990 often fails with a 'TLV response size
mismatch' error:
[ 133.064659] Bluetooth: hci0: setting up wcn3990
[ 133.489150] Bluetooth: hci0: QCA controller version 0x02140201
[ 133.495245] Bluetooth:
On Wed, 2019-03-06 at 18:52 +0800, Nicolas Boichat wrote:
> On Tue, Feb 26, 2019 at 9:11 PM Qii Wang wrote:
> >
> > Add i2c compatible for MT8183. Compare to MT2712 i2c controller,
> > MT8183 has different register offsets. Ltiming_reg is added to
> > adjust low width of SCL. Arb clock and
On Thu, Jan 10, 2019 at 06:40:00PM +0100, Lubomir Rintel wrote:
> The XO-1 and XO-1.5 batteries apparently differ in an ability to report
> ambient temperature. Add a different compatible string to the 1.5
> battery.
Hi Lubomir,
Thanks for the recent Cc and pointer to here. In general, I have no
On Thu, Mar 7, 2019 at 5:13 AM Joel Fernandes wrote:
>
> Hi Masahiro,
> Thanks for review, my replies are inline:
>
> On Wed, Mar 06, 2019 at 09:26:14PM +0900, Masahiro Yamada wrote:
> > On Mon, Mar 4, 2019 at 1:15 AM Joel Fernandes wrote:
> > >
> > > This report is for an older version of the
On Wed, 2019-03-06 at 18:49 +0800, Nicolas Boichat wrote:
> One thing I missed from Matthias' comment on v4:
> https://patchwork.kernel.org/patch/10822083/
>
> On Wed, Mar 6, 2019 at 6:44 PM Nicolas Boichat wrote:
> >
> > On Tue, Feb 26, 2019 at 9:11 PM Qii Wang wrote:
> > >
> > > When two i2c
We want to have some more space in our queue for processing incoming
multicast packets, so we can process more of them without dropping
them prematurely. It is useful to be able to increase this limit on
higher-spec platforms that can handle more items.
For the particular use case here at Allied
We want to be able to keep more spaces available in our queue for
processing incoming multicast traffic (adding (S,G) entries) - this lets
us learn more groups faster, rather than dropping them at this stage.
Signed-off-by: Brodie Greenfield
---
Documentation/networking/ip-sysctl.txt | 8
We want to be able to keep more spaces available in our queue for
processing incoming IPv6 multicast traffic (adding (S,G) entries) - this
lets us learn more groups faster, rather than dropping them at this stage.
Signed-off-by: Brodie Greenfield
---
Documentation/networking/ip-sysctl.txt | 8
On Thu, Mar 7, 2019 at 5:31 AM Joel Fernandes wrote:
>
>
> > On Sat, Mar 2, 2019 at 2:00 PM kbuild test robot wrote:
> > >
> > > Hi Joel,
> > >
> > > Thank you for the patch! Yet something to improve:
> > >
> > > [auto build test ERROR on linus/master]
> > > [also build test ERROR on v5.0-rc8]
>
On Wed, Mar 6, 2019 at 7:56 PM Mimi Zohar wrote:
> The kexec and kernel modules patches in this patch set continues to
> ignore IMA. This patch set should up front either provide an
> alternative solution to coordinate the different signature
> verification methods or rely on the architecture
[Re: [PATCH v5 00/18] mfd: demodularization of non-modular drivers] On
07/03/2019 (Thu 00:10) Pavel Machek wrote:
> On Wed 2019-01-16 13:24:31, Lee Jones wrote:
> > [...]
> >
> > > Paul Gortmaker (18):
> > > mfd: aat2870-core: Make it explicitly non-modular
> > > mfd: adp5520: Make it
On Thu, Mar 7, 2019 at 6:02 AM Ben Hutchings wrote:
>
> [Trying again with an alternate address for Manoj.]
>
> kernel-package is maintained by Manoj Srivastava (cc'd), not by the
> Debian kernel team.
>
> On Thu, 2019-03-07 at 01:00 +0900, Masahiro Yamada wrote:
> > Since commit 3812b8c5c5d5
Is this just converting spaces to tabs?
Looks identical at first glance otherwise (see screenshot)
On Wed, Mar 6, 2019 at 4:23 PM Enrico Weigelt, metux IT consult
wrote:
>
> Formatting of Kconfig files doesn't look so pretty, so just
> take damp cloth and clean it up.
>
> Signed-off-by: Enrico
On Wed, 2019-03-06 at 15:58 -0800, Matthew Garrett wrote:
> 3) The integration with IMA has been dropped for now. IMA is in the
> process of adding support for architecture-specific policies that will
> interact correctly with the lockdown feature, and a followup patch will
> integrate that so we
pte_unmap() compiles away on some powerpc platforms, so silence the
warnings below by using the argument to pte_unmap() as a nop. Also, fix
checkpatch.pl warnings "Single statement macros should not use a do {}
while (0) loop".
mm/memory.c: In function 'copy_pte_range':
mm/memory.c:820:24:
On Sat, Mar 2, 2019 at 1:43 AM Oded Gabbay wrote:
>
> When parsing the address of an internal command buffer, the driver prints
> an error if the buffer's address is not in the range of the device's DRAM
> or SRAM memory address space.
>
> Use %px to print the real address that the user gave the
Bjorn Helgaas wrote:
> On Tue, Mar 5, 2019 at 5:26 PM Eric Wong wrote:
> > Bjorn Helgaas wrote:
>
> > > Any pointers? I guess there's no mutt backend that can read a
> > > public-inbox archive directly?
> >
> > There's mutt patches to support reading over NNTP, so that
> > works:
> >
> >
Add new fixed clock osc_hdmi_phy_27m.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
index 8e9d6d5..fbcdd4d 100644
---
There is another 27MHz OSC inside i.MX8MQ's display block and
it can be one of reference clocks of all PLLs, add it into clock
tree and also add it as PLL's reference clock.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx8mq.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Add IMX8MQ_CLK_HDMI_PHY_27M clock for i.MX8MQ clock tree.
Signed-off-by: Anson Huang
---
include/dt-bindings/clock/imx8mq-clock.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/dt-bindings/clock/imx8mq-clock.h
b/include/dt-bindings/clock/imx8mq-clock.h
index
On 27.02.19 08:18, Morris Ku wrote:
Hi,
first of all: the code is pretty unreadable. I doubt that anybody here
seriously likes to review that (nor take it into mainline).
Formatting should be consistent - see other drivers.
./scripts/checkpatch.pl is your friend. You really shut run it and
I am sorry to have missed some comment, and reply the mail again.
On Wed, 2019-02-20 at 15:41 +0100, Matthias Brugger wrote:
>
> On 20/02/2019 13:33, Qii Wang wrote:
> > Add i2c compatible for MT8183. Compare to MT2712 i2c controller,
> > MT8183 has different registers, offsets and clock.
> >
>
On 2019/3/6 下午7:05, Arnd Bergmann wrote:
On some architectures, the MMU can be disabled, leading to access_ok()
becoming an empty macro that does not evaluate its size argument,
which in turn produces an unused-variable warning:
drivers/vhost/vhost.c:1191:9: error: unused variable 's'
On Tue, 5 Mar 2019, Andreas Schwab wrote:
> On Mar 05 2019, Finn Thain wrote:
>
> > interesting that the kernel's strlen implementation in
> > include/linux/string.h can't achieve this.
>
> This implementation is only available if ARCH_HAS_FORTIFY_SOURCE.
>
I see. Perhaps we could add
Hi Jiada
Thank you for your patch
> This patch moves the 'static' keyword to the front of the
> declaration to fix the compiler warnings
>
> Fixes: linux-next commit 7674bec4fc09 ("ASoC: rsnd: update BSDSR/BSDISR
> handling")
> Signed-off-by: Jiada Wang
> ---
Acked-by: Kuninori Morimoto
Hi Jiada
Thank you for your patch
> lockdep warns us that priv->lock and k->k_lock can cause a
> deadlock when after acquire of k->k_lock, process is interrupted
> by src, while in another routine of src .init, k->k_lock is
> acquired with priv->lock held.
>
> This patch avoids a potential
On 2019/3/7 上午12:31, Michael S. Tsirkin wrote:
+static void vhost_set_vmap_dirty(struct vhost_vmap *used)
+{
+ int i;
+
+ for (i = 0; i < used->npages; i++)
+ set_page_dirty_lock(used->pages[i]);
This seems to rely on page lock to mark page dirty.
Could it happen
If netlbl_sock_setattr() is failed, it directly returns rc and forgets
to free secattr.
BUG: memory leak
unreferenced object 0x8883c3ea4200 (size 2664):
comm "syz-executor.2", pid 8813, jiffies 4297264419 (age 156.090s)
hex dump (first 32 bytes):
7f 00 00 01 7f 00 00 01 eb 7f ed 71 4e
(Please remove at least LKML when responding. Mailing lists are a
scattershot attempt to reach others who might be interested in this
topic since I'm not aware of any linux-udf mailing list. )
A few months ago I stumbled across an interesting bit of abandonware in
the Sourceforge CVS repo
On 3/6/2019 6:30 PM, Adrian Hunter wrote:
On 2/03/19 7:20 AM, Sowjanya Komatineni wrote:
This patch adds a quirk for setting CMD_TIMING to 1 in descriptor
for DCMD with R1B response type to allow the command to be sent to
device during data activity or busy time.
Tegra186 CQHCI host has bug
On 2019/3/7 上午2:43, Souptick Joarder wrote:
On Wed, Mar 6, 2019 at 12:48 PM Jason Wang wrote:
Signed-off-by: Jason Wang
Is the change log left with any particular reason ?
Nope, will add the log.
Thanks
---
drivers/vhost/vhost.c | 46 --
On 2019/3/6 下午6:56, Christophe de Dinechin wrote:
On 6 Mar 2019, at 08:18, Jason Wang wrote:
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 46 --
1 file changed, 28 insertions(+), 18 deletions(-)
diff --git a/drivers/vhost/vhost.c
On 2019/3/6 下午6:45, Christophe de Dinechin wrote:
On 6 Mar 2019, at 08:18, Jason Wang wrote:
This is used to hide the metadata address from virtqueue helpers. This
will allow to implement a vmap based fast accessing to metadata.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 94
lockdep warns us that priv->lock and k->k_lock can cause a
deadlock when after acquire of k->k_lock, process is interrupted
by src, while in another routine of src .init, k->k_lock is
acquired with priv->lock held.
This patch avoids a potential deadlock by not calling soc_device_match()
in SRC
compiler complains about following declarations
sound/soc/sh/rcar/src.c:174:1: warning: 'static' is not at beginning of
declaration [-Wold-style-declaration]
const static u32 bsdsr_table_pattern1[] = {
^
sound/soc/sh/rcar/src.c:183:1: warning: 'static' is not at beginning of
declaration
two issues were found due to linux-next commit
7674bec4fc09 ("ASoC: rsnd: update BSDSR/BSDISR handling")
this patch-set address these two issues
Jiada Wang (2):
ASoC: rsnd: src: Avoid a potential deadlock
ASoC: rsnd: src: fix compiler warnings
sound/soc/sh/rcar/core.c | 3 +++
Here's v2 of my little helper for sending patches to maintainers.
changes v2:
- don't check for topdir 'firmware', which had been removed recently
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
This is a little helper script for mailing patches out of a git
branch to the corresponding maintainers.
Essentially, it scans the touched files, asks get_maintainer.pl
for their maintainers and calls git-send-email for mailing out
the patches.
Syntax:
./scripts/git-send-patch []
Examples:
Hi Linus,
Please consider pulling changes to scripts/leaking_addresses.pl
I've started using my kernel.org email address. I believe its the key
you care about not the email address this email is sent from, the tag is
signed as usual.
thanks,
Tobin.
The following changes since commit
From: YueHaibing
register_snap_client may return NULL, all the callers
check it, but only print a warning. This will result in
NULL pointer dereference in unregister_snap_client and other
places.
It has always been used like this since v2.6
Reported-by: Dan Carpenter
Signed-off-by: YueHaibing
Formatting of Kconfig doesn't look so pretty, so just take
a damp cloth and clean it up.
Signed-off-by: Enrico Weigelt, metux IT consult
---
drivers/uio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/uio/Kconfig b/drivers/uio/Kconfig
index 7e8dc78..4286b73
Hi, Bibby:
On Thu, 2019-03-07 at 09:39 +0800, CK Hu wrote:
> Hi, Bibby:
>
> On Wed, 2019-03-06 at 17:50 +0800, Bibby Hsieh wrote:
> > cmdq driver provide a function that get the relationship
> > of sub system number from device node for client.
> > add specification for #subsys-cells,
On 2019-03-07 06:10, Matthias Kaehlcke wrote:
Rename STATE_IN_BAND_SLEEP_ENABLED to QCA_IN_BAND_SLEEP_ENABLED.
The constant represents a flag (multiple flags can be set at once),
not a unique state of the controller or driver. Also use the BIT()
macro to specify the position of the flag instead
--
Dear Friend,
I am Mrs Clara David. am sending you this brief letter to solicit your
partnership to transfer $18.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsclarad...@gmail.com)
1 - 100 of 943 matches
Mail list logo
