devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>,
	brendan.higgins@linux.dev, benh@kernel.crashing.org,
	joel@jms.id.au, andi.shyti@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	andrew@codeconstruct.com.au, p.zabel@pengutronix.de,
	andriy.shevchenko@linux.intel.com, linux-i2c@vger.kernel.org,
	openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v13 1/3] dt-bindings: i2c: aspeed: support for AST2600-i2cv2
Date: Mon, 19 Aug 2024 12:34:30 +0200	[thread overview]
Message-ID: <7237aa34-9821-4ba7-a45b-3b1d598bc282@kernel.org> (raw)
In-Reply-To: <20240819092850.1590758-2-ryan_chen@aspeedtech.com>

On 19/08/2024 11:28, Ryan Chen wrote:
> Add ast2600-i2cv2 compatible and aspeed,global-regs, aspeed,enable-dma
> and description for ast2600-i2cv2.
> 
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> Reviewed-by: Krzysztof Kozlowski <krzk+dt@kernel.org>

?!?

What happened here? Why are you amending tags?!? That's not allowed. You
cannot change received tags, change people names or their data! And how
is it even possible, srsly, how do you even work with git? Git would
never do it, so you had to do it on purpose via some weird workflow.

Best regards,
Krzysztof


  reply	other threads:[~2024-08-19 10:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  9:28 [PATCH v13 0/3] Add ASPEED AST2600 I2Cv2 controller driver Ryan Chen
2024-08-19  9:28 ` [PATCH v13 1/3] dt-bindings: i2c: aspeed: support for AST2600-i2cv2 Ryan Chen
2024-08-19 10:34   ` Krzysztof Kozlowski [this message]
2024-08-20  1:29     ` Ryan Chen
2024-08-20  6:18       ` Krzysztof Kozlowski
2024-08-20  6:50         ` Ryan Chen
2024-08-20 10:01           ` Krzysztof Kozlowski
2024-08-21  2:29             ` Ryan Chen
2024-08-19  9:28 ` [PATCH v13 2/3] i2c: aspeed: support AST2600 i2c new register mode driver Ryan Chen
2024-08-19 14:17   ` Andy Shevchenko
2024-08-21  6:43     ` Ryan Chen
2024-08-21 11:53       ` Andy Shevchenko
2024-08-22  2:24         ` Ryan Chen
2024-08-22 13:32           ` Andy Shevchenko
2024-08-23  6:23             ` Ryan Chen
2024-08-23 14:03               ` Andy Shevchenko
2024-08-26  7:50                 ` Ryan Chen
2024-08-26 10:38                   ` Andy Shevchenko
2024-08-28  2:34                     ` Ryan Chen
2024-08-28 13:55                       ` Andy Shevchenko
2024-08-19 15:28   ` kernel test robot
2024-08-19 17:10   ` kernel test robot
2024-08-19  9:28 ` [PATCH v13 3/3] i2c: aspeed: support AST2600 i2c new register slave " Ryan Chen

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=7237aa34-9821-4ba7-a45b-3b1d598bc282@kernel.org \
    --to=krzk@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=brendan.higgins@linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=ryan_chen@aspeedtech.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;
as well as URLs for NNTP newsgroup(s).