From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Justin He <Justin.He@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] make '%pD' print the full path of file
Date: Wed, 14 Jul 2021 17:17:28 +0300 [thread overview]
Message-ID: <YO7x+OA3Osq73ooP@smile.fi.intel.com> (raw)
In-Reply-To: <AM6PR08MB43763816EBF217940F5B3E15F7139@AM6PR08MB4376.eurprd08.prod.outlook.com>
On Wed, Jul 14, 2021 at 01:24:48PM +0000, Justin He wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Wednesday, June 23, 2021 5:18 PM
> > On Wed, Jun 23, 2021 at 01:50:07PM +0800, Jia He wrote:
...
> > > v2:
> >
> > Should be v6 now. So, next v7, otherwise you confuse bots and people.
> >
> > My remark was for you for the future submission, this one is already
> > spoiled.
> >
> Sorry for the verbose, the next version of this series should be
> v7 or v3?
v7 with changelog explaining each version difference. I have no idea how many
you issued due to the numbering confusion.
...
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
I think it's last time I'm answering message from you with this footer. Can you
please close this deal once for ever?
Ah, and usually I do not answer on private emails on Open Source matters. LKML is restored.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-07-14 14:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 5:50 [PATCH v2 0/4] make '%pD' print the full path of file Jia He
2021-06-23 5:50 ` [PATCH v2 1/4] fs: introduce helper d_path_unsafe() Jia He
2021-06-23 9:10 ` Andy Shevchenko
2021-06-24 5:48 ` Justin He
2021-07-14 8:33 ` Justin He
2021-07-14 9:17 ` Andy Shevchenko
2021-06-28 5:13 ` Justin He
2021-06-28 9:06 ` Petr Mladek
2021-07-02 6:36 ` Justin He
2021-06-23 5:50 ` [PATCH v2 2/4] lib/vsprintf.c: make '%pD' print the full path of file Jia He
2021-06-23 9:14 ` Andy Shevchenko
2021-06-24 9:01 ` Petr Mladek
2021-06-24 10:49 ` Andy Shevchenko
2021-06-25 2:29 ` Justin He
2021-06-25 2:32 ` Justin He
2021-06-23 5:50 ` [PATCH v2 3/4] lib/test_printf.c: split write-beyond-buffer check in two Jia He
2021-06-23 9:16 ` Andy Shevchenko
2021-06-23 5:50 ` [PATCH v2 4/4] lib/test_printf.c: add test cases for '%pD' Jia He
2021-06-23 9:17 ` [PATCH v2 0/4] make '%pD' print the full path of file Andy Shevchenko
[not found] ` <AM6PR08MB43763816EBF217940F5B3E15F7139@AM6PR08MB4376.eurprd08.prod.outlook.com>
2021-07-14 14:17 ` Andy Shevchenko [this message]
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=YO7x+OA3Osq73ooP@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Justin.He@arm.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox