All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	mm-commits@vger.kernel.org, rostedt@goodmis.org,
	pmladek@suse.com, senozhatsky@chromium.org
Subject: Re: [merged] seq_buf-add-seq_buf_do_printk-helper.patch removed from -mm tree
Date: Sat,  6 May 2023 00:28:05 +0000	[thread overview]
Message-ID: <20230506002805.121855-1-sj@kernel.org> (raw)
In-Reply-To: <CAJD7tkY9wBYX6JNf7D6tHTHRyYac_U+JKzRab+RJUKHCAG4zgw@mail.gmail.com>

On Fri, 5 May 2023 17:00:20 -0700 Yosry Ahmed <yosryahmed@google.com> wrote:

> On Fri, May 5, 2023 at 4:57 PM SeongJae Park <sj@kernel.org> wrote:
> >
> > Hi Andrew,
> >
> > On Fri, 05 May 2023 15:45:21 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > >
> > > The quilt patch titled
> > >      Subject: seq_buf: add seq_buf_do_printk() helper
> > > has been removed from the -mm tree.  Its filename was
> > >      seq_buf-add-seq_buf_do_printk-helper.patch
> > >
> > > This patch was dropped because it was merged into mainline or a subsystem tree
> >
> > Just for headup.  I just found the latest mm-unstable indeed dropped the patch
> > but a patch[1] depends on it.  As a result, build fails as below.
> 
> That patch was merged into Linus's tree, so I assumed that's why it
> was dropped from mm-unstable. Perhaps I am wrong.

Same to my assumption, and fit with the original mail's explanation.  I
confirmed the patch has merged in the mainline as commit 96928d9032a7.  So this
will be fixed if 1) mm-unstable is rebased on v6.4-rc1, 2) the dropped patch is
added again on mm-unstable, or 3) the patch[1] currently triggering the failure
is dropped.  This is never an important issue for me, so I don't have any
preference or opinion about the fix.  I just wanted to save time for others who
might got report of this.

[1] https://lore.kernel.org/mm-commits/20230502201509.B8711C433D2@smtp.kernel.org/


Thanks,
SJ

> 
> >
> >       CC      mm/memcontrol.o
> >     /mm/memcontrol.c: In function ‘mem_cgroup_print_oom_meminfo’:
> >     /mm/memcontrol.c:1693:2: error: implicit declaration of function ‘seq_buf_do_printk’; did you mean ‘seq_buf_bprintf’? [-Werror=implicit-function-declaration]
> >      1693 |  seq_buf_do_printk(&s, KERN_INFO);
> >           |  ^~~~~~~~~~~~~~~~~
> >           |  seq_buf_bprintf
> >     cc1: some warnings being treated as errors
> >
> > [1] https://lore.kernel.org/mm-commits/20230502201509.B8711C433D2@smtp.kernel.org/
> >
> >
> > Thanks,
> > SJ

  reply	other threads:[~2023-05-06  0:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 22:45 [merged] seq_buf-add-seq_buf_do_printk-helper.patch removed from -mm tree Andrew Morton
2023-05-05 23:57 ` SeongJae Park
2023-05-06  0:00   ` Yosry Ahmed
2023-05-06  0:28     ` SeongJae Park [this message]
2023-05-06  0:57       ` Andrew Morton

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=20230506002805.121855-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=yosryahmed@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.