linux-kernel - Re: [PATCH v2 1/1] Documentation: core-api: Drop :export: for int

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZL/nTi3LNPiLI8dF@smile.fi.intel.com>
Date:   Tue, 25 Jul 2023 18:16:30 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Mark Brown <broonie@...nel.org>
Cc:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v2 1/1] Documentation: core-api: Drop :export: for
 int_log.h

On Tue, Jul 25, 2023 at 03:51:44PM +0100, Mark Brown wrote:
> On Tue, Jul 25, 2023 at 05:40:54PM +0300, Andy Shevchenko wrote:
> > On Tue, Jul 25, 2023 at 03:27:58PM +0100, Mark Brown wrote:
> 
> > > There was some random patch you just sent me the message ID for in the
> > > replies to something from Stephen which I'm fairly sure I queued,
> > > perhaps it was a different thing or git thought it was a noop when it
> > > was applied?
> 
> > The first version is here [1].
> > Then it was a discussion about Linux Next build issues [2].
> 
> > In the discussion I mentioned:
> 
> >   The 20230713165320.14199-1-andriy.shevchenko@...ux.intel.com had been sent.
> 
> > which is exactly what [1] is.
> 
> > I have no idea how it can be a noop, but the patch is missing as far
> > as I can tell.
> 
> > This thread is v2 of what was in [1].
> 
> > [1]: https://lore.kernel.org/linux-doc/20230713165320.14199-1-andriy.shevchenko@linux.intel.com/
> > [2]: https://lore.kernel.org/linux-next/20230713121627.17990c86@canb.auug.org.au/T/#u
> 
> So there's two versions of the patch and for some reason v1 was
> mentioned yesterday but there's also a v2 version?

Yes, and I forgot to initially Cc you for v2.

If you are using b4, you can take Message ID of this message and I am sure it
capable to retrieve v2 of the patch. Or I can resend with you in Cc list.

-- 
With Best Regards,
Andy Shevchenko