linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Osipenko <digetx@gmail.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Franky Lin <franky.lin@broadcom.com>,
	Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Wright Feng <wright.feng@cypress.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v2 1/2] cfg80211: Add wiphy_info_once()
Date: Wed, 23 Jun 2021 10:15:47 +0200	[thread overview]
Message-ID: <4485b4d67e7d54702f7c35a0f6fe6ffd24b613be.camel@sipsolutions.net> (raw)
In-Reply-To: <46a3cb5a-2ce3-997b-154d-dd4e1b7333d1@gmail.com> (sfid-20210619_130247_991465_6815775A)

On Sat, 2021-06-19 at 14:02 +0300, Dmitry Osipenko wrote:
> 
> Johannes, are these patches good to you?
> 
Yeah, that's fine. I was going to pick it up now but I guess it'll be
faster for Kalle to do that, so

Acked-by: Johannes Berg <johannes@sipsolutions.net>

and I'll assign it to Kalle in patchwork.

johannes


  reply	other threads:[~2021-06-23  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 21:15 [PATCH v2 1/2] cfg80211: Add wiphy_info_once() Dmitry Osipenko
2021-05-11 21:15 ` [PATCH v2 2/2] brcmfmac: Silence error messages about unsupported firmware features Dmitry Osipenko
2021-06-18 20:44 ` [PATCH v2 1/2] cfg80211: Add wiphy_info_once() Dmitry Osipenko
2021-06-19  6:27   ` Kalle Valo
2021-06-19 11:02     ` Dmitry Osipenko
2021-06-23  8:15       ` Johannes Berg [this message]
2021-06-23 17:46 ` Kalle Valo

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=4485b4d67e7d54702f7c35a0f6fe6ffd24b613be.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=andy.shevchenko@gmail.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=davem@davemloft.net \
    --cc=digetx@gmail.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wright.feng@cypress.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).