linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
	jk@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [Patch next] powerpc: pseries/dtl.c should include asm/firmware.h
Date: Thu, 02 Apr 2009 11:01:00 +0530	[thread overview]
Message-ID: <49D44D94.1020702@in.ibm.com> (raw)
In-Reply-To: <25834.1238632443@neuling.org>

Michael Neuling wrote:
> It's great that you're sending patches to fix these issues but it's not
> quite formatted as the maintainers like.
>
> The patch needs to be included inline in the message, rather than as an
> attachment.  You can see it as an attachment here:
>   http://ozlabs.org/pipermail/linuxppc-dev/2009-April/070122.html
> .. as opposed to the required inline format like this patch:
>   http://ozlabs.org/pipermail/linuxppc-dev/2009-April/070120.html
>   
Yeah .. just being lazy. Moving from thunderbird to mutt have been
on my TODO list for a long time. I will use this as a trigger to
move to a different mail client. Thanks Mikey.

Regards
-Sachin


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

      reply	other threads:[~2009-04-02  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090401164450.f8192631.sfr@canb.auug.org.au>
2009-04-01 10:27 ` [Patch next] powerpc: pseries/dtl.c should include asm/firmware.h Sachin Sant
2009-04-02  0:34   ` Michael Neuling
2009-04-02  5:31     ` Sachin Sant [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=49D44D94.1020702@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=sfr@canb.auug.org.au \
    /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).