Hello.
On 06.11.20 09:10, Alex Shi wrote:
Signed-off-by: Alex Shi
Cc: Alexander Aring
Cc: Stefan Schmidt
Cc: "David S. Miller"
Cc: Jakub Kicinski
Cc: linux-w...@vger.kernel.org
Cc: net...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
net/ieee802154/nl802154.c | 4
1 file chan
On Mon, 02 Nov 2020, Kalle Valo wrote:
> Lee Jones writes:
>
> > [Last batch!]
> >
> > This set is part of a larger effort attempting to clean-up W=1
> > kernel builds, which are currently overwhelmingly riddled with
> > niggly little warnings.
> >
> > Lee Jones (41):
> > wil6210: wmi: Correc
On Fri, Nov 6, 2020 at 3:17 AM Jeremy Cline wrote:
>
> Make use of the devm_drm_dev_alloc() API to bind the lifetime of
> nouveau_drm structure to the drm_device. This is important because a
> reference to nouveau_drm is accessible from drm_device, which is
> provided to a number of DRM layer call
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
>
> Lee Jones (23):
> mtd: mtdpart: Fix misdocumented function parameter 'mtd'
> mtd: devices: phram: File headers are not good candidates
On Fri, 6 Nov 2020 at 13:03, Mel Gorman wrote:
>
> On Wed, Nov 04, 2020 at 09:42:05AM +, Mel Gorman wrote:
> > While it's possible that some other factor masked the impact of the patch,
> > the fact it's neutral for two workloads in 5.10-rc2 is suspicious as it
> > indicates that if the patch
Lee Jones writes:
> On Mon, 02 Nov 2020, Kalle Valo wrote:
>
>> Lee Jones writes:
>>
>> > [Last batch!]
>> >
>> > This set is part of a larger effort attempting to clean-up W=1
>> > kernel builds, which are currently overwhelmingly riddled with
>> > niggly little warnings.
>> >
>> > Lee Jones
On 08/10/2020 10:26, John Garry wrote:
Hi Will, Mark,
Can you have a look at this series please?
You were cc'ed on the v5 rebase of the userspace part which I sent out a
little while ago.
Cheers,
John
To allow perf tool to identify a specific implementation of a PMU for
event alias matchin
On 11/2/20 5:23 PM, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/mtd/spi-nor/controllers/hisi-sfc.c:328: warning: Function parameter
> or member 'np' not described in 'hisi_spi_nor_register'
> drivers/mtd/spi-nor/controllers/hisi-sfc.c:328: warning: Functio
On Fri, 6 Nov 2020 14:13:17 +0100
Petr Mladek wrote:
> JFYI, the code reading and writing the cache looks good to me.
>
> It is still possible that some entries might stay unused (filled
> with zeroes) but it should be hard to hit in practice. It
> is good enough from my POV.
You mean the part
On Fri, Oct 16, 2020 at 10:40 PM Frank Wunderlich wrote:
> From: Frank Wunderlich
>
> mt7622 is reported by mediatek to have only 6 pwm channels
> so drop pindefines for 7th channel
>
> Signed-off-by: Frank Wunderlich
This patch (3/3) applied to the pinctrl tree.
Please apply 1-2 to the ARM S
On Fri, Nov 06, 2020 at 12:42:50PM +0100, Pawel Laszczak wrote:
> This patch introduce new Cadence USBSS DRD driver to linux kernel.
>
> The Cadence USBSS DRD Controller is a highly configurable IP Core which
> can be instantiated as Dual-Role Device (DRD), Peripheral Only and
> Host Only (XHCI)co
On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko wrote:
>
> 06.11.2020 09:15, Viresh Kumar пишет:
> > Setting regulators for count as 0 doesn't sound good to me.
> >
> > But, I understand that you don't want to have that if (have_regulator)
> > check, and it is a fair request. What I will instead do
From: Sven Van Asbroeck
Commit 6f197fb63850 ("lan743x: Added fixed link and RGMII support")
assumes that chips with an internal PHY will never have a devicetree
entry. This is incorrect: even for these chips, a devicetree entry
can be useful e.g. to pass the mac address from bootloader to chip:
On Fri, Oct 16, 2020 at 11:56:56AM -0700, Sudarshan Rajagopalan wrote:
> When section mappings are enabled, we allocate vmemmap pages from
> physically continuous memory of size PMD_SIZE using
> vmemmap_alloc_block_buf(). Section mappings are good to reduce TLB
> pressure. But when system is highly
Hi Tushar,
On Sun, 2020-11-01 at 14:26 -0800, Tushar Sugandhi wrote:
> System administrators should be able to choose which kernel subsystems
> they want to measure the critical data for. To enable that, an IMA policy
> option to choose specific kernel subsystems is needed. This policy option
> wo
On Sun, Nov 1, 2020 at 10:01 AM Paul Cercueil wrote:
> Abuse the pin function pointer to store the pin function value directly,
> when all the pins of a group have the same function value. Now when the
> pointer value is <= 3 (unsigned), the pointer value is used as the pin
> function; otherwise
Hi Lee,
Lee Jones wrote on Fri, 6 Nov 2020 13:32:47
+:
> > This set is part of a larger effort attempting to clean-up W=1
> > kernel builds, which are currently overwhelmingly riddled with
> > niggly little warnings.
> >
> > Lee Jones (23):
> > mtd: mtdpart: Fix misdocumented function par
On Sat, Oct 31, 2020 at 1:01 AM Kent Gibson wrote:
> On Fri, Oct 30, 2020 at 03:52:24PM +0100, Bartosz Golaszewski wrote:
> > The series no longer applies on top of v5.10-rc1. Could you rebase and
> > resend?
>
> Nuts, it relies on my doc tidy-up series that Linus has pulled into
> fixes, and so
Thanks,
applied to nvme-5.11
On Fri, Nov 06, 2020 at 02:15:45PM +0100, Guennadi Liakhovetski wrote:
> Hi Mathieu, Arnaud,
>
> On Thu, Nov 05, 2020 at 03:50:28PM -0700, Mathieu Poirier wrote:
> > From: Arnaud Pouliquen
> >
> > Make the RPMSG name service announcement a stand alone driver so that it
> > can be reused by other
We are trying to reach you as regards the estate of Late George Brumley, you
were made one of the beneficiaries of his estate. Do get back to me at your
earliest convenience. The Trustees
Hi Tushar,
On Sun, 2020-11-01 at 14:26 -0800, Tushar Sugandhi wrote:
> Currently, IMA does not restrict random data sources from measuring
> their data using ima_measure_critical_data(). Any kernel data source can
> call the function, and it's data will get measured as long as the input
> event_da
On Fri, Nov 06, 2020 at 04:43:17AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:9e39aef3 usb: misc: brcmstb-usb-pinmap: Make sync_all_pins..
> git tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> console outp
On 05/11/2020 20:07, Lee Jones wrote:
> On Thu, 05 Nov 2020, Tomi Valkeinen wrote:
>
>> On 05/11/2020 16:45, Lee Jones wrote:
>>> Fixes the following W=1 kernel build warning(s):
>>>
>>> drivers/gpu/drm/omapdrm/dss/dsi.c: In function ‘_dsi_print_reset_status’:
>>> drivers/gpu/drm/omapdrm/dss/dsi
Am 2020-11-06 09:11, schrieb Michael Walle:
Am 2020-11-06 03:00, schrieb Leo Li:
-Original Message-
From: Michael Walle
Sent: Thursday, November 5, 2020 1:35 PM
To: linux-...@vger.kernel.org; devicet...@vger.kernel.org; linux-
ker...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
From: Alexander Sverdlin
Linux doesn't own the memory immediately after the kernel image. On Octeon
bootloader places a shared structure right close after the kernel _end,
refer to "struct cvmx_bootinfo *octeon_bootinfo" in cavium-octeon/setup.c.
If check_kernel_sections_mem() rounds the PFNs up
v1 --> v2:
Update the detection of invalid mce priorities, the WARN_ON() is needed.
v1:
Remove the WARN_ON() in mce_register_decode_chain().
Zhen Lei (1):
x86/mce: correct the detection of invalid mce priorities
arch/x86/include/asm/mce.h | 3 ++-
arch/x86/kernel/cpu/mce/core.c | 3 ++-
2
enum mce_notifier_prios {
MCE_PRIO_LOWEST,
...
MCE_PRIO_CEC
};
After commit c9c6d216ed28 ("x86/mce: Rename "first" function as "early""),
the range of invalid priorities is changed. Add a new enumeration value
MCE_PRIO_HIGHEST, so that people can add enumeration values grea
On Fri, Nov 06, 2020 at 01:37:30PM +0800, Alex Shi wrote:
> There are some macros unused, they causes much gcc warnings. Let's
> remove them to tame gcc.
>
> net/dsa/tag_brcm.c:51:0: warning: macro "BRCM_EG_RC_SWITCH" is not used
> [-Wunused-macros]
> net/dsa/tag_brcm.c:53:0: warning: macro "BRCM_
On Wed, Nov 4, 2020 at 4:25 PM Arnaud de Turckheim wrote:
>
> This patch set fixes the irq_mask/irq_unmask functions and enables the
> PLX PEX8311 local interrupts.
>
> With the current version of the driver, gpiomon (from libgpiod) or a
> poll(2) on the sysfs value are not working. According to
>
On Fri 2020-11-06 08:41:31, Steven Rostedt wrote:
> On Fri, 6 Nov 2020 14:13:17 +0100
> Petr Mladek wrote:
>
> > JFYI, the code reading and writing the cache looks good to me.
> >
> > It is still possible that some entries might stay unused (filled
> > with zeroes) but it should be hard to hit i
> On Nov 6, 2020, at 12:40 AM, Alex Shi wrote:
>
> The macro is unused, remove it to tame gcc warning:
> fs/nfsd/nfs3proc.c:702:0: warning: macro "nfsd3_fhandleres" is not used
> [-Wunused-macros]
>
> Signed-off-by: Alex Shi
> Cc: "J. Bruce Fields"
> Cc: Chuck Lever
> Cc: linux-...@vger.
The MT29F2G01AAAED is a single die, 2Gb Micron SPI NAND Flash with 4-bit
ECC
Signed-off-by: Thirumalesha Narasimhappa
---
v6: Reverted the SPINAND_OP_VARIANTS() as they were in v4 for
MT29F2G01AAAED device
v5: As per the review comments, the changes were reverted to the v2,
except the MT29F2G01
On Wed, Nov 4, 2020 at 2:26 PM Dmitry Osipenko wrote:
>
> Add lockdep class in order to fix debug warnings that are coming from a
> legit nested use of irq_set_irq_wake() by the Tegra GPIO driver.
>
> WARNING: possible recursive locking detected
> ...
> (irq_set_irq_wake) from (tegra_gpio_irq_
On Wed, Nov 4, 2020 at 6:04 PM Dmitry Osipenko wrote:
>
> Use raw_spinlock in order to fix spurious messages about invalid context
> when spinlock debugging is enabled. This happens because there is a legit
> nested raw_spinlock->spinlock locking usage within IRQ-related code. IRQ
> core uses raw
On Fri, 06 Nov 2020, Tomi Valkeinen wrote:
> On 05/11/2020 20:07, Lee Jones wrote:
> > On Thu, 05 Nov 2020, Tomi Valkeinen wrote:
> >
> >> On 05/11/2020 16:45, Lee Jones wrote:
> >>> Fixes the following W=1 kernel build warning(s):
> >>>
> >>> drivers/gpu/drm/omapdrm/dss/dsi.c: In function ‘_dsi
Do not print an error trace when deferring probe for clock resources.
Version 2: Remark from Guenter and Ahmad
use dev_err_probe instead
Etienne Carriere (1):
watchdog: stm32_iwdg: don't print an error on probe deferral
drivers/watchdog/stm32_iwdg.c | 13 +
1 file
On Fri, 06 Nov 2020, Miquel Raynal wrote:
> Hi Lee,
>
> Lee Jones wrote on Fri, 6 Nov 2020 13:32:47
> +:
>
> > > This set is part of a larger effort attempting to clean-up W=1
> > > kernel builds, which are currently overwhelmingly riddled with
> > > niggly little warnings.
> > >
> > > Lee
From: Etienne Carriere
Do not print an error trace when deferring probe for clock resources.
Signed-off-by: Etienne Carriere
Signed-off-by: Christophe Roullier
---
drivers/watchdog/stm32_iwdg.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/watchdog/
On Fri, 06 Nov 2020, Kalle Valo wrote:
> Lee Jones writes:
>
> > On Mon, 02 Nov 2020, Kalle Valo wrote:
> >
> >> Lee Jones writes:
> >>
> >> > [Last batch!]
> >> >
> >> > This set is part of a larger effort attempting to clean-up W=1
> >> > kernel builds, which are currently overwhelmingly ri
We have for some time the assign_bit() API to replace open coded
if (foo)
set_bit(n, bar);
else
clear_bit(n, bar);
Use this API in VT keyboard library code.
Signed-off-by: Andy Shevchenko
---
drivers/tty/vt/keyboard.c | 5 +
1 file changed, 1
There are few places when GENMASK() or BIT() macro is suitable and makes code
easier to understand.
Signed-off-by: Andy Shevchenko
---
drivers/tty/vt/keyboard.c | 48 +++
1 file changed, 24 insertions(+), 24 deletions(-)
diff --git a/drivers/tty/vt/keyboard.c
Instead of 10, 13 use \n, \r respectively.
Signed-off-by: Andy Shevchenko
---
drivers/tty/vt/keyboard.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c
index bfe54b9822af..647c343f61fb 100644
--- a/drivers/tty/vt/key
On Fri, Nov 6, 2020 at 12:44 AM Sameer Pujar wrote:
>
>
> >> Move ACONNECT documentation to YAML format.
> >>
> >> Signed-off-by: Sameer Pujar
> >> ---
> >> .../bindings/bus/nvidia,tegra210-aconnect.txt | 44 ---
> >> .../bindings/bus/nvidia,tegra210-aconnect.yaml | 86
> >> +
certs/blacklist.c:84: warning: Function parameter or member 'hash' not
described in 'mark_hash_blacklisted'
Signed-off-by: Alex Shi
Cc: David Howells
Cc: David Woodhouse
Cc: keyri...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
certs/blacklist.c | 2 +-
1 file changed, 1 insertion(
Hi,
On Tue, Nov 03, 2020 at 01:41:59PM -0800, Amy Parker wrote:
> I'm currently working on improving some accessory drivers to hopefully
> submit to a future kernel tree. The drivers are assorted for headphones,
> mice, keyboards, and other assorted accessories. Which driver category
> or folder w
On Wed, Nov 04, 2020 at 04:03:36PM -0800, Sudarshan Rajagopalan wrote:
> Did you have a chance to review this patch? It is reviewed by others and
> haven't seen any Nacks. This patch will be useful to have so that memory
> hotremove doesn't fail when such PMD_SIZE pages aren't available.. which is
On Fri, Nov 06, 2020 at 10:36:02AM +, Will Deacon wrote:
> Commit ce3d31ad3cac ("arm64/smp: Move rcu_cpu_starting() earlier") ensured
> that RCU is informed early about incoming CPUs that might end up calling
> into printk() before they are online. However, if such a CPU fails the
> early CPU f
On Fri, 6 Nov 2020 22:28:38 +0800
Thirumalesha Narasimhappa wrote:
> The MT29F2G01AAAED is a single die, 2Gb Micron SPI NAND Flash with 4-bit
> ECC
>
> Signed-off-by: Thirumalesha Narasimhappa
> ---
>
> v6: Reverted the SPINAND_OP_VARIANTS() as they were in v4 for
> MT29F2G01AAAED device
>
>
On Fri, Nov 06, 2020 at 02:31:44PM +0100, Karol Herbst wrote:
> On Fri, Nov 6, 2020 at 3:17 AM Jeremy Cline wrote:
> >
> > Make use of the devm_drm_dev_alloc() API to bind the lifetime of
> > nouveau_drm structure to the drm_device. This is important because a
> > reference to nouveau_drm is acces
On Fri, Nov 6, 2020 at 6:14 AM Adrian Ratiu wrote:
>
> From: Nathan Chancellor
>
> Drop warning because kernel now requires GCC >= v4.9 after
> commit 6ec4476ac825 ("Raise gcc version requirement to 4.9").
>
> Reported-by: Nick Desaulniers
> Signed-off-by: Nathan Chancellor
> Signed-off-by: Adr
On Fri, 06 Nov 2020, Jiri Slaby wrote:
> On 06. 11. 20, 12:12, Lee Jones wrote:
> > I cannot recreate the issue or work out why:
> >
> > # THE OUTPUT
> > # *_port.o and *_early.o were both built
> You have to _link_ to see linker errors ;).
>
> Like make vmlinux
The default make that I am us
On 06/11/2020 14:58, Kurt Kanzenbach wrote:
On Fri Nov 06 2020, Arnd Bergmann wrote:
On Fri, Nov 6, 2020 at 12:35 PM Grygorii Strashko
wrote:
On 06/11/2020 09:56, Wang Qing wrote:
+++ b/drivers/net/ethernet/ti/am65-cpts.c
@@ -1001,8 +1001,7 @@ struct am65_cpts *am65_cpts_create(struct de
When sync_state support got introduced recently, by default we try to
set the NoCs to run initially at maximum rate. But as these values are
aggregated, we may end with a really big clock rate value, which is
then converted from "u64" to "long" during the clock rate rounding.
But on 32bit platforms
On Fri, Nov 06, 2020 at 03:02:41PM +0530, Sumit Garg wrote:
> On Thu, 5 Nov 2020 at 10:37, Jarkko Sakkinen wrote:
> >
> > On Tue, Nov 03, 2020 at 09:31:42PM +0530, Sumit Garg wrote:
> > > Add support for TEE based trusted keys where TEE provides the
> > > functionality
> > > to seal and unseal tr
Hi Robin,
Something similar can happen in normal use, where the scheduler
relocates processes all over the CPUs in the system as time goes by,
which causes the total rcache size to continue to grow. And in
addition to this, the global depot continues to grow very slowly as
well. But when it d
'ret' in 2 functions are not used. and one of them is a void function.
So remove them to avoid gcc warning:
kernel/trace/ftrace.c:4166:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
kernel/trace/ftrace.c:5571:6: warning: variable ‘ret’ set but not used
[-Wunused-but-set-var
The variable is unused and cause gcc warning:
fs/coda/file.c:241:6: warning: variable ‘err’ set but not used
[-Wunused-but-set-variable]
So let's remove it.
Signed-off-by: Alex Shi
Cc: Jan Harkes
Cc: c...@cs.cmu.edu
Cc: codal...@coda.cs.cmu.edu
Cc: linux-kernel@vger.kernel.org
---
fs/coda/f
On Sat, Oct 10, 2020 at 01:19:42PM +0200, Wolfram Sang wrote:
> On Mon, Oct 05, 2020 at 02:49:49PM +0200, Geert Uytterhoeven wrote:
> > The Mellanox BlueField I2C controller is only present on Mellanox
> > BlueField SoCs. Hence add a dependency on MELLANOX_PLATFORM, to prevent
> > asking the user
The transmit phase register value is never cleared during hw params.
So once hw params sets this bit to handle a two channel format, it
remains configured for dual-phase, which is not desirable for mono
playback.
Signed-off-by: Kyle Russell
---
sound/soc/pxa/mmp-sspa.c | 1 +
1 file changed, 1 i
On Fri, Nov 06, 2020 at 11:22:03AM +0800, Xuewen Yan wrote:
> According to the original code logic:
> cfs_rq->avg.util_avg
> sa->util_avg = * se->load.weight
> cfs_rq->avg.load_avg
> but for fair_sched_class in 64bits platform:
> se->load.weight =
the variable 'level' is unused, so remove it to avoid the gcc complain:
lib/decompress_unlzo.c:46:5: warning: variable ‘level’ set but not used
[-Wunused-but-set-variable]
Signed-off-by: Alex Shi
Cc: linux-kernel@vger.kernel.org
---
lib/decompress_unlzo.c | 3 +--
1 file changed, 1 insertion(+)
From: Sven Van Asbroeck
Commit f3186dd87669 ("spi: Optionally use GPIO descriptors for CS GPIOs")
introduced the optional use of GPIO descriptors for chip selects.
A side-effect of this change: when a SPI bus uses GPIO descriptors,
all its client devices have SPI_CS_HIGH set in spi->mode. This f
Currently the fwnode API and things that rely on it like fw_devlink will
not reliably work for devices created from DT since each subsystem that
creates devices must individually set dev->fwnode in addition to setting
dev->of_node, currently a number of subsystems don't do so. Ensure that
this can'
On Thu, Nov 5, 2020 at 7:00 PM Hugh Dickins wrote:
>
> I don't know why this was addressed to me in particular (easy to imagine
> I've made a mod at some time that bears on this, but I haven't found it);
> but have spent longer considering the patch than I should have done -
> apologies to everyon
On Thu, Nov 05, 2020 at 11:26:44AM -0800, Saravana Kannan wrote:
> On Thu, Nov 5, 2020 at 9:12 AM Mark Brown wrote:
> > > of_node_get(nc);
> > > spi->dev.of_node = nc;
> > > + spi->dev.fwnode = of_fwnode_handle(nc);
> > Why is this a manual step in an individual subsystem rather
Hi Rob,
On 05/11/20 10:23 pm, Rob Herring wrote:
> On Mon, Nov 02, 2020 at 10:41:37AM -0600, Nishanth Menon wrote:
>> On 15:41-20201102, Kishon Vijay Abraham I wrote:
>>> PCIe controller in J721E supports a maximum of 32 outbound regions.
>>> commit 4e5833884f66 ("arm64: dts: ti: k3-j721e-main: Ad
Make "cdns,max-outbound-regions" optional property with the default
being 32.
Link: http://lore.kernel.org/r/20201105165331.GA55814@bogus
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/pci/cdns-pcie-ep.yaml| 3 ---
Documentation/devicetree/bindings/pci/ti,j721e-p
This adds MAINTAINERS
Signed-off-by: Konstantin Komarov
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 78e908ed14f3..f7d67b7bfe80 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12474,6 +12474,13 @@ T: git
git://git.kernel.org/pub/s
This adds bitmap
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/bitfunc.c | 135
fs/ntfs3/bitmap.c | 1504
2 files changed, 1639 insertions(+)
create mode 100644 fs/ntfs3/bitfunc.c
create mode 100644 fs/ntfs3/bitmap.c
diff --git a/fs/ntfs3/b
This adds compression
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/lznt.c | 452
1 file changed, 452 insertions(+)
create mode 100644 fs/ntfs3/lznt.c
diff --git a/fs/ntfs3/lznt.c b/fs/ntfs3/lznt.c
new file mode 100644
index ..edba9
This adds file operations and implementation
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/dir.c | 568 ++
fs/ntfs3/file.c| 1146 +++
fs/ntfs3/frecord.c | 2697
fs/ntfs3/namei.c | 576 ++
fs/ntfs3/record.c
This adds attrib operations
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/attrib.c | 1395 +++
fs/ntfs3/attrlist.c | 463 ++
fs/ntfs3/xattr.c| 1073 +
3 files changed, 2931 insertions(+)
create mode 1006
Make "cdns,max-outbound-regions" optional DT property in all the
platforms using Cadence PCIe core.
Kishon Vijay Abraham I (2):
dt-bindings: PCI: Make "cdns,max-outbound-regions" optional property
PCI: cadence: Do not error if "cdns,max-outbound-regions" is not found
Documentation/devicetree
This patch adds NTFS Read-Write driver to fs/ntfs3.
Having decades of expertise in commercial file systems development and huge
test coverage, we at Paragon Software GmbH want to make our contribution to
the Open Source Community by providing implementation of NTFS Read-Write
driver for the Linux
This adds NTFS journal
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/fslog.c | 5221 ++
1 file changed, 5221 insertions(+)
create mode 100644 fs/ntfs3/fslog.c
diff --git a/fs/ntfs3/fslog.c b/fs/ntfs3/fslog.c
new file mode 100644
index ..
This adds NTFS3 in fs/Kconfig and fs/Makefile
Signed-off-by: Konstantin Komarov
---
fs/Kconfig | 1 +
fs/Makefile | 1 +
2 files changed, 2 insertions(+)
diff --git a/fs/Kconfig b/fs/Kconfig
index aa4c12282301..eae96d55ab67 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -145,6 +145,7 @@ menu "DOS
On Thu, Nov 05, 2020 at 12:18:23PM +0100, Anders Roxell wrote:
> While trying to do 'make dtbs_install' the following error shows up
>
> make[3]: *** No rule to make target
>
> '/srv/src/kernel/next/out/obj-arm64-next-20201105/dtbsinstall/freescale/imx8mm-kontron-n801x-s.dts',
> needed by '__
Now that "cdns,max-outbound-regions" is made an optional property, do
not error out if "cdns,max-outbound-regions" device tree property is
not found.
Link: http://lore.kernel.org/r/20201105165331.GA55814@bogus
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/cadence/pcie-cadence-
This adds Kconfig, Makefile and doc
Signed-off-by: Konstantin Komarov
---
Documentation/filesystems/ntfs3.rst | 112
fs/ntfs3/Kconfig| 23 ++
fs/ntfs3/Makefile | 11 +++
3 files changed, 146 insertions(+)
create mode 10064
This adds headers and misc files
Signed-off-by: Konstantin Komarov
---
fs/ntfs3/debug.h | 61 +++
fs/ntfs3/ntfs.h| 1262
fs/ntfs3/ntfs_fs.h | 989 ++
fs/ntfs3/upcase.c | 77 +++
4 files changed, 2389 inserti
Now that the MBUS quirks are applied by our global notifier, we can
remove them from our DRM driver.
Suggested-by: Christoph Hellwig
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/sun4i_backend.c | 19 ---
1 file changed, 19 deletions(-)
diff --git a/drivers/gpu/drm/sun
So far most of the drivers with the MBUS quirks had to duplicate the
code to deal with DT compatibility and enforcing the DMA offsets.
Let's move for a more maintainable solution by putting everything in a
notifier that would take care of setting up the DMA offsets for all the
MBUS devices.
Sugge
Now that the MBUS quirks are applied by our global notifier, we can
remove them from Cedrus. Since the only quirk was whether or not we had
to apply that DMA quirk, we can also remove the quirks infrastructure.
Suggested-by: Christoph Hellwig
Signed-off-by: Maxime Ripard
---
drivers/staging/med
Now that the MBUS quirks are applied by our global notifier, we can
remove them from our CSI driver for the A10.
Suggested-by: Christoph Hellwig
Signed-off-by: Maxime Ripard
---
.../platform/sunxi/sun4i-csi/sun4i_csi.c | 27 ---
1 file changed, 27 deletions(-)
diff --git a
Commit e0d072782c73 ("dma-mapping: introduce DMA range map, supplanting
dma_pfn_offset") introduced a regression in our code since the second
backed to probe will now get -EINVAL back from dma_direct_set_offset and
will prevent the entire DRM device from probing.
Ignore -EINVAL as a temporary meas
Now that the MBUS quirks are applied by our global notifier, we can
remove them from our CSI driver for the A31.
Suggested-by: Christoph Hellwig
Signed-off-by: Maxime Ripard
---
.../media/platform/sunxi/sun6i-csi/sun6i_csi.c | 17 -
1 file changed, 17 deletions(-)
diff --git a
Hi,
Here's an attempt to removing the dma_direct_set_offset calls we have in
numerous drivers and move all those quirks into a global notifier as suggested
by Robin.
Let me know what you think,
Maxime
Maxime Ripard (7):
drm/sun4i: backend: Fix probe failure with multiple backends
soc: sunxi:
of_dma_configure is called by the core before probe gets called so this
is redundant.
Signed-off-by: Maxime Ripard
---
drivers/media/platform/sunxi/sun8i-di/sun8i-di.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/media/platform/sunxi/sun8i-di/sun8i-di.c
b/drivers/media/platfor
There is no way to remount procfs mountpoint with subset=pid option
without it. This is done in order not to make visible what was hidden
since some checks occur during mount.
This patch makes this limitation explicit and demonstrates the error.
Signed-off-by: Alexey Gladkov
---
fs/proc/root.c
Allow to mount of procfs with subset=pid option even if the entire
procfs is not fully accessible to the user.
Signed-off-by: Alexey Gladkov
---
fs/namespace.c | 27 ---
fs/proc/root.c | 17 ++---
include/linux/fs.h | 1 +
3 files changed, 27 insertio
Cache the mounters credentials and make access to the net directories
contingent of the permissions of the mounter of proc.
Show /proc/self/net only if mounter has CAP_NET_ADMIN and if proc is
mounted with subset=pid option.
Signed-off-by: Alexey Gladkov
---
fs/proc/proc_net.c | 8
If only the dynamic part of procfs is mounted (subset=pid), then there is no
need to check if procfs is fully visible to the user in the new user namespace.
Changelog
-
v4:
* Set SB_I_DYNAMIC only if pidonly is set.
* Add an error message if subset=pid is canceled during remount.
v3:
* Ad
Hi Randy,
Randy Dunlap writes:
> On 11/2/20 11:19 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20201102:
>>
>
> on x86_64:
>
> when CONFIG_BRIDGE=m:
>
> ld: drivers/net/ethernet/marvell/prestera/prestera_switchdev.o: in function
> `prestera_bridge_port_event':
> prestera_switc
On Thu, Nov 05, 2020 at 10:30:05PM -0500, Hewenliang wrote:
> From: hewenliang
>
> It is necessary to initialize the value of ident mapping offset.
Why is it necessary?
> This can not only avoid using dirty data,
What happens to designated initializers when some of the members are not
explicit
On 2020-11-02 18:12:38 [+], Christoph Hellwig wrote:
> > to not break that assumption you just mentioned and provide
> > |static inline void blk_mq_complete_request_local(struct request *rq)
> > |{
> > | rq->q->mq_ops->complete(rq);
> > |}
> >
> > so that completion issued fro
Hi Lakshmi, Tushar,
This patch defines a new critical_data builtin policy. Please update
the Subject line.
On Sun, 2020-11-01 at 14:26 -0800, Tushar Sugandhi wrote:
> From: Lakshmi Ramasubramanian
>
> The IMA hook to measure kernel critical data, namely
> ima_measure_critical_data(), could be
On Thu, Nov 05, 2020 at 05:47:21PM +, Robin Murphy wrote:
> On 2020-11-05 16:43, Thierry Reding wrote:
> > On Thu, Sep 24, 2020 at 01:27:25PM +0200, Thierry Reding wrote:
> > > On Tue, Sep 15, 2020 at 02:36:48PM +0200, Thierry Reding wrote:
> > > > On Mon, Sep 14, 2020 at 04:08:29PM -0600, Rob
On 2020-11-05 12:56, Andre Przywara wrote:
From: Ard Biesheuvel
Implement arch_get_random_seed_*() for ARM based on the firmware
or hypervisor provided entropy source described in ARM DEN0098.
This will make the kernel's random number generator consume entropy
provided by this interface, at ea
On Fri, 6 Nov 2020 at 16:30, Marc Zyngier wrote:
>
> On 2020-11-05 12:56, Andre Przywara wrote:
> > From: Ard Biesheuvel
> >
> > Implement arch_get_random_seed_*() for ARM based on the firmware
> > or hypervisor provided entropy source described in ARM DEN0098.
> >
> > This will make the kernel's
401 - 500 of 1117 matches
Mail list logo
