All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: jeremy.katz@gmail.com, akpm@osdl.org, jgarzik@pobox.com,
	katzj@redhat.com, linux-kernel@vger.kernel.org,
	torvalds@osdl.org
Subject: Re: [PATCH] PPC64 iSeries viodasd proc file
Date: Wed, 23 Jun 2004 16:55:38 -0700	[thread overview]
Message-ID: <20040623235538.GA22791@kroah.com> (raw)
In-Reply-To: <200406232354.i5NNsnCL029470@supreme.pcug.org.au>

On Thu, Jun 24, 2004 at 09:54:49AM +1000, Stephen Rothwell wrote:
> From: Greg KH <greg@kroah.com>
> > 
> > I agree, I don't think that many things have disappeared from /proc just
> > yet, right?  You should just have more information than what you
> > previously did, right?  Or did scsi drop their /proc support fully?
> 
> What started this discussion is that I had to drop all the proc support
> from the iSeries virtual devices while attempting to get the drivers
> into the mainline kernel.

Ok, but that support was never in mainline, right?  :)

Yeah I know, distro trees...

greg k-h

  reply	other threads:[~2004-06-23 23:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 23:54 [PATCH] PPC64 iSeries viodasd proc file Stephen Rothwell
2004-06-23 23:55 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-06-18  6:54 Stephen Rothwell
2004-06-18 15:09 ` Jeff Garzik
2004-06-18 15:17   ` Christoph Hellwig
2004-06-20 19:52     ` Jeremy
2004-06-20 21:11       ` Christoph Hellwig
2004-06-21  6:04       ` Greg KH
     [not found]         ` <cb5afee10406210914451dc6@mail.gmail.com>
2004-06-23 21:15           ` Jeremy Katz
2004-06-23 21:45             ` Jeff Garzik
2004-06-23 22:03             ` Greg KH
2004-06-24  0:38               ` Jeff Garzik
2004-06-24 20:59                 ` Greg KH
2004-06-24 21:25                   ` Jeff Garzik

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=20040623235538.GA22791@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=jeremy.katz@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=katzj@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 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.