linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	urezki@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Jan 11 (mm/vmalloc.c)
Date: Fri, 12 Jan 2024 09:12:47 +0100	[thread overview]
Message-ID: <ZaD0f7dDz4GCKh-v@pc636> (raw)
In-Reply-To: <74388269-0a03-4c10-8408-fc204c843fd7@infradead.org>

On Thu, Jan 11, 2024 at 03:51:50PM -0800, Randy Dunlap wrote:
> 
> 
> On 1/10/24 19:48, Stephen Rothwell wrote:
> > Hi all,
> > 
> > News: the merge window has opened, so please do not add any material
> > intended for v6.9 to your linux-next included branches until asfter
> > v6.8-rc1 has been released.
> > 
> > Changes since 20240110:
> > 
> 
> on riscv 64-bit, i386, and UML:
> 
> ../mm/vmalloc.c: In function 'vmalloc_dump_obj':
> ../mm/vmalloc.c:4691:22: warning: 'addr' is used uninitialized [-Wuninitialized]
>  4691 |                 va = __find_vmap_area(addr, &vn->busy.root);
>       |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../mm/vmalloc.c:4684:23: note: 'addr' was declared here
>  4684 |         unsigned long addr;
>       |                       ^~~~
> 
> 
Yesterday i sent out the fix.

https://lore.kernel.org/linux-mm/ZaARXdbigD1hWuOS@pc638.lan/T/

--
Uladzislau Rezki


      parent reply	other threads:[~2024-01-12  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240111144846.74e443a7@canb.auug.org.au>
2024-01-11 23:51 ` Randy Dunlap
2024-01-12  2:47   ` Stephen Rothwell
2024-01-12  8:12   ` Uladzislau Rezki [this message]

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=ZaD0f7dDz4GCKh-v@pc636 \
    --to=urezki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox