From: James Morse <james.morse@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Julien Grall <julien.grall@citrix.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] arm64: Add missing linux/bug.h include in asm/pgtable.h
Date: Tue, 15 Dec 2015 10:18:15 +0000 [thread overview]
Message-ID: <566FE8E7.4000401@arm.com> (raw)
In-Reply-To: <20151214170725.GC27918@e104818-lin.cambridge.arm.com>
On 14/12/15 17:07, Catalin Marinas wrote:
> If they take the mmdebug.h patch, it's even better. Please let us know
> how that goes.
Andrew Morton's Robot wrote:
> The patch titled
> Subject: include/linux/mmdebug.h: should include linux/bug.h
> has been added to the -mm tree. Its filename is
> include-linux-mmdebugh-should-include-linux-bugh.patch
>
> This patch should soon appear at
> http://ozlabs.org/~akpm/mmots/broken-out/include-linux-mmdebugh-should-include-linux-bugh.patch
> and later at
> http://ozlabs.org/~akpm/mmotm/broken-out/include-linux-mmdebugh-should-include-linux-bugh.patch
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
Thanks,
James
prev parent reply other threads:[~2015-12-15 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 16:07 [PATCH] arm64: Add missing linux/bug.h include in asm/pgtable.h Julien Grall
2015-12-14 16:22 ` Catalin Marinas
2015-12-14 16:26 ` Julien Grall
2015-12-14 16:38 ` Catalin Marinas
2015-12-14 16:47 ` James Morse
2015-12-14 17:07 ` Catalin Marinas
2015-12-15 10:18 ` James Morse [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=566FE8E7.4000401@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=julien.grall@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=will.deacon@arm.com \
/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