public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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] ceph: Amend checking to fix `make W=1` build breakage
Date: Mon, 24 Nov 2025 20:43:37 +0200	[thread overview]
Message-ID: <aSSnWaDHK5Yyq_Ae@smile.fi.intel.com> (raw)
In-Reply-To: <82c49caff875cc131951a7e5d59ecb45efbb9224.camel@ibm.com>

On Mon, Nov 24, 2025 at 05:47:04PM +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:42:13PM +0000, Viacheslav Dubeyko wrote:
> > > On Mon, 2025-11-10 at 21:43 +0200, andriy.shevchenko@linux.intel.com wrote:

...

> > > I think we can take the patch as it. It looks good. Probably, it makes sense to
> > > take a deeper look in the code on our side.
> > > 
> > > Reviewed-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> > 
> > Thanks, can this be applied? My builds are still broken.
> 
> The patchset has been applied on testing branch already [1].

Thanks for the information. The Linux Next still has no that branch in.
I recommend to write Stephen a message to include your testing branch or
something like that into Linux Next, so it will get more test coverage.

> Ilya, when are we planning to send this patchset upstream?

> [1] https://github.com/ceph/ceph-client.git

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-11-24 18:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 14:44 [PATCH v1 1/1] ceph: Amend checking to fix `make W=1` build breakage Andy Shevchenko
2025-11-10 19:37 ` Viacheslav Dubeyko
2025-11-10 19:43   ` andriy.shevchenko
2025-11-10 20:42     ` Viacheslav Dubeyko
2025-11-24 15:09       ` andriy.shevchenko
2025-11-24 17:47         ` Viacheslav Dubeyko
2025-11-24 18:43           ` andriy.shevchenko [this message]
2025-11-24 18:49             ` Viacheslav Dubeyko
2025-11-24 18:58               ` andriy.shevchenko
2025-11-10 19:48   ` Gregory Farnum
2025-11-10 19:57     ` Viacheslav Dubeyko
2025-11-10 20:00       ` Gregory Farnum
2025-11-10 20:03         ` Viacheslav Dubeyko
2025-11-25  9:55 ` david laight
2025-11-25 10:17   ` Andy Shevchenko
2025-11-25 12:05     ` david laight
2025-11-25 18:24   ` Viacheslav Dubeyko

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=aSSnWaDHK5Yyq_Ae@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