From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 1/1] Documentation: core-api: Drop :export: for int_log.h
Date: Tue, 25 Jul 2023 18:16:30 +0300 [thread overview]
Message-ID: <ZL/nTi3LNPiLI8dF@smile.fi.intel.com> (raw)
In-Reply-To: <4f6c9be9-22bd-472e-a20a-cd361b46e005@sirena.org.uk>
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@linux.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
next prev parent reply other threads:[~2023-07-25 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 10:49 [PATCH v2 1/1] Documentation: core-api: Drop :export: for int_log.h Andy Shevchenko
2023-07-25 13:12 ` Jonathan Corbet
2023-07-25 13:16 ` Andy Shevchenko
2023-07-25 13:46 ` Mark Brown
2023-07-25 14:06 ` Andy Shevchenko
2023-07-25 14:27 ` Mark Brown
2023-07-25 14:40 ` Andy Shevchenko
2023-07-25 14:51 ` Mark Brown
2023-07-25 15:16 ` Andy Shevchenko [this message]
2023-07-25 19:20 ` Mark Brown
2023-07-26 14:45 ` Andy Shevchenko
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=ZL/nTi3LNPiLI8dF@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.