All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Darshana Padmadas <darshanapadmadas@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 0/5] Replace memcpy with ether_addr_copy and fix checkpatch warning
Date: Wed, 18 Mar 2015 14:37:44 +0100	[thread overview]
Message-ID: <20150318133744.GA9270@kroah.com> (raw)
In-Reply-To: <c163a2cd-36f7-440f-8857-93eeace05b5c@googlegroups.com>

On Wed, Mar 18, 2015 at 06:05:16AM -0700, Darshana Padmadas wrote:
> Sorry, about that. Have sent v2 for patches 1/5 and 2/5 that broke the build.

Please resend everything, the whole patch set is long-gone from my
queue.

thanks,

greg k-h


      reply	other threads:[~2015-03-18 13:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 19:18 [PATCH 0/5] Replace memcpy with ether_addr_copy and fix checkpatch warning Darshana Padmadas
2015-03-16 19:18 ` [PATCH 1/5] Staging: rtl8192e: Replace memcpy with ether_addr_copy Darshana Padmadas
     [not found]   ` <cover.1426681038.git.darshanapadmadas@gmail.com>
2015-03-18 12:34     ` [PATCH v2 " Darshana Padmadas
2015-03-18 12:36       ` [Outreachy kernel] " Julia Lawall
2015-03-18 12:35     ` [PATCH v2 2/5] Staging: rtl8192e: Use ether_addr_copy instead of memcpy Darshana Padmadas
2015-03-18 13:01       ` [PATCH v3 " Darshana Padmadas
2015-03-16 19:18 ` [PATCH " Darshana Padmadas
2015-03-16 19:18 ` [PATCH 3/5] Staging: rtl8192e: Use ether_addr_copy replacing memcpy Darshana Padmadas
2015-03-16 19:18 ` [PATCH 4/5] Staging: rtl8192e: Use ether_addr_copy for aligned addresses Darshana Padmadas
2015-03-16 19:18 ` [PATCH 5/5] Staging: rtl8192e: replace memcpy with ether_addr_copy for aligned structures Darshana Padmadas
2015-03-17 15:33 ` [Outreachy kernel] [PATCH 0/5] Replace memcpy with ether_addr_copy and fix checkpatch warning Jes Sorensen
2015-03-18 10:19 ` Greg KH
2015-03-18 13:05   ` Darshana Padmadas
2015-03-18 13:37     ` Greg KH [this message]

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=20150318133744.GA9270@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=darshanapadmadas@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 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.