From: Ming Lei <ming.lei@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
Nilay Shroff <nilay@linux.ibm.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-um@lists.infradead.org
Subject: Re: arch/um/drivers/ubd_kern.c:780:13: warning: stack frame size (2152) exceeds limit (2048) in 'ubd_device_release'
Date: Sat, 17 Jan 2026 15:50:45 +0800 [thread overview]
Message-ID: <aWs_VTjkaD5yHB-o@fedora> (raw)
In-Reply-To: <202601171315.t7AOGOhS-lkp@intel.com>
On Sat, Jan 17, 2026 at 02:00:56PM +0800, kernel test robot wrote:
> Hi Ming,
>
> FYI, the error/warning still remains.
Hello,
`arch/um/drivers/ubd_kern.c` is maintained by UML subsystem:
ming@fedora:~/git/linux$ ./scripts/get_maintainer.pl arch/um/drivers/ubd_kern.c
Richard Weinberger <richard@nod.at> (maintainer:USER-MODE LINUX (UML))
Anton Ivanov <anton.ivanov@cambridgegreys.com> (maintainer:USER-MODE LINUX (UML))
Johannes Berg <johannes@sipsolutions.net> (maintainer:USER-MODE LINUX (UML),commit_signer:2/3=67%)
...
linux-um@lists.infradead.org (open list:USER-MODE LINUX (UML))
linux-kernel@vger.kernel.org (open list)
Thanks,
Ming
next prev parent reply other threads:[~2026-01-17 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 6:00 arch/um/drivers/ubd_kern.c:780:13: warning: stack frame size (2152) exceeds limit (2048) in 'ubd_device_release' kernel test robot
2026-01-17 7:50 ` Ming Lei [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-13 22:43 kernel test robot
2026-04-03 8:43 kernel test robot
2026-02-27 10:37 kernel test robot
2025-12-14 7:04 kernel test robot
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=aWs_VTjkaD5yHB-o@fedora \
--to=ming.lei@redhat.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nilay@linux.ibm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
/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.