From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: rust-for-linux@vger.kernel.org, benno.lossin@proton.me
Subject: Re: [PATCH v2] rust: add 'firmware' field support to module! macro
Date: Sun, 12 May 2024 18:53:56 +0200 [thread overview]
Message-ID: <CANiq72kJQp_GHnr2cD7e8s5CJ=Sawz9ad_QVFrUxqDUppe4FNw@mail.gmail.com> (raw)
In-Reply-To: <20240509.085826.1793889118157877475.fujita.tomonori@gmail.com>
On Thu, May 9, 2024 at 1:58 AM FUJITA Tomonori
<fujita.tomonori@gmail.com> wrote:
>
> I'll try to push QT2025 for 6.11 via netdev tree. So I hope features
> which QT2025 needs to be merged for 6.10, especially a feature that
> would be conflicted in rust and netdev trees.
>
> That's exactly why I hope that this patch is merged for 6.10, as I
> wrote above. The cleanup will be merged via rust tree. It makes
> complicated to put this patch into QT2025 patchset for netdev tree.
>
> But I don't think that this patch is an exception to the -rc5 rule. So
> please push this patch for 6.11. I'll think about a way to push
> QT2025.
Thanks for confirming. If netdev wants to apply QT2025 for 6.11, they
could perhaps carry this patch with our Acked-by -- it seems simple
enough. Another option is creating a branch and merge it in both trees
if needed.
Cheers,
Miguel
prev parent reply other threads:[~2024-05-12 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 12:35 [PATCH v2] rust: add 'firmware' field support to module! macro FUJITA Tomonori
2024-05-07 23:11 ` FUJITA Tomonori
2024-05-08 14:46 ` Miguel Ojeda
2024-05-08 23:58 ` FUJITA Tomonori
2024-05-12 16:53 ` Miguel Ojeda [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='CANiq72kJQp_GHnr2cD7e8s5CJ=Sawz9ad_QVFrUxqDUppe4FNw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=benno.lossin@proton.me \
--cc=fujita.tomonori@gmail.com \
--cc=rust-for-linux@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).