From: Ivan Safonov <insafonov@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Michael Straube <straube.linux@gmail.com>,
gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "staging:r8188eu: use lib80211 CCMP decrypt"
Date: Wed, 2 Jan 2019 22:03:32 +0300 [thread overview]
Message-ID: <0acf4a76-c5e2-9a5f-bc57-04794b515107@gmail.com> (raw)
In-Reply-To: <99d2e692-6a6b-b880-c8c2-99944f8a5f52@lwfinger.net>
On 1/2/19 12:38 AM, Larry Finger wrote:
> On 1/1/19 3:02 AM, Ivan Safonov wrote:
>> I suggested a patch for loading modules from interruptible mode, but
>> this patch remained unclaimed (
>> http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-August/124851.html
>> ).
>>
>> For some reason I thought that this patch had been removed and did not
>> track the fate of this code (
>> http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-August/124573.html
>> ).
>
> That patch was quite extensive, but had only a minimal commit message.
> I'm surprised that it did not get a bad review, but I can see why it was
> ignored.
> > Where did you submit that patch? It certainly was never in my mailbox.
I send patches to emails from get_maintainer.pl list:
ivan@alpha ~/source/kernels/staging $ git format-patch
515ce733e86ee2e1bea4dba76d2d4491013d0f73^..515ce733e86ee2e1bea4dba76d2d4491013d0f73
-o /tmp/
/tmp/0001-staging-r8188eu-Use-lib80211-to-encrypt-CCMP-tx-fram.patch
ivan@alpha ~/source/kernels/staging $ ./scripts/get_maintainer.pl
/tmp/0001-staging-r8188eu-Use-lib80211-to-encrypt-CCMP-tx-fram.patch
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING
SUBSYSTEM,commit_signer:16/16=100%,authored:1/16=6%,added_lines:345/1450=24%)
Ivan Safonov <insafonov@gmail.com>
(commit_signer:7/16=44%,authored:6/16=38%,added_lines:337/1450=23%,removed_lines:1380/1605=86%)
Michael Straube <straube.linux@gmail.com>
(commit_signer:6/16=38%,authored:6/16=38%,added_lines:715/1450=49%,removed_lines:92/1605=6%)
Santha Meena Ramamoorthy <santhameena13@gmail.com>
(commit_signer:2/16=12%,authored:2/16=12%)
Dan Carpenter <dan.carpenter@oracle.com> (commit_signer:1/16=6%)
Hans de Goede <hdegoede@redhat.com> (authored:1/16=6%)
devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
There is no your email.
>
> Larry
next prev parent reply other threads:[~2019-01-02 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 18:39 Michael Straube
2019-01-01 2:17 ` Larry Finger
2019-01-01 9:02 ` Ivan Safonov
2019-01-01 19:45 ` Michael Straube
2019-01-01 21:38 ` Larry Finger
2019-01-02 19:03 ` Ivan Safonov [this message]
2019-01-01 19:31 ` Michael Straube
2019-01-02 1:06 ` Larry Finger
2019-01-02 19:35 ` Ivan Safonov
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=0acf4a76-c5e2-9a5f-bc57-04794b515107@gmail.com \
--to=insafonov@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=straube.linux@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
all inboxes | Powered by JetHome®