All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Dong Aisheng <aisheng.dong@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Alexander Sverdlin <alexander.sverdlin@siemens.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 1/1] i2c: lpi2c: use clk notifier for rate changes
Date: Wed, 8 Nov 2023 10:18:14 +0100	[thread overview]
Message-ID: <ZUtSVr/cI/EVgq0M@ninjato> (raw)
In-Reply-To: <20231108091513.6ddwhu6o6lbvvmag@zenone.zhora.eu>

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


> If you see your part in my reply down here you see that some
> parts are missing. Perhaps there is a bug in lei that has missed
> the top part of your patch because in lore I see that, indeed,
> there is nothing wrong with your mail.

Seems to be a lei bug, indeed. I can apply the patch from my mutt inbox
without a problem.


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

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Dong Aisheng <aisheng.dong@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Alexander Sverdlin <alexander.sverdlin@siemens.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 1/1] i2c: lpi2c: use clk notifier for rate changes
Date: Wed, 8 Nov 2023 10:18:14 +0100	[thread overview]
Message-ID: <ZUtSVr/cI/EVgq0M@ninjato> (raw)
In-Reply-To: <20231108091513.6ddwhu6o6lbvvmag@zenone.zhora.eu>


[-- Attachment #1.1: Type: text/plain, Size: 330 bytes --]


> If you see your part in my reply down here you see that some
> parts are missing. Perhaps there is a bug in lei that has missed
> the top part of your patch because in lore I see that, indeed,
> there is nothing wrong with your mail.

Seems to be a lei bug, indeed. I can apply the patch from my mutt inbox
without a problem.


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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-11-08  9:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 14:12 [PATCH v7 1/1] i2c: lpi2c: use clk notifier for rate changes Alexander Stein
2023-11-07 14:12 ` Alexander Stein
2023-11-07 21:20 ` Andi Shyti
2023-11-07 21:20   ` Andi Shyti
2023-11-08  6:46   ` Alexander Stein
2023-11-08  6:46     ` Alexander Stein
2023-11-08  9:15     ` Andi Shyti
2023-11-08  9:15       ` Andi Shyti
2023-11-08  9:18       ` Wolfram Sang [this message]
2023-11-08  9:18         ` Wolfram Sang
2023-11-08 10:26         ` Andi Shyti
2023-11-08 10:26           ` Andi Shyti
2023-11-08 23:38 ` Andi Shyti
2023-11-08 23:38   ` Andi Shyti
2023-11-09  7:54   ` Alexander Stein
2023-11-09  7:54     ` Alexander Stein
2023-11-09  9:10     ` Andi Shyti
2023-11-09  9:10       ` Andi Shyti
2023-11-10 12:27       ` Andi Shyti
2023-11-10 12:27         ` Andi Shyti
2023-11-14 12:27         ` Alexander Stein
2023-11-14 12:27           ` Alexander Stein
2023-12-19 16:56           ` Wolfram Sang
2023-12-19 16:56             ` Wolfram Sang

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=ZUtSVr/cI/EVgq0M@ninjato \
    --to=wsa@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=alexander.sverdlin@siemens.com \
    --cc=andi.shyti@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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.