On Tue, 14 Jul 2020 22:25:04 +0800
Wei Yongjun wrote:
> Fix sparse build warning:
>
> init/main.c:305:6: warning:
> symbol 'xbc_namebuf' was not declared. Should it be static?
Good catch!
Acked-by: Masami Hiramatsu
Thank you,
>
> Signed-off-by: Wei Yongjun
> ---
> init/main.c | 2 +-
>
On 7/13/2020 11:35 PM, Randy Dunlap wrote:
From: Randy Dunlap
Fix build errors when CONFIG_PCI_MSI is not enabled by making the
driver depend on PCI_MSI:
ld: drivers/dma/idxd/device.o: in function `idxd_mask_msix_vector':
device.c:(.text+0x26f): undefined reference to `pci_msi_mask_irq'
On 14/07/20 13:45, Sudeep Holla wrote:
> Commit c8ff5841a90b ("rtc: pl031: switch to
> rtc_time64_to_tm/rtc_tm_to_time64")
> seemed to have accidentally removed the call to pl031_alarm_irq_enable
> from pl031_set_alarm while switching to 64-bit apis.
>
> Let us add back the same to get the set
On Mon, Jul 13, 2020 at 9:47 PM Anup Patel wrote:
>
> On Tue, Jul 14, 2020 at 8:07 AM Rob Herring wrote:
> >
> > On Sat, Jun 27, 2020 at 09:49:57PM +0530, Anup Patel wrote:
> > > We add DT bindings documentation for CLINT device.
> > >
> > > Signed-off-by: Anup Patel
> > > Reviewed-by: Palmer
Depending on how you look at it, you can either say that:
a) There is a PDC hardware issue (with the specific IP rev that exists
on sc7180) that causes the PDC not to work properly when configured
to handle dual edges.
b) The dual edge feature of the PDC hardware was only added in later
Hi,
On Tue, Jul 14, 2020 at 3:54 AM Marc Zyngier wrote:
>
> Hi Doug,
>
> On 2020-07-13 16:26, Douglas Anderson wrote:
> > Depending on how you look at it, you can either say that:
> > a) There is a PDC hardware issue (with the specific IP rev that exists
> >on sc7180) that causes the PDC not
Include gcc reset bindings in ipq8074 device tree
Signed-off-by: Sivaprakash Murugesan
---
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/ipq8074.dtsi
b/arch/arm64/boot/dts/qcom/ipq8074.dtsi
index 5303821300b4..be2690c31433
Include gcc reset bindings in ipq8074 gcc clock controller
Signed-off-by: Sivaprakash Murugesan
---
drivers/clk/qcom/gcc-ipq8074.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/qcom/gcc-ipq8074.c b/drivers/clk/qcom/gcc-ipq8074.c
index 443e28cda8ed..dbc10b6ebac2 100644
---
The patch series https://lwn.net/Articles/825325/ wrongly added clock
bindings into reset bindings. This is caught by
kernel test robot after it got merged into the clk-next
tree.
To avoid these kind of future mistakes it is better we split up the reset
bindings from clock bindings.
Since the
Remove ipq8074 gcc reset bindings from gcc clock bindings file,
so that it can be added in reset bindings.
This will avoid confusion while adding new clock and resets.
Reported-by: kernel test robot
Signed-off-by: Sivaprakash Murugesan
---
include/dt-bindings/clock/qcom,gcc-ipq8074.h | 139
Add gcc resets found in ipq8074 devices. These were previously added
along with clock bindings.
Signed-off-by: Sivaprakash Murugesan
---
include/dt-bindings/reset/qcom,gcc-ipq8074.h | 141 +++
1 file changed, 141 insertions(+)
create mode 100644
Mostly missing or incorrect (bitrotted) function parameters.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/fcoe/fcoe_ctlr.c:139: warning: Function parameter or member
'mode' not described in 'fcoe_ctlr_init'
drivers/scsi/fcoe/fcoe_ctlr.c:604: warning: Function parameter or
On Tue, 2020-07-14 at 16:38 +1000, Daniel Axtens wrote:
> Hi Nayna,
>
> Thanks! Would you be able to fold in some of the information from my
> reply to v1 into the changelog? Until we have public PAPR release with
> it, that information is the extent of the public documentation. It would
> be
On Tue, Jul 14, 2020 at 03:37:51PM +0800, Tiezhu Yang wrote:
> On 06/12/2020 09:30 AM, Tiezhu Yang wrote:
> > Use DECLARE_PCI_FIXUP_EARLY instead of DECLARE_PCI_FIXUP_HEADER
> > for bridge_class_quirk() in pci-loongson.c, otherwise the fixup
> > has no effect.
> >
> > Fixes: 1f58cca5cf2b ("PCI:
The 07/14/2020 16:29, Nikolay Aleksandrov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On 14/07/2020 10:34, Horatiu Vultur wrote:
> > This patch adds a new port attribute, IFLA_BRPORT_MRP_IN_OPEN, which
> > allows to notify the
Claudiu Beznea writes:
> Correct typo in logarithmic_accumulation() description.
>
> Signed-off-by: Claudiu Beznea
> ---
> kernel/time/timekeeping.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index
On 2020-07-14 16:04, Douglas Anderson wrote:
Depending on how you look at it, you can either say that:
a) There is a PDC hardware issue (with the specific IP rev that exists
on sc7180) that causes the PDC not to work properly when configured
to handle dual edges.
b) The dual edge feature
On 11.07.20 15:37, Shawn Guo wrote:
> On Wed, Jun 17, 2020 at 09:38:20AM +0200, Martin Kepplinger wrote:
>> From: "Angus Ainslie (Purism)"
>>
>> Add a devicetree description for the Librem 5 phone. The early batches
>> that have been sold are supported as well as the mass-produced device
>>
Hi Palmer,
On Sat, Jul 11, 2020 at 10:43 PM Palmer Dabbelt wrote:
> This still slightly changes the accounting numbers, but I don't think it does
> so in a way that's meaningful enough to care about. SIGBUS is the only one
> that might happen frequently enough to notice, I doubt anyone cares
* dillon min [200714 07:03]:
> Hi Stephen,
>
> Thanks for your patience, step by step help on my patch reviewing.
Thanks I'll update my fixes branch with v4 version.
Tony
On 7/14/20 5:07 PM, Lee Jones wrote:
Mostly missing or incorrect (bitrotted) function parameters.
Fixes the following W=1 kernel build warning(s):
drivers/scsi/fcoe/fcoe_ctlr.c:139: warning: Function parameter or member
'mode' not described in 'fcoe_ctlr_init'
Em Tue, Jul 14, 2020 at 09:05:10PM +0900, Namhyung Kim escreveu:
> Hello,
>
> On Tue, Jul 14, 2020 at 5:37 PM Alexey Budankov
> wrote:
> >
> >
> > Changes in v11:
> > - added comments to struct ctl_fd
> > - explicitly coded data_size decrement
>
> Acked-by: Namhyung Kim
So, I think v10 had
On 2020/7/14 0:59, Catalin Marinas wrote:
>> +config ARM64_TLBI_RANGE
>> +bool "Enable support for tlbi range feature"
>> +default y
>> +depends on AS_HAS_TLBI_RANGE
>> +help
>> + ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a
>> + range of input
The Toradex Colibri iMX6ULL board has a special USB hardware design.
With runtime-pm enabled USB reset itself continuously. Furthermore the
OTG port is also not enumerating devices if the Chipidea IP is in
runtime sleep mode and a device or host gets plugged in.
This patch adds the opportunity to
The Colibri iMX6ULL has a somewhat special hardware design due to some
legacy decisions regarding USB OTG. This leads to different issues
when runtime PM is enabled.
Disable runtime power management on colibri-imx6ull USB.
Signed-off-by: Philippe Schenker
---
Changes in v2: None
Chipidea depends on some hardware signals to be there in order
for runtime-pm to work well. Add the possibility to disable runtime
power management that is necessary for certain boards.
Signed-off-by: Philippe Schenker
---
Changes in v2: None
Ack, just with a note:
On Tue, Jul 14, 2020 at 4:06 AM Christoph Hellwig wrote:
>
> --- a/arch/x86/include/asm/uaccess.h
> +++ b/arch/x86/include/asm/uaccess.h
> @@ -33,7 +33,7 @@ static inline void set_fs(mm_segment_t fs)
> set_thread_flag(TIF_FSCHECK);
> }
>
> -#define segment_eq(a,
Em Tue, Jul 14, 2020 at 12:59:34PM +0200, Peter Zijlstra escreveu:
> On Mon, Jul 13, 2020 at 03:51:52PM -0300, Arnaldo Carvalho de Melo wrote:
>
> > > > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > > > index 856d98c36f56..a2397f724c10 100644
> > > > --- a/kernel/events/core.c
> >
On Tue, Jul 14, 2020 at 07:36:06AM +0100, Giovanni Cabiddu wrote:
> Add device IDs for the following Intel QuickAssist devices: DH895XCC,
> C3XXX and C62X.
>
> The defines in this patch are going to be referenced in two independent
> drivers, qat and vfio-pci.
>
> Signed-off-by: Giovanni Cabiddu
On Tue, Jul 14, 2020 at 4:08 AM Christoph Hellwig wrote:
>
> Add helpers to wrap the get_fs/set_fs magic for undoing any damange done
> by set_fs(KERNEL_DS). There is no real functional benefit, but this
> documents the intent of these calls better, and will allow stubbing the
> functions out
On Tue, Jul 14, 2020 at 1:41 AM Michal Hocko wrote:
>
> On Fri 10-07-20 12:19:37, Shakeel Butt wrote:
> > On Fri, Jul 10, 2020 at 11:42 AM Roman Gushchin wrote:
> > >
> > > On Fri, Jul 10, 2020 at 07:12:22AM -0700, Shakeel Butt wrote:
> > > > On Fri, Jul 10, 2020 at 5:29 AM Michal Hocko wrote:
On Tue, Jul 14, 2020 at 6:30 AM Eric W. Biederman wrote:
>
> Please let me know if you see something wrong.
Ack, looks good to me.
Linus
On 7/14/20 8:33 AM, Hans de Goede wrote:
Hi,
On 7/14/20 10:09 AM, Jing Xiangfeng wrote:
snd_byt_cht_es8316_mc_probe() misses to call put_device() in an error
path. Add the missed function call to fix it.
Fixes: ba49cf6f8e4a ("ASoC: Intel: bytcht_es8316: Add quirk for
inverted jack
On 14/07/2020 18:07, Horatiu Vultur wrote:
> The 07/14/2020 16:29, Nikolay Aleksandrov wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
>> content is safe
>>
>> On 14/07/2020 10:34, Horatiu Vultur wrote:
>>> This patch adds a new port attribute,
On Tue, Jul 14, 2020 at 12:09 AM Christoph Hellwig wrote:
>
> On Fri, Jul 10, 2020 at 08:25:35AM -0700, Linus Torvalds wrote:
> >
> > Ack. All the patches looked like no-ops to me, but with better naming
> > and clarity.
>
> Is that a formal Acked-by?
Yup, the patch series looks fine to me, and
On Fri, Jul 10, 2020 at 12:19:37PM -0700, Shakeel Butt wrote:
> On Fri, Jul 10, 2020 at 11:42 AM Roman Gushchin wrote:
> >
> > On Fri, Jul 10, 2020 at 07:12:22AM -0700, Shakeel Butt wrote:
> > > On Fri, Jul 10, 2020 at 5:29 AM Michal Hocko wrote:
> > > >
> > > > On Thu 09-07-20 12:47:18, Roman
Hi,
On Fri, Jul 10, 2020 at 10:11 AM Steev Klimaszewski wrote:
>
>
> On 7/10/20 9:47 AM, Doug Anderson wrote:
> > Hi,
> >
> >
> > But should I continue on this path,
> > It's probably worth getting dithering working on your sdm845 anyway in
> > case anyone actually does put a 6bpp panel on this
://en.wikipedia.org/wiki/Flexible_array_member
[2] https://github.com/KSPP/linux/issues/79
Tested-by: kernel test robot
Link:
https://github.com/GustavoARSilva/linux-hardening/blob/master/cii/kernel-ci/hpilo-20200714.md
Signed-off-by: Gustavo A. R. Silva
---
drivers/misc/hpilo.c | 2
During setup():
...
for ns in h0 r1 h1 h2 h3
do
create_ns ${ns}
done
...
while in cleanup():
...
for n in h1 r1 h2 h3 h4
do
ip netns del ${n} 2>/dev/null
done
...
and after removing the stderr redirection in
On Tue, 2020-07-14 at 09:46 +0200, Hannes Reinecke wrote:
> On 7/13/20 10:00 AM, Lee Jones wrote:
> > Haven't been used since 2006.
> >
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/scsi/aic7xxx/aic79xx_osm.c: In function
> > ‘ahd_linux_queue_abort_cmd’:
> >
On Mon, Jul 13, 2020 at 12:42:35PM +0100, Chris Down wrote:
> In Facebook production, we've seen cases where cgroups have been put
> into allocator throttling even when they appear to have a lot of slack
> file caches which should be trivially reclaimable.
>
> Looking more closely, the problem is
+Suren Baghdasaryan +Hridya Valsaraju who support the ashmem driver.
On Tue, Jul 14, 2020 at 7:18 AM Michal Hocko wrote:
>
> On Tue 14-07-20 22:08:59, Hillf Danton wrote:
> >
> > On Tue, 14 Jul 2020 10:26:29 +0200 Michal Hocko wrote:
> > > On Tue 14-07-20 13:32:05, Hillf Danton wrote:
> > > >
>
config: microblaze-randconfig-r011-20200714 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
git
On Tue, Jul 14, 2020 at 01:19:55PM +0100, Chris Down wrote:
> That is, even with pr_err_ratelimited, we still end up logging on basically
> every single write, even though it's from the same TGID writing to the same
> MSRs, and end up becoming >80% of kmsg.
>
> Of course, one can boot with
On Tue, Jul 14, 2020 at 4:32 AM Jarkko Sakkinen
wrote:
>
> On Fri, Jul 10, 2020 at 11:25:44AM -0700, Andrey Pronin wrote:
> > > Why does not tpm_del_char_device need this?
> >
> > "Not" is a typo in the sentence above, right? tpm_del_char_device *does*
> > need the fix. When tpm_class_shutdown is
The following commit has been merged into the irq/urgent branch of tip:
Commit-ID: e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb
Gitweb:
https://git.kernel.org/tip/e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb
Author:Thomas Gleixner
AuthorDate:Thu, 09 Jul 2020 11:53:06 +02:00
On Mon, Jul 13, 2020 at 03:49:27PM +0100, Lee Jones wrote:
> Both PIN_PINGROUP_ENTRY_Y() and DRV_PINGROUP_ENTRY_Y() macros are
> called for each of the 2 pin groups defined here, and both of them
> initialise 'drv_reg', causing the compiler to complain.
>
> Only initialise 'drv_reg' once.
>
>
On 7/11/20 6:39 AM, Alexander A. Klimov wrote:
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
On Tue 14-07-20 08:32:09, Shakeel Butt wrote:
> On Tue, Jul 14, 2020 at 1:41 AM Michal Hocko wrote:
> >
> > On Fri 10-07-20 12:19:37, Shakeel Butt wrote:
> > > On Fri, Jul 10, 2020 at 11:42 AM Roman Gushchin wrote:
> > > >
> > > > On Fri, Jul 10, 2020 at 07:12:22AM -0700, Shakeel Butt wrote:
> >
On Tue, Jul 14, 2020 at 01:04:42PM +0200, Saheed Olayemi Bolarinwa wrote:
> From: Bolarinwa Olayemi Saheed
> ...
> Bolarinwa Olayemi Saheed (14):
> IB/hfi1: Check the return value of pcie_capability_read_*()
> misc: rtsx: Check the return value of pcie_capability_read_*()
> ath9k: Check
On Fri, Jul 10, 2020 at 03:59:46PM +0200, Johan Hovold wrote:
> Commit 33ae787b74fc ("serial: tegra: add support to ignore read") added
> support for dropping input in case CREAD isn't set, but for PIO the
> ignore_status_mask wasn't checked until after the character had been
> put in the receive
The 07/14/2020 18:33, Nikolay Aleksandrov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On 14/07/2020 18:07, Horatiu Vultur wrote:
> > The 07/14/2020 16:29, Nikolay Aleksandrov wrote:
> >> EXTERNAL EMAIL: Do not click links or open
On Fri, Jul 10, 2020 at 03:59:47PM +0200, Johan Hovold wrote:
> The struct tty_port is part of the uart state and will never be NULL in
> the receive helpers. Drop the bogus NULL checks and rename the
> pointer-variables "port" to differentiate them from struct tty_struct
> pointers (which can be
On Tue, Jul 14, 2020 at 4:11 PM Sebastian Andrzej Siewior
wrote:
>
> On 2020-07-14 15:54:57 [+0200], Rafael J. Wysocki wrote:
> > On Tue, Jul 14, 2020 at 3:44 PM Sebastian Andrzej Siewior
> > wrote:>
> > > On 2020-06-24 23:49:52 [+0200], Stephen Berman wrote:
> > >
> > > Let me summarize the
On 14.07.2020 18:16, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jul 14, 2020 at 09:05:10PM +0900, Namhyung Kim escreveu:
>> Hello,
>>
>> On Tue, Jul 14, 2020 at 5:37 PM Alexey Budankov
>> wrote:
>>>
>>>
>>> Changes in v11:
>>> - added comments to struct ctl_fd
>>> - explicitly coded data_size
On Tue, Jul 14, 2020 at 10:16:36AM -0400, Steven Rostedt wrote:
> > That's just how the code was; it treated vmlinux as the NULL module, and
> > as such needed a static_call_mod allocated to host the static_call_sites
> > pointer.
> >
> > That is, the static_call_key has a single linked list
On Tue, 14 Jul 2020 14:35:16 + Ooi, Joyce wrote:
> > I'm no device tree expert but these look like config options rather than HW
> > description. They also don't appear to be documented in the next patch.
>
> The poll_freq are part of the msgdma prefetcher IP, whereby it
> specifies the
On Tue, Jul 14, 2020 at 4:20 AM wrote:
>
> On 2020-07-13 22:50, Rob Clark wrote:
> > On Mon, Jul 13, 2020 at 8:59 AM wrote:
> >>
> >> On 2020-07-10 22:38, Rob Clark wrote:
> >> > On Thu, Jun 18, 2020 at 7:09 AM Kalyan Thota
> >> > wrote:
> >> >>
> >> >> This change adds support to scale src clk
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
>
> Can't see them being used anywhere and the compiler doesn't complain
> that they're missing, so ...
Aren't they needed for automatic module loading in certain configurations?
> Fixes the following W=1 kernel build warning(s):
>
>
On Tue, 2020-07-14 at 08:55 -0700, Jakub Kicinski wrote:
> On Tue, 14 Jul 2020 14:35:16 + Ooi, Joyce wrote:
> > > I'm no device tree expert but these look like config options rather than
> > > HW
> > > description. They also don't appear to be documented in the next patch.
> >
> > The
On Tue, Jul 14, 2020 at 02:31:00PM +0200, John Paul Adrian Glaubitz wrote:
> Hi Christoph!
>
> On 7/14/20 2:18 PM, Christoph Hellwig wrote:
> > can you take a look and possibly pick up the series below that untangles
> > and sorts out minor issues with the sh ioremap and dma code?
> >
> > I sent
On Tue, Jul 14, 2020 at 11:17:01PM +0800, Zhenyu Ye wrote:
> On 2020/7/14 0:59, Catalin Marinas wrote:
> >> +config ARM64_TLBI_RANGE
> >> + bool "Enable support for tlbi range feature"
> >> + default y
> >> + depends on AS_HAS_TLBI_RANGE
> >> + help
> >> +ARMv8.4-TLBI provides TLBI
On Tue, Jul 14, 2020 at 4:51 PM Lee Jones wrote:
>
> If we fail to use a variable, even a 'dummy' one, then the compiler
> complains that it is set but not used. We know this is fine, so we
> set it to its own value here.
Which is kind of ugly in my personal view. I hope that the compiler
will
Le dimanche 12 juillet 2020 à 19:59 -0300, Ezequiel Garcia a écrit :
> On Sat, 2020-07-11 at 10:21 +, Jonas Karlman wrote:
> > On 2020-07-10 23:49, Nicolas Dufresne wrote:
> > > Le vendredi 10 juillet 2020 à 09:25 -0300, Ezequiel Garcia a écrit :
> > > > +Nicolas
> > > >
> > > > On Fri,
Borislav Petkov writes:
On Tue, Jul 14, 2020 at 01:19:55PM +0100, Chris Down wrote:
That is, even with pr_err_ratelimited, we still end up logging on basically
every single write, even though it's from the same TGID writing to the same
MSRs, and end up becoming >80% of kmsg.
Of course, one can
Hi Bjorn,
On Mon, Jun 22, 2020 at 12:59:55AM -0700, Bjorn Andersson wrote:
> In modern Qualcomm platforms the mutex region of the TCSR is forked off
> into its own block, all with a offset of 0 and stride of 4096, and in
> some of these platforms no other registers in this region is accessed
>
On Tue, 14 Jul 2020 17:54:17 +0200
Peter Zijlstra wrote:
> > I guess that is, why did moving the initialization early require an
> > allocation where initializing it later did not? What allocation are we
> > avoiding?
>
> The other way around. Before this patch initialization required an
>
Add device-tree binding documentation to represent Tegra194
CPU Complex with compatible string under 'cpus' node. This
can be used by drivers like cpufreq which don't have their
node or CPU Complex node to bind to. Also, documenting
'nvidia,bpmp' property which points to BPMP device.
Hi Kirill,
On Tue, Jul 14, 2020 at 10:33:06AM +0300, Kirill A. Shutemov wrote:
> On Sun, Jul 12, 2020 at 03:58:06PM -0700, Linus Torvalds wrote:
> > Anybody else have any opinions?
>
> Maybe we just shouldn't allow move_normal_pmd() if ranges overlap?
>
> Other option: pass 'overlaps' down to
On 13-07-20, 13:55, Dave Jiang wrote:
>
>
> On 7/10/2020 2:38 AM, Serge Semin wrote:
> > On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote:
> > > On Fri, Jul 10, 2020 at 01:45:44AM +0300, Serge Semin wrote:
> > > > There are DMA devices (like ours version of Synopsys DW DMAC) which
Hello Michael,
On Tue, Jul 14, 2020 at 01:31:13PM +0200, Michael Walle wrote:
> Am 2020-07-13 10:47, schrieb Uwe Kleine-König:
> > I already thought about proposing pwm_get_rate_hw(), but for now there
> > is (AFAICT) no user who would need it. And it's hard to know which
> > variant is actually
Le lundi 13 juillet 2020 à 11:15 +0300, Stanimir Varbanov a écrit :
> Add menu control for VP9 codec levels. A total of 14 levels are
> defined for Profile 0 (8bit) and Profile 2 (10bit). Each level
> is a set of constrained bitstreams coded with targeted resolutions,
> frame rates, and bitrates.
On 2020-07-14 17:53:15 [+0200], Rafael J. Wysocki wrote:
> > shows the pattern and we nailed it down that it comes from
> > thermal_get_temp().
>
> acpi_evaluate_integer() doesn't show up in the trace, though, AFAICS.
I deducted it. acpi_thermal_get_temperature() -> acpi_evaluate_integer()
and
On 7/14/20 5:59 PM, Rich Felker wrote:
> I'd like to have a way to test the DMA changes or testing feedback
> from someone using an affected configuration just because they're
> sufficiently nontrivial (Adrian might be able to do this? If so that'd
> be great; if not let me know if it's testable
changed symbols N_SHORT_PACKET_LUT_ENTRIES, N_LONG_PACKET_ENTRIES,
N_CSI_RX_FE_CTRL_DLANES, N_CSI_RX_BE_SID_WIDTH to static because they
were not declared earlier.
Signed-off-by: B K Karthik
---
.../media/atomisp/pci/css_2401_system/host/csi_rx.c | 8
1 file changed, 4
From: Yanfei Xu
when get_unused_fd_flags gets failure, userfaultfd_ctx_cachep will
be freed by userfaultfd_fops's release function which is the
userfaultfd_release. So we could return directly after fput().
userfaultfd_release()->userfaultfd_ctx_put(ctx)
Fixes: d08ac70b1e0d (Wire UFFD up to
Hi,
This patch-set adds initial support for a new Intel Movidius SoC code-named
Keem Bay. The SoC couples an ARM Cortex A53 CPU with an Intel Movidius VPU.
This initial patch-set enables only the minimal set of components required
to make the Keem Bay EVM board boot into initramfs.
Changes from
From: Daniele Alessandrelli
Add power domain dt-bindings for Keem Bay SoC.
Signed-off-by: Daniele Alessandrelli
---
include/dt-bindings/power/keembay-power.h | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 include/dt-bindings/power/keembay-power.h
diff --git
From: Daniele Alessandrelli
Add initial device tree for Intel Movidius SoC code-named Keem Bay.
This initial DT includes nodes for Cortex-A53 cores, UARTs, GIC, PSCI,
and PMU.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
MAINTAINERS| 1
From: Daniele Alessandrelli
Add maintainers for the new Intel Movidius SoC code-named Keem Bay.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b4a43a9e7fbc..b151d0fc0588
From: Daniele Alessandrelli
Add initial device tree for Keem Bay EVM board. With this minimal device
tree the board boots fine using an initramfs image.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
MAINTAINERS | 1 +
From: Daniele Alessandrelli
Add ARCH_KEEMBAY configuration option to support Intel Movidius SoC
code-named Keem Bay.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
arch/arm64/Kconfig.platforms | 5 +
1 file changed, 5 insertions(+)
diff --git
From: Daniele Alessandrelli
Document Intel Movidius SoC code-named Keem Bay, along with the Keem Bay
EVM board.
Reviewed-by: Dinh Nguyen
Signed-off-by: Daniele Alessandrelli
---
.../devicetree/bindings/arm/keembay.yaml | 19 +++
1 file changed, 19 insertions(+)
create
From: Daniele Alessandrelli
Add clock dt-bindings for Keem Bay SoC.
Signed-off-by: Daniele Alessandrelli
---
include/dt-bindings/clock/keembay-clocks.h | 188 +
1 file changed, 188 insertions(+)
create mode 100644 include/dt-bindings/clock/keembay-clocks.h
diff --git
The cpus.yaml binding documents what's in 'cpu' nodes, not 'cpus'
node. AIUI, the latter is what you want. You should do your own schema
file here.
Do you mean to change existing file name from 'cpus.yaml' to 'cpu.yaml'
and create new 'cpus.yaml' file?
I think it's better to incorporate the
This implements the mount_setattr() syscall. While the new mount api
allows to change the properties of a superblock there is currently no
way to change the mount properties of a mount or mount tree using mount
file descriptors which the new mount api is based on. In addition the
old mount api has
On Tue, Jul 14, 2020 at 06:53:26PM +0300, Alexey Budankov wrote:
>
> On 14.07.2020 18:16, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jul 14, 2020 at 09:05:10PM +0900, Namhyung Kim escreveu:
> >> Hello,
> >>
> >> On Tue, Jul 14, 2020 at 5:37 PM Alexey Budankov
> >> wrote:
> >>>
> >>>
> >>>
Hey everyone,
This series can be found at:
https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=mount_setattr
https://gitlab.com/brauner/linux/-/commits/mount_setattr
https://github.com/brauner/linux/tree/mount_setattr
This implements the mount_setattr() syscall which has
Add a range of selftests for the new mount_setattr() syscall to verify
that it works as expected. This tests that:
- no invalid flags can be specified
- changing properties of a single mount works and leaves other mounts in
the mount tree unchanged
- changing a mount tre to read-only when one of
Changing mount options always ends up taking lock_mount_hash() but when
MNT_READONLY is requested and neither the mount nor the superblock are
not already MNT_READONLY we end up taking the lock, dropping it, and
retaking it to change the other mount attributes. Instead of this,
acquire the lock
do_reconfigure_mnt() used to take the down_write(>s_umount) lock
which seems unnecessary since we're not changing the superblock. We're
only checking whether it is already read-only. Setting other mount
attributes is protected by lock_mount_hash() afaict and not by s_umount.
So I think the
Hey everyone,
So it looks like this was a red herring. We were getting spurious
interrupts which I suspect caused the console code to get called in
some critical section. Once we fixed the spurious interrupts we no
longer see the issue. Sorry for the noise.
Thanks,
Raul
On Thu, Jul 9, 2020 at
Signed-off-by: Christian Brauner
---
man2/mount_setattr.2 | 296 +++
1 file changed, 296 insertions(+)
create mode 100644 man2/mount_setattr.2
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
new file mode 100644
index 0..aae10525e
---
On Sun, Jul 12, 2020 at 11:01:13AM +0100, Jon Hunter wrote:
> This series adds support for in-band debug messaging for the BPMP and
> updates the BPMP ABI to align with the latest version.
>
> Jon Hunter (4):
> firmware: tegra: Use consistent return variable name
> firmware: tegra: Prepare
On 7/14/2020 9:08 AM, Vinod Koul wrote:
On 13-07-20, 13:55, Dave Jiang wrote:
On 7/10/2020 2:38 AM, Serge Semin wrote:
On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote:
On Fri, Jul 10, 2020 at 01:45:44AM +0300, Serge Semin wrote:
There are DMA devices (like ours version
Vladimir Oltean writes:
[...]
>> Acked-by: Vladimir Oltean
>>
>> Thanks,
>> -Vladimir
>
> Of course, it would be good if you sent a new version with the sha1sum
> of the Fixes: tag having the right length, otherwise people will
> complain.
Ah, thanks for reminding! I entirely forgot about
On Tue, Jul 14, 2020 at 9:08 AM Joel Fernandes wrote:
>
> I was thinking we should not call move_page_tables() with overlapping ranges
> at all, just to keep things simple.
No, we're not breaking the existing stack movement code just to keep
things simple.
The rule is "make it as simple as
On Mon, Jul 13, 2020 at 11:41 PM Junxiao Bi wrote:
>
> On 7/13/20 11:17 PM, Song Liu wrote:
>
> > On Thu, Jul 9, 2020 at 4:36 PM Junxiao Bi wrote:
> >> The following deadlock was captured. The first process is holding
> >> 'kernfs_mutex'
> >> and hung by io. The io was staging in
On Tue, Jul 14, 2020 at 10:44:49AM -0500, Gustavo A. R. Silva wrote:
> There is a regular need in the kernel to provide a way to declare
> having a dynamically sized set of trailing elements in a structure.
> Kernel code should always use “flexible array members”[1] for these
> cases. The older
On Mon, Jul 13, 2020 at 11:41 PM Christoph Hellwig wrote:
>
> On Thu, Jul 09, 2020 at 04:32:07PM -0700, h...@zytor.com wrote:
> > On July 9, 2020 8:17:57 AM PDT, Christoph Hellwig wrote:
> > >Hi all,
> > >
> > >this series starts to move the early init code away from requiring
> > >KERNEL_DS to
1 - 100 of 1986 matches
Mail list logo
