On Tue, 9 Oct 2018 14:47:32 -0400 Johannes Weiner wrote:
> Make it easier to catch bugs in the shadow node shrinker by adding a
> counter for the shadow nodes in circulation.
>
> Signed-off-by: Johannes Weiner
> ---
> include/linux/mmzone.h | 1 +
> mm/vmstat.c| 1 +
>
On 10/09/2018 03:30 PM, Tony Lindgren wrote:
> * Grygorii Strashko [181009 20:10]:
>>
>>
>> On 10/09/2018 09:40 AM, Tony Lindgren wrote:
>>> * Grygorii Strashko [181008 23:54]:
+Examples:
+ phy_gmii_sel: phy-gmii-sel {
+ compatible = "ti,am3352-phy-gmii-sel";
+
Ok, I tried it with the version compiled from the latest sources and I
don't get the segfault, so it must be an issue with the version
distributed with Fedora 27.
Tony
On Tue, Oct 9, 2018 at 4:47 PM Anthony LaTorre wrote:
>
> I can try building perf from the latest sources. I've attached the
>
On Tue, Oct 09, 2018 at 04:47:31PM -0500, Anthony LaTorre wrote:
> I can try building perf from the latest sources. I've attached the
> perf.data and perf.data.tar.bz2 from the test program I sent earlier.
cool, reproduced.. it seems to get introduced by:
2a9d5050dc84 perf script: Show correct
Commit d5269c4553a6 ("remoteproc: qcom: q6v5: Propagate EPROBE_DEFER")
fixed up our probe code to handle -EPROBE_DEFER, but it ignored one of
our interrupts, and it also didn't really handle all the other error
codes you might get (e.g., with a bad DT definition). Handle those all
explicitly.
On 09/10/2018 22:39, Heiner Kallweit wrote:
> On 09.10.2018 16:40, Chris Clayton wrote:
>> Thanks to Maciej and Heiner for their replies.
>>
>> On 09/10/2018 13:32, Maciej S. Szmigiero wrote:
>>> On 07.10.2018 21:36, Chris Clayton wrote:
Hi again,
I didn't think there was
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
head: b69c2e20f6e4046da84ce5b33ba1ef89cb087b40
commit: b69c2e20f6e4046da84ce5b33ba1ef89cb087b40 [4/4] resource: Clean it up a
bit
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
WARNING: convert(1)
On Fri 27 Jul 06:14 PDT 2018, Loic Pallardy wrote:
> int rproc_fw_sanity_check(struct rproc *rproc, const struct firmware *fw)
> diff --git a/drivers/remoteproc/remoteproc_virtio.c
> b/drivers/remoteproc/remoteproc_virtio.c
[..]
> @@ -114,6 +122,10 @@ static struct virtqueue *rp_find_vq(struct
On Tue, Oct 09, 2018 at 10:56:14PM +, Leonard Crestez wrote:
> On Tue, 2018-10-09 at 08:37 +, Abel Vesa wrote:
> > +struct clk *imx_clk_composite_8m_flags(const char *name,
> > + const char **parent_names,
> > + int
Hi Jiri,
Yes, this happens when entry->map is NULL. While your fix seems correct, the
following commit from Milian Wolff had already addressed this. I think this
was pulled in with one of Arnaldo's recent perf/urgent updates.
ff4ce2885af8 ("perf report: Don't try to map ip to invalid map")
Hi Nathan,
On Mon, Oct 08, 2018 at 03:20:41PM -0700, Nathan Chancellor wrote:
> Clang warns:
>
> drivers/platform/chrome/chromeos_tbmc.c:102:14: warning: duplicate
> 'const' declaration specifier [-Wduplicate-decl-specifier]
> static const SIMPLE_DEV_PM_OPS(chromeos_tbmc_pm_ops, NULL,
>
Hi all,
Changes since 20181009:
The ext4 tree lost its build failure.
The kvm-ppc tree gained a conflict against the kvm-arm tree.
Non-merge commits (relative to Linus' tree): 9423
8942 files changed, 420582 insertions(+), 194157 deletions
On Tue, Oct 09, 2018 at 12:24:55PM -0400, Thara Gopinath wrote:
> Thermal governors can respond to an overheat event for a cpu by
> capping the cpu's maximum possible frequency. This in turn
> means that the maximum available compute capacity of the
> cpu is restricted. But today in linux kernel,
* Yi Sun wrote:
> On 18-10-09 12:54:27, Ingo Molnar wrote:
> >
> > * Yi Sun wrote:
> >
> > > Follow PV spinlock mechanism to implement the callback functions
> > > to allow the CPU idling and kicking operations on Hyper-V.
> >
> > > +#if defined(CONFIG_SMP)
> > > +
On 10/7/18, 2:03 PM, "Linus Walleij" wrote:
>> TIMER_INTR_MASK register (Base Address of Timer + 0x38) is not designed
>> for masking interrupts on ast2500 chips, and it's not even listed in
>> ast2400 datasheet, so it's not safe to access TIMER_INTR_MASK on aspeed
>> chips.
>>
>> Similarly,
Laurent Pinchart schrieb:
> Hi Josh,
>
> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
>> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
>>> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley
On Tue, Oct 09, 2018 at 02:05:01PM -0700, Guenter Roeck wrote:
> On Mon, Oct 08, 2018 at 08:30:01PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.160 release.
> > There are 113 patches in this series, all will be posted as a response
> > to this one.
On Wed, Oct 10, 2018 at 09:42:46AM +0530, Naresh Kamboju wrote:
> On Tue, 9 Oct 2018 at 21:44, Greg Kroah-Hartman
> wrote:
> >
> > On Mon, Oct 08, 2018 at 08:29:40PM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.18.13 release.
> > > There are 168
On Fri 27 Jul 06:14 PDT 2018, Loic Pallardy wrote:
> This patch creates a dedicated vdev subdevice for each vdev declared
> in firmware resource table and associates carveout named "vdev%dbuffer"
> (with %d vdev index in resource table) if any as dma coherent memory pool.
>
> Then vdev subdevice
On Tue, Oct 09, 2018 at 12:25:01PM -0400, Thara Gopinath wrote:
> cpu_capacity relflects the maximum available capacity of a cpu. Thermal
> pressure on a cpu means this maximum available capacity is reduced. This
> patch reduces the average thermal pressure for a cpu from its maximum
> available
From: Kuninori Morimoto
74aup1g157gw needs i0 and i1 pin as input, select and output it by
sel gpio pin. This driver adds new 74aup1g157gw as clock multiplexer.
"nxp,74aup1g157gw-clk" will select most closest input as output,
"nxp,74aup1g157gw-audio-clk" will select 48kHz/44.1kHz categorized
From: Kuninori Morimoto
74aup1g157gw needs i0 and i1 pin as input, select and output it by
sel gpio pin. This patch adds description for 74aup1g157gw as clock
multiplexer.
"nxp,74aup1g157gw-clk" will select most closest input as output,
"nxp,74aup1g157gw-audio-clk" will select 48kHz/44.1kHz
On 18-10-09 12:54:27, Ingo Molnar wrote:
>
> * Yi Sun wrote:
>
> > Follow PV spinlock mechanism to implement the callback functions
> > to allow the CPU idling and kicking operations on Hyper-V.
>
> > +#if defined(CONFIG_SMP)
> > + smp_ops.smp_prepare_boot_cpu = hv_smp_prepare_boot_cpu;
> >
Hi Adam
Yes, MMC_DDR52 can use pins_100mhz. You can do that, thanks!
Best Regards
Bough Chen
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org
> [mailto:linux-mmc-ow...@vger.kernel.org] On Behalf Of Adam Ford
> Sent: 2018年10月9日 21:38
> To: linux-...@vger.kernel.org; Linux
Hi Enric,
On Wed, Oct 3, 2018 at 4:01 AM Enric Balletbo i Serra
wrote:
>
> Hi Emil,
>
> Many thanks to catch this and fix. Some comments below.
>
> You missed to add the v2, please send the next patch with v3 prefix.
>
> On 28/9/18 19:08, Emil Karlson wrote:
> > Commit
Hi Arnaldo,
Did you get a chance to look at this again?
On Thu, Aug 30, 2018, at 14:50, Benjamin Peterson wrote:
> Thanks for the review.
>
> On Thu, Aug 30, 2018, at 11:28, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Aug 27, 2018 at 08:53:44PM -0700, Benjamin Peterson escreveu:
> > > Example
On 10/09/2018 07:28 PM, Zi Yan wrote:
> cc: Naoya Horiguchi (who proposed to use !_PAGE_PRESENT && !_PAGE_PSE for x86
> PMD migration entry check)
>
> On 8 Oct 2018, at 23:58, Anshuman Khandual wrote:
>
>> A normal mapped THP page at PMD level should be correctly differentiated
>> from a PMD
On Tue, 9 Oct 2018 at 21:45, Greg Kroah-Hartman
wrote:
>
> On Mon, Oct 08, 2018 at 08:30:41PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.75 release.
> > There are 94 patches in this series, all will be posted as a response
> > to this one. If
On Tue, 9 Oct 2018 at 00:03, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.160 release.
> There are 113 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 Wed, Oct 10, 2018 at 1:54 AM Luis Henriques wrote:
>
> Current implementation of cephfs fallocate isn't correct as it doesn't
> really reserve the space in the cluster, which means that a subsequent
> call to a write may actually fail due to lack of space. In fact, it is
> currently possible
Hi Greg,
Sorry for the late in the cycle request, but this one is fairly urgent.
Please pull thi fix to chrome platform. A patch that landed
for 4.19 broke cros_ec based chromebooks' keyboards, and this fixes them.
Thanks,
Benson
The following changes since commit
Hi Suzuki
On 2018/10/10 1:22, Suzuki K Poulose wrote:
>
>
> On 08/10/18 13:34, Dongjiu Geng wrote:
>> The commit 539aee0edb9f ("KVM: arm64: Share the parts of
>> get/set events useful to 32bit") shares the get/set events
>> helper for arm64 and arm32, it is better also share the check
>> for
Hi Lee,
Sorry for the super late reply to your email before. I wanted to make sure
this wasn't dropped so we could get this into v4.20.
Thanks,
Benson
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the
Hi Enrico,
On Wed, Oct 03, 2018 at 11:45:06AM -0700, Enrico Granata wrote:
> From: Enrico Granata
>
> This commit allows cros_ec_lpc to register a direct IRQ instead of relying
> on the ACPI notification chain to receive MKBP events.
>
> This change is done in the interest of allowing reduced
Hi,friend,
This is Daniel Murray and i am from Sinara Group Co.Ltd Group Co.,LTD in Russia.
We are glad to know about your company from the web and we are interested in
your products.
Could you kindly send us your Latest catalog and price list for our trial order.
Best Regards,
Daniel Murray
Hi Emil,
On Wed, Oct 3, 2018 at 11:43 AM Emil Karlson wrote:
>
> Commit 57e94c8b974db2d83c60e1139c89a70806abbea0 caused cros-ec keyboard events
> be truncated on many chromebooks so that Left and Right keys on Column 12 were
> always 0. Use ret as memcpy len to fix this.
>
> The old code was
Hi Greg,
please pull s390 fixes for 4.19:
The following changes since commit 4b92e7fd76e94624e3d5ff56b3d6a5788c4a7ac8:
Merge tag 'mtd/fixes-for-4.19-rc5' of git://git.infradead.org/linux-mtd
(2018-09-20 11:25:20 +0200)
are available in the git repository at:
Hi Filippo,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linux-sof-driver/master]
[also build test ERROR on v4.19-rc7 next-20181009]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Installation Notes for Teo En Ming Extremely Simple Linux 1810.08
=
Definitely must watch YouTube video: https://www.youtube.com/watch?v=YrJADssqaQU
Author: Mr. Turritopsis Dohrnii Teo En Ming
Country: Singapore
Start: 8th October
Hi Michael, Stephen, Rob, Mark
These adds 74aup1g157gw 2-input multiplexer as clock driver.
Kuninori Morimoto (2):
dt-bindings: clock: add description of 74aup1g157gw
clk: add 74aup1g157gw 2-input multiplexer as clock driver
The function name in the comment is not correct.
Signed-off-by: Wei Yang
---
include/linux/rbtree_augmented.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/rbtree_augmented.h b/include/linux/rbtree_augmented.h
index af8a61be2d8d..9510c677ac70 100644
---
Hi Jacek,
On 10 October 2018 at 02:37, Jacek Anaszewski
wrote:
> Hi Baolin,
>
> On 10/09/2018 02:01 PM, Baolin Wang wrote:
>> Hi Jacek and Pavel,
>>
>> On 5 October 2018 at 04:00, Jacek Anaszewski
>> wrote:
>>> Hi Baolin,
>>>
>>> On 10/03/2018 03:21 AM, Baolin Wang wrote:
Hi Jacek,
Hi Paul,
Today's linux-next merge of the kvm-ppc tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
233a7cb23531 ("kvm: arm64: Allow tuning the physical address size for VM")
from the kvm-arm tree and commit:
aa069a996951 ("KVM: PPC: Book3S HV: Add a VM capability to
> -Original Message-
> From: Esben Haabendal On Behalf Of Esben
> Haabendal
> Sent: 2018年10月9日 19:21
> To: Chuanhua Han
> Cc: Boris Brezillon ; broo...@kernel.org;
> linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH 1/2] spi: spi-mem: Add the
On 10/09/2018 07:44 PM, Michal Hocko wrote:
> On Fri 05-10-18 13:04:43, Anshuman Khandual wrote:
>> Does the following sound close enough to what you are looking for ?
>
> I do not think so
Okay.
>
>> diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
>> index 9df1d59..070c419
On 09-10-18, 10:40, Pierre Yves MORDRET wrote:
>
>
> On 10/07/2018 06:00 PM, Vinod wrote:
> > On 28-09-18, 15:01, Pierre-Yves MORDRET wrote:
> >> This patch adds support of DMA/MDMA chaining support.
> >> It introduces an intermediate transfer between peripherals and STM32 DMA.
> >> This
From: John Hubbard
For infiniband code that retains pages via get_user_pages*(),
release those pages via the new put_user_page(), or
put_user_pages*(), instead of put_page()
This is a tiny part of the second step of fixing the problem described
in [1]. The steps are:
1) Provide
From: John Hubbard
Introduces put_user_page(), which simply calls put_page().
This provides a way to update all get_user_pages*() callers,
so that they call put_user_page(), instead of put_page().
Also introduces put_user_pages(), and a few dirty/locked variations,
as a replacement for
From: John Hubbard
Changes since v4:
-- Changed the new put_user_page*() functions to operate only on the head
page, because that's how the final version of those functions will work.
(Andrew Morton's feedback prompted this, thanks!)
-- Added proper documentation of the new
From: John Hubbard
An upcoming patch requires a way to operate on each page that
any of the get_user_pages_*() variants returns.
In preparation for that, consolidate the error handling for
__get_user_pages(). This provides a single location (the "out:" label)
for operating on the collected set
On Tue, 9 Oct 2018 at 21:44, Greg Kroah-Hartman
wrote:
>
> On Mon, Oct 08, 2018 at 08:29:40PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.18.13 release.
> > There are 168 patches in this series, all will be posted as a response
> > to this one. If
On Wed, 10 Oct 2018, Tetsuo Handa wrote:
> syzbot is hitting RCU stall due to memcg-OOM event.
> https://syzkaller.appspot.com/bug?id=4ae3fff7fcf4c33a47c1192d2d62d2e03efffa64
>
> What should we do if memcg-OOM found no killable task because the allocating
> task
> was oom_score_adj == -1000 ?
Hi Dmitry,
I agree the bug is neither subtle nor recent, not security relevant and
will affect only a handful of users at best.
If you're worried about weakening the rules around stable releases, by
all means go ahead and veto the inclusion of these patches in the next
stable release.
On Tue, 9 Oct 2018, Mel Gorman wrote:
> > The page allocator is expecting __GFP_NORETRY for thp allocations per its
> > comment:
> >
> > /*
> > * Checks for costly allocations with __GFP_NORETRY, which
> > * includes THP page fault allocations
> >
On Tue, Oct 09, 2018 at 03:20:42PM -0700, Joel Fernandes (Google) wrote:
> Add tests to verify sealing memfds with the F_SEAL_FS_WRITE works as
> expected.
>
> Cc: dan...@google.com
> Cc: minc...@google.com
> Signed-off-by: Joel Fernandes (Google)
> ---
>
Hi Theodore,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
fs/ext4/super.c: In function 'parse_options':
fs/ext4/super.c:1976:26: warning: unused variable 'grp_qf_name'
[-Wunused-variable]
char *p, *usr_qf_name, *grp_qf_name;
On Tue, Oct 09, 2018 at 02:38:59PM -0700, Andrew Morton wrote:
> On Tue, 9 Oct 2018 13:14:00 -0700 "Joel Fernandes (Google)"
> wrote:
>
> > Android needs to mremap large regions of memory during memory management
> > related operations. The mremap system call can be really slow if THP is
> >
Hi,
On Tue, Oct 9, 2018 at 3:33 PM Brian Norris wrote:
> + if (q6v5->wdog_irq < 0) {
> + if (q6v5->wdog_irq != -EPROBE_DEFER)
> + dev_err(>dev,
> + "failed to retrieve wdog IRQ: %d\n",
> +
I have some questions about my assumptions writing this code. I
definitely have something wrong.
(Given my comments in invalidatepage, it should be clear I'm not quite
confident that it's doing the right thing.)
I thought writpeage could not be called while PagePrivate is not set.
It is set
On 09.10.2018 22:36, Heiner Kallweit wrote:
> On 09.10.2018 16:40, Chris Clayton wrote:
>> Thanks to Maciej and Heiner for their replies.
>>
>> On 09/10/2018 13:32, Maciej S. Szmigiero wrote:
>>> On 07.10.2018 21:36, Chris Clayton wrote:
Hi again,
I didn't think there was anything
On 10/8/18 5:14 PM, Andrew Morton wrote:
> On Mon, 8 Oct 2018 14:16:22 -0700 john.hubb...@gmail.com wrote:
>
>> From: John Hubbard
[...]
>> +/*
>> + * Pages that were pinned via get_user_pages*() should be released via
>> + * either put_user_page(), or one of the put_user_pages*() routines
>> +
On Tue, 2018-10-09 at 14:47 -0400, Johannes Weiner wrote:
> No need to use the preemption-safe lruvec state function inside the
> reclaim region that has irqs disabled.
>
> Signed-off-by: Johannes Weiner
Reviewed-by: Rik van Riel
On Tue, 2018-10-09 at 14:47 -0400, Johannes Weiner wrote:
> The shadow shrinker is invoked per NUMA node, but the shadow limit
> enforced for cgroups is based on the page counter, which isn't NUMA
> aware. Instead of shrinking shadow pages to desired_size, we end up
> with desired_size *
Hello Michael,
> That already works, doesn't it? So all that you'd need is an offline
> tool to precompute what drivers to actually build with a given config.
>
> 'make -n' with some suitable output mangling might do the job.
>
> There may well be other ways to achieve your stated goal, without
Thank you!
Please let me know if it needs any rework!
Leonardo Bras
On Sat, Oct 6, 2018 at 4:50 PM Masahiro Yamada
wrote:
>
> Hi Leonardo, David,
>
>
>
> On Fri, Oct 5, 2018 at 11:32 AM Leonardo Bras wrote:
> >
> > Hello David,
> >
> > My name is Leonardo and I am new to kernel development.
On Tue, 9 Oct 2018 at 00:08, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.132 release.
> There are 59 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 Fri, 28 Sep 2018, Mark Brown wrote:
> On Fri, Sep 28, 2018 at 10:14:37AM +0300, Matti Vaittinen wrote:
>
> > I was just wondering if I could do something to help get this patch
> > series applied? Mark, have you had the time to take a look on pickable
> > ranges addition yet? Should I do some
Hi
On 10/8/2018 12:26 PM, Bjorn Andersson wrote:
On Sun 07 Oct 01:07 PDT 2018, Craig wrote:
Any updates on this?
FWIW I used qcom,sdhci-msm-v5 on QCS404 successfully.
Regards,
Bjorn
The base address and interrupt numbers needs to be updated in your dt.
you can refer the below link to
On Mon, Oct 08, 2018 at 08:31:34PM +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Stephen Boyd
>
> [ Upstream commit b55326dc969ea2d704a008d9a97583b128f54f4f ]
>
> The interrupt controller
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/s390/kernel/setup.c
between commit:
b45248da1a33 ("s390: unify stack size definitions")
ee46f78659ac ("s390: add support for virtually mapped kernel stacks")
from the s390 tree and commit:
This patch allows for AT_BENEATH and AT_THIS_ROOT to safely permit ".."
resolution (in the case of AT_BENEATH the resolution will still fail if
".." resolution would resolve a path outside of the root -- while
AT_THIS_ROOT will chroot(2)-style scope it). "proclink" jumps are still
disallowed
Commit-ID: 2a7adf6ce643fdeec051dc88e5250b08c83bbb67
Gitweb: https://git.kernel.org/tip/2a7adf6ce643fdeec051dc88e5250b08c83bbb67
Author: Reinette Chatre
AuthorDate: Wed, 3 Oct 2018 15:17:03 -0700
Committer: Ingo Molnar
CommitDate: Tue, 9 Oct 2018 08:50:47 +0200
x86/intel_rdt: Fix
On Mon, Oct 08, 2018 at 05:13:51PM -0600, Shuah Khan wrote:
> On 10/08/2018 12:29 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.18.13 release.
> > There are 168 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Mon, Oct 08, 2018 at 12:43:05PM -0600, Shuah Khan wrote:
> On Sun, Oct 7, 2018 at 9:48 AM Greg KH wrote:
> >
> > Hi all,
> >
> > Yet again, it's time for a kernel -rc release. This one is bigger than
> > -rc6 was, for a variety of unrelated reasons it seems. Lots of
> > different trees being
On Tue, Oct 9, 2018 at 9:03 AM tip-bot for Kees Cook wrote:
>
> Commit-ID: 184d47f0fd365108bd06ab26cdb3450b716269fd
> Gitweb:
> https://git.kernel.org/tip/184d47f0fd365108bd06ab26cdb3450b716269fd
> Author: Kees Cook
> AuthorDate: Mon, 8 Oct 2018 16:54:34 -0700
> Committer: Ingo Molnar
For lower resolutions, incase of encoder, the compressed
frame size is more than half of the corresponding input
YUV. Keep the size as same as YUV considering worst case.
Signed-off-by: Malathi Gottam
---
drivers/media/platform/qcom/venus/helpers.c | 2 +-
1 file changed, 1 insertion(+), 1
Add USERPTR to queue access methods by adding this
support to io_modes on both the planes.
Signed-off-by: Malathi Gottam
---
drivers/media/platform/qcom/venus/venc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/qcom/venus/venc.c
On Fri, Oct 5, 2018 at 8:41 PM Dmitry Torokhov wrote:
>
> Whiskers is a foldable base, and thus requires combining "base presence"
> signal coming from EC with base state signal (folded/unfolded) coming
> from USB/HID interface to produce proper SW_TABLET_MODE event.
>
> Signed-off-by: Nicolas
I've Cc:-ed a handful of gents who worked on CFS bandwidth details to widen the
discussion.
Patch quoted below.
Looks like a real bug that needs to be fixed - and at first sight the quota of
1000 looks very
low - could we improve the arithmetics perhaps?
A low quota of 1000 is used because
On Thu 04-10-18 11:34:11, David Rientjes wrote:
> On Thu, 4 Oct 2018, Michal Hocko wrote:
>
> > > And prior to the offending commit, there were three ways to control thp
> > > but two ways to determine if a mapping was eligible for thp based on the
> > > implementation detail of one of those
On 9 October 2018 07:01:57 BST, Veerabhadrarao Badiganti
wrote:
>Hi
>
>
>On 10/8/2018 12:26 PM, Bjorn Andersson wrote:
>> On Sun 07 Oct 01:07 PDT 2018, Craig wrote:
>>
>>> Any updates on this?
>>>
>> FWIW I used qcom,sdhci-msm-v5 on QCS404 successfully.
>>
>> Regards,
>> Bjorn
>
>The base
[Cc Oleg]
On Fri 05-10-18 15:32:08, Yong-Taek Lee wrote:
> It is introduced by commit 44a70adec910 ("mm, oom_adj: make sure
> processes sharing mm have same view of oom_score_adj"). Most of
> user process's mm_users is bigger than 1 but only one thread group.
> In this case, for_each_process loop
The need for some sort of control over VFS's path resolution (to avoid
malicious paths resulting in inadvertent breakouts) has been a very
long-standing desire of many userspace applications. This patchset is a
revival of Al Viro's old AT_NO_JUMPS[1,2] patchset (which was a variant
of David
Add the following flags to allow various restrictions on path
resolution (these affect the *entire* resolution, rather than just the
final path component -- as is the case with most other AT_* flags).
The primary justification for these flags is to allow for programs to be
far more strict about
The need for some sort of control over VFS's path resolution (to avoid
malicious paths resulting in inadvertent breakouts) has been a very
long-standing desire of many userspace applications. This patchset is a
revival of Al Viro's old AT_NO_JUMPS[1,2] patchset (which was a variant
of David
On Fri, 28 Sep 2018, Rob Herring wrote:
> On Fri, Sep 28, 2018 at 12:46 AM Lee Jones wrote:
> >
> > On Wed, 26 Sep 2018, Rob Herring wrote:
> >
> > > On Mon, Sep 17, 2018 at 04:33:22PM +0100, Charles Keepax wrote:
> > > > Signed-off-by: Charles Keepax
> > > > ---
> > > >
Hi Morimoto-san
Thanks for your comment
On 2018/10/09 9:44, Kuninori Morimoto wrote:
Hi Jiada
SSI can work in following modes
1. Basic Mode: (channel 1, 2, 4, 6, 8, 16)
2. TDM Extended Mode: (channel 6, 8)
3. TDM Split Mode: (channel 1, 2)
4. TDM Ex-Split mode: (Channel 2, 4, 6, 8, 10)
On Mon, Oct 8, 2018 at 5:11 PM Waldemar Rymarkiewicz
wrote:
>
> From: Waldemar Rymarkiewicz
>
> The governor updates dbs_info->requested_freq only after increasing or
> decreasing frequency. There is, however, an use case when this is not
> sufficient.
>
> Imagine, external module constraining
Hi Anurag,
On Wednesday 12 September 2018 09:52 PM, Anurag Kumar Vulisha wrote:
> ZynqMP SoC has a Gigabit Transceiver with four lanes. All the high speed
> peripherals such as USB, SATA, PCIE, Display Port and Ethernet SGMII can
> rely on any of the four GT lanes for PHY layer. This patch adds
On Tue 09-10-18 08:23:30, Michal Hocko wrote:
> [Cc Oleg]
JFYI there was new submission
http://lkml.kernel.org/r/20181008011931epcms1p82dd01b7e5c067ea99946418bc97de46a@epcms1p8
>
> On Fri 05-10-18 15:32:08, Yong-Taek Lee wrote:
> > It is introduced by commit 44a70adec910 ("mm, oom_adj: make
On Mon, 8 Oct 2018 at 14:50, Marek Szyprowski wrote:
>
> To get ARM Architected Timers working on Samsung Exynos SoCs, one has to
> first configure and enable Exynos Multi-Core Timer, because they both
> share some common hardware blocks. This patch adds a mode of cooperation
> with arch_timer
From: Lucas Stach
This is a new clock type introduced on i.MX8.
Signed-off-by: Lucas Stach
Signed-off-by: Abel Vesa
Reviewed-by: Sascha Hauer
---
drivers/clk/imx/Makefile | 1 +
drivers/clk/imx/clk-frac-pll.c | 215 +
drivers/clk/imx/clk.h
From: Lucas Stach
The SCCG is a new PLL type introduced on i.MX8. Add support for this.
The driver currently misses the PLL lock check, as the preliminary
documentation mentions lock configurations, but is quiet about where
to find the actual lock status signal.
Signed-off-by: Lucas Stach
From: Lucas Stach
This adds the binding for the i.MX8MQ Clock Controller Module.
Signed-off-by: Lucas Stach
Signed-off-by: Abel Vesa
Reviewed-by: Rob Herring
---
.../devicetree/bindings/clock/imx8mq-clock.txt | 20 ++
include/dt-bindings/clock/imx8mq-clock.h | 395
From: Lucas Stach
Add driver for the Clock Control Module found on i.MX8MQ.
This is largely based on the downstream driver from Anson Huang and
Bai Ping at NXP, plus the imx composite clock from Abel Vesa at NXP,
with only some small adaptions to mainline from me.
Signed-off-by: Lucas Stach
Since a lot of clocks on imx8m are formed by a mux, gate, predivider and
divider, the idea here is to combine all of those into one composite clock,
but we need to deal with both predivider and divider at the same time and
therefore we add the imx_clk_composite_8m_divider_ops and register
the
Changes since v9:
* Replaced DIV_ROUND_UP_ULL with DIV_ROUND_UP
* Renamed the entire composite to composite-8m
Abel Vesa (1):
clk: imx: add imx composite clock
Lucas Stach (4):
dt-bindings: add binding for i.MX8MQ CCM
clk: imx: add fractional PLL output clock
clk: imx: add SCCG PLL
Quoting kbuild test robot (2018-10-08 21:56:25)
> Hi Stephen,
>
> I love your patch! Perhaps something to improve:
[...]
>net/mac80211/sta_info.h:588: warning: Function parameter or member
> 'tx_stats.packets' not described in 'sta_info'
>net/mac80211/sta_info.h:588: warning: Function
Thank you Alex for the prompt response and fix!
it works perfectly now..
Mansour..
On 10/08/2018 10:25 AM, Alexander Shishkin wrote:
> Alexander Shishkin writes:
>
>> "Alharthi, Mansour A" writes:
>>
>>> Hello all,
>> Hi,
>>
>>> Assume this test code:
>>>
>>> thread_start(){
>>> ...
>>>
Store -k clockid frequency into Perf trace to enable timestamps
derived metrics conversion into wall clock time on reporting stage.
Below is the example of perf report output:
tools/perf/perf record -k raw -- ../../matrix/linux/matrix.gcc
...
[ perf record: Captured and wrote 31.222 MB
1 - 100 of 1434 matches
Mail list logo
