From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>,
"justinstitt@google.com" <justinstitt@google.com>
Cc: "Coelho, Luciano" <luciano.coelho@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Berg, Johannes" <johannes.berg@intel.com>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Stern, Avraham" <avraham.stern@intel.com>,
"nathan@kernel.org" <nathan@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>,
"edumazet@google.com" <edumazet@google.com>,
"trix@redhat.com" <trix@redhat.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>
Subject: Re: [PATCH] iwlwifi: mvm: fix clang -Wformat warnings
Date: Thu, 4 Aug 2022 10:23:14 +0000 [thread overview]
Message-ID: <b084853fe9d9bac6b3d5fd037053b09cce0aa6bb.camel@intel.com> (raw)
In-Reply-To: <87sfmoq786.fsf@kernel.org>
On Tue, 2022-07-26 at 17:27 +0300, Kalle Valo wrote:
> Justin Stitt <justinstitt@google.com> writes:
>
> > Any chance a maintainer could take a look at this patch? I am trying
> > to get it through this cycle and we are so close to enabling the
> > -Wformat option for Clang. There's only a handful of patches remaining
> > until the patch enabling this warning can be sent!
>
> Gregory, can I take this directly to wireless-next? I assigned it to me
> in patchwork.
>
Sorry for the long delay. Yes, it looks like a good fix. Thanks!
next prev parent reply other threads:[~2022-08-04 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:29 Justin Stitt
2022-07-18 17:37 ` Justin Stitt
2022-07-26 14:27 ` Kalle Valo
2022-08-04 10:23 ` Greenman, Gregory [this message]
2022-07-18 20:58 ` Nick Desaulniers
2022-07-27 10:48 ` wifi: " 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=b084853fe9d9bac6b3d5fd037053b09cce0aa6bb.camel@intel.com \
--to=gregory.greenman@intel.com \
--cc=avraham.stern@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes.berg@intel.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luciano.coelho@intel.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=trix@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
all inboxes | Powered by JetHome®