linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org, mhocko@suse.cz,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	Richard Weinberger <richard@nod.at>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: mmotm 2019-02-04-17-47 uploaded (fs/binfmt_elf.c)
Date: Mon, 4 Feb 2019 20:26:43 -0800	[thread overview]
Message-ID: <08a894b1-66f6-19bf-67be-c9b7b1b01126@infradead.org> (raw)
In-Reply-To: <20190205014806.rQcAx%akpm@linux-foundation.org>

On 2/4/19 5:48 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-02-04-17-47 has been uploaded to
> 
>    http://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> http://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (4.x
> or 4.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series

on x86_64 UML: (although should be many places)

../fs/binfmt_elf.c: In function ‘write_note_info’:
../fs/binfmt_elf.c:2122:19: error: ‘tmp’ undeclared (first use in this function)
   for (i = 0; i < tmp->num_notes; i++)
                   ^



-- 
~Randy

  reply	other threads:[~2019-02-05  4:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05  1:48 mmotm 2019-02-04-17-47 uploaded akpm
2019-02-05  4:26 ` Randy Dunlap [this message]
2019-02-05  6:43   ` [PATCH -mm] elf: fixup compilation Alexey Dobriyan
2019-02-05  7:58   ` mmotm 2019-02-04-17-47 uploaded (fs/binfmt_elf.c) Stephen Rothwell

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=08a894b1-66f6-19bf-67be-c9b7b1b01126@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=richard@nod.at \
    --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;
as well as URLs for NNTP newsgroup(s).