From: Mike Christie <michaelc@cs.wisc.edu>
To: Konrad Rzeszutek <konrad@darnok.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, greg@kroah.com, dwm@enoyolf.org,
darnok@68k.org, pjones@redhat.com, konradr@redhat.com,
konradr@linux.vnet.ibm.com, randy.dunlap@oracle.com,
hpa@zytor.com, lenb@kernel.org, mike.anderson@us.ibm.com,
dwm@austin.ibm.com, arjan@infradead.org,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH] Add iSCSI iBFT support (v0.4.5)
Date: Tue, 29 Jan 2008 13:13:28 -0600 [thread overview]
Message-ID: <479F7AD8.5050707@cs.wisc.edu> (raw)
In-Reply-To: <200801281404.54155.konrad@darnok.org>
Konrad Rzeszutek wrote:
> On Sunday 27 January 2008 01:01:23 you wrote:
>>> On Fri, 25 Jan 2008 18:06:29 -0400 Konrad Rzeszutek <konrad@darnok.org>
>>> wrote: Hey Andrew,
>>>
>>> Please add this patch along with Greg KH's kobject fixes.
>> erm, OK. But I don't think I'm the appropriate conduit for iscsi paches.
>>
>> By what path _does_ iscsi ode get into the tree, anyway? Mike is listed as
>> maintainer...
>
> This is a bit tricky b/c this goes to the drivers/firmware and also depends on
> the kobject changes in Greg KH tree. But I should have included Mike on the
> CC which I keep on forgetting <sigh>.
>
It is probably better if it goes through Greg or Andrew. It will not
conflict with any iscsi patches. It looks like it is heavier on kobject
and sysfs and has some acpi digging magic, and almost no iscsi stuff in
there.
next prev parent reply other threads:[~2008-01-29 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:06 [PATCH] Add iSCSI iBFT support (v0.4.5) Konrad Rzeszutek
2008-01-27 6:01 ` Andrew Morton
2008-01-27 6:01 ` Andrew Morton
2008-01-27 16:47 ` Randy Dunlap
2008-01-28 11:27 ` Andy Whitcroft
2008-01-28 19:04 ` Konrad Rzeszutek
2008-01-28 19:11 ` Doug Maxey
2008-01-28 19:35 ` H. Peter Anvin
2008-01-28 20:46 ` Konrad Rzeszutek
2008-01-28 21:13 ` Peter Jones
2008-01-30 21:47 ` Konrad Rzeszutek
2008-01-29 19:13 ` Mike Christie [this message]
2008-01-29 19:44 ` 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=479F7AD8.5050707@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=arjan@infradead.org \
--cc=darnok@68k.org \
--cc=dwm@austin.ibm.com \
--cc=dwm@enoyolf.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=konrad@darnok.org \
--cc=konradr@linux.vnet.ibm.com \
--cc=konradr@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.anderson@us.ibm.com \
--cc=pjones@redhat.com \
--cc=randy.dunlap@oracle.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.