[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YtWq1vX+8VylSa4G@dev-arch.thelio-3990X>
Date: Mon, 18 Jul 2022 11:47:50 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Justin Stitt <justinstitt@...gle.com>
Cc: Justin Stitt <jstitt007@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v3] include/uapi/linux/swab.h: move explicit cast outside
ternary
On Mon, Jul 18, 2022 at 11:25:27AM -0700, Justin Stitt wrote:
> On Mon, Jul 18, 2022 at 11:22 AM Nathan Chancellor <nathan@...nel.org> wrote:
> >
> > On Mon, Jul 18, 2022 at 11:12:25AM -0700, Justin Stitt wrote:
> > > Any chance a maintainer could take a look at this patch? I am trying
> > > to get it through this cycle and we are so close to enabling the
> > > -Wformat option for Clang. This patch fixes over 50 warnings and
> > > there's only a handful of patches remaining until we can enable
> > > -Wformat.
> >
> > I think this change is already picked up? It's in -next.
>
> Oh, awesome!
>
> > https://git.kernel.org/akpm/mm/c/d30dfd490f7dc4cb6a7c11a647bd1ff7a22139e7
> > https://git.kernel.org/next/linux-next/c/d30dfd490f7dc4cb6a7c11a647bd1ff7a22139e7
>
> How did you track this down? I wasn't able to find any references to
> my patch in -next through kernel.org.
If you have a copy of the linux-next repo, you can just run:
$ git log --author "Justin Stitt" --oneline
after updating it (or 'git log <file>', whichever works) to quickly
survey.
Through the cgit web interface on kernel.org, the easiest way would be
searching your name in the upper right search bar with the "Author"
option. Otherwise, I typically look through the git log of a particular
file by appending "log/" + the full path of the file to the repository
URL like so:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/include/uapi/linux/swab.h
Sometimes maintainer trees might not funnel into -next (they should be)
but your patch might still be picked up. You can pass the '--scm'
argument to get_maintainer.pl to see if the MAINTAINERS file has a git
tree associated with it and do the same thing as above to see if the
patch has been accepted (you might need to analyze the different
branches).
Cheers,
Nathan
Powered by blists - more mailing lists