From: Kalle Valo <kvalo@codeaurora.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 5/6] ath9k: make relay callbacks const
Date: Wed, 18 Nov 2020 19:15:39 +0200 [thread overview]
Message-ID: <87eekqvb5w.fsf@codeaurora.org> (raw)
In-Reply-To: <87y2iyvbpr.fsf@codeaurora.org> (Kalle Valo's message of "Wed, 18 Nov 2020 19:03:44 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Jani Nikula <jani.nikula@intel.com> writes:
>
>> Now that relay_open() accepts const callbacks, make relay callbacks
>> const.
>>
>> Cc: Kalle Valo <kvalo@codeaurora.org>
>> Cc: QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
>> Cc: linux-wireless@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Can I take this to my ath tree or what's the plan?
Ah, saw patch 1 only now. So I assume this goes via some other tree:
Acked-by: Kalle Valo <kvalo@codeaurora.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
Subject: Re: [Intel-gfx] [PATCH 5/6] ath9k: make relay callbacks const
Date: Wed, 18 Nov 2020 19:15:39 +0200 [thread overview]
Message-ID: <87eekqvb5w.fsf@codeaurora.org> (raw)
In-Reply-To: <87y2iyvbpr.fsf@codeaurora.org> (Kalle Valo's message of "Wed, 18 Nov 2020 19:03:44 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Jani Nikula <jani.nikula@intel.com> writes:
>
>> Now that relay_open() accepts const callbacks, make relay callbacks
>> const.
>>
>> Cc: Kalle Valo <kvalo@codeaurora.org>
>> Cc: QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
>> Cc: linux-wireless@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Can I take this to my ath tree or what's the plan?
Ah, saw patch 1 only now. So I assume this goes via some other tree:
Acked-by: Kalle Valo <kvalo@codeaurora.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-18 17:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 16:53 [PATCH 1/6] relay: allow the use of const callback structs Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-18 16:53 ` [PATCH 2/6] drm/i915: make relay callbacks const Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` [PATCH 3/6] ath10k: " Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-18 17:13 ` Kalle Valo
2020-11-18 17:13 ` [Intel-gfx] " Kalle Valo
2020-11-18 17:13 ` Kalle Valo
2020-11-18 16:53 ` [PATCH 4/6] ath11k: " Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-19 9:31 ` Jani Nikula
2020-11-19 9:31 ` [Intel-gfx] " Jani Nikula
2020-11-19 9:31 ` Jani Nikula
2020-11-19 11:40 ` Kalle Valo
2020-11-19 11:40 ` [Intel-gfx] " Kalle Valo
2020-11-19 11:40 ` Kalle Valo
2020-11-18 16:53 ` [PATCH 5/6] ath9k: " Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 17:03 ` Kalle Valo
2020-11-18 17:03 ` [Intel-gfx] " Kalle Valo
2020-11-18 17:15 ` Kalle Valo [this message]
2020-11-18 17:15 ` Kalle Valo
2020-11-18 16:53 ` [PATCH 6/6] blktrace: " Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 18:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] relay: allow the use of const callback structs Patchwork
2020-11-18 18:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-11-18 19:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-19 4:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-11-19 8:11 ` [PATCH 1/6] " Christoph Hellwig
2020-11-19 8:11 ` [Intel-gfx] " Christoph Hellwig
2020-11-19 8:11 ` Christoph Hellwig
2020-11-19 8:11 ` Christoph Hellwig
2020-11-19 8:11 ` Christoph Hellwig
2020-11-19 8:11 ` [Intel-gfx] " Christoph Hellwig
2020-11-19 8:11 ` Christoph Hellwig
2020-11-19 8:11 ` Christoph Hellwig
2020-11-23 18:01 ` Jani Nikula
2020-11-23 18:01 ` [Intel-gfx] " Jani Nikula
2020-11-23 18:01 ` Jani Nikula
2020-11-23 18:01 ` Jani Nikula
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=87eekqvb5w.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.