linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: pmarzo <marzo.pedro@gmail.com>
Cc: devel@driverdev.osuosl.org, haticeerturk27@gmail.com,
	linux-kernel@vger.kernel.org, joe@perches.com,
	dilekuzulmez@gmail.com, navyasri.tech@gmail.com
Subject: Re: [PATCH 2/3 v4] Staging: rtl8192u: Remove two useless lines at ieee80211_wep_null
Date: Tue, 2 Jun 2015 22:40:43 +0900	[thread overview]
Message-ID: <20150602134043.GA16837@kroah.com> (raw)
In-Reply-To: <1433252105.20244.3.camel@CEM14014B>

On Tue, Jun 02, 2015 at 03:35:05PM +0200, pmarzo wrote:
> Ok, I will download your staging tree and regenerate patches 1/3 and 2/3
> with that git tree. That would be v5 1/2 and 2/2 new patches.
> Just one (probably very stupid) question, why do you need me to resend
> the patches? I mean, both of them apply cleanly to your staging tree
> with patch 3/3 already merged.

Because I don't have them in my inbox anywhere.

I average about 1000 emails a day, not including high-volume mailing
lists (lkml, linux-fsdev, etc.)  Once I deal with an email, I delete it
as it does me no good to keep them around for no reason.

thanks,

greg k-h

  reply	other threads:[~2015-06-02 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  0:25 [PATCH 0/3 v4] Staging: rtl8192u: Fix coding style issues at ieee80211_crypt_wep.c Pedro Marzo Perez
2015-05-21  0:25 ` [PATCH 1/3 v4] Staging: rtl8192u: Simplify error check code at prism2_wep_init Pedro Marzo Perez
2015-05-21  0:25 ` [PATCH 2/3 v4] Staging: rtl8192u: Remove two useless lines at ieee80211_wep_null Pedro Marzo Perez
2015-05-31  1:39   ` Greg KH
2015-06-01 22:19     ` pmarzo
2015-06-02  5:21       ` Greg KH
2015-06-02  8:08         ` pmarzo
2015-06-02  8:25           ` Greg KH
2015-06-02 13:35             ` pmarzo
2015-06-02 13:40               ` Greg KH [this message]
2015-06-03  7:20                 ` pmarzo
2015-05-21  0:25 ` [PATCH 3/3 v4] Staging: rtl8192u: Correct include indentation and openning braces at new line Pedro Marzo Perez

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=20150602134043.GA16837@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dilekuzulmez@gmail.com \
    --cc=haticeerturk27@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marzo.pedro@gmail.com \
    --cc=navyasri.tech@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;
as well as URLs for NNTP newsgroup(s).