On Mon, Jul 08, 2019 at 09:03:59AM -0400, Joel Fernandes wrote:
> > Actually, the intent was to only allow this to be changed at boot time.
> > Of course, if there is now a good reason to adjust it, it needs
> > to be adjustable. So what situation is making you want to change
> >
08.07.2019 2:38, Dmitry Osipenko пишет:
> The Tegra's clocksource driver got some rework recently and now the
> internal/local CPU timers usage is discouraged on Tegra20/30 SoCs in
> a favor of the platform-specific timers that are assigned as per-CPU
> clocksources because they do not suffer from
Hi Oleksij,
Any comments on this?
On Thu, Jun 27, 2019 at 11:14 AM Daniel Baluta wrote:
>
> Some of i.MX8 processors (e.g i.MX8QM, i.MX8QXP) contain
> the Tensilica HiFi4 DSP for advanced pre- and post-audio
> processing.
>
> The communication between Host CPU and DSP firmware is
> taking
Hi Linus,
please pull enhancements for the parisc architecture for kernel 5.3 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-5.3-1
Dynamic ftrace support by Sven Schnelle and a header guard fix by Denis Efremov.
Thanks,
Helge
On Mon, 8 Jul 2019 at 20:33, Fuqian Huang wrote:
>
> Introduce local variable 'struct device *dev' and use it instead of
> dereferencing it repeatly.
>
> Signed-off-by: Fuqian Huang
Looks good to me. Thanks.
Reviewed-by: Baolin Wang
> ---
> drivers/power/supply/sc27xx_fuel_gauge.c | 47
>
Hi Fuqian,
On Mon, 8 Jul 2019 at 20:33, Fuqian Huang wrote:
>
> devm_add_action_or_reset() is introduced as a helper function which
> internally calls devm_add_action(). If devm_add_action() fails
> then it will execute the action mentioned and return the error code.
> This reduce source code
On 08-07-19, 16:11, k.koniec...@partner.samsung.com wrote:
> From: Kamil Konieczny
>
> Add enable regulators to dev_pm_opp_set_regulators() and disable
> regulators to dev_pm_opp_put_regulators(). This prepares for
> converting exynos-bus devfreq driver to use dev_pm_opp_set_rate().
>
>
On Mon, 2019-07-08 at 23:14 -0400, J. Bruce Fields wrote:
> On Thu, Jul 04, 2019 at 04:57:48PM -0700, Joe Perches wrote:
> > Probable cut typo - use the correct field size.
>
> Huh, that's been there forever, I wonder why we haven't seen crashes?
> Oh, I see, name and authname both have the same
Hi, Viresh
> On 08-07-19, 08:54, Anson Huang wrote:
> > Each OPP has "opp-supported-hw" property as below, the first value
> > needs to be checked with speed grading fuse, and the second one needs
> > to be checked with market segment fuse, ONLY both of them passed, then
> > this OPP is
On 7/9/19 5:38 AM, Subhra Mazumdar wrote:
>
> On 7/8/19 10:24 AM, Parth Shah wrote:
>> When searching for an idle_sibling, scheduler first iterates to search for
>> an idle core and then for an idle CPU. By maintaining the idle CPU mask
>> while iterating through idle cores, we can mark
On 08. 07. 19, 21:02, Martin Hundebøll wrote:
> Guessing the base tty for a gsm0710 multiplexed serial device is not
> currently possible, which makes it racy to use with multiple modems.
>
> Add a way to map the physical serial tty to its related mux devices
> using a ioctl.
...
> ---
Hi Nick,
Will post next version with the changes you have suggested.
There is a comment below.
On 07/07/2019 03:43 PM, Nicholas Piggin wrote:
Abhishek Goel's on July 4, 2019 7:18 pm:
Currently, the cpuidle governors determine what idle state a idling CPU
should enter into based on heuristics
There is only one functional change: the unnecessary check
"if (sctrl.enable != 1) return -EFAULT;" is removed, because when we're in
hv_synic_cleanup(), we're absolutely sure sctrl.enable must be 1.
The new functions hv_synic_disable/enable_regs() will be used by a later patch
to support
On Tue, Jul 9, 2019 at 12:52 PM Aneesh Kumar K.V
wrote:
>
> On 7/9/19 7:50 AM, Oliver O'Halloran wrote:
> > On Tue, Jul 9, 2019 at 12:22 AM Aneesh Kumar K.V
> > wrote:
> >>
> >> Christophe Leroy writes:
> >>
> >>> *snip*
> >>> + if (IS_ENABLED(CONFIG_PPC64))
> >>> + isync();
>
This is needed for hibernation, e.g. when we resume the old kernel, we need
to disable the "current" kernel's hypercall page and then resume the old
kernel's.
Signed-off-by: Dexuan Cui
---
arch/x86/hyperv/hv_init.c | 34 ++
1 file changed, 34 insertions(+)
diff
On 08. 07. 19, 21:02, Martin Hundebøll wrote:
> The n_gsm driver handles registration of /dev/gsmttyX nodes, so there's
> no need to do mknod manually.
>
> Signed-off-by: Martin Hundebøll
> ---
> Documentation/serial/n_gsm.rst | 10 --
> 1 file changed, 10 deletions(-)
>
> diff --git
This is needed when we resume the old kernel from the "current" kernel.
Signed-off-by: Dexuan Cui
---
drivers/hv/vmbus_drv.c | 40
1 file changed, 40 insertions(+)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index 72d5a7c..1c2d935
Hi,
This is the first patchset to enable hibernation when Linux VM runs on Hyper-V.
A second patchset to enhance the high-level VSC drivers (hv_netvsc,
hv_storvsc, etc.) for hibernation will be posted later. The second patchset
depends on this first patchset, so I hope this pathset can be
This is needed for hibernation, e.g. when we resume the old kernel, we need
to disable the "current" kernel's TSC page and then resume the old kernel's.
Signed-off-by: Dexuan Cui
---
drivers/clocksource/hyperv_timer.c | 25 +
1 file changed, 25 insertions(+)
diff --git
This is needed when we resume the old kernel from the "current" kernel.
Signed-off-by: Dexuan Cui
---
drivers/hv/connection.c | 3 +--
drivers/hv/hyperv_vmbus.h | 2 ++
drivers/hv/vmbus_drv.c| 40
3 files changed, 43 insertions(+), 2 deletions(-)
The high-level VSC drivers will implement device-specific callbacks.
Signed-off-by: Dexuan Cui
---
drivers/hv/vmbus_drv.c | 42 ++
include/linux/hyperv.h | 3 +++
2 files changed, 45 insertions(+)
diff --git a/drivers/hv/vmbus_drv.c
When the VM resumes, the host re-sends the offers. We should not add the
offers to the global vmbus_connection.chn_list again.
Added some debug code, in case the host screws up the exact info related to
the offers.
Signed-off-by: Dexuan Cui
---
drivers/hv/channel_mgmt.c | 28
-Original Message-
From: Leo Li
Sent: 2019年7月9日 3:41
To: Biwen Li ; a.zu...@towertech.it;
alexandre.bell...@bootlin.com
Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Xiaobo Xie
; Jiafei Pan ; Ran Wang
; Biwen Li
Subject: RE: [PATCH 1/2] rtc/fsl: add FTM alarm driver
Hello Arnd,
(Added Randy who also sent a patch to fix this)
On Mon, 2019-07-08 at 18:10 +0200, Arnd Bergmann wrote:
> On Mon, Jul 8, 2019 at 3:24 PM Vaittinen, Matti
> wrote:
>
> > On Mon, 2019-07-08 at 14:41 +0200, Arnd Bergmann wrote:
> > > With CONFIG_BD70528_WATCHDOG=m, a built-in rtc
On 2019/07/08 18:42, Eiichi Tsukata wrote:
>
>
> On 2019/07/08 17:58, Eiichi Tsukata wrote:
>
>>
>> By the way, is there possibility that the WARNING(#GP in execve(2)) which
>> Steven
>> previously hit? :
>> https://lore.kernel.org/lkml/20190321095502.47b51...@gandalf.local.home/
>>
>>
Hi Mathieu,
On Mon, Jul 08, 2019 at 11:33:59AM -0600, Mathieu Poirier wrote:
> On Wed, 19 Jun 2019 at 21:45, Leo Yan wrote:
> >
> > Arm and arm64 architecture reserve some memory regions prior to the
> > symbol '_stext' and these memory regions later will be used by device
> > module and BPF
The pull request you sent on Mon, 08 Jul 2019 12:40:05 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> siginfo-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5ad18b2e60b75c7297a998dea702451d33a052ed
Thank you!
--
Le 08/07/2019 à 21:14, Nathan Chancellor a écrit :
On Mon, Jul 08, 2019 at 11:19:30AM +1000, Michael Ellerman wrote:
On Fri, 2019-05-10 at 09:24:48 UTC, Christophe Leroy wrote:
Cache instructions (dcbz, dcbi, dcbf and dcbst) take two registers
that are summed to obtain the target address.
Hi,
Now that a rebased copy of the mali-dp tree has been merged into the
drm tree, please clean up the mali-dp tree as it is causing conflicts.
--
Cheers,
Stephen Rothwell
pgpPThBmE24nb.pgp
Description: OpenPGP digital signature
On Sun, Jul 07, 2019 at 05:49:35PM +0200, Salvatore Mesoraca wrote:
> Al Viro wrote:
> >
> > On Sat, Jul 06, 2019 at 12:54:47PM +0200, Salvatore Mesoraca wrote:
> >
> > > +#define sara_warn_or_return(err, msg) do { \
> > > + if ((sara_wxp_flags & SARA_WXP_VERBOSE))\
> > > +
On Mon, Jul 08, 2019 at 08:37:42PM -0400, Valdis Klētnieks wrote:
> I have an out-of-tree driver for the exfat file system that I beaten into
> shape
> for upstreaming. The driver works, and passes sparse and checkpatch (except
> for a number of line-too-long complaints).
>
> Do you want this
Wen Yang writes:
> The cpu variable is still being used in the of_get_property() call
> after the of_node_put() call, which may result in use-after-free.
>
> Fixes: a9acc26b75f ("cpufreq/pasemi: fix possible object reference leak")
> Signed-off-by: Wen Yang
> Cc: "Rafael J. Wysocki"
> Cc:
The pull request you sent on Mon, 8 Jul 2019 10:10:05 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/92c1d6522135050cb377a18cc6e30d08dfb87efb
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Mon, 8 Jul 2019 09:56:20 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/df2a40f549e6b73aad98b0c03f400c00d284816b
Thank you!
--
Deet-doot-dot, I am a bot.
On 08-07-19, 08:54, Anson Huang wrote:
> Each OPP has "opp-supported-hw" property as below, the first value needs to be
> checked with speed grading fuse, and the second one needs to be checked with
> market segment fuse, ONLY both of them passed, then this OPP is supported. It
> calls
The pull request you sent on Mon, 8 Jul 2019 23:08:00 +0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4d2fa8b44b891f0da5ceda3e5a1402ccf0ab6f26
Thank you!
--
Deet-doot-dot, I am a
On Mon, 8 Jul 2019 at 21:02, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.1.17 release.
> There are 96 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Tue, Jul 9, 2019 at 1:53 AM Andy Lutomirski wrote:
>
>
>
> > On Jul 8, 2019, at 3:35 AM, Thomas Gleixner wrote:
> >
> >> On Mon, 8 Jul 2019, Pingfan Liu wrote:
> >>> On Mon, Jul 8, 2019 at 3:44 AM Thomas Gleixner wrote:
> >>>
> On Fri, 5 Jul 2019, Pingfan Liu wrote:
>
> I hit
The current format of *.mod is like this:
line 1: directory path to the .ko file
line 2: a list of objects linked into this module
line 3: unresolved symbols (only when CONFIG_TRIM_UNSED_SYMBOLS=y)
Now that *.mod and *.ko are created in the same directory, the line 1
provides no valuable
Towards the goal of removing MODVERDIR, read out modules.order to get
the list of modules to be processed. This is simpler than parsing *.mod
files in $(MODVERDIR).
For external modules, $(KBUILD_EXTMOD)/modules.order should be read.
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.modpost
Nothing depends on this, so it is dead code.
Signed-off-by: Masahiro Yamada
---
I will apply this to kbuild tree since it is trivial.
drivers/scsi/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/Makefile b/drivers/scsi/Makefile
index
Towards the goal of removing MODVERDIR, read out modules.order to get
the list of modules to be installed. This is simpler than parsing *.mod
files in $(MODVERDIR).
For external modules, $(KBUILD_EXTMOD)/modules.order should be read.
Signed-off-by: Masahiro Yamada
---
scripts/Makefile.modinst
Currently, *.mod is created as a side-effect of obj-m.
Split out *.mod as a dedicated build rule, which allows to
unify the %.c -> %.o rule, and remove the single-used-m rule.
This also makes the incremental build of allmodconfig faster because
it saves $(NM) invocation when there is no change
Currently, only the top-level modules.order drops duplicated entries.
The modules.order files in sub-directories potentially contain
duplication. To list out the paths of all modules, I want to use
modules.order instead of parsing *.mod files in $(MODVERDIR).
To achieve this, I want to rip off
Now that there is no rule for 'prepare1', it can go away.
Signed-off-by: Masahiro Yamada
---
Makefile | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/Makefile b/Makefile
index 958fafa605b9..b284863e7ea0 100644
--- a/Makefile
+++ b/Makefile
@@ -1094,7 +1094,7 @@
Towards the goal of removing MODVERDIR, read out modules.order to get
the list of modules to be signed. This is simpler than parsing *.mod
files in $(MODVERDIR).
The modules_sign target is only supported for in-kernel modules.
So, this commit does not take care of external modules.
While descending directories, Kbuild produces objects for modules,
but final *.ko files are linked in the modpost.
To keep track of modules, Kbuild creates a *.mod file in $(MODVERDIR)
for every module it is building. Some post-processing steps read the
necessary information from *.mod files.
Currently, $(objtree)/modules.order is touched in two places.
In the 'prepare0' rule, scripts/Makefile.build creates an empty
modules.order while processing 'obj=.'
In the 'modules' rule, the top-level Makefile overwrites it with
the correct list of modules.
It might be a good side-effect that
Removing the 'kernel/' prefix will make our life easier because we can
simply do 'cat modules.order' to get all built modules with full paths.
Currently, we parse the first line of '*.mod' files in $(MODVERDIR).
Since we have duplicated functionality here, I plan to remove MODVERDIR
entirely.
In
This series kills the long standing MODVERDIR.
Since MODVERDIR has a flat structure, it cannot avoid a race
condition when somebody introduces a module name conflict.
Kbuild now reads modules.order to get the list of all modules.
The post-processing/installation stages will be more robust
and
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
WARNING in bpf_jit_free
WARNING: CPU: 0 PID: 9077 at kernel/bpf/core.c:851 bpf_jit_free+0x157/0x1b0
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 9077 Comm: kworker/0:3 Not tainted
On Mon, 8 Jul 2019 at 20:58, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.58 release.
> There are 90 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Mon, Jul 08, 2019 at 09:29:04PM +0300, Dmitry V. Levin wrote:
> The syscall entry/exit is now exposed via PTRACE_GETEVENTMSG,
> update the test accordingly.
Oh yes, thank you!
Acked-by: Kees Cook
-Kees
>
> Reported-by: kernel test robot
> Signed-off-by: Dmitry V. Levin
> ---
>
>Hi,
>
>Pawel Laszczak writes:
+void cdns3_role_stop(struct cdns3 *cdns)
>>>
>>>not static? Why is it so that _start() is static but _stop() is not?
>>>Looks fishy
>>
>> This function is used in cdns3_role_stop in debugfs.c file so it can't
>> be static.
>
>it's still super fishy. Why don't
On 2019/7/8 21:46, Boris Ostrovsky wrote:
On 7/7/19 5:15 AM, Zhenzhong Duan wrote:
+static uint32_t __init xen_platform_hvm(void)
+{
+ if (xen_pv_domain())
+ return 0;
+
+ if (xen_pvh_domain() && nopv) {
+ /* Guest booting via the Xen-PVH boot entry
Hi Linus,
Please pull this loadpin update for v5.3-rc1. Details below...
Thanks!
-Kees
The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:
Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)
are available in the Git repository at:
On Mon, Jul 8, 2019 at 5:35 PM Thomas Gleixner wrote:
>
> On Mon, 8 Jul 2019, Pingfan Liu wrote:
> > On Mon, Jul 8, 2019 at 3:44 AM Thomas Gleixner wrote:
> > >
> > > On Fri, 5 Jul 2019, Pingfan Liu wrote:
> > >
> > > > I hit a bug on an AMD machine, with kexec -l nr_cpus=4 option. nr_cpus
> >
On Mon, 8 Jul 2019 at 20:53, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.133 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
Hi Linus,
Please pull these pstore updates for v5.3-rc1. Details below...
Thanks!
-Kees
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the Git repository at:
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+4da3ff23081bafe74...@syzkaller.appspotmail.com
Tested on:
commit: b9321614 bpf: fix precision bit propagation for BPF_ST ins..
git tree:
sst_platform_pcm_pointer is called from both snd_pcm_period_elapsed and
from snd_pcm_ioctl. Calling read timestamp results in recalculating
pcm_delay and buffer_ptr (sst_calc_tstamp) which consumes buffers in a
faster rate than intended.
In a tested BSW system with chtrt5650, for a rate of 48000,
Hi all,
On Mon, 8 Jul 2019 13:39:58 +1000 Stephen Rothwell
wrote:
>
> After merging the netfilter-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from :
> include/net/netfilter/nft_meta.h:6:21: warning: 'key' is narrower than values
> of its
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/infiniband/sw/siw/siw_cm.c: In function 'siw_create_listen':
drivers/infiniband/sw/siw/siw_cm.c:1978:3: error: implicit declaration of
function 'for_ifa'; did you mean 'fork_idle'?
#syz test: https://github.com/anakryiko/linux bpf-fix-precise-bpf_st
The pull request you sent on Mon, 08 Jul 2019 08:58:58 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git
> next-integrity
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8b68150883ca466a23e90902dd4113b22e692f04
Thank you!
--
#syz test: https://github.com/anakryiko/linux bpf-fix-precise-bpf_st
Hi all,
On Tue, 25 Jun 2019 16:04:32 +1000 Stephen Rothwell
wrote:
>
> After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/net/wireless/intersil/p54/txrx.c: In function 'p54_rx_data':
> drivers/net/wireless/intersil/p54/txrx.c:386:28:
> > > > +
> > > > + /* restore registers by regcache_sync */
> > > > + fsl_esai_register_restore(esai_priv);
> > > > +
> > > > + regmap_update_bits(esai_priv->regmap, REG_ESAI_TCR,
> > > > +ESAI_xCR_xPR_MASK, 0);
> > > > +
The main purpose of this patch series is to extend the
hip04_eth driver to support HI13X1_GMAC.
The offset and bitmap of some registers of HI13X1_GMAC
are different from hip04_eth common soc. In addition,
the definition of send descriptor and parsing descriptor
are different from hip04_eth common
HI13X1 changed the offsets and bitmaps for tx_desc
registers in the same peripheral device on different
models of the hip04_eth.
Signed-off-by: Jiangfeng Xiao
---
drivers/net/ethernet/hisilicon/hip04_eth.c | 34 +++---
1 file changed, 31 insertions(+), 3 deletions(-)
HI13X1_GMAC changed the offsets and bitmaps for
GE_TX_LOCAL_PAGE_REG registers in the same peripheral
device on different models of the hip04_eth. With the
default configuration, HI13X1_GMAC can also work without
any writes to the GE_TX_LOCAL_PAGE_REG register.
Signed-off-by: Jiangfeng Xiao
---
In general, group is the same as the port, but some
boards specify a special group for better load
balancing of each processing unit.
Signed-off-by: Jiangfeng Xiao
---
drivers/net/ethernet/hisilicon/hip04_eth.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
HI13X1 changed the offsets and bitmaps for rx_desc
registers in the same peripheral device on different
models of the hip04_eth.
Signed-off-by: Jiangfeng Xiao
---
drivers/net/ethernet/hisilicon/hip04_eth.c | 9 +
1 file changed, 9 insertions(+)
diff --git
Extend the hip04_eth driver to support HI13X1_GMAC.
Enable it with CONFIG_HI13X1_GMAC option.
Signed-off-by: Jiangfeng Xiao
---
drivers/net/ethernet/hisilicon/Kconfig | 10
drivers/net/ethernet/hisilicon/hip04_eth.c | 37 --
2 files changed, 40
The buf unit size of HI13X1_GMAC is cache_line_size,
which is 64, so the address we write to the buf register
needs to be shifted right by 6 bits.
The 31st bit of the PPE_CFG_CPU_ADD_ADDR register
of HI13X1_GMAC indicates whether to release the buffer
of the message, and the low indicates that it
HI13X1_GMAC delete request for soft reset at first,
otherwise, the subsequent initialization will not
take effect.
Signed-off-by: Jiangfeng Xiao
---
drivers/net/ethernet/hisilicon/hip04_eth.c | 24
1 file changed, 24 insertions(+)
diff --git
In general, group is the same as the port, but some
boards specify a special group for better load
balancing of each processing unit.
Signed-off-by: Jiangfeng Xiao
---
Documentation/devicetree/bindings/net/hisilicon-hip04-net.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
This patch fixes the following warning from sparse:
hip04_eth.c:533:23: warning: cast to restricted __be16
hip04_eth.c:533:23: warning: cast to restricted __be16
hip04_eth.c:533:23: warning: cast to restricted __be16
hip04_eth.c:533:23: warning: cast to restricted __be16
hip04_eth.c:534:23:
This patch fixes the following warning from sparse:
hip04_eth.c:468:25: warning: incorrect type in assignment
hip04_eth.c:468:25:expected unsigned int [usertype] send_addr
hip04_eth.c:468:25:got restricted __be32 [usertype]
hip04_eth.c:469:25: warning: incorrect type in assignment
Hi all,
After merging the rdma tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from /home/sfr/next/next/include/rdma/rdma_counter.h:12,
from :
/home/sfr/next/next/include/rdma/ib_verbs.h:2126:27: error: field
'port_counter' has incomplete
[ Adding a few mailing lists, since the thrust of my email is about
more people being around and involved, and the pull requests
themselves were indeed cc'd to the mailing lists too ]
On Thu, Jul 4, 2019 at 9:15 AM David Howells wrote:
>
> I have a bunch of keyrings patches to be pulled in
add jpeg enc device tree node
Signed-off-by: Xia Jiang
---
arch/arm/boot/dts/mt2701.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index 51e1305c6471..560f27fd9d9e 100644
--- a/arch/arm/boot/dts/mt2701.dtsi
Add mtk jpeg encode v4l2 driver based on jpeg decode, because that jpeg
decode and encode have great similarities with function operation.
add EXIF enable control for jpeg encode.
Signed-off-by: Xia Jiang
---
drivers/media/platform/mtk-jpeg/Makefile | 5 +-
Switch GPLv2 license to SPDX license.
Signed-off-by: Xia Jiang
---
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 9 +
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.h | 9 +
drivers/media/platform/mtk-jpeg/mtk_jpeg_dec_hw.c| 9 +
Rename the files which are for decode feature. This is a preparing
patch since the jpeg enc patch will be added later.
Signed-off-by: Xia Jiang
---
drivers/media/platform/mtk-jpeg/Makefile | 2 +-
drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 4 ++--
Add JPEG ENC device tree node document.
Signed-off-by: Xia Jiang
---
.../bindings/media/mediatek-jpeg-encoder.txt | 33 +++
1 file changed, 33 insertions(+)
create mode 100644
Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.txt
diff --git
This patchset add support for mt2701 JPEG ENC support.
This is the compliance test result for jpeg dec and enc.
The JPEG dec log:
v4l2-compliance -d /dev/video0
v4l2-compliance SHA: 08fed4d0edb1492b91d9d1054c36fed95c372eaa, 32 bits
Heiner Kallweit 於 2019年7月9日 週二 上午2:27寫道：
>
> On 08.07.2019 08:37, AceLan Kao wrote:
> > We have many commits in the driver which enable and then disable ASPM
> > function over and over again.
> >commit b75bb8a5b755 ("r8169: disable ASPM again")
> >commit 0866cd15029b ("r8169: enable ASPM
On 07/08/2019 11:09 PM, Peter Zijlstra wrote:
On Mon, Jul 08, 2019 at 09:23:19AM +0800, Wei Wang wrote:
This patch enables the LBR related features in Arch v4 in advance,
though the current vPMU only has v2 support. Other arch v4 related
support will be enabled later in another series.
Arch v4
Le lun. 8 juil. 2019 à 22:04, Rob Herring a écrit :
On Fri, Jun 07, 2019 at 05:44:05PM +0200, Paul Cercueil wrote:
Right now none of the Ingenic-based boards probe this driver from
devicetree. This driver defined three compatible strings for the
exact
same behaviour. Before these
On Tue, Jul 09, 2019 at 11:02:24AM +0800, YueHaibing wrote:
> Fix Kconfig dependency warning and subsequent build errors
> caused by OF is not set:
>
> WARNING: unmet direct dependencies detected for NET_DSA_VITESSE_VSC73XX
> Depends on [n]: NETDEVICES [=y] && HAVE_NET_DSA [=y] && OF [=n] &&
The pull request you sent on Fri, 05 Jul 2019 22:20:44 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/keys-namespace-20190627
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2e12256b9a76584fa3a6da19210509d4775aee36
Thank you!
--
The pull request you sent on Tue, 2 Jul 2019 13:28:33 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
> tags/audit-pr-20190702
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/61fc5771f5e729a2ce235af42f69c8506725e84a
Thank you!
--
The pull request you sent on Tue, 2 Jul 2019 13:28:37 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
> tags/selinux-pr-20190702
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7c0f89634892693fc0b46f25e0a6d57bd6dd5698
Thank you!
--
The pull request you sent on Fri, 05 Jul 2019 22:13:34 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/keys-request-20190626
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f771fde82051976a6fc0fd570f8b86de4a92124b
Thank you!
--
The pull request you sent on Fri, 05 Jul 2019 22:03:39 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/keys-misc-20190619
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/504b69eb3c95180bc59f1ae9096ad4b10bbbf254
Thank you!
--
The pull request you sent on Thu, 27 Jun 2019 01:50:47 +0300:
> git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20190625
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/884922591e2b58fd7f1018701f957446d1ffac4d
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 05 Jul 2019 22:30:39 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> tags/keys-acl-20190703
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0f75ef6a9cff49ff612f7ce0578bced9d0b38325
Thank you!
--
On Thu, Jul 04, 2019 at 04:57:48PM -0700, Joe Perches wrote:
> Probable cut typo - use the correct field size.
Huh, that's been there forever, I wonder why we haven't seen crashes?
Oh, I see, name and authname both have the same size.
Anyway, makes sense, thanks. Will apply for 5.3.
(Unless
Hi, Leonard
> On 7/8/2019 10:55 AM, anson.hu...@nxp.com wrote:
> > To reduce the suspend/resume latency, CPU's max supported frequency
> > should be used during low level suspend/resume phase, "opp-suspend"
> > property is NOT feasible since OPP defined in DT could be NOT
> > supported according
1 - 100 of 1336 matches
Mail list logo
