On Mon, Jun 24, 2019 at 02:59:16PM +0200, Fredrik Noring wrote:
> Hi Christoph,
>
> > Can you send me the patch formally so that I can queue it up for the
> > dma-mapping tree?
>
> That patch would be detrimental to local memory devices, as previously
> discussed, so I would like to suggest a
Hi all,
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: error: implicit declaration of
function 'ktime_get_boot_ns'; did you mean
On Mon, 24 Jun 2019, Matthew Garrett wrote:
> > We are still not resolved on granularity. Stephen has said he's not sure
> > if a useful policy can be constructed with just confidentiality and
> > integrity settings. I'd be interested to know JJ and Casey's thoughts on
> > lockdown policy
On 25/06/19, 1:51 AM, "Sasha Levin" wrote:
> On Tue, Jun 25, 2019 at 02:33:06AM +0530, Ajay Kaher wrote:
> > coredump: fix race condition between mmget_not_zero()/get_task_mm()
> > and core dumping
> >
> > [PATCH v4 1/3]:
> > Backporting of commit 04f5866e41fb70690e28397487d8bd8eea7d712a
>
> When all header files below include/drm are self-contained it will be a
> single line:
>
> header-test-y += $(all_headers_with_subdir)
In reality it will likely be the above, and then a list of
header-test-n += foo.h
For the header files that we for one or the other reason do not want
On Tue, Dec 18, 2018 at 09:55:45PM -0800, David Miller wrote:
> From: Sukumar Gopalakrishnan
> Date: Wed, 19 Dec 2018 10:57:02 +0530
>
> > Hi David,
> >
> > There are two patch for this issue:
> >1) Your changes which removes cache_resolve_queue_len
> > 2) Hangbin's changes which make
When there is not enough space on your storage device, the build will
fail with 'No space left on device' error message.
The reason is obvious from the message, so you will free up some disk
space, then you will resume the build.
However, sometimes you may still see a mysterious error message:
On Sun, Jun 23, 2019, Joe Perches wrote:
> > x86/cpu: Create Zhaoxin processors architecture support file
> >
> []
> > diff --git a/arch/x86/kernel/cpu/zhaoxin.c b/arch/x86/kernel/cpu/zhaoxin.c
> []
> > +static void init_zhaoxin_cap(struct cpuinfo_x86 *c)
> > +{
> > + u32 lo, hi;
> > +
> > +
On Mon, 24 Jun 2019, syzbot wrote:
> Hello,
CC++ Peterz
>
> syzbot found the following crash on:
>
> HEAD commit:dc636f5d Add linux-next specific files for 20190620
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=162b68b1a0
> kernel config:
Rong,
On Tue, 25 Jun 2019, Rong Chen wrote:
> On 6/22/19 3:08 AM, Thomas Gleixner wrote:
> > >
> > > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m
> > > 2G
> > I cannot reproduce that issue. What's the underlying hardware machine?
>
> brand: Genuine Intel(R) CPU 000
Stephen Rothwell writes:
> 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: error: implicit declaration
> of function
On Tue, 25 Jun 2019, Kalle Valo wrote:
> Stephen Rothwell writes:
> > ---
> > drivers/net/wireless/intersil/p54/txrx.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/intersil/p54/txrx.c
> > b/drivers/net/wireless/intersil/p54/txrx.c
> > index
On Tue, 25 Jun 2019, Linus Torvalds wrote:
> On Mon, Jun 24, 2019 at 10:34 PM Lee Jones wrote:
> >
> > Hopefully this is more to your liking.
>
> I would actually have preferred you to throw the old buggy "fix" away,
> and just do the final state.
You okayed the follow-up patch, so I took it
merged into cifs-2.6.git for-next
On Mon, Jun 24, 2019 at 3:25 PM Colin King wrote:
>
> From: Colin Ian King
>
> Field ia_valid is being debugged with the field name iavalid, fix this.
>
> Signed-off-by: Colin Ian King
> ---
> fs/cifs/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Mon, 24 Jun 2019, Dan Murphy wrote:
> Lee
>
> On 6/24/19 9:42 AM, Lee Jones wrote:
> > On Wed, 05 Jun 2019, Dan Murphy wrote:
> >
> > > Hello
> > >
> > > The v5 patchset missed adding in the new validation code.
> > > Patch 1 of the v5 series was squashed into patch 4 of the v5 series.
> >
Tony,
On Tue, 25 Jun 2019, Tony W Wang-oc wrote:
> On Sun, Jun 23, 2019, Joe Perches wrote:
> > > x86/cpu: Create Zhaoxin processors architecture support file
> > >
> > []
> > > diff --git a/arch/x86/kernel/cpu/zhaoxin.c b/arch/x86/kernel/cpu/zhaoxin.c
> > []
> > > +static void
On Mon, Jun 24, 2019 at 07:13:17PM +, Eugeniy Paltsev wrote:
> Hi Christoph,
>
> Yep I've reviewed and tested it for both cases:
> - coherent/noncoherent dma
> - allocation from atomic_pool/regular allocation
>
> everything works fine for ARC.
Thanks. I've applied the whole series to the
On 24/06/2019 23.53, Nick Desaulniers wrote:
> On Thu, Jun 20, 2019 at 1:46 PM Rasmus Villemoes
> wrote:
>>
>> I've pushed them to https://github.com/Villemoes/linux/tree/dyndebug_v6
>> . They rebase pretty cleanly to just about anything you might prefer
>> testing on. Enabling it for arm64 or
Hi Kalle,
On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>
> Thanks for the report. Any suggestions how to handle this? Or do we let
> Linus take care of this?
Just let Linus take care of it ... mention it in the pull request ... I guess
DaveM needs to know, right?
--
Cheers,
Stephen
Initial introduction of Lenovo Hr855xg2 family equipped with
Aspeed 2500 BMC SoC. Hr855xg2 is a x86 server development kit
with a ASPEED ast2500 BMC manufactured by Lenovo.
Specifically, This adds the Hr855xg2 platform device tree file
used by the Hr855xg2 BMC machines.
This also adds an entry of
In ipvlan l3s mode, ingress packet is switched to slave interface and
delivers to l4 stack. This may cause two problems:
1. When slave is in an ns different from master, the behavior of stack
in slave ns may cause confusion for users. For example, iptables, tc,
and other l2/l3 functions
On Thu, 13 Jun 2019, Matti Vaittinen wrote:
> ROHM BD71847 PMIC datasheet was published.
> Add datasheet link for BD71847 as well.
>
> Signed-off-by: Matti Vaittinen
> ---
> Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 2 ++
> 1 file changed, 2 insertions(+)
Applied, thanks.
On (06/19/19 00:12), John Ogness wrote:
> On 2019-06-18, Sergey Senozhatsky wrote:
> >> + struct prb_reserved_entry e;
> >> + char *s;
> >> +
> >> + s = prb_reserve(, , 32);
> >> + if (s) {
> >> + sprintf(s, "Hello, world!");
> >> + prb_commit();
> >> + }
> >
> > A nit:
Stephen Rothwell writes:
> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>>
>> Thanks for the report. Any suggestions how to handle this? Or do we let
>> Linus take care of this?
>
> Just let Linus take care of it ... mention it in the pull request ...
Thanks, I'll do that.
> I guess
When there is not enough space on your storage device, the build will
fail with 'No space left on device' error message.
The reason is obvious from the message, so you will free up some disk
space, then you will resume the build.
However, sometimes you may still see a mysterious error message:
On Tue, 25 Jun 2019, Stephen Rothwell wrote:
> Hi Kalle,
>
> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
> >
> > Thanks for the report. Any suggestions how to handle this? Or do we let
> > Linus take care of this?
>
> Just let Linus take care of it ... mention it in the pull request
Commit-ID: d48e0cd8fcaf314175a15d3076d7a1e71bd4e628
Gitweb: https://git.kernel.org/tip/d48e0cd8fcaf314175a15d3076d7a1e71bd4e628
Author: Jason A. Donenfeld
AuthorDate: Mon, 24 Jun 2019 11:15:39 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 08:54:51 +0200
timekeeping:
From: Anson Huang
i.MX8MM's GPT1 clock mux option #5 should be sys_pll1_80m,
NOT sys_pll1_800m, correct it.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx8mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/imx/clk-imx8mm.c
From: Anson Huang
i.MX8MM has no sys3_pll2_out clock, PWM3 clock's mux option #4
should be sys_pll3_out, sys3_pll2_out is a typo, fix it.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx8mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi liaoweixiong,
On 25.06.19 05:08, Greg KH wrote:
> On Tue, Jun 25, 2019 at 09:02:29AM +0800, liaoweixiong wrote:
>> In case of the last page containing bitflips (ret > 0),
>> spinand_mtd_read() will return that number of bitflips for the last
>> page. But to me it looks like it should instead
Jacky Bai would like to recall the message, "[PATCH 2/2] clk: imx8mm: GPT1
clock mux option #5 should be sys_pll1_80m".
OK for me.
BR
Jacky Bai
> -Original Message-
> From: anson.hu...@nxp.com [mailto:anson.hu...@nxp.com]
> Sent: Tuesday, June 25, 2019 3:06 PM
> To: mturque...@baylibre.com; sb...@kernel.org; shawn...@kernel.org;
> s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com;
> Leonard
Okay, will correct it and send v5 after rebase.
>On 25-06-19, 16:17, Vinod Koul wrote:
> On 14-06-19, 16:17, yibin.g...@nxp.com wrote:
> > From: Robin Gong
> >
> > There are some differences between vf610 and next i.mx7ulp. Put such
> > differences into static driver data for distiguish easily at
On Mon, Jun 24, 2019 at 04:57:22PM -0700, Alan Mikhak wrote:
> Modify nvme_alloc_sq_cmds() to call pci_free_p2pmem()
> to free the memory it allocated using pci_alloc_p2pmem()
> in case pci_p2pmem_virt_to_bus() returns null.
>
> Make sure not to call pci_free_p2pmem() if pci_alloc_p2pmem()
>
pon., 24 cze 2019 o 20:22 Enrico Weigelt, metux IT consult
napisał(a):
>
> On 24.06.19 12:46, Bartosz Golaszewski wrote:
>
> >> The patch seems pretty trivial and doesn't change any actual code, so
> >> I don't see hard resons for rejecting it.
> >>
> >
> > In its current form it makes the code
Reviewed-by: Robin Gong
> -Original Message-
> From: Sven Van Asbroeck
> Subject: [PATCH] dmaengine: imx-sdma: fix use-after-free on probe error path
>
> If probe() fails anywhere beyond the point where
> sdma_get_firmware() is called, then a kernel oops may occur.
>
> Problematic
On (06/25/19 15:45), Sergey Senozhatsky wrote:
> On (06/19/19 00:12), John Ogness wrote:
> > On 2019-06-18, Sergey Senozhatsky wrote:
> > >> +struct prb_reserved_entry e;
> > >> +char *s;
> > >> +
> > >> +s = prb_reserve(, , 32);
> > >> +if (s) {
> > >> +
Hi Aliasgar,
Please state the driver in question in the Subject. So:
[PATCHv2] staging/media/davinci_vpfe: fix style problems
That way it is clear to reviewers which driver is modified.
Also there is no need for '1/1' if there is only one patch.
Regards,
Hans
On 6/21/19 6:34 AM,
On Mon, Jun 24, 2019 at 03:53:04PM -0500, Gustavo A. R. Silva wrote:
> Once the C++17 `__attribute__((fallthrough))` is more widely handled by C
> compilers,
>From what I read that attribute landed in the exact same GCC version as
the warning. And last I checked clang wasn't there yet anyway.
>
On 6/21/19 8:39 AM, Aliasgar Surti wrote:
> From: Aliasgar Surti
>
> checkpatch reported "WARNING: line over 80 characters".
> This patch fixes the warning for file soc_camera/soc_ov5642.c
FYI: we're not accepting patches for staging/media/soc_camera: these
are obsolete and broken drivers.
On Tue, Jun 25, 2019 at 12:28:23AM +0200, Miguel Ojeda wrote:
> On Mon, Jun 24, 2019 at 10:53 PM Gustavo A. R. Silva
> wrote:
> >
> > Once the C++17 `__attribute__((fallthrough))` is more widely handled by C
> > compilers,
> > static analyzers, and IDEs, we can switch to using that instead.
On Mon, Jun 24, 2019 at 10:10:16AM -0600, Logan Gunthorpe wrote:
> Yes, that's correct. The intent was to invert it so the dma_map could
> happen at the start of the process so that P2PDMA code could be called
> with all the information it needs to make it's decision on how to map;
> without
On Mon, Jun 24, 2019 at 01:57:49PM -0700, Joe Perches wrote:
> > Once the C++17 `__attribute__((fallthrough))` is more widely handled by C
> > compilers,
> I doubt waiting is better.
> If the latest compilers catch it, it's
> probably good enough.
Yeah, I don't see the point either; GCC does
On Mon, Jun 24, 2019 at 10:07:56AM -0600, Logan Gunthorpe wrote:
> > For one passing a dma_addr_t through the block layer is a layering
> > violation, and one that I think will also bite us in practice.
> > The host physical to PCIe bus address mapping can have offsets, and
> > those offsets
Hi Jassi,
> -Original Message-
> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
> Sent: 2019年6月21日 0:50
> To: Peng Fan
> Cc: Rob Herring ; Mark Rutland
> ; Sudeep Holla ; Florian
> Fainelli ; , Sascha Hauer ;
> dl-linux-imx ; Shawn Guo ;
> feste...@gmail.com; Devicetree List ; Linux
On Mon, 24 Jun 2019 04:40:10 PDT (-0700), mark.rutl...@arm.com wrote:
I'm very confused by this patch. The title says arm64, yet the code is
under arch/csky/, and the code in question refers to HARTs, which IIUC
is RISC-V terminology.
On Mon, Jun 24, 2019 at 12:04:29AM +0800, guo...@kernel.org
On Mon, 24 Jun 2019 03:40:07 PDT (-0700), w...@kernel.org wrote:
On Thu, Jun 20, 2019 at 05:33:03PM +0800, Guo Ren wrote:
On Wed, Jun 19, 2019 at 8:39 PM Will Deacon wrote:
>
> On Wed, Jun 19, 2019 at 08:18:04PM +0800, Guo Ren wrote:
> > On Wed, Jun 19, 2019 at 5:12 PM Will Deacon wrote:
> >
Hi Sudeep,
> Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
>
> On Thu, Jun 20, 2019 at 10:21:09AM +, Peng Fan wrote:
> > Hi Sudeep,
> >
> > > Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
> > >
> > > On Mon, Jun 03, 2019 at 04:30:05PM +0800,
Without 'set -e', shell scripts continue running even after any
error occurs. The missed 'set -e' is a typical bug in shell scripting.
For example, when a disk space shortage occurs while this script is
running, it actually ends up with generating a truncated capflags.c.
Yet, mkcapflags.sh
Commit-ID: bf10c97adbd0dc8fa65c35d5b0c0dc281a68ac8e
Gitweb: https://git.kernel.org/tip/bf10c97adbd0dc8fa65c35d5b0c0dc281a68ac8e
Author: YueHaibing
AuthorDate: Tue, 25 Jun 2019 11:45:48 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:22:14 +0200
x86/jump_label: Make
[+bpf list]
On Tue, Jun 25, 2019 at 08:20:56AM +0200, Thomas Gleixner wrote:
> On Mon, 24 Jun 2019, syzbot wrote:
>
> > Hello,
>
> CC++ Peterz
>
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:dc636f5d Add linux-next specific files for 20190620
> > git tree:
On Thu, Jun 20, 2019 at 09:26:48PM +0200, Michal Hocko wrote:
> On Thu 13-06-19 11:43:21, Christoph Hellwig wrote:
> > The code hasn't been used since it was added to the tree, and doesn't
> > appear to actually be usable. Mark it as BROKEN until either a user
> > comes along or we finally give
On Tue, Jun 25, 2019 at 09:10:25AM +0200, Bartosz Golaszewski wrote:
> pon., 24 cze 2019 o 20:22 Enrico Weigelt, metux IT consult
> napisał(a):
> >
> > On 24.06.19 12:46, Bartosz Golaszewski wrote:
> >
> > >> The patch seems pretty trivial and doesn't change any actual code, so
> > >> I don't see
Hi Jassi
> Subject: Re: [PATCH V2 2/2] mailbox: introduce ARM SMC based mailbox
>
> On Mon, Jun 3, 2019 at 3:28 AM wrote:
> >
> > From: Peng Fan
> >
> > This mailbox driver implements a mailbox which signals transmitted
> > data via an ARM smc (secure monitor call) instruction. The mailbox
> >
On Tue, Jun 25, 2019 at 04:35:50AM +, Joel Stanley wrote:
> Hi Greg,
>
> On Mon, 17 Jun 2019 at 05:41, Joel Stanley wrote:
> >
> > On Mon, 17 Jun 2019 at 02:09, Alistair Popple wrote:
> > >
> > > On Monday, 21 January 2019 11:15:58 AM AEST Eddie James wrote:
> > > > SBE fifo operations
On Tue, Jun 25, 2019 at 10:30:32AM +0530, sudheer v wrote:
> Hi Greg,
> When i last submitted patches, i have not added change-logs.
> and also used custom debugs instead of kernel dynamic debugs.
> So i have resubmitted the patches , considering you have discarded old set.
> I want to send any
Commit-ID: 2ef085bd110c5723ca08a522608ac3468dc304bd
Gitweb: https://git.kernel.org/tip/2ef085bd110c5723ca08a522608ac3468dc304bd
Author: Reinette Chatre
AuthorDate: Mon, 24 Jun 2019 13:34:27 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:26:11 +0200
x86/resctrl:
On Mon, 24 Jun 2019 06:08:50 PDT (-0700), vladimir.mur...@arm.com wrote:
On 6/24/19 12:54 PM, Christoph Hellwig wrote:
On Mon, Jun 24, 2019 at 12:47:07PM +0100, Vladimir Murzin wrote:
Since you are using binfmt_flat which is kind of 32-bit only I was expecting to
see
CONFIG_COMPAT (or
wt., 25 cze 2019 o 09:30 Greg Kroah-Hartman
napisał(a):
>
> On Tue, Jun 25, 2019 at 09:10:25AM +0200, Bartosz Golaszewski wrote:
> > pon., 24 cze 2019 o 20:22 Enrico Weigelt, metux IT consult
> > napisał(a):
> > >
> > > On 24.06.19 12:46, Bartosz Golaszewski wrote:
> > >
> > > >> The patch seems
On 6/22/19 3:10 PM, Chanwoo Choi wrote:
> Hi,
>
> 2019년 6월 14일 (금) 오후 6:54, Lukasz Luba 님이 작성:
>>
>> Define new performance events supported by Exynos5422 SoC counters.
>> The counters are built-in in Dynamic Memory Controller and provide
>> information regarding memory utilization.
>>
>>
On Mon, Jun 24, 2019 at 01:02:06PM +0530, Vidya Sagar wrote:
> On 6/20/2019 4:25 PM, Thierry Reding wrote:
> > On Wed, Jun 12, 2019 at 03:23:35PM +0530, Vidya Sagar wrote:
> > > Add P2U (PIPE to UPHY) and PCIe controller nodes to device tree.
> > > The Tegra194 SoC contains six PCIe controllers
All the files added to 'targets' are cleaned. Adding the same file
to both 'targets' and 'clean-files' is redundant.
Signed-off-by: Masahiro Yamada
---
arch/x86/kernel/cpu/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/kernel/cpu/Makefile
On Mon, Jun 24, 2019 at 09:10:15PM +0200, Jann Horn wrote:
> That part of the documentation only talks about cases where you have a
> control dependency on the return value of the refcount operation. But
> refcount_inc() does not return a value, so this isn't relevant for
> refcount_inc().
>
>
On 19. 6. 25. 오후 4:31, Lukasz Luba wrote:
>
>
> On 6/22/19 3:10 PM, Chanwoo Choi wrote:
>> Hi,
>>
>> 2019년 6월 14일 (금) 오후 6:54, Lukasz Luba 님이 작성:
>>>
>>> Define new performance events supported by Exynos5422 SoC counters.
>>> The counters are built-in in Dynamic Memory Controller and provide
>>>
From: Jon Hunter
> Any further feedback? I am still seeing this issue on today's -next.
Apologies but I was in FTO.
Is there any possibility you can just disable the ethX configuration in
the rootfs mount and manually configure it after rootfs is done ?
I just want to make sure in which
Hi,
Looks like at least drivers/net/wireless/ti wlcore driver has stopped
working in Linux next with commit 901bb9891855 ("nl80211: require and
validate vendor command policy"). Reverting the commit above makes it
work again.
It fails with the warning below, any ideas what goes wrong?
Regards,
On Mon, Jun 24, 2019 at 05:21:07PM -0500, Josh Poimboeuf wrote:
> On Mon, Jun 24, 2019 at 11:18:44AM +0200, Peter Zijlstra wrote:
> > The current notifiers have the following error handling pattern all
> > over the place:
> >
> > int nr;
> >
> > ret = __foo_notifier_call_chain(, val_up,
On Fri, Jun 21, 2019 at 10:39:11AM -0300, Jason Gunthorpe wrote:
>
> Hmm, this function, and the other, goes on to do:
>
> if (unlikely(!access_ok((void __user *)start, len)))
> return 0;
>
> and I thought that access_ok takes in the tagged pointer?
>
> How about
On 20.06.19 00:32, Alexander Duyck wrote:
> This series provides an asynchronous means of hinting to a hypervisor
> that a guest page is no longer in use and can have the data associated
> with it dropped. To do this I have implemented functionality that allows
> for what I am referring to as
> Why are you all arguing with a all-but-instinguishable-from-a-bot persona
I am curious if another meeting at a Linux conference
can adjust this view.
> about a patch that I will never apply?
I hope that you can get into a more constructive mood a bit later
for the reconsideration of the
On Mon, Jun 24, 2019 at 04:58:10PM -0400, Frank Ch. Eigler wrote:
> Hi -
>
> > > While auditing all module notifiers I noticed a whole bunch of fail
> > > wrt the return value. Notifiers have a 'special' return semantics.
>
> From peterz's comments, the patches, it's not obvious to me how one is
On Fri, Jun 21, 2019 at 10:39:11AM -0300, Jason Gunthorpe wrote:
> Hmm, this function, and the other, goes on to do:
>
> if (unlikely(!access_ok((void __user *)start, len)))
> return 0;
>
> and I thought that access_ok takes in the tagged pointer?
>
> How about re-order
On Mon, Jun 24, 2019 at 01:42:13PM -0700, Joe Perches wrote:
> On Mon, 2019-06-24 at 22:25 +0200, Peter Zijlstra wrote:
> > I hate it when people cross-post to moderated lists, and
> > this thing just made me do it :-(
>
> Maybe:
That seems to work,
Tested-by: Peter Zijlstra (Intel)
Thanks!
From: Katsuhiro Suzuki
> I checked drivers/net/ethernet/stmicro/stmmac/stmmac_main.c and found
> stmmac_init_phy() is going to fail if ethernet device node does not
> have following property:
>- phy-handle
>- phy
>- phy-device
>
> This commit broke the device-trees such as
On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote:
> Hi,
>
> Looks like at least drivers/net/wireless/ti wlcore driver has stopped
> working in Linux next with commit 901bb9891855 ("nl80211: require and
> validate vendor command policy"). Reverting the commit above makes it
> work again.
>
On Fri, Jun 21, 2019 at 11:05:42AM -0300, Jason Gunthorpe wrote:
> Today this check is only being done on the get_user_pages_fast() -
> after this patch it is also done for __get_user_pages_fast().
>
> Which means __get_user_pages_fast is now non-functional on a range of
> MIPS CPUs, but that
Thomas Gleixner writes:
> On Tue, 25 Jun 2019, Stephen Rothwell wrote:
>
>> Hi Kalle,
>>
>> On Tue, 25 Jun 2019 09:23:33 +0300 Kalle Valo wrote:
>> >
>> > Thanks for the report. Any suggestions how to handle this? Or do we let
>> > Linus take care of this?
>>
>> Just let Linus take care of it
Am 24.06.2019 23:58, schrieb Colin King:
> From: Colin Ian King
>
> There is a potential integer overflow when int 2 is left shifted
> as this is evaluated using 32 bit arithmetic but is being used in
> a context that expects an expression of type s64. Fix this by
> shifting 2ULL to avoid a
Commit-ID: 4d33ebb02c45738296ffde4b8f2089edaf75be1c
Gitweb: https://git.kernel.org/tip/4d33ebb02c45738296ffde4b8f2089edaf75be1c
Author: Catalin Marinas
AuthorDate: Mon, 24 Jun 2019 14:56:24 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:43:38 +0200
vdso: Remove
VAG power control is improved to fit the manual. This fixes as
minimum one bug: if customer muxes Headphone to Line-In right after boot
w/o playing any sound, the VAG power remains off that leads to poor
sound quality from line-in.
I.e. after boot:
- Connect sound source to Line-In jack;
-
SGTL5000_SMALL_POP is a bit mask, not a value. Usage of
correct definition makes device probing code more clear.
Signed-off-by: Oleksandr Suvorov
---
sound/soc/codecs/sgtl5000.c | 2 +-
sound/soc/codecs/sgtl5000.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Change VAG power on/off control according to the following algorithm:
- turn VAG power ON on the 1st incoming event.
- keep it ON if there is any active VAG consumer (ADC/DAC/HP/Line-In).
- turn VAG power OFF when there is the latest consumer's pre-down event
come.
- always delay after VAG power
This control mute/unmute the ADC input of SGTL5000
using its CHIP_ANA_CTRL register.
Signed-off-by: Oleksandr Suvorov
---
sound/soc/codecs/sgtl5000.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/codecs/sgtl5000.c b/sound/soc/codecs/sgtl5000.c
index 5e49523ee0b67..bb58c997c6914
To enable "zero cross detect" for ADC/HP, change
HP_ZCD_EN/ADC_ZCD_EN bits only instead of writing the whole
CHIP_ANA_CTRL register.
Signed-off-by: Oleksandr Suvorov
---
sound/soc/codecs/sgtl5000.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
If VDDA != VDDIO and any of them is greater than 3.1V, charge pump
source can be assigned automatically.
Signed-off-by: Oleksandr Suvorov
---
sound/soc/codecs/sgtl5000.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/sound/soc/codecs/sgtl5000.c
Prepare to use SND_SOC_DAPM_PRE_POST_PMU definition to
reduce coming code size and make it more readable.
Signed-off-by: Oleksandr Suvorov
---
include/sound/soc-dapm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/sound/soc-dapm.h b/include/sound/soc-dapm.h
index
Commit-ID: b4b12aca00d509a233abd28990194628adcd71e6
Gitweb: https://git.kernel.org/tip/b4b12aca00d509a233abd28990194628adcd71e6
Author: Catalin Marinas
AuthorDate: Mon, 24 Jun 2019 14:58:12 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:43:38 +0200
arm64: vdso:
On Fri, Jun 21, 2019 at 11:28:24AM -0300, Jason Gunthorpe wrote:
> On Tue, Jun 11, 2019 at 04:40:56PM +0200, Christoph Hellwig wrote:
> > We only support the generic GUP now, so rename the config option to
> > be more clear, and always use the mm/Kconfig definition of the
> > symbol and select it
Hi,
Am Dienstag, 25. Juni 2019, 09:46:12 CEST schrieb Jose Abreu:
> From: Katsuhiro Suzuki
>
> > I checked drivers/net/ethernet/stmicro/stmmac/stmmac_main.c and found
> > stmmac_init_phy() is going to fail if ethernet device node does not
> > have following property:
> >- phy-handle
> >
On Tue, Jun 25, 2019 at 02:43:00AM +0200, Frederic Weisbecker wrote:
> Yeah, unfortunately there is no atomic_add_not_zero_return().
There is atomic_fetch_add_unless().
On Mon, Jun 24, 2019 at 03:56:38PM -0600, Rob Herring wrote:
> Convert the armadeus,st0700-adapt panel binding to DT schema.
>
> Cc: Thierry Reding
> Cc: Sam Ravnborg
> Cc: Maxime Ripard
> Cc: Laurent Pinchart
> Cc: dri-de...@lists.freedesktop.org
> Signed-off-by: Rob Herring
Reviewed-by:
Commit-ID: 53d87b37a2a4a4b6b0c7f8073c4be04022252e26
Gitweb: https://git.kernel.org/tip/53d87b37a2a4a4b6b0c7f8073c4be04022252e26
Author: Catalin Marinas
AuthorDate: Mon, 24 Jun 2019 15:00:19 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:43:38 +0200
arm64: compat: No
> Oh so it's another troll then?
I am just a contributor.
> Good to know, ignoring from now on.
The opinions can vary for my contributions as usual.
I hope that the software development attention can evolve in more
positive ways again.
Regards,
Markus
Commit-ID: c82d735b3d3f0bbfd49a6a4da96bd27c4ba57eb0
Gitweb: https://git.kernel.org/tip/c82d735b3d3f0bbfd49a6a4da96bd27c4ba57eb0
Author: Thomas Gleixner
AuthorDate: Mon, 24 Jun 2019 02:34:24 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 25 Jun 2019 09:44:08 +0200
MAINTAINERS: Add
I'm announcing the release of the 4.19.56 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 5.1.15 kernel.
All users of the 5.1 kernel series must upgrade.
The updated 5.1.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.1.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.14.130 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index 2a55dd5bee0a..9d0715c300b1 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 129
+SUBLEVEL = 130
EXTRAVERSION =
NAME = Petit Gorille
@@ -650,6 +650,7 @@ KBUILD_CFLAGS
On Mon, Jun 24, 2019 at 11:42:34AM +0100, Ignat Korchagin wrote:
> Hi Greg,
>
> > > For us it seems applying the following 4 mainline patches makes 4.19.x
> > > branch perf compile with GCC-9:
> > >
> > > 4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use
> > > strlcpy() as a shorter
diff --git a/Makefile b/Makefile
index 3addd4c286fa..a76c61f77bcd 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 55
+SUBLEVEL = 56
EXTRAVERSION =
NAME = "People's Front"
@@ -652,6 +652,7 @@ KBUILD_CFLAGS
1 - 100 of 1265 matches
Mail list logo
