From: Kalle Valo <kvalo@codeaurora.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Joe Perches <joe@perches.com>,
linux-wireless@vger.kernel.org, kbuild test robot <lkp@intel.com>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: wireless-drivers: random cleanup patches piling up
Date: Mon, 01 Feb 2016 08:21:48 +0000 [thread overview]
Message-ID: <878u34j0wz.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160201044142.GC4072@sudip-pc> (Sudip Mukherjee's message of "Mon, 1 Feb 2016 10:11:42 +0530")
Sudip Mukherjee <sudipm.mukherjee@gmail.com> writes:
> Sure, I am starting that way. I checked in patchwork and I do not see
> any checkpatch related patch pending (except staging, which Greg will
> handle). I think you must have cleared all of them.
They are in deferred state. The search functionality in patchwork is not
that intuitive and they are not easy to find so here's a direct link:
https://patchwork.kernel.org/project/linux-wireless/list/?state\x10&orderÚte
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-01 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wpr3x9ln.fsf@kamboji.qca.qualcomm.com>
2016-01-22 0:52 ` wireless-drivers: random cleanup patches piling up Joe Perches
2016-01-22 7:30 ` Dan Carpenter
2016-01-22 12:21 ` Kalle Valo
2016-01-22 15:12 ` John W. Linville
2016-01-22 15:54 ` Kalle Valo
2016-01-26 5:40 ` Sudip Mukherjee
2016-01-29 8:08 ` Kalle Valo
2016-02-01 4:53 ` Sudip Mukherjee
2016-02-01 8:21 ` Kalle Valo [this message]
2016-03-16 0:57 ` Julian Calaby
2016-03-16 9:22 ` Kalle Valo
2016-03-16 9:42 ` Julian Calaby
2016-03-18 1:06 ` Julian Calaby
2016-01-22 18:05 ` Joe Perches
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=878u34j0wz.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lkp@intel.com \
--cc=sudipm.mukherjee@gmail.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