Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandriva.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Bernhard Walle <walle@corscience.de>,
	linux-mips@linux-mips.org, ralf@linux-mips.org,
	ddaney@caviumnetworks.com, akpm@linux-foundation.org,
	ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: N32: Fix getdents64 syscall for n32
Date: Fri, 03 Sep 2010 10:53:31 +0200	[thread overview]
Message-ID: <m3pqwvb438.fsf@anduin.mandriva.com> (raw)
In-Reply-To: <20100903084213.GA32339@lst.de> (Christoph Hellwig's message of "Fri, 3 Sep 2010 10:42:13 +0200")

Christoph Hellwig <hch@lst.de> writes:

Hi,

> I'm not sure why people suddenly started Ccing me on utterly random
> patches, but could you guys please bloody stop it?  Thanks!

I guess the explanation is the one below :

$ ./scripts/get_maintainer.pl -f arch/mips/kernel/scall64-n32.S
Ralf Baechle <ralf@linux-mips.org>
David Daney <ddaney@caviumnetworks.com>
Andrew Morton <akpm@linux-foundation.org>
"Eric W. Biederman" <ebiederm@xmission.com>
Christoph Hellwig <hch@lst.de>
linux-mips@linux-mips.org
linux-kernel@vger.kernel.org


Arnaud

  reply	other threads:[~2010-09-03  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  8:15 [PATCH] MIPS: N32: Fix getdents64 syscall for n32 Bernhard Walle
2010-09-03  8:42 ` Christoph Hellwig
2010-09-03  8:53   ` Arnaud Patard [this message]
2010-09-03  8:55     ` Christoph Hellwig
2010-09-03  9:13     ` Bernhard Walle
2010-09-03 10:01       ` Ralf Baechle
2010-09-03 11:27         ` Bernhard Walle
2010-09-19 23:51 ` Ralf Baechle
2010-09-21  7:49   ` Bernhard Walle
  -- strict thread matches above, loose matches on Subject: below --
2010-09-08  7:35 Bernhard Walle

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=m3pqwvb438.fsf@anduin.mandriva.com \
    --to=apatard@mandriva.com \
    --cc=akpm@linux-foundation.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=ebiederm@xmission.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=walle@corscience.de \
    /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