On Fri, 12 Feb 2021 21:13:34 +0900
William Breathitt Gray wrote:
> ERANGE is a semantically better error code to return when an argument
> value falls outside the supported limit range of a device.
#define ERANGE 34 /* Math result not representable */
Not generally applicable to
On Fri, 12 Feb 2021 21:13:42 +0900
William Breathitt Gray wrote:
> This patch adds high-level documentation about the Counter subsystem
> character device interface.
>
> Signed-off-by: William Breathitt Gray
> ---
> Documentation/driver-api/generic-counter.rst | 243 +++---
>
On Fri, Feb 12, 2021 at 01:48:36PM -0800, Dave Hansen wrote:
> On 2/12/21 1:47 PM, Andy Lutomirski wrote:
> >> What about adding a property to the TD, e.g. via a flag set during TD
> >> creation,
> >> that controls whether unaccepted accesses cause #VE or are, for all
> >> intents and
> >>
On Sun, Feb 14, 2021 at 7:19 AM Al Viro wrote:
>
> Making sendfile() to pipe destination do the right thing, should
> make "fs/pipe: allow sendfile() to pipe again" redundant. Sat in -next
> for 3 weeks...
Just to clarify: this says "fixes", but I get the feeling that you
meant for me
On 14/02/2021 19:00, Linus Torvalds wrote:
> On Sun, Feb 14, 2021 at 10:42 AM Ramsay Jones
> wrote:
>>
>>>
>>> I looked around but didn't find any hints how to fix this. Any pointers
>>> I missed (added the sparse list to cc:)?
>>
>> This is a limitation of sparse; when using the 'stringize'
Replace of_drm_find_panel with drm_of_find_panel_or_bridge
for finding panel, this indeed help to find the bridge if
bridge support added.
Added NULL in bridge argument, same will replace with bridge
parameter once bridge supported.
Signed-off-by: Jagan Teki
---
Changes for v3:
- none
This series convert Allwinner DSI controller to full functional
drm bridge driver for supporting slave panel, bridges.
Here, are the previous version changes[1].
The key concern about these changes is about kms hotplug which
indeed not compatible with bridge conversion. However, I did
try
Some display panels would come up with a non-DSI output which
can have an option to connect DSI interface by means of bridge
converter.
This DSI to non-DSI bridge converter would require a bridge
driver that would communicate the DSI controller for bridge
functionalities.
So, add support for
DRM bridge drivers have build-in handling of treating all display
pipeline components as bridges.
So, convert the existing to a drm bridge driver with a built-in
encoder support for compatibility with existing component drivers.
Signed-off-by: Jagan Teki
---
Changes for v3:
- new patch
The pull request you sent on Sun, 14 Feb 2021 18:13:28 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/
> for-rc8-5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/28a17338738839494752c5da3e12c889a55219db
Thank you!
--
Deet-doot-dot,
The pull request you sent on Mon, 15 Feb 2021 02:02:19 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-fixes-v5.11-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ab30c7f9c3ca2599f5ab3e4d29ae56453c8668e5
Thank you!
Hi all,
On Mon, 25 Jan 2021 16:32:55 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the pidfd tree got a conflict in:
>
> fs/f2fs/acl.c
>
> between commit:
>
> 7cf2e6173b2d ("f2fs: enhance to update i_mode and acl atomically in
> f2fs_setattr()")
>
> from the f2fs tree
The pull request you sent on Sun, 14 Feb 2021 11:34:14 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> tags/x86_urgent_for_v5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c553021498640050340924bd62fa580e253467ac
Thank you!
--
Hi all,
On Mon, 25 Jan 2021 09:12:56 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the risc-v tree got conflicts in:
>
> drivers/soc/Kconfig
> drivers/soc/Makefile
>
> between commit:
>
> 89d4f98ae90d ("ARM: remove zte zx platform")
>
> from the arm-soc tree and
Hi all,
On Mon, 25 Jan 2021 17:18:18 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the pidfd tree got a conflict in:
>
> security/integrity/ima/ima_api.c
>
> between commit:
>
> 2b4a2474a202 ("IMA: generalize keyring specific measurement constructs")
>
> from the
Hi all,
On Mon, 25 Jan 2021 11:12:23 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> net/ipv4/tcp.c
>
> between commit:
>
> 7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.")
>
> from the net-next tree and
On Sat, Feb 13, 2021 at 10:54 AM Guenter Roeck wrote:
>
> Hi,
>
> On Thu, Jan 21, 2021 at 02:57:12PM -0800, Saravana Kannan wrote:
> > This allows fw_devlink to create device links between consumers of an
> > interrupt and the supplier of the interrupt.
> >
> > Cc: Marc Zyngier
> > Cc: Kevin
Hi Juergen,
On 11/02/2021 10:16, Juergen Gross wrote:
When creating a new event channel with 2-level events the affinity
needs to be reset initially in order to avoid using an old affinity
from earlier usage of the event channel port. So when tearing an event
channel down reset all affinity
On Sun, Feb 14, 2021 at 11:35:36AM -0800, Linus Torvalds wrote:
> Just to clarify: this says "fixes", but I get the feeling that you
> meant for me to pull tomorrow in the 5.12 merge window?
>
> I like the patches, but they don't seem to be anything hugely urgent.
> They should make "sendfile to
There are places in the camss driver where camss_get_pixel_clock() is
called to get the pixel rate (using V4L2_CID_PIXEL_RATE control) and to
calculate the link frequency from it. There is a case when this would
not work: when V4L2_CID_PIXEL_RATE gets the rate at which the pixels are
read
From: Vladimir Lypak
Because of u32 type being used to store pixel clock rate, expression used
to calculate pipeline clocks (pixel_clock * bpp) produces wrong value due
to integer overflow. This patch changes data type used to store, pass and
retrieve pixel_clock from u32 to u64 to make this
Hi Juergen,
On 11/02/2021 10:16, Juergen Gross wrote:
When changing the cpu affinity of an event it can happen today that
(with some unlucky timing) the same event will be handled on the old
and the new cpu at the same time.
Avoid that by adding an "event active" flag to the per-event data and
The first patch is the start of the work discussed in the "[RFC] Repurpose
V4L2_CID_PIXEL_RATE for the sampling rate in the pixel array" thread [1].
I plan to send a few other similar patches for other CSI receiver drivers,
and if the current patchset needs to wait for those before it can be
Hi all,
On Tue, 2 Feb 2021 09:01:35 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the arm-soc tree got a conflict in:
>
> arch/arm/Kconfig.debug
>
> between commits:
>
> 9ca4efec0aba ("ARM: 9040/1: use DEBUG_UART_PHYS and DEBUG_UART_VIRT for sti
> LL_UART")
>
Hi all,
On Thu, 4 Feb 2021 15:58:46 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the drivers-x86 tree got a conflict in:
>
> drivers/gpu/drm/gma500/Kconfig
> drivers/gpu/drm/gma500/mdfld_device.c
> drivers/gpu/drm/gma500/mdfld_dsi_output.c
>
On Fri, 12 Feb 2021 21:13:37 +0900
William Breathitt Gray wrote:
> This is a reimplementation of the Generic Counter driver interface.
> There are no modifications to the Counter subsystem userspace interface,
> so existing userspace applications should continue to run seamlessly.
>
> The
SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge
controller IC's from Texas Instruments.
SN65DSI83 - Single Channel DSI to Single-link LVDS bridge
SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge
SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge
Right now the bridge driver is
On 2/12/21 2:23 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/hddl_device/Kconfig
> b/drivers/misc/hddl_device/Kconfig
> index e1ae81fdf177..7f9a6a685275 100644
> --- a/drivers/misc/hddl_device/Kconfig
> +++ b/drivers/misc/hddl_device/Kconfig
> @@ -12,3 +12,15 @@ config
On Fri, Jan 29, 2021 at 01:18:55PM +, Christoph Hellwig wrote:
> On Fri, Jan 29, 2021 at 04:11:05PM +0300, Denis Kirjanov wrote:
> > Do you mean just:
>
> We'll still need to lock the parent inode.
Not just "lock", we wouldd need to have the lock _held_ across the
entire sequence. Without
On Fri, 12 Feb 2021 21:13:46 +0900
William Breathitt Gray wrote:
> The LSI/CSI LS7266R1 chip provides programmable output via the FLG pins.
> When interrupts are enabled on the ACCES 104-QUAD-8, they occur whenever
> FLG1 is active. Four functions are available for the FLG1 signal: Carry,
>
On Sun, Feb 14, 2021 at 11:33 AM Andi Kleen wrote:
>
> On Fri, Feb 12, 2021 at 01:48:36PM -0800, Dave Hansen wrote:
> > On 2/12/21 1:47 PM, Andy Lutomirski wrote:
> > >> What about adding a property to the TD, e.g. via a flag set during TD
> > >> creation,
> > >> that controls whether unaccepted
Am 2021-02-14 03:24, schrieb Vladimir Oltean:
On Sun, Feb 14, 2021 at 03:18:49AM +0100, Michael Walle wrote:
Am 14. Februar 2021 02:57:33 MEZ schrieb Vladimir Oltean
:
>Hi Michael,
>
>On Sun, Feb 14, 2021 at 02:04:05AM +0100, Michael Walle wrote:
>> at803x_aneg_done() checks if
Hi all,
On Tue, 19 Jan 2021 10:45:36 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the hid tree got a conflict in:
>
> arch/arm64/configs/defconfig
>
> between commit:
>
> 74b87103b3d0 ("arm64: defconfig: Enable HID multitouch")
>
> from the qcom tree and commit:
>
>
On 2021-02-12 13:49, Miquel Raynal wrote:
Hello,
mda...@codeaurora.org wrote on Fri, 12 Feb 2021 01:00:47 +0530:
On 2021-02-11 19:37, Miquel Raynal wrote:
> Hello,
>
> Manivannan Sadhasivam wrote on Wed,
> 10 Feb 2021 14:31:44 +0530:
>
>> On Fri, Jan 29, 2021 at 03:09:19AM +0530, Md Sadre
On Sun, Feb 14, 2021 at 01:00:42PM -0800, Stephen Boyd wrote:
> Quoting Andrew Lunn (2021-02-13 08:04:34)
> > > I'm trying to see if we can make lives better for everyone by exposing
> > > the warnings by default in the drivers/clk/ directory now that there are
> > > supposedly none left.
Hi all,
On Wed, 27 Jan 2021 22:43:51 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> fs/hugetlbfs/inode.c
>
> between commit:
>
> 2f221d6f7b88 ("attr: handle idmapped mounts")
>
> from the pidfd tree and commit:
>
>
Hi all,
On Mon, 8 Feb 2021 23:37:16 +1100 Stephen Rothwell
wrote:
>
> After merging the v4l-dvb tree, today's linux-next build (htmldocs)
> produced this warning:
>
> include/media/v4l2-async.h:178: warning: expecting prototype for
> v4l2_async_notifier_add_fwnode_subdev(). Prototype was for
Nothing unexpected or particularly scary happened this week, so here
we are - with 5.11 tagged and pushed out.
In fact, it's a smaller-than-average set of commits from rc7 to final,
which makes me happy. And I already have several pull requests lined
up for tomorrow, so we're all set for the
On Thu, Feb 11, 2021 at 06:52:36PM -0800, Randy Dunlap wrote:
> >>> arch/alpha/lib/csum_partial_copy.c:328:1: error: no previous prototype
> >>> for 'csum_and_copy_from_user' [-Werror=missing-prototypes]
> > 328 | csum_and_copy_from_user(const void __user *src, void *dst, int
> > len,
> >
Hi Arjun,
On Sun, 14 Feb 2021 13:40:38 -0800 Arjun Roy wrote:
>
> Sorry, I was confused from the prior email. Is any action required at
> the moment, or not?
No. This is just something that the net-next and bpf-next maintainers
need to sort out when they merge their trees.
--
Cheers,
Stephen
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 358feceebbf68f33c44c6650d14455389e65282d
commit: 5fe6b98ae00dc2e0ac24ef8a45d828b82a4aae90 drm/amd/display: Update dmub
code
date: 3 months ago
config: i386-randconfig-a014-20200624 (attached as .config)
On Fri, Feb 12, 2021 at 12:43:59PM +0800, Nicolas Boichat wrote:
> We hit an issue when upgrading Go compiler from 1.13 to 1.15 [1],
> as we use Go's `io.Copy` to copy the content of
> `/sys/kernel/debug/tracing/trace` to a temporary file.
>
> Under the hood, Go 1.15 uses `copy_file_range`
On 21-02-14 16:30:09, Al Viro wrote:
> On Tue, Feb 09, 2021 at 04:02:55PM -0800, Ben Widawsky wrote:
>
> > +static int handle_mailbox_cmd_from_user(struct cxl_memdev *cxlmd,
> > + const struct cxl_mem_command *cmd,
> > + u64
On Sun, Feb 14, 2021 at 07:49:22PM +0800, Stephen Zhang wrote:
> Masahiro Yamada 于2021年2月13日周六 下午8:46写道：
> > This is the steps I tested.
> >
> >
> > masahiro@oscar:~/ref/linux$ make O=build defconfig all -j24
> > [ snip ]
> > masahiro@oscar:~/ref/linux$
> >
Hi Sameer
> > /*
> > * Parse dai->sysclk come from "clocks = <>"
> > * (if system has common clock)
> > * or "system-clock-frequency = "
> > * or device's module clock.
> > */
>
> Yes, this can be rephrased now.
Thanks.
It is not a
Lontium Lt8912 is a DSI to HDMI bridge.
Signed-off-by: Adrien Grassein
---
MAINTAINERS | 1 +
drivers/gpu/drm/bridge/Kconfig | 14 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/lontium-lt8912.c | 719
4
Lontium LT8912 is a DSI to HDMI bridge.
Signed-off-by: Adrien Grassein
---
.../display/bridge/lontium,lt8912.yaml| 102 ++
MAINTAINERS | 5 +
2 files changed, 107 insertions(+)
create mode 100644
Hello,
this patch set adds the support of the Lontium lt8912 MIPI to HDMI
bridge in the kernel.
It's only support the video part, not the audio part yet
since I don't have the datasheet of this component.
I get the current i2c configuration from Digi and
Boundary drivers.
Developed using the
On Mon, Feb 15, 2021 at 09:41:31AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 8 Feb 2021 10:33:48 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the xfs tree got a conflict in:
> >
> > fs/xfs/xfs_ioctl.c
> >
> > between commit:
> >
> > f736d93d76d3 ("xfs:
idt77252 is broken and wont load on amd64 systems
modprobe idt77252 shows the following
idt77252_init: skb->cb is too small (48 < 56)
Add packed attribute to struct idt77252_skb_prv and struct atm_skb_data
so that the total size can be <= sizeof(skb->cb)
Also convert runtime size
On Sun, Feb 14, 2021 at 03:14:56PM -0800, Ben Widawsky wrote:
> On 21-02-14 16:30:09, Al Viro wrote:
> > On Tue, Feb 09, 2021 at 04:02:55PM -0800, Ben Widawsky wrote:
> >
> > > +static int handle_mailbox_cmd_from_user(struct cxl_memdev *cxlmd,
> > > + const struct
> According to Errata #23 "The per-CPU GbE interrupt is limited to Core
> 0", we can't use the per-cpu interrupt mechanism on the Armada 3700
> familly.
>
> This is correctly checked for RSS configuration, but the initial queue
> mapping is still done by having the queues spread across all the
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 358feceebbf68f33c44c6650d14455389e65282d
commit: 8d58f222e85f01da0c0e1fc1e77986c86de889e2 ubsan: disable UBSAN_ALIGNMENT
under COMPILE_TEST
date: 9 months ago
config: s390-randconfig-r014-20210215
On Sun, Feb 14, 2021 at 11:50:12PM +, Al Viro wrote:
> check that len is reasonable
> p = kmalloc(offsetof(struct foo, string[len]), GFP_KERNEL);
> copy_from_user(p, user_object, len);
offsetof(struct foo, string[len]), that is
optoe is an i2c based driver that supports read/write access to all
the pages (tables) of MSA standard SFP and similar devices (conforming
to the SFF-8472 spec), MSA standard QSFP and similar devices (conforming
to the SFF-8636 spec) and CMIS and similar devices (conforming to the
Common
On Thu, Jan 28, 2021 at 9:52 AM Masahiro Yamada wrote:
>
> These are NOT exported to userspace.
>
> The headers listed in arch/sparc/include/uapi/asm/Kbuild are exported.
>
> Signed-off-by: Masahiro Yamada
Applied to linux-kbuild/fixes.
> ---
>
> arch/sparc/include/asm/Kbuild | 2 --
> 1
On Sun, Feb 14, 2021 at 8:49 PM Stephen Zhang wrote:
>
> Masahiro Yamada 于2021年2月13日周六 下午8:46写道：
> > This is the steps I tested.
> >
> >
> > masahiro@oscar:~/ref/linux$ make O=build defconfig all -j24
> > [ snip ]
> > masahiro@oscar:~/ref/linux$
> >
On 2/12/21 2:22 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/vpumgr/Kconfig b/drivers/misc/vpumgr/Kconfig
> new file mode 100644
> index ..bb82ff83afd3
> --- /dev/null
> +++ b/drivers/misc/vpumgr/Kconfig
> @@ -0,0 +1,9 @@
> +config VPUMGR
> + tristate "VPU Manager"
On 2/12/21 2:22 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/intel_tsens/Kconfig
> b/drivers/misc/intel_tsens/Kconfig
> index 8b263fdd80c3..be8d27e81864 100644
> --- a/drivers/misc/intel_tsens/Kconfig
> +++ b/drivers/misc/intel_tsens/Kconfig
> @@ -14,6 +14,20 @@ config
SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge
controller IC's from Texas Instruments.
SN65DSI83 - Single Channel DSI to Single-link LVDS bridge
SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge
SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge
Driver is adding bridge
On 2/12/21 2:22 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/intel_tsens/Kconfig
> b/drivers/misc/intel_tsens/Kconfig
> index bfb8fe1997f4..8b263fdd80c3 100644
> --- a/drivers/misc/intel_tsens/Kconfig
> +++ b/drivers/misc/intel_tsens/Kconfig
> @@ -13,3 +13,16 @@ config
On 2/12/21 2:23 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/hddl_device/Kconfig
> b/drivers/misc/hddl_device/Kconfig
> new file mode 100644
> index ..e1ae81fdf177
> --- /dev/null
> +++ b/drivers/misc/hddl_device/Kconfig
> @@ -0,0 +1,14 @@
> +# Copyright (C) 2020
Hi Casey,
On Tue, 2021-01-26 at 08:40 -0800, Casey Schaufler wrote:
> Integrity measurement may filter on security module information
> and needs to be clear in the case of multiple active security
> modules which applies. Provide a boot option ima_rules_lsm= to
> allow the user to specify an
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 358feceebbf68f33c44c6650d14455389e65282d
commit: 1465af12e254a68706e110846f59cf0f09683184 btrfs: tree-checker: fix false
alert caused by legacy btrfs root item
date: 4 months ago
config:
On Sun, 2021-02-14 at 10:58 +0100, David Hildenbrand wrote:
[...]
> > And here we come to the question "what are the differences that
> > justify a new system call?" and the answer to this is very
> > subjective. And as such we can continue bikeshedding forever.
>
> I think this fits into the
Hi all,
On Mon, 18 Jan 2021 15:08:04 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> include/asm-generic/vmlinux.lds.h
>
> between commits:
>
> 9a427556fb8e ("vmlinux.lds.hf41b233de0ae: catch compound literals into data
> and BSS")
>
Quoting Daniel Palmer (2021-02-10 21:22:03)
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 85856cff506c..a29c15444d0e 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -379,6 +379,7 @@ source "drivers/clk/ingenic/Kconfig"
> source "drivers/clk/keystone/Kconfig"
Hi all,
On Wed, 27 Jan 2021 10:00:38 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the fscache tree got a conflict in:
>
> include/linux/fs.h
>
> between commit:
>
> ba73d98745be ("namei: handle idmapped mounts in may_*() helpers")
>
> from the pidfd tree and commit:
>
>From QPIC version 2.0 onwards new register got added to
read last codeword. This change will add the READ_LOCATION_LAST_CW_n
register.
For first three code word READ_LOCATION_n register will be
use.For last code word READ_LOCATION_LAST_CW_n register will be
use.
Signed-off-by: Md Sadre Alam
Hi all,
On Thu, 28 Jan 2021 16:56:11 +1100 Stephen Rothwell
wrote:
>
> On Mon, 25 Jan 2021 15:02:13 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the scsi-mkp tree got a conflict in:
> >
> > drivers/scsi/gdth.c
> >
> > between commit:
> >
> > 537896fabed1
we should check for valid resident atribute offset and length before
loading STANDARD_INFORMATION attribute in ntfs_read_locked_inode()
let's make that check a bit earlier in the same function to avoid
use-after-free bug
Reported-and-tested-by:
Hi all,
On Mon, 1 Feb 2021 14:42:59 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the irqchip tree got a conflict in:
>
>
> Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
>
> between commit:
>
> 752b0aac99c7 ("dt-bindings: irq:
On Mon, Aug 10, 2020 at 5:30 PM Geert Uytterhoeven wrote:
>
> Hi Sedat,
>
> On Tue, Jul 21, 2020 at 10:19 AM Sedat Dilek wrote:
> > You happen to know if I can configure in my ~/.gitconfig to pull
> > linux-git stuff from two repositories - check first git.kernel.org
> > then GitHub.
> >
> >
Hi all,
On Mon, 8 Feb 2021 10:33:48 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the xfs tree got a conflict in:
>
> fs/xfs/xfs_ioctl.c
>
> between commit:
>
> f736d93d76d3 ("xfs: support idmapped mounts")
>
> from the pidfd tree and commit:
>
> 7317a03df703 ("xfs:
Linus Torvalds wrote:
> But no, it's not a replacement for actual code review after the fact.
>
> If you think email has too long latency for review, and can't use
> public mailing lists and cc the people who are maintainers, then I
> simply don't want your patches.
I think we were talking at
On Fri, Feb 12, 2021 at 03:54:48PM -0800, Darrick J. Wong wrote:
> On Sat, Feb 13, 2021 at 10:27:26AM +1100, Dave Chinner wrote:
> > On Fri, Feb 12, 2021 at 03:07:39PM -0800, Ian Lance Taylor wrote:
> > > On Fri, Feb 12, 2021 at 3:03 PM Dave Chinner wrote:
> > > >
> > > > On Fri, Feb 12, 2021 at
> > Does this even need to be configurable? What is the cost of turning it on?
> > How does having less pools affect the system? Does average latency go up?
> > When would i consider an underrun actually a good thing?
> >
> > Maybe it should just be hard coded on? Or we should try to detect when
Hi all,
After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
In file included from drivers/gpu/drm/gma500/mdfld_output.c:28:
arch/x86/include/asm/intel_scu_ipc.h:23:12: warning: 'struct module' declared
inside parameter list will not be visible
On Fri, 12 Feb 2021 12:20:21 +0200
Alexandru Ardelean wrote:
> From: Lars-Peter Clausen
>
> This change adds support for cyclic DMA transfers using the IIO buffer DMA
> infrastructure.
> To do this, userspace must set the IIO_BUFFER_BLOCK_FLAG_CYCLIC flag on the
> block when enqueueing them
On Fri, 12 Feb 2021 21:13:25 +0900
William Breathitt Gray wrote:
> Duplicate ABIs are not valid, so let's consolidate these sysfs
> attributes into the main sysfs-bus-counter documentation file.
This is sensible to do, but is there any duplicate ABI? I went
looking for any resulting build
On Sat, 2021-02-13 at 18:45 +0530, Dwaipayan Ray wrote:
> Add documentation for kernel script checkpatch.pl.
> This documentation is also parsed by checkpatch to
> enable a verbose mode.
>
> The message types in checkpatch are documented with rst
> field lists. A total of 33 checkpatch type
Hi ,
On Sat, Feb 13, 2021 at 11:12:37AM +0800, kernel test robot wrote:
> Hi "Guido,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on usb/usb-testing]
> [also build test WARNING on v5.11-rc7 next-20210211]
> [If your patch is applied to the wrong git tree,
On Fri, 12 Feb 2021 21:13:33 +0900
William Breathitt Gray wrote:
> Only a select set of modes (function, action, etc.) are valid for a
> given device configuration. This patch ensures that invalid modes result
> in a return -EINVAL. Such a situation should never occur in reality, but
> it's good
Linus,
I am sending an early pull request with the material that does not depend
on any bare metal changes, especially since ARM64 and PPC submaintainers
have already sent their stuff to me.
The following changes since commit 87aa9ec939ec7277b730786e19c161c9194cc8ca:
KVM: x86/mmu: Fix TDP MMU
On Fri, Feb 12, 2021 at 10:56:19AM +0100, David Hildenbrand wrote:
> On 12.02.21 10:55, David Hildenbrand wrote:
> > On 08.02.21 12:08, Mike Rapoport wrote:
> > > +#ifdef CONFIG_SPARSEMEM
> > > + /*
> > > + * Sections in the memory map may not match actual populated
> > > + * memory, extend the
On 2/12/21 2:23 PM, mgr...@linux.intel.com wrote:
> diff --git a/drivers/misc/intel_tsens/Kconfig
> b/drivers/misc/intel_tsens/Kconfig
> index be8d27e81864..5cfe6b4004e5 100644
> --- a/drivers/misc/intel_tsens/Kconfig
> +++ b/drivers/misc/intel_tsens/Kconfig
> @@ -28,6 +28,18 @@ config
On Fri, Feb 12, 2021 at 02:18:20PM +0100, Michal Hocko wrote:
> On Fri 12-02-21 11:42:15, David Hildenbrand wrote:
> > On 12.02.21 11:33, Michal Hocko wrote:
> [...]
> > > I have to digest this but my first impression is that this is more heavy
> > > weight than it needs to. Pfn walkers should
drivers/staging/hikey9xx/hi6421-spmi-pmic.c:51: WARNING: please, no space
before tabs
drivers/staging/hikey9xx/hi6421-spmi-pmic.c:52: WARNING: please, no space
before tabs
drivers/staging/hikey9xx/hi6421-spmi-pmic.c:53: WARNING: please, no space
before tabs
Dne 14. 02. 21 v 7:43 Perry Yuan napsal(a):
>>> @@ -287,6 +291,18 @@ static int rt715_sdca_put_volsw(struct snd_kcontrol
>>> *kcontrol,
>>> return err;
>>> }
>>>
>>> +#if IS_ENABLED(CONFIG_DELL_PRIVACY)
>>> + /* dell privacy LED trigger state changed by muted/unmute
On Sun, Feb 14, 2021 at 10:42 AM Ramsay Jones
wrote:
>
> >
> > I looked around but didn't find any hints how to fix this. Any pointers
> > I missed (added the sparse list to cc:)?
>
> This is a limitation of sparse; when using the 'stringize' pre-processor
> operator #, the maximum size of the
drm_bridge_attach has stacked the bridge chain, so the bridge
that gets pushed last can trigger its bridge function pre_enable
first from drm_atomic_bridge_chain_pre_enable.
This indeed gives a chance to trigger slave bridge pre_enable
first without triggering its host bridge pre_enable for the
On Mon, Jan 25, 2021 at 10:01:48PM +0530, Naresh Kamboju wrote:
> commit 8a3cc755b13808eba74846dfd1033fcbc21f9a65
> Author: Al Viro
> Date: Sun Mar 8 09:16:37 2020 -0400
>
> coredump: don't bother with do_truncate()
>
> have dump_skip() just remember how much needs to be skipped,
>
Enable 100Mhz and 200MHz pinmux and corrsesponding voltage supplies
to enable SDR104 on usdhc1 connecting the WiFi chip.
Signed-off-by: Adam Ford
diff --git a/arch/arm64/boot/dts/freescale/imx8mn-beacon-som.dtsi
b/arch/arm64/boot/dts/freescale/imx8mn-beacon-som.dtsi
index
Quoting Daniel Palmer (2021-02-10 21:22:00)
> Simple header to document the relationship between the MPLL outputs
> and which divider they come from.
>
> Output 0 is missing because it should not be consumed.
>
> Signed-off-by: Daniel Palmer
> Acked-by: Rob Herring
> ---
Applied to clk-next
Quoting Daniel Palmer (2021-02-10 21:22:03)
> This adds a basic driver for the MPLL block found in MStar/SigmaStar
> ARMv7 SoCs.
>
> Currently this driver is only good for calculating the rates of it's
> outputs and the actual configuration must be done before the kernel
> boots. Usually this is
Quoting Daniel Palmer (2021-02-10 21:22:02)
> Add a devm helper for clk_hw_register_fixed_factor() so that drivers that
> internally
> register fixed factor clocks for things like dividers don't need to manually
> unregister
> them on remove or if probe fails.
>
> Signed-off-by: Daniel Palmer
On Sun, 14 Feb 2021 04:00:31 +0800, kernel test robot said:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: dcc0b49040c70ad827a7f3d58a21b01fdb14e749
> commit: 67a5a68013056cbcf0a647e36cb6f4622fb6a470 gcc-plugins: fix gcc 11
> indigestion with
Hi!
> > Unfortunately, for some reason request-pull is not willing to
> > cooperate, so I'm just doing this manually.
>
> The reason request-pull doesn't cooperate is actually spelled out explicitly:
>
> > pavel@duo:/data/l/linux-leds$ git request-pull master
> >
Quoting Daniel Palmer (2021-02-10 21:22:01)
> Add a binding description for the MStar/SigmaStar MPLL clock block.
>
> Signed-off-by: Daniel Palmer
> ---
Applied to clk-next
Hi all,
On Mon, 11 Jan 2021 13:08:51 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the char-misc tree got conflicts in:
>
> include/linux/mod_devicetable.h
> scripts/mod/devicetable-offsets.c
> scripts/mod/file2alias.c
>
> between commit:
>
> eb0e90a82098
1 - 100 of 306 matches
Mail list logo
