public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Kevin Hilman <khilman@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	kernel-janitors@vger.kernel.org, Andrew Davis <afd@ti.com>
Subject: Re: [linux-i2c] Patch notification: DaVinci: 2 patches updated
Date: Thu, 8 Jun 2023 15:41:34 +0200	[thread overview]
Message-ID: <ZIHajpkxV/PFPcb8@shikoro> (raw)
In-Reply-To: <ae8ede44-e7a9-c086-d17e-68c33b4482e0@web.de>


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


> Unfortunately, it seems that the patch quality was still improvable.

It was not perfect but good enough.

> * How will the patch integration evolve further for suggestions which seem to be
>   still in waiting queues?

Easy, it will evolve quite similar with the amount of review/reviewers.

> * How far back would you like to support the known development history
>   for discussed Linux software components?

Dunno, if I got the question right, but I don't want to break existing
stuff. Why do you ask?


[-- 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-06-08 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168613080300.11524.2783831689498520603@legolas.ozlabs.org>
2023-06-08  7:09 ` [linux-i2c] Patch notification: DaVinci: 2 patches updated Markus Elfring
2023-06-08  7:47   ` Wolfram Sang
2023-06-08  8:21     ` Markus Elfring
2023-06-08 11:26       ` Wolfram Sang
2023-06-08 11:48         ` Markus Elfring
2023-06-08 13:41           ` Wolfram Sang [this message]
2023-06-08 19:03             ` Markus Elfring
2023-06-08 20:23               ` Wolfram Sang
2023-06-09  6:26         ` Markus Elfring

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=ZIHajpkxV/PFPcb8@shikoro \
    --to=wsa@the-dreams.de \
    --cc=Markus.Elfring@web.de \
    --cc=afd@ti.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=nsekhar@ti.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