public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Xinming Hu <huxm@marvell.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Nishant Sarmukadam <nishants@marvell.com>,
	Wei-Ning Huang <wnhuang@chromium.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Cathy Luo <cluo@marvell.com>, Zhiyuan Yang <yangzy@marvell.com>,
	Tim Song <songtao@marvell.com>,
	"Xu (Shanghai) Wang" <xwang4@marvell.com>,
	James Cao <jcao@marvell.com>, Ganapathi Bhat <gbhat@marvell.com>
Subject: Re: [EXT] Re: [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size
Date: Tue, 21 Nov 2017 11:58:35 +0000	[thread overview]
Message-ID: <1511265515364.63169@marvell.com> (raw)
In-Reply-To: <CAPDyKFqZqbNHgtqnNoXAA_htqWDbPqvcz6hOZWQvfa5dZ5pj2Q@mail.gmail.com>

Hi Ulf,

Would you mind re-posting a re-based series instead? In that way
you hopefully get some more people's attention as well.
>>> Sure. Could you please point the latest mmc git code base ? I guess it is
https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/
But looks quite old.
 
Regards,
Simon
________________________________________
From: Ulf Hansson <ulf.hansson@linaro.org>
Sent: Tuesday, November 21, 2017 19:44
To: Xinming Hu
Cc: Nishant Sarmukadam; Wei-Ning Huang; linux-mmc@vger.kernel.org; Cathy Luo; Zhiyuan Yang; Tim Song; Xu (Shanghai) Wang; James Cao; Ganapathi Bhat
Subject: [EXT] Re: [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size

External Email

----------------------------------------------------------------------
On 16 November 2017 at 14:57, Xinming Hu <huxm@marvell.com> wrote:
> Hi Ulf,
>
> Could you please let us know if you have any further review comments on this patch series.

Seems like this fallen through the cracks.

Would you mind re-posting a re-based series instead? In that way you
hopefully get some more people's attention as well.

Kind regards
Uffe

>
> Regards,
> Simon


>
>> -----Original Message-----
>> From: Amitkumar Karwar
>> Sent: 2016年8月9日 18:16
>> To: Ulf Hansson <ulf.hansson@linaro.org>
>> Cc: Nishant Sarmukadam <nishants@marvell.com>; Wei-Ning Huang
>> <wnhuang@chromium.org>; linux-mmc@vger.kernel.org; Cathy Luo
>> <cluo@marvell.com>; Xinming Hu <huxm@marvell.com>
>> Subject: RE: [PATCH v4 1/2] mmc: API for accessing host supported maximum
>> segment count and size
>>
>> Hi Ulf,
>>
>> > From: Amitkumar Karwar [mailto:akarwar@marvell.com]
>> > Sent: Thursday, June 16, 2016 2:53 PM
>> > To: linux-wireless@vger.kernel.org
>> > Cc: Nishant Sarmukadam; Wei-Ning Huang; linux-mmc@vger.kernel.org;
>> > Cathy Luo; Xinming Hu; Amitkumar Karwar
>> > Subject: [PATCH v4 1/2] mmc: API for accessing host supported maximum
>> > segment count and size
>> >
>> > From: Xinming Hu <huxm@marvell.com>
>> >
>> > sdio device drivers need be able to get the host supported max_segs
>> > and max_seg_size, so that they know the buffer size to allocate while
>> > utilizing the scatter/gather DMA buffer list.
>> >
>> > This patch provides API for this purpose.
>> >
>> > Signed-off-by: Xinming Hu <huxm@marvell.com>
>> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
>> > ---
>> > v2: v2 was submitted with minor improvement like replacing BUG_ON()
>> > with
>> > WARN_ON()
>> > v3: Addressed below review comments from Ulf Hansson
>> >     a) In v3, patch has been split into two separate patches.
>> >     b) Patch 1/2 introduces an API to fetch max_seg_size and max_segs
>> >     c) Replaced WARN_ON() with proper error code when sg_ptr->length
>> > is invalid
>> >     d) Instead of duplicating the code in mmc_io_rw_extended(), extra
>> > bool parameter
>> >        has been added to this function and used it in new APIs for SG.
>> > v4: Removed WARN_ON() calls in newly added APIs. It's gets called in
>> > probe handler.
>> >     Caller already takes care of it(Shawn Lin).
>> > ---
>> >  drivers/mmc/core/sdio_io.c                          | 21
>> > +++++++++++++++++++++
>> >  .../wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c   |  6 +++---
>> >  include/linux/mmc/sdio_func.h                       |  3 +++
>> >  3 files changed, 27 insertions(+), 3 deletions(-)
>> >
>>
>> Please let me know if you have any further review comments for this patch
>> series.
>>
>> Regards,
>> Amitkumar

  reply	other threads:[~2017-11-21 11:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16  9:23 [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size Amitkumar Karwar
2016-06-16  9:23 ` [PATCH v4 2/2] mmc: sdio support external scatter gather list Amitkumar Karwar
2016-08-09 10:16 ` [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size Amitkumar Karwar
2017-11-16 13:57   ` Xinming Hu
2017-11-21 11:44     ` Ulf Hansson
2017-11-21 11:58       ` Xinming Hu [this message]
2017-11-21 15:13         ` [EXT] " Ulf Hansson
2017-11-22  1:58           ` Xinming Hu
     [not found] ` <1466069006-10757-1-git-send-email-akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2016-12-22  9:09   ` Amitkumar Karwar

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=1511265515364.63169@marvell.com \
    --to=huxm@marvell.com \
    --cc=cluo@marvell.com \
    --cc=gbhat@marvell.com \
    --cc=jcao@marvell.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nishants@marvell.com \
    --cc=songtao@marvell.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wnhuang@chromium.org \
    --cc=xwang4@marvell.com \
    --cc=yangzy@marvell.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