From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: broonie@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2021-08-09-19-18 uploaded
Date: Mon, 9 Aug 2021 23:27:43 -0700 [thread overview]
Message-ID: <20210809232743.a95e8f111f697eaff9418b2c@linux-foundation.org> (raw)
In-Reply-To: <3bc14281-4cfe-7cd6-1b88-128e51d08c3a@infradead.org>
On Mon, 9 Aug 2021 21:25:27 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> Hm, my patch scripts usually work, but this one gives me:
>
> Hunk #5 FAILED at 603.
> Hunk #6 FAILED at 701.
> 2 out of 19 hunks FAILED -- rejects in file include/linux/memcontrol.h
oops, sorry, let me redo...
prev parent reply other threads:[~2021-08-10 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 2:19 akpm
2021-08-10 4:25 ` Randy Dunlap
2021-08-10 6:27 ` Andrew Morton [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=20210809232743.a95e8f111f697eaff9418b2c@linux-foundation.org \
--to=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=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