From: Masami Hiramatsu <mhiramat@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Will Deacon <will@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the arm64-fixes tree
Date: Mon, 5 Aug 2019 16:37:03 +0900 [thread overview]
Message-ID: <20190805163703.da632d5800c15a96ee79bf9d@kernel.org> (raw)
In-Reply-To: <20190803101533.GA58477@iMac.local>
On Sat, 3 Aug 2019 11:15:34 +0100
Catalin Marinas <catalin.marinas@arm.com> wrote:
> On Sat, Aug 03, 2019 at 09:42:12AM +0900, Masami Hiramatsu wrote:
> > On Fri, 2 Aug 2019 07:48:13 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > In commit
> > >
> > > 72de4a283cb1 ("arm64: kprobes: Recover pstate.D in single-step exception handler")
> > >
> > > Fixes tag
> > >
> > > Fixes: commit 7419333fa15e ("arm64: kprobe: Always clear pstate.D in breakpoint exception handler")
> > >
> > > has these problem(s):
> > >
> > > - leading word 'commit' unexpected
> >
> > Oops, sorry. It was my mistake to add "commit", it should be removed.
> > Will, should I remove it? or could you modify on your tree?
>
> No need to. Will fixed it already.
Thank you Will and Catalin!
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2019-08-05 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 21:48 linux-next: Fixes tag needs some work in the arm64-fixes tree Stephen Rothwell
2019-08-03 0:42 ` Masami Hiramatsu
2019-08-03 10:15 ` Catalin Marinas
2019-08-05 7:37 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-06 18:35 Stephen Rothwell
2019-07-31 22:06 Stephen Rothwell
2019-08-01 9:34 ` Will Deacon
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=20190805163703.da632d5800c15a96ee79bf9d@kernel.org \
--to=mhiramat@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=will@kernel.org \
/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).