Re: [git pull] New firewire stack (updated)

Christoph Hellwig wrote:
> ACK from me.  I still have some comments but none of them is a merge
> blocker.

I put one small fix that Kristian sent on hold (const char * vs char *
for shostt->proc_name) to let a related patch go to scsi-misc first.
So this open item is my fault, not his. :-)
-- 
Stefan Richter
-=====-=-=== -=-= -=-=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [git pull] New firewire stack
  - From: Kristian Høgsberg <[email protected]>
- [git pull] New firewire stack (updated)
  - From: Stefan Richter <[email protected]>
- Re: [git pull] New firewire stack (updated)
  - From: Christoph Hellwig <[email protected]>

Prev by Date: Re: [RFC] memory hotremove patch take 2 [02/10] (make page unused)
Next by Date: Re: [RFC] memory hotremove patch take 2 [03/10] (drain all pages)
Previous by thread: Re: [git pull] New firewire stack (updated)
Next by thread: Re: [git pull] New firewire stack
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]