Following commit d8f090dbeafd ("rtc: max77686: Do not allow interrupt to
fire before system resume"), RTC wake-ups stopped working on Jetson TX2
and Jetson Xavier platforms. The Jetson TX2 uses the max77620 PMIC and
the Jetson Xavier uses max20024 PMIC. Both of these PMICs have the same
max77620
On 8/5/20 6:17 AM, Grygorii Strashko wrote:
On 05/08/2020 14:32, Vinod Koul wrote:
On 05-08-20, 14:27, Peter Ujfalusi wrote:
The original commit mixed up the forward and completion ring IDs for the
rx flow configuration.
Acked-By: Vinod Koul
Fixes: 4927b1ab2047 ("dmaengine: ti:
On Fri, Jul 31, 2020 at 8:47 PM Andrii Nakryiko
wrote:
>
> On Fri, Jul 31, 2020 at 6:47 PM Ian Rogers wrote:
> >
> > On Tue, Jul 21, 2020 at 11:58 PM Andrii Nakryiko
> > wrote:
> > >
> > > On Tue, Jul 21, 2020 at 10:44 PM Ian Rogers wrote:
> > > >
> > > > When bpftool dumps types and enum
Hi Thomas,
On 8/6/2020 10:10 AM, Thomas Gleixner wrote:
Megha,
"Dey, Megha" writes:
-Original Message-
From: Jason Gunthorpe
Subject: Re: [PATCH RFC v2 02/18] irq/dev-msi: Add support for a new DEV_MSI
irq domain
can you please fix your mail client not to copy the whole header
On Thursday, 2020-07-16 at 16:52:45 +03, Jarkko Sakkinen wrote:
> From: Sean Christopherson
>
> Configure SGX as part of feature control MSR initialization and update
> the associated X86_FEATURE flags accordingly. Because the kernel will
> require the LE hash MSRs to be writable when running
Em Wed, Aug 05, 2020 at 11:34:41AM +0200, Jiri Olsa escreveu:
> Moving clockid_res_ns under clock struct, so we have
> clock related stuff in one place.
Thanks, applied.
- Arnaldo
> Signed-off-by: Jiri Olsa
> ---
> tools/perf/builtin-record.c | 6 +++---
> tools/perf/util/env.h | 2 +-
On Thu, Aug 06, 2020 at 02:16:26PM +0530, Naresh Kamboju wrote:
> On Thu, 6 Aug 2020 at 01:29, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.7.14 release.
> > There are 7 patches in this series, all will be posted as a response
> > to this one. If
The following changes since commit 92ed301919932f13b9172e525674157e983d:
Linux 5.8-rc7 (2020-07-26 14:14:06 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.9-rc1
for you to fetch changes up to
On Thu, Aug 06, 2020 at 05:55:15PM +0200, Thierry Reding wrote:
> if (IS_ERR(drvdata->enb_gpio)) {
> ret = PTR_ERR(drvdata->enb_gpio);
> - dev_err(>dev, "Failed to get enable GPIO: %d\n", ret);
> + if (ret != -EPROBE_DEFER)
> +
On Wed, Aug 5, 2020 at 6:39 PM Alex Shi wrote:
>
>
>
> 在 2020/8/4 下午10:29, Alexander Duyck 写道:
> > On Tue, Aug 4, 2020 at 3:04 AM Alex Shi wrote:
> >>
> >>
> >>
> >> 在 2020/8/4 上午6:37, Alexander Duyck 写道:
>
> shrink_inactive_list() also diverts any unevictable pages that it finds
>
Looks good.
On 2020-08-05 9:14 p.m., Mark Tomlinson wrote:
> For hardware that only supports 32-bit writes to PCI there is the
> possibility of clearing RW1C (write-one-to-clear) bits. A rate-limited
> messages was introduced by fb2659230120, but rate-limiting is not the
> best choice here. Some
Hello Pavel and Rob,
thanks much for review.
On Thursday 06 of August 2020 16:47:13 Rob Herring wrote:
> On Tue, Aug 04, 2020 at 11:20:21AM +0200, Pavel Machek wrote:
> > On Tue 2020-08-04 11:18:17, Pavel Machek wrote:
> > > Hi!
> > >
> > > > The commit text again to make checkpatch happy.
> > >
On Thu, 06 Aug 2020 13:08:13 +0200,
Vinod Koul wrote:
>
> On 23-07-20, 22:33, Takashi Iwai wrote:
> > On Thu, 23 Jul 2020 17:56:12 +0200,
> > Vinod Koul wrote:
> > >
> > > On 23-07-20, 15:17, Takashi Iwai wrote:
> > > > On Thu, 23 Jul 2020 15:05:22 +0200,
> > > > Vinod Koul wrote:
> > > > >
> >
Hi,
Static analysis with Coverity has detected a potential issue with the
following commit:
commit 0b0e299720bb99428892a23ecbd2b4b7f61ccf6d
Author: Vladimir Oltean
Date: Mon Aug 3 19:48:23 2020 +0300
net: dsa: sja1105: use detected device id instead of DT one on mismatch
The analysis is
Hi Prabhakar,
On Mon, Aug 03, 2020 at 03:31:45PM +0100, Lad Prabhakar wrote:
> During testing this sensor on iW-RainboW-G21D-Qseven platform in 8-bit DVP
> mode with rcar-vin bridge noticed the capture worked fine for the first run
> (with yavta), but for subsequent runs the bridge driver waited
From: Colin Ian King
There are spelling mistakes in warning messages. Fix these.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ti/wl1251/main.c | 2 +-
drivers/net/wireless/ti/wlcore/cmd.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
As discussed recently, the current interface for the
Decoded Picture Buffer is not enough to properly
support field coding.
This commit introduces enough semantics to support
frame and field coding, and to signal how DPB entries
are "used for reference".
Signed-off-by: Ezequiel Garcia
---
v2:
*
DPB entry PicNum maximum value is 2*MaxFrameNum for interlaced
content (field_pic_flag=1).
As specified, MaxFrameNum is 2^(log2_max_frame_num_minus4 + 4)
and log2_max_frame_num_minus4 is in the range of 0 to 12,
which means pic_num should be a 32-bit field.
The v4l2_h264_dpb_entry struct needs
Commit 0b0393d59eb4a ("media: uapi: h264: clarify
expected scaling_list_4x4/8x8 order") improved the
documentation on H264 scaling lists order.
This commit improves the documentation by clarifying
that the lists themselves are expected in raster scan order.
Signed-off-by: Ezequiel Garcia
---
On Thu, Aug 06, 2020 at 04:41:44PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Aug 06, 2020 at 08:05:10AM -0700, Doug Anderson wrote:
> > Yet if I go check mainline the patch is not there. This came to my
> > attention since we had my patch picked to the Chrome OS 4.19 tree and
> >
Here's a new round for the H.264 uAPI cleanup, which as discussed
aims at being stabilized and promoted as a first-class public uAPI soon.
It should be noted that there is already GStreamer native
support for this interface, which will be part of 1.18,
once it's released.
I have pushed a branch
On 8/6/20 2:11 PM, Stephen Smalley wrote:
> On 8/6/20 4:03 AM, Thiébaud Weksteen wrote:
>
>> From: Peter Enderborg
>>
>> Add further attributes to filter the trace events from AVC.
>
> Please include sample usage and output in the description.
>
>
Im not sure where you want it to be.
In the
From: Colin Ian King
There is a spelling mistake in a pr_info message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/mmc/host/sdhci-pci-o2micro.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-pci-o2micro.c
The current implementation for gbcodec_mixer_dapm_ctl_put() uses
uninitialized gbvalue for comparison with updated value. This was found
using static analysis with coverity.
Uninitialized scalar variable (UNINIT)
11. uninit_use: Using uninitialized value
gbvalue.value.integer_value[0].
460
The H.264 specification requires in section 7.4.3 "Slice header semantics",
that the following values shall be the same in all slice headers:
pic_parameter_set_id
frame_num
field_pic_flag
bottom_field_flag
idr_pic_id
pic_order_cnt_lsb
delta_pic_order_cnt_bottom
From: Colin Ian King
The memory allocation failure checking for in and out is currently
checking if the pointers are valid rather than the contents of what
they point to. Hence the null check on failed memory allocations is
incorrect. Fix this by adding the missing indirection in the check.
On Wed, Aug 05, 2020 at 08:35:15AM -0500, Alex Elder wrote:
>
> I think the fix is to add a call to this:
>
> ret = gb_audio_gb_get_control(module->mgmt_connection, data->ctl_id,
> GB_AUDIO_INVALID_INDEX, );
>
> before the field within gbvalue is
On Thu, Aug 6, 2020 at 1:04 PM Doug Smythies wrote:
>
> On 2020.08.05 09:56 Rafael J. Wysocki wrote:
>
> > v6 -> v7:
> >* Cosmetic changes in store_energy_performance_prefernce() to reduce the
> > LoC number and make it a bit easier to read. No intentional functional
> > impact.
>
From: Colin Ian King
There are spelling mistakes in two debug messages. As recommended
by Wolfram Sang, these can be removed as there is plenty of debug
in the driver core.
Signed-off-by: Colin Ian King
---
V2: remove the debug rather than fixing the spelling
---
From: Colin Ian King
There are some spelling mistakes in rtw_info messages. Fix these.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/realtek/rtw88/rtw8822b.c | 4 ++--
drivers/net/wireless/realtek/rtw88/rtw8822c.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On 8/6/20 10:44 AM, Sowjanya Komatineni wrote:
On 8/6/20 10:27 AM, Dmitry Osipenko wrote:
06.08.2020 20:12, Sowjanya Komatineni пишет:
On 8/6/20 9:41 AM, Sowjanya Komatineni wrote:
On 8/6/20 9:10 AM, Dmitry Osipenko wrote:
06.08.2020 18:59, Sowjanya Komatineni пишет:
...
Confirmed from
On 8/6/20 3:49 PM, Stephen Smalley wrote:
> On Thu, Aug 6, 2020 at 9:45 AM Stephen Smalley
> wrote:
>> On 8/6/20 8:32 AM, Stephen Smalley wrote:
>>
>>> On 8/6/20 8:24 AM, peter enderborg wrote:
>>>
On 8/6/20 2:11 PM, Stephen Smalley wrote:
> On 8/6/20 4:03 AM, Thiébaud Weksteen wrote:
On 8/6/20 5:03 PM, Stephen Smalley wrote:
> On Thu, Aug 6, 2020 at 10:51 AM peter enderborg
> wrote:
>> On 8/6/20 3:49 PM, Stephen Smalley wrote:
>>> On Thu, Aug 6, 2020 at 9:45 AM Stephen Smalley
>>> wrote:
On 8/6/20 8:32 AM, Stephen Smalley wrote:
> On 8/6/20 8:24 AM, peter
Currently there is the xlate() callback, which is used by providers for
mapping the nodes from phandle arguments. That's fine for simple mappings,
but the phandle arguments could contain an additional data, such as tag
information. Let's create another callback xlate_extended() for the cases
where
On Thursday, 2020-07-16 at 16:52:52 +03, Jarkko Sakkinen wrote:
> Add an ioctl, which performs ENCLS[EADD] that adds new visible page to an
> enclave, and optionally ENCLS[EEXTEND] operations that hash the page to the
> enclave measurement. By visible we mean a page that can be mapped to the
>
Increase the number of interconnect-cells, as now we can include
the tag information. The consumers can specify the path tag as an
additional argument to the endpoints.
Tested-by: Sibi Sankar
Reviewed-by: Sibi Sankar
Reviewed-by: Matthias Kaehlcke
Signed-off-by: Georgi Djakov
---
Implement a function to parse the arguments of the "interconnects" DT
property and populate the interconnect path tags if this information
is available.
Tested-by: Sibi Sankar
Reviewed-by: Sibi Sankar
Signed-off-by: Georgi Djakov
---
drivers/interconnect/qcom/icc-rpmh.c | 27
Let's document that we now support specifying path tag information in the
arg cells of the 'interconnects' DT property. This information would be
populated when the xlate_extended() callback is used.
Specifying the tag in DT will allow the interconnect framework to do the
aggregation based on the
Use the qcom_icc_xlate_extended() in order to parse tags, that are
specified as an additional arguments to the path endpoints in DT.
Tested-by: Sibi Sankar
Reviewed-by: Sibi Sankar
Reviewed-by: Matthias Kaehlcke
Signed-off-by: Georgi Djakov
---
drivers/interconnect/qcom/sdm845.c | 2 +-
1
From: Colin Ian King
There is a spelling mistake in a netdev_err error message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/net/can/grcan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/can/grcan.c b/drivers/net/can/grcan.c
index
On Wed, 5 Aug 2020 20:14:28 +0200, Bartosz Golaszewski wrote:
> On Wed, Aug 5, 2020 at 4:36 PM Jean Delvare wrote:
> > I finally found the time to give it a try. Here's what my (tested)
> > prototype looks like:
>
> Hi Jean,
>
> this looks good at first glance.
>
> > ---
From: Colin Ian King
There is a spelling mistake in an ath6kl_err error message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ath/ath6kl/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath6kl/init.c
On 7/30/20 11:34 AM, David Hildenbrand wrote:
> Let's clean it up a bit, simplifying error handling and getting rid of
> the label.
Nit: the label was already removed by patch 1/6?
> Reviewed-by: Baoquan He
> Reviewed-by: Pankaj Gupta
> Cc: Andrew Morton
> Cc: Michal Hocko
> Cc: Michael S.
Hi!
Dne četrtek, 06. avgust 2020 ob 17:47:07 CEST je Paul Kocialkowski napisal(a):
> Hi,
>
> On Thu 06 Aug 20, 12:12, Ezequiel Garcia wrote:
> > From: Jernej Skrabec
> >
> > When dealing with with interlaced frames, reference lists must tell if
> > each particular reference is meant for top or
This patch series adds new DRM bridge driver for Cadence MHDP DPI/DP
bridge. The Cadence Display Port IP is also referred as MHDP (Mobile High
Definition Link, High-Definition Multimedia Interface, Display Port).
Cadence Display Port complies with VESA DisplayPort (DP) and embedded
Display Port
> -Original Message-
> From: Dmitry Osipenko
> Sent: Thursday, August 6, 2020 7:16 PM
> To: Rajesh Gumasta ; Laxman Dewangan
> ; Jonathan Hunter ;
> vk...@kernel.org; dan.j.willi...@intel.com; thierry.red...@gmail.com;
> p.za...@pengutronix.de; dmaeng...@vger.kernel.org; linux-
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 47ec5303d73ea344e84f46660fff693c57641386
commit: 428d5df1fa4f28daf622c48dd19da35585c9053c bpf, x86: Emit patchable
direct jump as tail call
date: 9 months ago
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
If
If xfs_sysfs_init is called with parent_kobj == NULL, UBSAN
shows the following warning:
UBSAN: null-ptr-deref in ./fs/xfs/xfs_sysfs.h:37:23
member access within null pointer of type 'struct xfs_kobj'
Call Trace:
dump_stack+0x10e/0x195
ubsan_type_mismatch_common+0x241/0x280
On Thu, Aug 06, 2020 at 02:19:53PM +0300, Andy Shevchenko wrote:
> On Tue, May 26, 2020 at 03:14:11PM -0400, Arvind Sankar wrote:
>
> Side question: are you going to submit a v3 of this?
> Or i.o.w. what is the status of this series?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
The
Hello,
Thank you for your patches! Currently I'm busy, but I'll take a look at it as
soon possible.
btw. can you tell me about more of your use case/work. I would like to
have some feedback about this stack. You can write a personal message,
if it is not for public.
On Wed, Aug 05, 2020 at
If protected virtualization is active on s390, the virtio queues are
not accessible to the host, unless VIRTIO_F_IOMMU_PLATFORM has been
negotiated. Use ccw_transport_features() to fail feature negociation
and consequently probe if that's not the case, preventing a host
error on access attempt.
Hi,
On Mon, Dec 2, 2019 at 8:36 AM Doug Anderson wrote:
>
> Hi,
>
> On Wed, Nov 20, 2019 at 11:18 AM Will Deacon wrote:
> >
> > On Sat, Oct 19, 2019 at 11:12:26AM -0700, Douglas Anderson wrote:
> > > This is commit fdfeff0f9e3d ("arm64: hw_breakpoint: Handle inexact
> > > watchpoint addresses")
From: Colin Ian King
There is a spelling mistake in a dev_err message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Thu, Aug 06, 2020 at 12:20:52PM +0200, Thomas Gleixner wrote:
> Uwe Kleine-König writes:
> > On Tue, Aug 04, 2020 at 11:16:03AM +0200, Ahmad Fatoum wrote:
> >> Generic GPIO consumers like gpio-keys use request_any_context_irq()
> >> to request a threaded handler if
From: Andrei Botila
CAAM accelerator only supports XTS-AES-128 and XTS-AES-256 since
it adheres strictly to the standard. All the other key lengths
are accepted and processed through a fallback as long as they pass
the xts_verify_key() checks.
Fixes: 226853ac3ebe ("crypto: caam/qi2 - add
> -Original Message-
> From: Avri Altman
> Sent: 06 August 2020 19:27
> To: Bean Huo ; daejun7.p...@samsung.com;
> j...@linux.ibm.com; martin.peter...@oracle.com; asuto...@codeaurora.org;
> bean...@micron.com; stanley@mediatek.com; c...@codeaurora.org;
> bvanass...@acm.org;
From: Andrei Botila
This patch series fixes some problems in CAAM's implementation of xts(aes):
- CAAM until Era 9 can't process XTS with 16B IV
- CAAM can only process in hardware XTS key lengths of 16B and 32B
- These hardware limitations are resolved through a fallback
This patch series
Hello
My name is George MikeI am a lawyer by profession. I wish to offer you
the next of kin to my client. You will inherit the sum of ($8.5 Million)
dollars my client left in the bank before his death.
My client is a citizen of your country who died in auto crash with his wife
and only son. I
From: Andrei Botila
A hardware limitation exists for CAAM until Era 9 which restricts
the accelerator to IVs with only 8 bytes. When CAAM has a lower era
a fallback is necessary to process 16 bytes IV.
Fixes: 226853ac3ebe ("crypto: caam/qi2 - add skcipher algorithms")
Cc: # v4.20+
From: Andrei Botila
Newer CAAM versions (Era 9+) support 16B IVs. Since for these devices
the HW limitation is no longer present newer version should process the
requests containing 16B IVs directly in hardware without using a fallback.
Signed-off-by: Andrei Botila
---
> > This adds an opt-in flag to the perf_event_open() syscall to retain
> > sibling events after their file descriptors are closed. In this case, the
> > actual events will be closed with the group leader.
>
> So having the 1:1 relation with filedesc imposes a resource limit on
> userspace.
>
>
Add a new DRM bridge driver for Cadence MHDP DPTX IP used in TI J721e SoC.
MHDP DPTX IP is the component that complies with VESA DisplayPort (DP) and
embedded Display Port (eDP) standards. It integrates uCPU running the
embedded Firmware (FW) interfaced over APB interface.
Basically, it takes a
On Thu, 6 Aug 2020 08:32:38 -0400
Stephen Smalley wrote:
> >
> > In the commit message or in a Documentation/trace/events-avc.rst ?
>
> I was just asking for it in the commit message / patch description. I
> don't know what is typical for Documentation/trace.
No, the Documentation/trace is
On Wed, 5 Aug 2020 07:57:44 +0200
Christian Eggers wrote:
> Support for AMS AS73211 JENCOLOR(R) Digital XYZ Sensor.
>
> This driver has no built-in trigger. In order for making triggered
> measurements, an external (software) trigger driver like
> iio-trig-hrtimer or iio-trig-sysfs is required.
06.08.2020 19:13, Dmitry Osipenko пишет:
> 06.08.2020 18:59, Sowjanya Komatineni пишет:
> ..
>> We cant use active status check for specific pads under calibration.
>> This is common bit for all pads.
>
> I'm not sure why this is a problem.
>
IIUC, the start_calibration() should wait for the
On Wed, Aug 5, 2020 at 5:01 AM Daniel Palmer wrote:
>
> Adds a YAML description of the binding for the msc313-intc.
>
> Signed-off-by: Daniel Palmer
> ---
> .../mstar,msc313-intc.yaml| 79 +++
> MAINTAINERS | 1 +
> 2 files
On Thu, Aug 06, 2020 at 01:50:29PM +0200, Nicolas Saenz Julienne wrote:
> > The latter is pretty much what I expect, as we only support the default and
> > per-device DMA CMAs.
>
> Fair enough, should I send a v3 with everything cleaned-up/rebased, or you'd
> rather pick it up from your version?
From: Andrei Botila
CAAM accelerator only supports XTS-AES-128 and XTS-AES-256 since
it adheres strictly to the standard. All the other key lengths
are accepted and processed through a fallback as long as they pass
the xts_verify_key() checks.
Fixes: c6415a6016bf ("crypto: caam - add support
This patch is used to fix ext4 direct I/O read error when
the read size is not aligned with block size.
Then, I will use a test to explain the error.
(1) Make a file that is not aligned with block size:
$dd if=/dev/zero of=./test.jar bs=1000 count=3
(2) I wrote a source file named
On 8/6/20 10:27 AM, Dmitry Osipenko wrote:
06.08.2020 20:12, Sowjanya Komatineni пишет:
On 8/6/20 9:41 AM, Sowjanya Komatineni wrote:
On 8/6/20 9:10 AM, Dmitry Osipenko wrote:
06.08.2020 18:59, Sowjanya Komatineni пишет:
...
Confirmed from HW designer, calibration FSM to finish takes worst
On Wed, 5 Aug 2020 07:57:43 +0200
Christian Eggers wrote:
> Add DT bindings for AMS AS73211 XYZ True Color Sensor.
>
> Signed-off-by: Christian Eggers
> Reviewed-by: Rob Herring
Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to poke at it.
Thanks,
Integrates UBSAN into the KUnit testing framework. It fails KUnit tests
whenever it reports undefined behavior.
Signed-off-by: Uriel Guajardo
---
lib/ubsan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/ubsan.c b/lib/ubsan.c
index cb9af3f6b77e..1460e2c828c8 100644
--- a/lib/ubsan.c
Hello Mark,
Other than patch 12, there is no comment on other patches from anyone as
of now.
[PATCH v5 12/12] dt-bindings: sound: lpass-cpu: Move to yaml format
I will plan to post patch12 only with comments addressed if other
changes does not have any comment. Please let me know your
On Thursday, 2020-07-16 at 16:52:42 +03, Jarkko Sakkinen wrote:
> From: Sean Christopherson
>
> Include SGX bit to the PF error codes and throw SIGSEGV with PF_SGX when
> a #PF with SGX set happens.
>
> CPU throws a #PF with the SGX set in the event of Enclave Page Cache Map
> (EPCM) conflict.
On Thu, Aug 06, 2020 at 02:04:18PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: fffe3ae0ee84e25d2befe2ae59bc32aa2b6bc77b
> commit: a62a8ef9d97da23762a588592c8b8eb50a8deb6a virtio-fs: add virtiofs
> filesystem
>
Adds an API to allow dynamic analysis tools to fail the currently
running KUnit test case.
- Always places the kunit test in the task_struct to allow other tools
to access the currently running KUnit test.
- Creates a new header file to avoid circular dependencies that could be
created from the
On 2020-08-06 11:05, Jason Liu wrote:
-Original Message-
From: Marc Zyngier
[...]
> No, this patch is not papering over a much deeper issue in the driver.
> This is just to make things better for the ARM64 kexec.
Yes, I'm sure it is... However:
request_irq()
clock off>
if
On 2020-08-06 15:58, Daniel Palmer wrote:
Hi Mark-PK,
On Thu, 6 Aug 2020 at 23:08, Mark-PK Tsai
wrote:
> Do you know if it would be possible to confirm if they are
> the
> same thing? MediaTek bought MStar a few years ago so it seems likely
> but I have no hard information.
>
Yes, it's for
Em Wed, Aug 05, 2020 at 10:56:56AM +0300, Alexey Budankov escreveu:
>
> Open access to per-process monitoring for CAP_PERFMON only
> privileged processes [1]. Extend ptrace_may_access() check
> in perf_events subsystem with perfmon_capable() to simplify
> user experience and make monitoring more
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 37f9e8b51dbe7f69d9f80aec98f1514f0cd4085e
Masami Hiramatsu (1):
bootconfig: Fix to find the initargs correctly
Muchun Song (1):
kprobes: Fix compiler warning for !CONFIG_KPROBES_ON_FTRACE
On Thursday, 2020-07-16 at 16:52:47 +03, Jarkko Sakkinen wrote:
> From: Sean Christopherson
>
> Enumerate Enclave Page Cache (EPC) sections via CPUID and add the data
> structures necessary to track EPC pages so that they can be easily borrowed
> for different uses.
>
> Embed section index to the
ers/crypto/Kconfig |3 +++
1 file changed, 3 insertions(+)
--- linux-next-20200806.orig/drivers/crypto/Kconfig
+++ linux-next-20200806/drivers/crypto/Kconfig
@@ -873,6 +873,9 @@ config CRYPTO_DEV_SA2UL
select CRYPTO_AES
select CRYPTO_AES_ARM64
select CRYPTO_ALGAPI
+
Em Wed, Aug 05, 2020 at 11:34:43AM +0200, Jiri Olsa escreveu:
> So it's possible to add new values. I did not find any place
> where the enum values are passed through some number type,
> so it's safe to make this change.
Thanks, applied.
- Arnaldo
> Signed-off-by: Jiri Olsa
> ---
>
From: "Steven Rostedt (VMware)"
On exit, if a process is preempted after the trace_sched_process_exit()
tracepoint but before the process is done exiting, then when it gets
scheduled in, the function tracers will not filter it properly against the
function tracing pid filters.
That is because
Em Wed, Aug 05, 2020 at 11:34:38AM +0200, Jiri Olsa escreveu:
> Move parse_clockid and all needed clcckid related stuff
> into clockid object. We are going to add clockid_name
> function in following change, so it's better it's placed
> in separated object and not in builtin-record.c.
>
> No
Em Mon, Jul 20, 2020 at 03:25:02PM -0700, Andi Kleen escreveu:
> But looks overall the patches look good to me now.
> (for the whole series)
> Reviewed-by: Andi Kleen
Thanks, applied.
- Arnaldo
From: Masami Hiramatsu
Since the parse_args() stops parsing at '--', bootconfig_params()
will never get the '--' as param and initargs_found never be true.
In the result, if we pass some init arguments via the bootconfig,
those are always appended to the kernel command line with '--'
even if the
From: Jernej Skrabec
When dealing with with interlaced frames, reference lists must tell if
each particular reference is meant for top or bottom field. This info
is currently not provided at all in the H264 related controls.
Make reference lists hold a structure which will also hold an
- On Aug 6, 2020, at 1:07 PM, Peter Oskolkov p...@posk.io wrote:
> On Thu, Aug 6, 2020 at 6:48 AM wrote:
>>
>> On Wed, Aug 05, 2020 at 05:08:58PM -0700, Peter Oskolkov wrote:
>>
>> Thanks for the Cc!
>
> Always a pleasure!
>
> (Sorry, included only membarrier maintainers in v1; in v2
On Wed, Aug 05, 2020 at 10:33:02AM -0700, Florian Fainelli wrote:
>
>
> On 8/5/2020 9:03 AM, Sudeep Holla wrote:
> > On Wed, Aug 05, 2020 at 06:34:36PM +0530, Viresh Kumar wrote:
> >> On 05-08-20, 12:04, Lukasz Luba wrote:
> >>> I know that Viresh is going to develop patches and improve these
>
On Tue, Aug 04, 2020 at 11:01:48PM +0800, Anson Huang wrote:
> Convert the vf610 gpio binding to DT schema format using json-schema.
>
> Signed-off-by: Anson Huang
> ---
> .../devicetree/bindings/gpio/gpio-vf610.txt| 63 -
> .../devicetree/bindings/gpio/gpio-vf610.yaml
Slice header syntax element 'first_mb_in_slice' can point
to the last macroblock, currently the field can only reference
65536 macroblocks which is insufficient for 8K videos.
Although unlikely, a 8192x4320 video (where macroblocks are 16x16),
would contain 138240 macroblocks on a frame.
As per
From: Philipp Zabel
Since pic_order_cnt_bit_size is not a syntax element itself, explicitly
state that it is the total size in bits of the pic_order_cnt_lsb,
delta_pic_order_cnt_bottom, delta_pic_order_cnt[0], and
delta_pic_order_cnt[1] syntax elements contained in the slice.
Signed-off-by:
The prediction weight parameters are only required under
certain conditions, which depend on slice header parameters.
As specified in section 7.3.3 Slice header syntax, the prediction
weight table is present if:
((weighted_pred_flag && (slice_type == P || slice_type == SP)) || \
From: Jernej Skrabec
When interlaced H264 content is being decoded, references must indicate
which field is being referenced. Currently this was done by checking
capture buffer flags. However, that is not correct because capture
buffer may hold both fields.
Fix this by checking newly introduced
On Thu, Aug 6, 2020 at 6:35 AM Ingo Molnar wrote:
>
>
> * kernel test robot wrote:
>
> > Greeting,
> >
> > FYI, we noticed a -43.3% regression of fio.read_iops due to commit:
> >
> >
> > commit: a0ac629ebe7b3d248cb93807782a00d9142fdb98 ("x86/copy_mc: Introduce
> > copy_mc_generic()")
> > url:
Currently, the SLICE_BASED and FRAME_BASED modes documentation
is misleading and not matching the intended use-cases.
Drop non-required fields SLICE_PARAMS 'start_byte_offset' and
DECODE_PARAMS 'num_slices' and clarify the decoding modes in the
documentation.
On SLICE_BASED mode, a single slice
On Wed, Aug 5, 2020 at 5:18 PM Michael S. Tsirkin wrote:
>
> On Wed, Aug 05, 2020 at 10:05:40AM -0700, Jim Mattson wrote:
> > On Tue, Jul 28, 2020 at 7:38 AM Vitaly Kuznetsov
> > wrote:
> > >
> > > PCIe config space can (depending on the configuration) be quite big but
> > > usually is sparsely
On 8/6/20 7:54 AM, Xianting Tian wrote:
> Try to merge continuous bio to current task's plug fisrt.
The patch looks fine to me, but I'd really like to see a bit more
changelog here. The commit message should explain why the change
is made, rather it's a very brief explanation of what it does.
If
The SLICE_PARAMS control is intended for slice-based
devices. In this mode, the OUTPUT buffer contains
a single slice, and so the buffer's plane payload size
can be used to query the slice size.
To reduce the API surface drop the size from the
SLICE_PARAMS control.
A follow-up change will remove
501 - 600 of 1104 matches
Mail list logo
