mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lucas tanure <tanureal@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH v3 1/2] regmap: spi: Set regmap max raw r/w from max_transfer_size
Date: Wed, 15 Sep 2021 13:37:03 +0100	[thread overview]
Message-ID: <ef63110f-a579-aaca-9bde-549392a0628c@opensource.cirrus.com> (raw)
In-Reply-To: <20210915123453.GD5389@sirena.org.uk>

On 9/15/21 13:34, Mark Brown wrote:
> On Wed, Sep 15, 2021 at 01:09:50PM +0100, Lucas Tanure wrote:
>> Set regmap raw read/write from spi max_transfer_size
>> so regmap_raw_read/write can split the access into chunks
>>
>> Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
>> ---
>>
>> Changes v2:
>> New series
>>
>> Changes v3:
>> None
> 
> How does this relate to the previous free standing copy of this patch
> you sent only two days ago on Monday?  You've dropped Charles'
> Reviewed-by so I guess there must be some change but this changelog
> claims there's nothing (and appears to claim that v2 was the first
> version...).
> 
Hi,

Yes, its exactly the same, I forgot to add the second patch the previous 
one.
I will resend with Charles review-by.

Thanks

  reply	other threads:[~2021-09-15 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 12:09 Lucas Tanure
2021-09-15 12:09 ` [PATCH v3 2/2] regmap: spi: Check raw_[read|write] against max message size Lucas Tanure
2021-09-15 12:51   ` Mark Brown
2021-09-15 12:34 ` [PATCH v3 1/2] regmap: spi: Set regmap max raw r/w from max_transfer_size Mark Brown
2021-09-15 12:37   ` Lucas tanure [this message]
2021-09-15 12:57     ` Mark Brown

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=ef63110f-a579-aaca-9bde-549392a0628c@opensource.cirrus.com \
    --to=tanureal@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rafael@kernel.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
all inboxes | Powered by JetHome®