All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Yunpeng Gao <yunpeng.gao@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for June 3 (staging)
Date: Thu, 4 Jun 2009 09:00:23 -0700	[thread overview]
Message-ID: <20090604160023.GA20118@suse.de> (raw)
In-Reply-To: <20090604232610.GA16053@intel.com>

On Fri, Jun 05, 2009 at 07:26:10AM +0800, Yunpeng Gao wrote:
> Hi Greg,
>    I have fixed these compiling bugs in file ffsport.c.

Great.

>    But just found that my email client (Outlook) will replace
>    TAB with blanks automatically. So, unfortunately, all the
>    TABs in my first submission patch have been changed to
>    blanks by the Outlook.

Heh.

>    So I'd like to use the Mutt email client and re-submit
>    the patch as below (the bug-fix of ffsport.c has been included).
>    Does it make sense?

Sure, I can replace the existing patch with this one if you want me to.
I'll go queue it up.

thanks,

greg k-h

  reply	other threads:[~2009-06-04 16:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  9:09 linux-next: Tree for June 3 Stephen Rothwell
2009-06-03 15:22 ` linux-next: Tree for June 3 (rfkill) Randy Dunlap
2009-06-03 15:29   ` Johannes Berg
     [not found]     ` <1244042950.4862.10.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-03 15:47       ` Gábor Stefanik
2009-06-03 15:47         ` Gábor Stefanik
2009-06-03 15:53         ` Johannes Berg
     [not found]   ` <4A269539.8020607-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-06-03 16:27     ` Johannes Berg
2009-06-03 16:27       ` Johannes Berg
2009-06-03 17:20   ` Randy Dunlap
2009-06-03 17:20     ` Randy Dunlap
2009-06-03 17:33     ` Johannes Berg
     [not found]       ` <1244050400.22105.0.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-03 22:48         ` Inaky Perez-Gonzalez
2009-06-03 22:48           ` Inaky Perez-Gonzalez
2009-06-03 15:24 ` linux-next: Tree for June 3 (staging) Randy Dunlap
2009-06-03 15:25   ` Greg KH
2009-06-03 15:40     ` Randy Dunlap
2009-06-03 23:11       ` Greg KH
2009-06-04  2:04         ` Gao, Yunpeng
2009-06-04  2:04           ` Gao, Yunpeng
2009-06-04 23:26         ` Yunpeng Gao
2009-06-04 16:00           ` Greg KH [this message]
2009-06-04 17:52           ` Greg KH
2009-06-05  3:31             ` Gao, Yunpeng
2009-06-05 18:58               ` Bartlomiej Zolnierkiewicz
2009-06-05 19:22                 ` Greg KH
2009-06-06 16:30                   ` Yunpeng Gao
2009-06-06  8:37                 ` Gao, Yunpeng
2009-06-04 22:07           ` mISDN: WARNING: at kernel/softirq.c:124 local_bh_enable+0x8f/0xb0() Mathias Kretschmer
2009-06-05  2:59             ` Andrew Morton
2009-06-05 10:01               ` Karsten Keil
2009-06-09 13:05                 ` Karsten Keil
2009-06-22 22:37                   ` Mathias Kretschmer
2009-06-05 18:45           ` linux-next: Tree for June 3 (staging) Bartlomiej Zolnierkiewicz
2009-06-05 20:15             ` Alan Cox
2009-06-06  8:35               ` Gao, Yunpeng
2009-06-03 15:44 ` linux-next: Tree for June 3 (staging++) Randy Dunlap
2009-06-03 15:50 ` linux-next: Tree for June 3 (driver core) Randy Dunlap
2009-06-03 21:22   ` Greg KH
2009-06-03 21:44     ` Eric W. Biederman

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=20090604160023.GA20118@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yunpeng.gao@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.