public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: linas@austin.ibm.com (Linas Vepstas)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <gregkh@suse.de>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] PCI patches for 2.6.16-rc1
Date: Wed, 1 Feb 2006 16:20:40 -0600	[thread overview]
Message-ID: <20060201222040.GM14705@austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601311813400.7301@g5.osdl.org>

On Tue, Jan 31, 2006 at 06:16:43PM -0800, Linus Torvalds was heard to remark:
> On Tue, 31 Jan 2006, Greg KH wrote:
> > 
> > linas:
> >       PCI Hotplug: PCI panic on dlpar add (add pci slot to running partition)
> >       PCI Hotplug/powerpc: module build break
> > 
> > linas@austin.ibm.com:
> >       powerpc/PCI hotplug: remove rpaphp_find_bus()
> >       powerpc/PCI hotplug: merge config_pci_adapter
> 
> Looks like Linas Vepstas doesn't have a good email address in his From: 
> fields.. As a result, the logs are nasty. 
> 
> Linas - could you _please_ fix your email setup, of if your email setup is 
> good, could whoever added the bogus "From: " line to the email please NOT 
> DO THAT HORRIBLE THING?

(OK, I'm red with embarrassment. I can only offer that email has
been an enemy for a while now).  

Is this better?

--linas

  parent reply	other threads:[~2006-02-01 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  2:04 [GIT PATCH] PCI patches for 2.6.16-rc1 Greg KH
2006-02-01  2:16 ` Linus Torvalds
2006-02-01  4:03   ` Greg KH
2006-02-01  4:19     ` Linus Torvalds
2006-02-01  7:21       ` Junio C Hamano
2006-02-01 22:20   ` Linas Vepstas [this message]
2006-02-01 22:39     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2006-01-20 19:04 Greg KH
2006-01-20 19:23 ` Greg KH

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=20060201222040.GM14705@austin.ibm.com \
    --to=linas@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=torvalds@osdl.org \
    /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