public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Joe Perches <joe@perches.com>, Ryan Mallon <rmallon@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] coda: Remove unnecessary OOM messages
Date: Tue, 31 Jan 2012 22:10:45 -0500	[thread overview]
Message-ID: <189650fe-7304-4762-a353-e355609f3e84@email.android.com> (raw)
In-Reply-To: <1328055976.14714.7.camel@joe2Laptop>

Joe Perches <joe@perches.com> wrote:

>On Wed, 2012-02-01 at 11:23 +1100, Ryan Mallon wrote:
>> On 01/02/12 11:21, Joe Perches wrote:
>> > Maybe because alloc/free functions are
>> > used relatively infrequently, maybe it'd
>> > be better to not declare the functions
>> > inline but add them to coda_linux.c
>> Sure, either approach is fine. Do you want to add the patch to your
>series?
>
>I think Jan can work it out properly if he wants it.

It looks good to me, I have no problem if you want to add it to your series.

Jan


  reply	other threads:[~2012-02-01  3:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 22:42 [PATCH 0/4] fs: Remove unnecessary OOM messages Joe Perches
2012-01-31 22:42 ` [PATCH 1/4] coda: " Joe Perches
2012-02-01  0:04   ` Ryan Mallon
2012-02-01  0:21     ` Joe Perches
2012-02-01  0:23       ` Ryan Mallon
2012-02-01  0:26         ` Joe Perches
2012-02-01  3:10           ` Jan Harkes [this message]
2012-02-01  3:42             ` Joe Perches
2012-01-31 22:42 ` [PATCH 2/4] jffs2: " Joe Perches
2012-02-03  7:00   ` Artem Bityutskiy
2012-01-31 22:42 ` [PATCH 3/4] reiserfs: " Joe Perches
2012-01-31 22:42 ` [PATCH 4/4] udf: " Joe Perches
2012-02-01 11:28   ` Jan Kara

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=189650fe-7304-4762-a353-e355609f3e84@email.android.com \
    --to=jaharkes@cs.cmu.edu \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmallon@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