All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Oleg Drokin <oleg.drokin@intel.com>
Subject: Re: [PATCH 5/5] lustre: add myself to list of people to CC on lustre patches
Date: Fri, 24 Jan 2014 11:12:58 +0300	[thread overview]
Message-ID: <20140124081258.GE7444@mwanda> (raw)
In-Reply-To: <1390538708-4120-6-git-send-email-green@linuxhacker.ru>

On Thu, Jan 23, 2014 at 11:45:08PM -0500, Oleg Drokin wrote:
> Signed-off-by: Oleg Drokin <oleg.drokin@intel.com>

Add yourself to MAINTAINERS if you really want email.  No one reads
the email addresses here.

regards,
dan carpenter


      parent reply	other threads:[~2014-01-24  8:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  4:45 [PATCH 0/5] Lustre fixes from my testing Oleg Drokin
2014-01-24  4:45 ` [PATCH 1/5] staging/lustre: fix compile warning with is_vmalloc_addr Oleg Drokin
2014-01-24  4:45 ` [PATCH 2/5] staging/lustre/lnet: Fix use after free in ksocknal_send Oleg Drokin
2014-01-24  4:45 ` [PATCH 3/5] lustre: Account for changelog_ext_rec in CR_MAXSIZE Oleg Drokin
2014-01-24  4:45 ` [PATCH 4/5] lustre: Correct KUC code max changelog msg size Oleg Drokin
2014-01-24  4:45 ` [PATCH 5/5] lustre: add myself to list of people to CC on lustre patches Oleg Drokin
2014-01-24  5:44   ` Joe Perches
2014-01-24  5:51     ` Oleg Drokin
2014-01-24  8:55       ` Geert Uytterhoeven
2014-01-25  3:23         ` Oleg Drokin
2014-01-28 19:28           ` Geert Uytterhoeven
2014-01-29 13:02             ` Greg Kroah-Hartman
2014-03-26  8:44           ` Geert Uytterhoeven
2014-03-26  9:02             ` Christoph Hellwig
2014-03-26 16:10             ` Oleg Drokin
2014-01-24  8:12   ` Dan Carpenter [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=20140124081258.GE7444@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=green@linuxhacker.ru \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.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.