From: Kalle Valo <kvalo@codeaurora.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 00/19] Pending Cleanup patches for 4.7
Date: Fri, 15 Apr 2016 11:53:47 -0000 [thread overview]
Message-ID: <87mvovqea7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGRGNgUiREy2WsSD6iRZ+annBYv+dGgMWvASb=Y5+eT4gJYE_A@mail.gmail.com> (Julian Calaby's message of "Fri, 8 Apr 2016 10:56:22 +1000")
Julian Calaby <julian.calaby@gmail.com> writes:
>>> [1] Oddly I cannot find patch 19 from patchwork, I don't know what
>>> happened to it. I do see it on the mailing list, though.
>>
>> Actually another nacked patch 16 also has disappeared from patchwork, so
>> I'm not going to apply that either. I'm starting to wonder that maybe
>> you removed these yourself from patchwork?
>
> I did do that: I updated both to "Rejected" when people NACKed them.
>
> Should I not have done that? I thought I was making things easier for you.
That does help, but I started to wonder what happened to them (did I do
something wrong etc) before I realised that you actually dropped them
yourself. Patchwork is sometimes a bit clumsy like this, so maybe an
email reply like "dropping these from patchwork" or similar is a good
idea?
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "Alexander Tsoy" <alexander@tsoy.me>,
"Alexey Khoroshilov" <khoroshilov@ispras.ru>,
"Andrea Merello" <andrea.merello@gmail.com>,
"Arend van Spriel" <arend@broadcom.com>,
"Arnd Bergmann" <arnd@arndb.de>,
ath9k-devel@lists.ath9k.org,
b43-dev <b43-dev@lists.infradead.org>,
"brcm80211 development" <brcm80211-dev-list@broadcom.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Byeoungwook Kim" <quddnr145@gmail.com>,
"Chaoming Li" <chaoming_li@realsil.com.cn>,
"Colin Ian King" <colin.king@canonical.com>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Eliad Peller" <eliad@wizery.com>,
"Emmanuel Grumbach" <emmanuel.grumbach@intel.com>,
"Eyal Reizer" <eyalreizer@gmail.com>,
"Franky Lin" <frankyl@broadcom.com>,
"Geliang Tang" <geliangtang@163.com>,
"Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
"Hante Meuleman" <meuleman@broadcom.com>,
"Ivan Safonov" <insafonov@gmail.com>,
"Jia-Ju Bai" <baijiaju1990@163.com>,
"Johannes Berg" <johannes.berg@intel.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>,
"Lars-Peter Clausen" <lars@metafoo.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Luciano Coelho" <luca@coelho.fi>,
"Luis Felipe Dominguez Vega" <lfdominguez@nauta.cu>,
"Markus Elfring" <elfring@users.sourceforge.net>,
"Miaoqing Pan" <miaoqing@codeaurora.org>,
"Nicholas Mc Guire" <hofrat@osadl.org>,
"Nicolas Pitre" <nico@linaro.org>,
"Oleksij Rempel" <linux@rempel-privat.de>,
"Pieter-Paul Giesberts" <pieterpg@broadcom.com>,
"QCA ath9k Development" <ath9k-devel@qca.qualcomm.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Sara Sharon" <sarasharon1@gmail.com>,
"Shahar Patury" <shaharp@ti.com>,
"Stanislav Yakovlev" <stas.yakovlev@gmail.com>,
"Stanislaw Gruszka" <sgruszka@redhat.com>,
"Tony Lindgren" <tony@atomide.com>
Subject: Re: [PATCH 00/19] Pending Cleanup patches for 4.7
Date: Fri, 15 Apr 2016 14:53:20 +0300 [thread overview]
Message-ID: <87mvovqea7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGRGNgUiREy2WsSD6iRZ+annBYv+dGgMWvASb=Y5+eT4gJYE_A@mail.gmail.com> (Julian Calaby's message of "Fri, 8 Apr 2016 10:56:22 +1000")
Julian Calaby <julian.calaby@gmail.com> writes:
>>> [1] Oddly I cannot find patch 19 from patchwork, I don't know what
>>> happened to it. I do see it on the mailing list, though.
>>
>> Actually another nacked patch 16 also has disappeared from patchwork, so
>> I'm not going to apply that either. I'm starting to wonder that maybe
>> you removed these yourself from patchwork?
>
> I did do that: I updated both to "Rejected" when people NACKed them.
>
> Should I not have done that? I thought I was making things easier for you.
That does help, but I started to wonder what happened to them (did I do
something wrong etc) before I realised that you actually dropped them
yourself. Patchwork is sometimes a bit clumsy like this, so maybe an
email reply like "dropping these from patchwork" or similar is a good
idea?
--
Kalle Valo
next prev parent reply other threads:[~2016-04-15 11:53 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 2:20 [PATCH 00/19] Pending Cleanup patches for 4.7 Julian Calaby
2016-03-18 2:27 ` [ath9k-devel] " Julian Calaby
2016-03-18 2:16 ` [ath9k-devel] [PATCH 01/19] ath9k: Remove unnecessary ?: operator Julian Calaby
2016-03-18 2:16 ` Julian Calaby
2016-04-07 16:38 ` [01/19] " Kalle Valo
2016-04-07 16:38 ` [ath9k-devel] " Kalle Valo
2016-03-18 2:20 ` [PATCH 02/19] ipw2x00: use to_pci_dev() Julian Calaby
2016-03-24 22:28 ` Stanislav Yakovlev
2016-03-18 2:21 ` [PATCH 03/19] wlcore: use to_delayed_work() Julian Calaby
2016-03-18 2:22 ` [PATCH 04/19] wl1251: " Julian Calaby
2016-03-18 2:22 ` [PATCH 05/19] rtlwifi: " Julian Calaby
2016-03-18 2:44 ` Larry Finger
2016-03-18 2:22 ` [ath9k-devel] [PATCH 06/19] ath9k_htc: Delete unnecessary variable initialisation Julian Calaby
2016-03-18 2:22 ` Julian Calaby
2016-03-18 2:23 ` [PATCH 07/19] brcmfmac: " Julian Calaby
2016-03-18 2:23 ` [PATCH 08/19] iwlegacy: Return directly if allocation fails in il_eeprom_init() Julian Calaby
2016-03-18 13:41 ` SF Markus Elfring
2016-03-18 14:33 ` Julian Calaby
2016-03-18 14:53 ` Dan Carpenter
2016-03-19 13:16 ` Julian Calaby
2016-03-18 2:24 ` [PATCH 09/19] iwl4965: Fix a null pointer dereference in il_tx_queue_free and il_cmd_queue_free Julian Calaby
2016-03-18 2:24 ` [PATCH 10/19] b43: Fix memory leaks in b43_bus_dev_ssb_init and b43_bus_dev_bcma_init Julian Calaby
2016-03-18 2:24 ` [PATCH 11/19] rtl818x_pci: Disable pci device in error handling code Julian Calaby
2016-03-18 2:25 ` [PATCH DETAIL 12/19] rsi: Delete unnecessary variable initialisation Julian Calaby
2016-03-18 2:25 ` [PATCH DETAIL 13/19] " Julian Calaby
2016-03-19 12:27 ` SF Markus Elfring
2016-03-19 13:15 ` Julian Calaby
2016-03-18 2:27 ` [PATCH MOREWORK 14/19] rtl818x_pci: Fix a memory leak in rtl8180_init_rx_ring Julian Calaby
2016-04-08 1:38 ` Julian Calaby
[not found] ` <CAN8YU5OqKhqaucUs04Xe3wT8D1_p3B8miWKDQLv-aGakr12ZWA@mail.gmail.com>
2016-04-11 0:11 ` Julian Calaby
2016-04-12 21:13 ` Andrea Merello
2016-04-26 9:08 ` [MOREWORK, " Kalle Valo
2016-03-18 2:27 ` [PATCH MOREWORK 15/19] rsi: Move variable initialisation into error code Julian Calaby
2016-03-18 2:28 ` [PATCH MOREWORK 16/19] rtlwifi: Implement 'rtl_addr_delay()' with a switch statement Julian Calaby
2016-03-18 2:38 ` Larry Finger
2016-03-18 3:32 ` Julian Calaby
2016-03-18 2:28 ` [PATCH MOREWORK 17/19] iwl4965: Fix a memory leak in error handling code of __il4965_up Julian Calaby
2016-03-18 10:48 ` Stanislaw Gruszka
2016-03-18 11:12 ` Julian Calaby
2016-03-18 11:22 ` Stanislaw Gruszka
2016-03-18 2:29 ` [PATCH MOREWORK 18/19] iwl4965: Fix more memory leaks in __il4965_up() Julian Calaby
2016-03-18 10:53 ` Stanislaw Gruszka
2016-03-21 13:28 ` Stanislaw Gruszka
2016-03-18 2:29 ` [PATCH CONTROVERSIAL 19/19] iwlegacy: Rename label in il_eeprom_init() Julian Calaby
2016-03-18 10:31 ` Stanislaw Gruszka
2016-03-18 10:42 ` Julian Calaby
2016-03-18 11:01 ` Dan Carpenter
2016-03-18 11:14 ` Julian Calaby
2016-04-07 12:07 ` [PATCH 00/19] Pending Cleanup patches for 4.7 Kalle Valo
2016-04-07 12:08 ` [ath9k-devel] " Kalle Valo
2016-04-07 16:37 ` Kalle Valo
2016-04-07 16:38 ` [ath9k-devel] " Kalle Valo
2016-04-08 0:56 ` Julian Calaby
2016-04-08 1:26 ` [ath9k-devel] " Julian Calaby
2016-04-08 1:35 ` Julian Calaby
2016-04-08 1:36 ` [ath9k-devel] " Julian Calaby
2016-04-15 12:04 ` Kalle Valo
2016-04-15 12:04 ` [ath9k-devel] " Kalle Valo
2016-04-15 11:53 ` Kalle Valo [this message]
2016-04-15 11:53 ` 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=87mvovqea7.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@lists.ath9k.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.