Re: linux-next: manual merge of the fscache tree with the pidfd tree

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") &

Re: linux-next: manual merge of the bpf-next tree with the net-next tree

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.&

Re: linux-next: manual merge of the risc-v tree with the arm-soc tree

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 platf

Re: linux-next: manual merge of the pidfd tree with the integrity tree

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 measu

Re: linux-next: manual merge of the pidfd tree with the vfs tree

Hi all, On Mon, 25 Jan 2021 17:00:54 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/namei.c > > between commit: > > e36cffed20a3 ("fs: make unlazy_walk() error handling consistent") > 1e

Re: linux-next: manual merge of the pidfd tree with the f2fs tree

Hi all, On Mon, 25 Jan 2021 16:48:06 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/f2fs/file.c > > between commits: > > 19bb7075d1a9 ("f2fs: fix out-of-repair __setattr_copy()") > 7cf2e617

Re: linux-next: manual merge of the pidfd tree with the f2fs tree

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_set

Re: linux-next: manual merge of the pidfd tree with the vfs tree

Hi all, On Mon, 25 Jan 2021 16:17:06 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/coredump.c > > between commit: > > 8a3cc755b138 ("coredump: don't bother with do_truncate()")

Re: linux-next: manual merge of the devicetree tree with the net-next tree

Hi all, On Thu, 21 Jan 2021 13:26:45 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the devicetree tree got a conflict in: > > Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.yaml > > between commit: > > 19d9a846d9fc ("dt-binding

Re: linux-next: manual merge of the hid tree with the qcom tree

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")

Re: linux-next: manual merge of the kspp tree with the mips tree

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

Re: linux-next: manual merge of the char-misc tree with the drivers-x86 tree

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: >

Re: linux-next: manual merge of the rcu tree with the block tree

Hi all, On Fri, 12 Feb 2021 08:30:27 -0700 Jens Axboe wrote: > > On 2/12/21 8:18 AM, Frederic Weisbecker wrote: > > On Thu, Feb 11, 2021 at 04:48:52PM +1100, Stephen Rothwell wrote: > >> Hi all, > >> > >> Today's linux-next merge of the rcu tree got

Re: linux-next: manual merge of the spi tree with the powerpc tree

Hi Mark, On Fri, 12 Feb 2021 12:27:59 + Mark Brown wrote: > > On Fri, Feb 12, 2021 at 03:31:42PM +1100, Stephen Rothwell wrote: > > > BTW Mark: the author's address in 258ea99fe25a uses a non existent domain > > :-( > > Ugh, I think that's something gone wrong

linux-next: Tree for Feb 12

rs/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (c05263df6c1a Merge tag 'gpio-fixe

linux-next: manual merge of the akpm-current tree with the fscache tree

consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc include/linux/pagemap.h index d2786607d297,20225b067583.. --- a/include/linux/pagemap.h +++ b/include/linux/pagemap.h @@@ -758,11 -75

linux-next: manual merge of the spi tree with the powerpc tree

consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. BTW Mark: the author's address in 258ea99fe25a uses a non existent domain :-( -- Cheers, Stephen Rothwell diff --cc drivers/spi/spi-mpc52xx.c index e6a30f232370,36f941500676.. --- a/drive

Re: linux-next: manual merge of the btrfs tree with the fscache tree

Hi Ira, On Thu, 11 Feb 2021 17:07:41 -0800 Ira Weiny wrote: > > On Fri, Feb 12, 2021 at 10:38:10AM +1100, Stephen Rothwell wrote: > > from the fscache tree and commit: > > > > 325a835476e3 ("iov_iter: Remove memzero_page() in favor of zero_user()") >

linux-next: manual merge of the net-next tree with the net tree

be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc include/uapi/linux/pkt_cls.h i

linux-next: manual merge of the btrfs tree with the fscache tree

with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc lib/iov_iter.c index 24413884b5ca,aa0d03b33a1e.. --- a/lib/iov_iter.c +++ b/lib/iov_iter.c @@@ -1048,9 -961,8 +1028,9 @@@ size_t iov_iter_zero(size_t bytes, stru

linux-next: Fixes tag needs some work in the ftrace tree

more than one line. Also, keep all the commit message tags together at the end of the message. -- Cheers, Stephen Rothwell pgpaYaXQ5y8kP.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 11

builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (291009f656e8 Merge tag 'pm-5.11-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm) Merging fixes/fixes (e71ba9452f0b Lin

linux-next: manual merge of the akpm-current tree with the fscache tree

fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts.

linux-next: manual merge of the rcu tree with the block tree

ainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc include/linux/rcupdate.h index 36c2119de702,fa819f878cb1.. -

linux-next: build failure after merge of the device-mapper tree

is guarded by CONFIG_BLK_DEV_ZONED. I have used the device-mapper tree from next-20210210 for today. -- Cheers, Stephen Rothwell pgpXPwd6I4dBp.pgp Description: OpenPGP digital signature

Re: [PATCH] of: irq: Fix the return value for of_irq_parse_one() stub

ceeded and the out_irq > pointer was filled with valid data. So, fix it to return an error value. > > Fixes: 1852ebd13542 ("of: irq: make a stub for of_irq_parse_one()") > Signed-off-by: Saravana Kannan Oops, sorry about that. Acked-by: Stephen Rothwell -- Cheers, Step

Re: linux-next: build failure after merge of the modules tree

a followup patch set per architecture when we know it works. -- Cheers, Stephen Rothwell pgpWNMgqkFzCv.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 10

my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Ste

Re: linux-next: build failure after merge of the powerpc tree

uct pt_regs *regs); > \ > \ > -__visible noinstr long func(struct pt_regs *regs)\ > +__visible ppc_noinstr long func(struct pt_regs *regs) > \ > {

linux-next: build failure after merge of the driver-core tree

vlink handling of interrupts/interrupts-extended") CONFIG_OF_IRQ depends on !SPARC so of_irq_parse_one() needs a stub. I have added the following patch for today. From: Stephen Rothwell Date: Wed, 10 Feb 2021 21:27:56 +1100 Subject: [PATCH] of: irq: make a stub for of_irq_parse_one()

linux-next: build warning after merge of the rdma tree

'port' not described in 'ib_port_immutable_read' Introduced by commit 7416790e2245 ("RDMA/core: Introduce and use API to read port immutable data") -- Cheers, Stephen Rothwell pgpwuShHZSpJp.pgp Description: OpenPGP digital signature

linux-next: build failure after merge of the iomem-mmap-vs-gup tree

modules") from the kvm tree. I have applied the following merge fix patch for today. From: Stephen Rothwell Date: Wed, 10 Feb 2021 20:29:22 +1100 Subject: [PATCH] mm: fixup for follow_pte() API change Signed-off-by: Stephen Rothwell --- mm/memory.c | 4 ++-- 1 file changed, 2 insert

Re: linux-next: qemu boot failure after merge of the tip tree

Hi Peter, On Mon, 1 Feb 2021 15:40:12 +0100 Peter Zijlstra wrote: > > On Mon, Feb 01, 2021 at 01:04:30PM +, Valentin Schneider wrote: > > On 01/02/21 20:09, Stephen Rothwell wrote: > > > Hi all, > > > > > > > Hi Stephen, > > > >

linux-next: build failure after merge of the drm-misc tree

for 'v3d_cache_clean_sched_ops.timedout_job') Caused by commit c10983e14e8f ("drm/scheduler: Job timeout handler returns status (v3)") I have used the drm-misc tree from next-20210209 for today. -- Cheers, Stephen Rothwell pgpgF7aCAHo1q.pgp Description: OpenPGP digital signature

linux-next: manual merge of the rdma tree with Linus' tree

o want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/infiniband/sw/rxe/rxe_net.c index 943914c2a50c,36d56163afac.. --- a/drivers/infiniband/sw/rxe/rxe_net.c +++ b/drive

linux-next: build failure after merge of the v4l-dvb tree

tree from next-20210209 for today. -- Cheers, Stephen Rothwell pgpMGzEs9n9ZT.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the arm-soc tree

Hi all, Commit 70ba3b1adbf5 ("arm64: defconfig: Enable RT5659") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpMjyQjBZ9rf.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the modules tree

entry > point > of the function "FN". > > I guess the presence of the extra dot symbols is confusing > scripts/gen_autoksyms.sh, so we get the dot symbols in autoksyms.h, which the > preprocessor doesn't like. I am wondering how this was never caught until now &g

linux-next: Signed-off-by missing for commit in the extcon tree

Hi all, Commit d8cc19be483a ("extcon: sm5502: Detect OTG when USB_ID is connected to ground") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpO1FP256sZo.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the clk tree

Hi all, Commits af5782442538 ("clk: meson: axg: Remove MIPI enable clock gate") 001cad0d3a15 ("clk: meson-axg: remove CLKID_MIPI_ENABLE") are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell pgpqfUHcilhGb.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 9

anks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (e0756cfc7d7c Merge tag 'trace-v5.11-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git

linux-next: build failure after merge of the powerpc tree

`unknown_exception' defined in .opd section in arch/powerpc/kernel/traps.o Not sure exactly which commit caused this, but it is most likkely part of a series in the powerpc tree. I have left the allyesconfig build broken for today. -- Cheers, Stephen Rothwell pgp1Ii7jqncWm.pgp Description: OpenPGP

linux-next: build failure after merge of the modules tree

;module: remove EXPORT_UNUSED_SYMBOL*") I have reverted that commit for today. -- Cheers, Stephen Rothwell pgp7solICn3f4.pgp Description: OpenPGP digital signature

linux-next: build warning after merge of the kvm tree

r Xen hypercall and shared_info updates") -- Cheers, Stephen Rothwell pgpo6unKR68dw.pgp Description: OpenPGP digital signature

Re: mmotm 2021-02-08-15-44 uploaded (drivers/media/i2c/rdacm2*.c)

vious export was in > drivers/media/i2c/rdacm20-camera_module.ko > WARNING: modpost: drivers/media/i2c/rdacm21-camera_module: > 'max9271_set_translation' exported twice. Previous export was in > drivers/media/i2c/rdacm20-camera_module.ko This was reported in yesterday' linux-next and is being worked on. -- Cheers, Stephen Rothwell pgpfbpQv7pyIb.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the kvm tree

Hi Paolo, On Mon, 8 Feb 2021 06:48:32 +1100 Stephen Rothwell wrote: > > On Fri, 5 Feb 2021 11:08:39 +0100 Paolo Bonzini wrote: > > > > On 05/02/21 06:02, Stephen Rothwell wrote: > > > > > > After merging the kvm tree, today's linux-next build (powerp

linux-next: Tree for Feb 8

n to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (b75dba7f472c Merge tag 'libnvdimm-fixes-5.11-rc7' of git://git.kernel.org/

linux-next: build warning after merge of the xfs tree

by commit f83d436aef5d ("xfs: increase the default parallelism levels of pwork clients") -- Cheers, Stephen Rothwell pgpZq8i86xG7O.pgp Description: OpenPGP digital signature

linux-next: build warning after merge of the drm-misc tree

score externally") -- Cheers, Stephen Rothwell pgpO_ryHaksWD.pgp Description: OpenPGP digital signature

linux-next: build warning after merge of the v4l-dvb tree

was for __v4l2_async_notifier_add_i2c_subdev() instead Maybe introduced by commit c1cc23625062 ("media: v4l2-async: Discourage use of v4l2_async_notifier_add_subdev") -- Cheers, Stephen Rothwell pgpTHep6cLqyu.pgp Description: OpenPGP digital signature

linux-next: manual merge of the akpm-current tree with Linus' tree

x-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the kvm tree

9f4 ("KVM: x86/mmu: Use an rwlock for the x86 MMU") I have used the kvm tree from next-20210204 for today. -- Cheers, Stephen Rothwell pgpnoy9Cw8PaV.pgp Description: OpenPGP digital signature

linux-next: build warning after merge of the v4l-dvb tree

/media/i2c/rdacm20-camera_module.ko Introduced by commit a59f853b3b4b ("media: i2c: Add driver for RDACM21 camera module") -- Cheers, Stephen Rothwell pgp_JUyohg3Le.pgp Description: OpenPGP digital signature

linux-next: manual merge of the xfs tree with the pidfd tree

consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc fs/xfs/xfs_ioctl.c index 3d4c7ca080fb,248083ea0276.. --- a/fs/xfs/xfs_ioctl.c +++ b/fs/xfs/xfs_ioctl.c @@@ -1280,9 -1275,9 +1280,10 @@@ xfs_ioctl

Re: linux-next: build failure after merge of the kvm tree

Hi Paolo, On Fri, 5 Feb 2021 11:08:39 +0100 Paolo Bonzini wrote: > > On 05/02/21 06:02, Stephen Rothwell wrote: > > Hi all, > > > > After merging the kvm tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > ERROR

Re: [PATCH 0/2] pci sysfs file iomem revoke support

nd it no longer panics for my simple boot test (PowerPC pseries_le_defconfig under qemu). -- Cheers, Stephen Rothwell pgpf3iU_oYjSC.pgp Description: OpenPGP digital signature

linux-next: Fixes tag needs some work in the soundwire tree

Please do not split Fixes tags over more than one line. -- Cheers, Stephen Rothwell pgppI9BVbHzjQ.pgp Description: OpenPGP digital signature

Re: [PATCH] staging: emxx_udc: Fix incorrectly defined global

gt; #define INT_VBUS 0 /* IRQ for GPIO_P153 */ > -struct gpio_desc *vbus_gpio; > -int vbus_irq; > +extern struct gpio_desc *vbus_gpio; > +extern int vbus_irq; > > /* Board dependence(Wait) */ > > -- > 2.29.2 > -- Cheers, Stephen Rothwell pgpQgXtY4h3E6.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 5

oing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (5c279c4cf206 Revert "x86/setup: don't remove E820_TYPE_RAM for pfn 0") Merging fixes/fixes (e71ba9452f0b

linux-next: manual merge of the hyperv tree with Linus' tree

ts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc arch/x86/hyperv/hv_init.c i

linux-next: build failure after merge of the kvm tree

is not EXPORTed. I have used the kvm tree from next-20210204 for today. -- Cheers, Stephen Rothwell pgpN3Sthvy7fZ.pgp Description: OpenPGP digital signature

linux-next: manual merge of the devicetree tree with the kbuild tree

consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc scripts/Makefile.lib index 6f248ff91982,b00855b247e0.. --- a/scripts/Makefile.lib +++ b/scripts/Makefile.lib @@@ -85,12 -81,14 +85,14 @@@ always-y +=

linux-next: build failure after merge of the amdgpu tree

) from the drm tree. I reverted the drm tree commit for now. -- Cheers, Stephen Rothwell pgpZpaeAj__Ir.pgp Description: OpenPGP digital signature

linux-next: build failure after merge of the pm tree

intel-mid: Remove unused leftovers (vRTC)") 975272714c6f ("x86/apb_timer: Remove driver for deprecated platform") 08a1ce661b5c ("mfd: intel_msic: Remove driver for deprecated platform") I have used the pm tree from next-20210204 for today. -- Cheers, Stephen Rothwell

linux-next: build warning after merge of the cifs tree

) | ^ Introduced by commit 6941febc7309 ("cifs: add new helper function for fscache conversion") -- Cheers, Stephen Rothwell pgpcUdfygs3Fg.pgp Description: OpenPGP digital signature

Re: linux-next: manual merge of the pidfd tree with the overlayfs tree

Hi all, On Mon, 25 Jan 2021 17:04:26 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/overlayfs/copy_up.c > > between commit: > > 06896fa3193d ("ovl: skip getxattr of security labels") >

Re: linux-next: manual merge of the pidfd tree with the overlayfs tree

Hi all, On Mon, 25 Jan 2021 17:07:16 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/overlayfs/inode.c > > between commit: > > 9c09be9e71c4 ("ovl: perform vfs_getxattr() with mounter creds") >

linux-next: Signed-off-by missing for commit in the kvm tree

Hi all, Commit 79033bebf6fa ("KVM: x86/xen: Fix coexistence of Xen and Hyper-V hypercalls") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell pgpnU0paJpzRj.pgp Description: OpenPGP digital signature

linux-next: Fixes tag needs some work in the kvm tree

ect has leading but no trailing quotes Please do not split Fixes tags over more than one line. Also, keep all the commit message tags together at the end of the message. -- Cheers, Stephen Rothwell pgp56fhBnpvD4.pgp Description: OpenPGP digital signature

linux-next: Fixes tag needs some work in the block tree

refactor open() flags handling"") has these problem(s): - SHA1 should be at least 12 digits long These can be fixed for future commits by setting core.abbrev to 12 (or more) or (for git v2.11 or later) just making sure it is not set (or set to "auto"). -- Cheers, Stephen

Re: linux-next: build failure after merge of the net-next tree

ch was badly wrapped and whitespace damaged :-)) -- Cheers, Stephen Rothwell pgp5jOrKzETAe.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 4

nd to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (61556703b610 Merge tag 'for-linus-5.11-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml) Merging fixes/fixes (e71ba9452f0b Linux 5.11

linux-next: build warning after merge of the drivers-x86 tree

type [-Wdiscarded-qualifiers] 66 | wdt_dev.dev.platform_data = (const struct intel_mid_wdt_pdata *)id->driver_data; |^ Introduced by commit a507e5d90f3d ("platform/x86: intel_scu_wdt: Get rid of custom x86 model comparison") -- Cheers, Ste

linux-next: manual merge of the drivers-x86 tree with the drm-misc tree

your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell pgpaRi5nUmz8J.pgp Description: OpenPGP digital signature

linux-next: build failure after merge of the net-next tree

I have used the net-next tree from next-20210203 fot today. -- Cheers, Stephen Rothwell pgpLTxD89R9gE.pgp Description: OpenPGP digital signature

Re: linux-next: build failure after merge of the akpm-current tree

Hi all, On Tue, 2 Feb 2021 20:03:24 +1100 Stephen Rothwell wrote: > > After merging the akpm-current tree, today's linux-next build (x86_64 > allnoconfig) failed like this: > > In file included from arch/x86/include/asm/page.h:76, > from arch/x86/include/as

Re: linux-next: build failure after merge of the akpm-current tree

Hi Pavel, On Wed, 3 Feb 2021 18:21:07 -0500 Pavel Tatashin wrote: > > Stephen, do you want to send a new patch based on the current > linux-next, or do you want me to send an updated version? I'll send another one and include it in linux-next today. -- Cheers, Stephen

linux-next: Signed-off-by missing for commit in the cifs tree

Hi all, Commit 37595a5c8a51 ("smb3: fix crediting for compounding when only one request in flight") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpGY3ohdy8Pm.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 3

man.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git

linux-next: build warning after merge of the usb tree

; | ^~~ Introduced by commit 29b01295a829 ("usb: typec: Add typec_partner_set_pd_revision") -- Cheers, Stephen Rothwell pgpgxp5mbIgrN.pgp Description: OpenPGP digital signature

linux-next: Fixes tag needs some work in the fscache tree

Hi all, In commit 51721d69bb95 ("afs: Fix error handling in afs_req_issue_op()") Fixes tag Fixes: 0dd1a43b5d74 ("afs: Fix error handling in afs_req_issue_op()") has these problem(s): - Target SHA1 does not exist I have no idea which commit you meant :-( -- Chee

Re: linux-next: Signed-off-by missing for commit in the arm-soc tree

Hi all, On Wed, 3 Feb 2021 06:57:54 +1100 Stephen Rothwell wrote: > > Hi all, > > Commit > > 4e238bfd83f3 ("ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode") > > is missing a Signed-off-by from its committer. This is actually in the arm-soc-fixes

linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree

Hi all, Commit 44c5bd08518c ("*** HAX FOR CI *** Revert "rtc: mc146818: Detect and handle broken RTCs"") is missing a Signed-off-by from its author and committer. Reverts are commits as well. -- Cheers, Stephen Rothwell pgpCITnOzLyan.pgp Description: OpenPGP digital signature

linux-next: Signed-off-by missing for commit in the arm-soc tree

Hi all, Commit 4e238bfd83f3 ("ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpKtSiQBkpMj.pgp Description: OpenPGP digital signature

linux-next: Tree for Feb 2

If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable M

linux-next: build failure after merge of the akpm-current tree

m: Stephen Rothwell Date: Tue, 2 Feb 2021 19:49:00 +1100 Subject: [PATCH] make is_pinnable_page a macro As it is currently defined before page_to_section() which it needs. Signed-off-by: Stephen Rothwell --- include/linux/mm.h | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

Re: linux-next: build failure after merge of the block tree

Hi all, On Tue, 2 Feb 2021 13:57:14 +1100 Stephen Rothwell wrote: > > After merging the block tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > block/bio.c: In function 'bio_add_zone_append_page': > block/bio.c:860:31: error: 'struct bio' h

linux-next: build failure after merge of the block tree

;queue; | ^~ Caused by commit 309dca309fc3 ("block: store a block_device pointer in struct bio") interacting with commit 9f678097f3de ("block: add bio_add_zone_append_page") from the btrfs tree. I applied the following merge fix up for today. Fr

linux-next: manual merge of the block tree with the btrfs tree

with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc fs/iomap/direct-io.c index e4c258a2cefc,ea1e8f696076.. --- a/fs/iomap/direct-io.c +++ b/fs/iomap/direct-io.c @@@ -292,13 -260,7 +289,14 @@@ iomap_dio_bio_actor

linux-next: manual merge of the arm-soc tree with the arm tree

ed, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc a

linux-next: Tree for Feb 1

, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (ac8c6edd20bc Merge tag 'efi-urgent-for-v5.11' of

linux-next: qemu boot failure after merge of the tip tree

e reverted that commit for today (which fixed the boot failure). -- Cheers, Stephen Rothwell spawn qemu-system-ppc64 -M pseries -m 2G -vga none -nographic -enable-kvm -kernel /home/sfr/next/powerpc_pseries_le_defconfig/vmlinux -initrd ./ppc64le-rootfs.cpio.gz KVM: Failed to create TCE64 table

linux-next: build warning after merge of the net-next tree

x5: Add devlink subfunction port documentation") -- Cheers, Stephen Rothwell pgpzLMlQ3f_wA.pgp Description: OpenPGP digital signature

linux-next: manual merge of the irqchip tree with the sunxi tree

be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc Documentation/devicetree/bindings/interrupt-

linux-next: build failure after merge of the drm-misc tree

for 'v3d_cache_clean_sched_ops.timedout_job') Caused by commit a6a1f036c74e ("drm/scheduler: Job timeout handler returns status (v3)") I have used the drm-misc tree from next-20210129 for today. -- Cheers, Stephen Rothwell pgpDziCi7Y0Jp.pgp Description: OpenPGP digital signature

Re: linux-next: build warning after merge of the drm tree

Hi all, On Fri, 22 Jan 2021 11:59:18 +1100 Stephen Rothwell wrote: > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > WARNING: unmet direct dependencies detected for DRM_I915_WERROR > Depends on [n]: HAS_IOMEM [=

linux-next: manual merge of the drm tree with Linus' tree

You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/gpu/drm/amd/pm/inc/amdgpu_smu.h index 0d797fa9f5cc,a087e00382e6.. --- a/drivers/gpu/drm/amd/pm/inc/amdgpu_smu.

Re: linux-next: manual merge of the pidfd tree with the overlayfs tree

Hi all, On Mon, 25 Jan 2021 16:23:36 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > fs/ecryptfs/inode.c > > between commit: > > 176cfe865da6 ("ecryptfs: fix uid translation for setxattr on >

linux-next: Signed-off-by missing for commit in the parisc-hd tree

Hi all, Commit ca7222dcfff4 ("parisc: Bump 64-bit IRQ stack size to 64 KB") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell pgpOlEOC_U0dq.pgp Description: OpenPGP digital signature

linux-next: build warning after merge of the char-misc tree

river for deprecated platform") -- Cheers, Stephen Rothwell pgp6NGnW_iehq.pgp Description: OpenPGP digital signature

<    1   2   3   4   5   6   7   8   9   10   >