From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 10018/11651] fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio'
Date: Sat, 14 May 2022 18:58:52 +0100 [thread overview]
Message-ID: <Yn/t3Fr/snB2tp8h@casper.infradead.org> (raw)
In-Reply-To: <202205150117.sd6HzBVm-lkp@intel.com>
On Sun, May 15, 2022 at 01:36:48AM +0800, kernel test robot wrote:
> config: hexagon-randconfig-r041-20220513 (https://download.01.org/0day-ci/archive/20220515/202205150117.sd6HzBVm-lkp@intel.com/config)
Hexagon. Don't care.
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 10018/11651] fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio'
Date: Sat, 14 May 2022 18:58:52 +0100 [thread overview]
Message-ID: <Yn/t3Fr/snB2tp8h@casper.infradead.org> (raw)
In-Reply-To: <202205150117.sd6HzBVm-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
On Sun, May 15, 2022 at 01:36:48AM +0800, kernel test robot wrote:
> config: hexagon-randconfig-r041-20220513 (https://download.01.org/0day-ci/archive/20220515/202205150117.sd6HzBVm-lkp(a)intel.com/config)
Hexagon. Don't care.
next prev parent reply other threads:[~2022-05-14 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 17:36 [linux-next:master 10018/11651] fs/ntfs/aops.c:378:12: warning: stack frame size (2224) exceeds limit (1024) in 'ntfs_read_folio' kernel test robot
2022-05-14 17:58 ` Matthew Wilcox [this message]
2022-05-14 17:58 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yn/t3Fr/snB2tp8h@casper.infradead.org \
--to=willy@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.