From: "Ricardo B. Marliere" <ricardo@marliere.net>
To: Tejun Heo <tj@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 3841/4021] kernel/workqueue.c:6798:32: error: passing 'const struct bus_type *' to parameter of type 'struct bus_type *' discards qualifiers
Date: Tue, 6 Feb 2024 14:48:19 -0300 [thread overview]
Message-ID: <wkj256gqj4ghtpfjiy57pbmtx7jfntv7vhfbeckbyk6fwzmpmb@6me7whi7slah> (raw)
In-Reply-To: <ZcEeOueCbrltxr_b@slm.duckdns.org>
Hi Tejun,
On 5 Feb 07:43, Tejun Heo wrote:
> Hello, Ricardo.
>
> On Mon, Feb 05, 2024 at 10:29:30AM -0300, Ricardo B. Marliere wrote:
> > I'm not sure how to flag this as invalid, since this is fixed already in
> > 32f78abe59c7 ("driver core: bus: constantify subsys_register() calls")
>
> So, when there are cross-tree dependencies, it's best to note them when
> sending out the patch so that the preparatory pulls can be made to avoid
> breaking the applying trees. I just reverted the patch for now and think
> it'd be best to route this patch through the driver-core tree. Can you
> please repost the patch and ask Greg to apply it.
Sorry for that, I'll resend to Greg then.
Thank you,
- Ricardo.
>
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2024-02-06 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 7:15 kernel test robot
2024-02-05 13:29 ` Ricardo B. Marliere
2024-02-05 17:43 ` Tejun Heo
2024-02-06 17:48 ` Ricardo B. Marliere [this message]
2024-02-05 17:41 ` [PATCH wq/for-6.9] Revert "workqueue: make wq_subsys const" Tejun Heo
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=wkj256gqj4ghtpfjiy57pbmtx7jfntv7vhfbeckbyk6fwzmpmb@6me7whi7slah \
--to=ricardo@marliere.net \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tj@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