From: Luben Tuikov <ltuikov-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
Subject: UASP: updates and merges
Date: Wed, 2 Mar 2011 11:05:05 -0800 (PST) [thread overview]
Message-ID: <147799.16314.qm@web31802.mail.mud.yahoo.com> (raw)
I've merged the latest master (dd9c154). The UASP driver saw the following update:
[USB] UASP: Unlock device after reset; EP updates
* Unlock the device after reset.
* Initialize urb->ep directly. struct
uasp_tport_info already records the struct
usb_host_endpoint which makes it easy to
directly initialize urb->ep. This anticipates
when drivers would have to initialize the ep in
the urb directly as opposed to the USB core
having to use pipes.
* Use the UAS pipe macros throughout the code for
endpoint indexes.
The branch can be found here off of master:
https://github.com/ltuikov/linux-2.6
Original posting of the UASP driver can be found here:
http://marc.info/?l=linux-usb&m=129165511732388&w=2
Luben
--- On Thu, 1/13/11, Luben Tuikov <ltuikov-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
> From: Luben Tuikov <ltuikov-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
> Subject: UASP: updates and merges
> To: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Greg KH" <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
> Date: Thursday, January 13, 2011, 2:45 AM
> The UASP driver allows you to connect
> to UAS devices and use them
> as SCSI devices.
>
> I've merged latest master (f87813) and resolved a conflict
> in drivers/scsi/sd.c by adding back the truncation of the
> mode sense data.
>
> The UASP driver saw the following update:
>
> [USB] UASP: factor out GFP flags and make
> them GFP_ATOMIC
>
> Factor out the GFP flags and make them
> atomic:
> 1) The SCSI subsystem uses GFP_ATOMIC, e.g.
> before
> calling the host's slave_alloc callback (at
> the
> time of this commit).
> 2) As we are a storage driver doing I/O, we
> should
> use the lowest denominator (highest
> priority)
> allocation, and of course we shouldn't sleep,
> thus
> use GFP_ATOMIC.
>
> The branch can be found here (off of master):
> https://github.com/ltuikov/linux-2.6
>
> Original posting of the UASP driver can be found here:
> http://marc.info/?l=linux-usb&m=129165511732388&w=2
>
> Luben
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-03-02 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 19:05 Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 6:49 UASP: updates and merges Luben Tuikov
2011-03-09 7:35 Luben Tuikov
2011-01-13 10:45 Luben Tuikov
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=147799.16314.qm@web31802.mail.mud.yahoo.com \
--to=ltuikov-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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