[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJuCfpFo5TGTiQxnOGck=Gf_osSt5=BvLGmZodwbU5RHScK5gQ@mail.gmail.com>
Date: Thu, 16 Jan 2025 10:29:12 -0800
From: Suren Baghdasaryan <surenb@...gle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-stable tree
On Thu, Jan 16, 2025 at 7:10 AM Suren Baghdasaryan <surenb@...gle.com> wrote:
>
> On Wed, Jan 15, 2025 at 10:05 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > After merging the mm-stable tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > include/linux/seqlock.h:341: warning: Function parameter or struct member 'start' not described in 'raw_seqcount_try_begin'
>
> Oops. Thanks for catching this! It should be:
>
> @start: count to be passed to read_seqcount_retry()
>
> Should I send a fixup to Andrew for inclusion into the mm tree?
I posted the fix at
https://lore.kernel.org/all/20250116182730.801497-1-surenb@google.com/
in case it's needed.
>
> >
> > Introduced by commit
> >
> > dba4761a3e40 ("seqlock: add raw_seqcount_try_begin")
> >
> > I seem to have missed this when it was first introduced, sorry.
> >
> > --
> > Cheers,
> > Stephen Rothwell
Powered by blists - more mailing lists