From: Kalle Valo <kvalo@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v1 1/1] wireless: Add KHZ_PER_GHZ to units.h and reuse
Date: Tue, 20 Feb 2024 18:57:24 +0200 [thread overview]
Message-ID: <874je3m5u3.fsf@kernel.org> (raw)
In-Reply-To: <ZdS2dRBPY8mj58rX@smile.fi.intel.com> (Andy Shevchenko's message of "Tue, 20 Feb 2024 16:25:57 +0200")
Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
> On Thu, Feb 15, 2024 at 07:23:06PM +0200, Kalle Valo wrote:
>> Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
>>
>> > The KHZ_PER_GHZ might be used by others (with the name aligned
>> > with similar constants). Define it in units.h and convert
>> > wireless to use it.
>
>> wireless patches go to wireless-next, not net-next. But no need resend
>> because of this.
>
> Aha, thanks. Note, I still don't see it in wireless-next tree. Is everything
> on track?
Yes, it's queued in patchwork:
https://patchwork.kernel.org/project/linux-wireless/patch/20240215154136.630029-1-andriy.shevchenko@linux.intel.com/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-02-20 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 15:41 [PATCH net-next v1 1/1] wireless: Add KHZ_PER_GHZ to units.h and reuse Andy Shevchenko
2024-02-15 17:23 ` Kalle Valo
2024-02-20 14:25 ` Andy Shevchenko
2024-02-20 16:57 ` Kalle Valo [this message]
2024-02-19 10:52 ` Simon Horman
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=874je3m5u3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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;
as well as URLs for NNTP newsgroup(s).