All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jens Thoms Toerring <jt@toerring.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] regmap: fix alignment issue
Date: Fri, 29 May 2020 23:20:52 +0100	[thread overview]
Message-ID: <20200529222052.GX4610@sirena.org.uk> (raw)
In-Reply-To: <20200529192538.GA28402@toerring.de>

[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]

On Fri, May 29, 2020 at 09:25:38PM +0200, Jens Thoms Toerring wrote:
> The assembly and disassembly of data to be sent to or received from a
> device invoke functions (regmap_format_XXX() and regmap_parse_XXX())
> that extract or insert data items from or into a buffer, using
> assignments. In some cases those functions are called with buffer

This doesn't apply against current code, please check and resend:

HEAD is now at 93b929922dba Merge series "regmap: provide simple bitops and use them in a driver" from Bartosz Golaszewski <brgl@bgdev.pl> Bartosz Golaszewski <bgolaszewski@baylibre.com>:
Applying: regmap: fix alignment issue
Using index info to reconstruct a base tree...
M	drivers/base/regmap/regmap.c
error: patch failed: drivers/base/regmap/regmap.c:261
error: drivers/base/regmap/regmap.c: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 regmap: fix alignment issue

(it also didn't apply against v5.7-rc1 and git didn't know the blobs it
was based on, the most recent change to that code was in 2015 it
seems...).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-05-29 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 19:25 [PATCH v3] regmap: fix alignment issue Jens Thoms Toerring
2020-05-29 22:14 ` Mark Brown
2020-05-29 22:20 ` Mark Brown [this message]
2020-06-01 11:54 ` 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=20200529222052.GX4610@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jt@toerring.de \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.