public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Vivek Gautam" <gautam.vivek@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, swarren@wwwdotorg.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	kgene.kim@samsung.com, stern@rowland.harvard.edu,
	linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 0/6] usb: host: Cleanup for ioremap'ing hcd memory
Date: Sat, 10 May 2014 18:25:56 +0400	[thread overview]
Message-ID: <1399731956.962771892@f256.i.mail.ru> (raw)
In-Reply-To: <1399723210-21569-1-git-send-email-gautam.vivek@samsung.com>

Sat, 10 May 2014 17:30:04 +0530 от Vivek Gautam <gautam.vivek@samsung.com>:
> Based on 'usb-next' branch of Greg's usb tree.
> 
> devm_ioremap_resource() API is advantageous over devm_ioremap()
> and should therefore be preferred to request any ioremap'ed address
> for hcd.
> 
> Changes from v1:
>  - Changed the way returned pointer is checked for error value
>    as pointed out in the review comment in the mailing list.

hcd->rsrc_len field can be removed entirely, since I cannot find any reason
how this filed can be used in the drivers now.
This is of course should be in an another series. This one looks good.

---


  parent reply	other threads:[~2014-05-10 14:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10 12:00 [PATCH v2 0/6] usb: host: Cleanup for ioremap'ing hcd memory Vivek Gautam
2014-05-10 12:00 ` [PATCH v2 1/6] usb: host: ehci-exynos: Use devm_ioremap_resource instead of devm_ioremap Vivek Gautam
2014-05-10 12:00 ` [PATCH v2 2/6] usb: host: ehci-msm: " Vivek Gautam
2014-05-10 12:00 ` [PATCH v2 3/6] usb: host: ehci-mv: " Vivek Gautam
2014-05-10 12:00 ` [PATCH v2 4/6] usb: host: ehci-spear: " Vivek Gautam
2014-05-10 12:00 ` [PATCH v2 5/6] usb: host: ehci-tegra: " Vivek Gautam
     [not found]   ` <1399723210-21569-6-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-12 16:58     ` Stephen Warren
2014-05-10 12:00 ` [PATCH v2 6/6] usb: host: ohci-exynos: " Vivek Gautam
2014-06-04 10:11   ` Vivek Gautam
     [not found]     ` <CAFp+6iFufCh6SVEF-HQA62ZsJGJGSebDSs28eqcrMy1X8e5vjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-04 13:13       ` Thierry Reding
2014-06-06 13:02         ` Vivek Gautam
     [not found]           ` <CAFp+6iEe8fvxboG79=2s=oe4BkQJYAoVUPtYkPdjJHCe+bC=8Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-06 22:52             ` Thierry Reding
2014-06-24  5:49               ` Vivek Gautam
2014-05-10 14:25 ` Alexander Shiyan [this message]
2014-05-11 14:45   ` [PATCH v2 0/6] usb: host: Cleanup for ioremap'ing hcd memory Vivek Gautam
     [not found] ` <1399723210-21569-1-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-12 14:08   ` Alan Stern

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=1399731956.962771892@f256.i.mail.ru \
    --to=shc_work@mail.ru \
    --cc=gautam.vivek@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox