kisskb: OK linus/axs101_defconfig/arcompact Tue Dec 17, 14:02
OK linus/axs101_defconfig/arcompact Tue Dec 17, 14:02 http://kisskb.ellerman.id.au/kisskb/buildresult/14070341/ Commit: Merge tag 'linux-kselftest-5.5-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest 6afa873170a612b2b9e392c19c523ed8aae6fbc9 Compiler: arc-buildroot-linux-uclibc-gcc (Buildroot 2015.08.1) 4.8.4 / GNU ld (GNU Binutils) 2.23.2 No errors found in log Possible warnings (2) -- :1511:2: warning: #warning syscall clone3 not implemented [-Wcpp] net/ipv4/tcp_input.c:4386:49: warning: array subscript is above array bounds [-Warray-bounds] ___ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc
kisskb: OK linus/axs103_smp_defconfig/arcv2 Tue Dec 17, 14:00
OK linus/axs103_smp_defconfig/arcv2 Tue Dec 17, 14:00
http://kisskb.ellerman.id.au/kisskb/buildresult/14070340/
Commit: Merge tag 'linux-kselftest-5.5-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
6afa873170a612b2b9e392c19c523ed8aae6fbc9
Compiler: arc-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 6.2.1
20160824 / GNU ld (GNU Binutils) 2.27.51.20160928
Possible errors
---
#define KERN_ERR KERN_SOH "3" /* error conditions */
#define KERN_ERR KERN_SOH "3" /* error conditions */
#define KERN_ERR KERN_SOH "3" /* error conditions */
#define KERN_ERR KERN_SOH "3" /* error conditions */
Possible warnings (89)
--
:1511:2: warning: #warning syscall clone3 not implemented [-Wcpp]
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
init/main.c:382:35: warning: format '%zu' expects argument of type 'size_t',
but argument 3 has type 'unsigned int' [-Wformat=]
init/main.c:386:35: warning: format '%zu' expects argument of type 'size_t',
but argument 3 has type 'unsigned int' [-Wformat=]
init/main.c:390:35: warning: format '%zu' expects argument of type 'size_t',
but argument 3 has type 'unsigned int' [-Wformat=]
init/main.c:825:37: warning: format '%zu' expects argument of type 'size_t',
but argument 3 has type '__kernel_size_t {aka unsigned int}' [-Wformat=]
drivers/base/regmap/regmap.c:1526:22: warning: format '%zu' expects argument of
type 'size_t', but argument 5 has type 'unsigned int' [-Wformat=]
drivers/base/component.c:196:24: warning: format '%zu' expects argument of type
'size_t', but argument 4 has type 'unsigned int' [-Wformat=]
kernel/dma/direct.c:32:4: warning: format '%zu' expects argument of type
'size_t', but argument 4 has type 'unsigned int' [-Wformat=]
drivers/base/regmap/regcache.c:715:20: warning: format '%zu' expects argument
of type 'size_t', but argument 4 has type 'unsigned int' [-Wformat=]
include/linux/kern_levels.h:5:18: warning: format '%zd' expects argument of
type 'signed size_t', but argument 3 has type 'size_t {aka unsigned int}'
[-Wformat=]
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kern_levels.h:5:18: warning: format '%zu' expects argument of
type 'size_t', but argument 2 has type 'unsigned int' [-Wformat=]
include/linux/kern_levels.h:5:18: warning: format '%zu' expects argument of
type 'size_t', but argument 2 has type 'unsigned int' [-Wformat=]
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/overflow.h:59:15: warning: comparison of distinct pointer types
lacks a cast
include/linux/overflow.h:60:15: warning: comparison of distinct pointer types
lacks a cast
fs/ext4/xattr.c:482:8: warning: format '%zu' expects argument of type 'size_t',
but argument 6 has type 'unsigned int' [-Wformat=]
include/linux/kern_levels.h:5:18: warning: format '%zd' expects argument of
type 'signed size_t', but argument 3 has type 'size_t {aka const unsigned int}'
[-Wformat=]
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
drivers/dma-buf/dma-buf.c:402:26: warning: format '%zu' expects argument of
type 'size_t', but argument 3 has type 'unsigned int' [-Wformat=]
include/linux/kernel.h:844:29: warning: comparison of distinct pointer types
lacks a cast
mm/percpu.c:1334:35: warning: format '%zu' expects argument of type 'size_t',
but argument 3 has type 'unsigned int' [-Wformat=]
mm/percpu.c:1349:35: warning: format '%zu' expects argument of type 'size_t',
but
kisskb: OK linus/axs101_defconfig/arcompact Tue Dec 17, 07:03
OK linus/axs101_defconfig/arcompact Tue Dec 17, 07:03 http://kisskb.ellerman.id.au/kisskb/buildresult/14069600/ Commit: Fix root mounting with no mount options 7de7de7ca0ae0fc70515ee3154af33af75edae2c Compiler: arc-buildroot-linux-uclibc-gcc (Buildroot 2015.08.1) 4.8.4 / GNU ld (GNU Binutils) 2.23.2 No errors found in log Possible warnings (2) -- :1511:2: warning: #warning syscall clone3 not implemented [-Wcpp] net/ipv4/tcp_input.c:4386:49: warning: array subscript is above array bounds [-Warray-bounds] ___ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc
Re: [uclibc-ng-devel] stdio fudging errno ?
On 12/14/19 1:37 AM, Florian Weimer wrote:
> * Vineet Gupta:
>
>> Here's a simple test case which shows the problem:
>>
>> #define _GNU_SOURCE
>> #include
>> #include
>> #include
>>
>> void main(void)
>> {
>> const char *this_func = "finite";
>> char *test_name;
>>
>> errno = 0;
>> if (asprintf (_name, "%s (%s)", this_func, "my-str") == -1)
>> abort ();
>>
>> printf("%d\n", errno); // <-- prints 11
>> }
>>
>> The errno unconditionally being set to EAGAIN seems to have been
>> introduced in commit 568ceebf6adfc58c64a95133311268db6 ("Fix
>> infinite loop when fopencookie custom write returns 0 on error")
>> bakc in 2016.
> For functions specified by standards, successful calls can alter errno
> unless specified otherwise. asprintf is not a standardized function,
> but it is reasonable to expect that a similar rule applies.
Right, but ...
1. Don't those standards specify the exact errno for specific scenarios and that
typically errno won't be changed to !0 if there was no error.
2. The EAGAIN being returned can be seen as "leaking" out of internal details of
the ensuing call stack.
3. This breaks the way uclibc test harness works. It clears the errno at the
start
of a call sequence and in the end when notices the change it trips. It expects
the
errno to be set (or not set) by the math routines and asprintf changing them
trips
it. glibc test harness is no different - it would have failed in similar way had
similar errno fudging existed there !
At any rate the fix is simple to only change errno in case of a failure.
Thx,
-Vineet
___
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
[GIT PULL REBASED] drm/arc: Yet another set of minor fixes
Hi David, Daniel! The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919: Linux 5.5-rc2 (2019-12-15 15:16:08 -0800) are available in the Git repository at: g...@github.com:abrodkin/linux.git tags/arcpgu-updates-2019.12.16 for you to fetch changes up to 0ff916e2ef6fb742e4906aac26c470314b59bae8: DRM: ARC: PGU: add ARGB format to supported format list (2019-12-16 13:53:05 +0300) Clean-up and fixes for FourCC handling in ARC PGU. Eugeniy Paltsev (4): DRM: ARC: PGU: fix framebuffer format switching DRM: ARC: PGU: cleanup supported format list code DRM: ARC: PGU: replace unsupported by HW RGB888 format by XRGB888 DRM: ARC: PGU: add ARGB format to supported format list drivers/gpu/drm/arc/arcpgu_crtc.c | 36 ++-- drivers/gpu/drm/arc/arcpgu_regs.h | 2 +- 2 files changed, 19 insertions(+), 19 deletions(-) Note this is based on the current drm/drm-next contents. Thanks, Alexey ___ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc
Re: [GIT PULL] drm/arc: Yet another set of minor fixes
On Fri, Dec 13, 2019 at 10:24:42AM +, Alexey Brodkin wrote: > Hi Daniel, > > > -Original Message- > > From: Daniel Vetter > > Sent: Friday, December 13, 2019 1:22 PM > > To: Alexey Brodkin > > Cc: Daniel Vetter ; David Airlie ; arcml > > > a...@lists.infradead.org>; Eugeniy Paltsev ; > > dri-de...@lists.freedesktop.org > > Subject: Re: [GIT PULL] drm/arc: Yet another set of minor fixes > > > > [snip] > > > > Not sure if you noticed re-spin of my pull-request in the previous > > > message. > > > Do you want me to send it in a separate email? > > > > Yeah I guess this got lost again. > > So should I re-send it in another email or you will pick it up > from existing thread? > > If I'm going to re-send it do I need to re-base it on today's drm/drm-next? I just tried to vacuum it in, but it chokes the scripts since it's multiple pull requests in one mail with quotes. So please redo in a clean mail. Wrt baseline, here's the recommendation in order of my preference: - Just stuff it into drm-misc-next - Base your tree on a tag from Linux - If you need a specific depedency, base your tree on drm-next with that patch included. - If it's even more complicated, do a multi-way topic branch with lots of coordination. Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch ___ linux-snps-arc mailing list linux-snps-arc@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-snps-arc
