From: Andrew Morton <akpm@linux-foundation•org>
To: Masami Hiramatsu (Google) <mhiramat@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Steven Rostedt <rostedt@goodmis•org>,
"Paul E. McKenney" <paulmck@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the ftrace tree
Date: Wed, 18 Oct 2023 08:13:49 -0700 [thread overview]
Message-ID: <20231018081349.b5762f6f2c362fa8f84df5d2@linux-foundation.org> (raw)
In-Reply-To: <20231019001038.ed0fa7568e95d2409eb6a697@kernel.org>
On Thu, 19 Oct 2023 00:10:38 +0900 Masami Hiramatsu (Google) <mhiramat@kernel•org> wrote:
> On Wed, 18 Oct 2023 14:18:57 +1100
> Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> > Hi all,
> >
> > The following commits are also in the mm tree as a different commit
> > (but the same patch):
> >
> > 2db949178eca ("fs/proc: Add boot loader arguments as comment to /proc/bootconfig")
> >
> > This is commit
> >
> > d120336bf502 ("fs/proc: add boot loader arguments as comment to /proc/bootconfig")
>
> Hmm, sorry, I picked this patch on my bootconfig/for-next branch because
> it depends on the bootconfig feature.
>
I dropped the copy from mm.git.
next prev parent reply other threads:[~2023-10-18 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 3:18 linux-next: duplicate patch in the ftrace tree Stephen Rothwell
2023-10-18 15:10 ` Masami Hiramatsu
2023-10-18 15:13 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 21:50 Stephen Rothwell
2023-09-04 22:36 ` Masami Hiramatsu
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=20231018081349.b5762f6f2c362fa8f84df5d2@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhiramat@kernel$(echo .)org \
--cc=paulmck@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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