All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: SeongJae Park <sj@kernel.org>, Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Jiayuan Chen <jiayuan.chen@shopee.com>,
	damon@lists.linux.dev, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Jun 11 (damon)
Date: Sun, 14 Jun 2026 11:42:34 -0700	[thread overview]
Message-ID: <20260614184235.101552-1-sj@kernel.org> (raw)
In-Reply-To: <4df95955-b255-4e5a-90c4-35db02f3111f@infradead.org>

Hello Randy,

On Sun, 14 Jun 2026 10:41:05 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:

> Hi,
> 
> On 6/11/26 7:33 AM, Mark Brown wrote:
> > Hi all,
> > 
> > Changes since 20260610:
> > 
> 
> Please add missing kernel-doc comments:
> 
> WARNING: ../include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
> WARNING: ../include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'

Thank you for notifying this!

The fixes should be trivial.  I made those and queued [1,2] on damon/next tree.
DAMON patches are merged into next tree via mm.git.  And mm.git is currently
closed for non-urgent issues to focus on making things for next merge window
stabilized.  I will therefore post the fixes after the next merge window is
closed (7.2-rc1 release).

Please let me know if I'm missing something or you have any different opinion.

[1] https://git.kernel.org/sj/c/892a69e2774fcface1202dbdc2ff62e433f487fa
[2] https://git.kernel.org/sj/c/b205766e8d676b9c9e3af828e736215bc54f4690


Thanks,
SJ

[...]

  reply	other threads:[~2026-06-14 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 14:33 linux-next: Tree for Jun 11 Mark Brown
2026-06-14 17:41 ` linux-next: Tree for Jun 11 (damon) Randy Dunlap
2026-06-14 18:42   ` SeongJae Park [this message]
2026-06-14 19:03     ` Randy Dunlap

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=20260614184235.101552-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=jiayuan.chen@shopee.com \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.