From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "idryomov@gmail.com" <idryomov@gmail.com>,
Xiubo Li <xiubli@redhat.com>,
"justinstitt@google.com" <justinstitt@google.com>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"morbo@google.com" <morbo@google.com>,
"nathan@kernel.org" <nathan@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nick.desaulniers+lkml@gmail.com"
<nick.desaulniers+lkml@gmail.com>
Subject: Re: [PATCH v1 1/1] libceph: Amend checking to fix `make W=1` build breakage
Date: Mon, 24 Nov 2025 20:44:34 +0200 [thread overview]
Message-ID: <aSSnkgFfOJxrKRvi@smile.fi.intel.com> (raw)
In-Reply-To: <d4a49f37f2ac64036f1bb254abcca6cef743074d.camel@ibm.com>
On Mon, Nov 24, 2025 at 05:45:55PM +0000, Viacheslav Dubeyko wrote:
> On Mon, 2025-11-24 at 17:09 +0200, andriy.shevchenko@linux.intel.com wrote:
> > On Mon, Nov 10, 2025 at 08:39:49PM +0000, Viacheslav Dubeyko wrote:
...
> > Thanks, can this be applied? My builds are still broken.
>
> The patchset has been applied on testing branch already [1].
Thanks again, and same recommendation as per previous email.
> Ilya, when are we planning to send this patchset upstream?
>
> [1] https://github.com/ceph/ceph-client.git
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-11-24 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 14:46 [PATCH v1 1/1] libceph: Amend checking to fix `make W=1` build breakage Andy Shevchenko
2025-11-10 19:28 ` Viacheslav Dubeyko
2025-11-10 19:36 ` andriy.shevchenko
2025-11-10 20:39 ` Viacheslav Dubeyko
2025-11-24 15:09 ` andriy.shevchenko
2025-11-24 17:45 ` Viacheslav Dubeyko
2025-11-24 18:44 ` andriy.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=aSSnkgFfOJxrKRvi@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=xiubli@redhat.com \
/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