linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thorsten Scherer <t.scherer@eckelmann.de>,
	 linux-kernel@vger.kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	 Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PULL] siox changes for 6.9
Date: Sat, 16 Mar 2024 08:37:04 +0100	[thread overview]
Message-ID: <k7pd3oar3e3mogaokjl7mykqy3w3cifl4dgbukmnsynyqgk5ze@ch5mn5xln2j7> (raw)
In-Reply-To: <o52ptgjxknpxhtyemb5xdjyobidejvzluicsoc5ceajy4pz4xy@6e3aecoiz7eh>

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

Hello Greg,

[Cc += Linus]

On Fri, Mar 08, 2024 at 10:20:05PM +0100, Uwe Kleine-König wrote:
> On Thu, Mar 07, 2024 at 09:38:07AM +0100, Uwe Kleine-König wrote:
> > On Thu, Mar 07, 2024 at 07:29:59AM +0000, Greg Kroah-Hartman wrote:
> > > Can you send me a "real" git pull request so that I can verify it is
> > > what you say it is (ideally with a signed tag)?
> > 
> > Sure, can do. I will do that tomorrow when (and if) my branch is in next
> > and so got a bit more exposure.
> 
> That has worked so far. So here comes the requested pull request. I
> dropped the two patches you collected in the meantime in your
> char-misc-next branch. The two branches (i.e. your char-misc-next and
> this PR's tag) merge without conflict.
> 
> The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
> 
>   Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git tags/siox/for-greg-6.9-rc1
> 
> for you to fetch changes up to db418d5f1ca5b7bafc8eaa9393ea18a7901bb0ed:
> 
>   siox: bus-gpio: Simplify using devm_siox_* functions (2024-03-08 22:01:10 +0100)
> 
> Please pull this for the 6.9-rc1 merge window.

I didn't hear anything back from you and wonder if there is still a
chance to get this in. I guess that's just you being busy with other
(and more important) stuff. Would it help you if I sent a pull request
to Linus directly?

The changes are in next leading to db418d5f1ca5 since next-20240308. (As
db418d5f1ca since next-20240312, I rebased as two of the six siox
patches got into char-misc-next that were picked up directly from the
mailing list. Before the rebase it was 4ab973203404.)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

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

  reply	other threads:[~2024-03-16  7:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19  7:46 [PATCH 0/4] siox: Move some complexity into the core Uwe Kleine-König
2024-02-19  7:46 ` [PATCH 1/4] siox: Don't pass the reference on a master in siox_master_register() Uwe Kleine-König
2024-02-19  7:46 ` [PATCH 2/4] siox: Provide a devm variant of siox_master_alloc() Uwe Kleine-König
2024-03-07  7:13   ` Uwe Kleine-König
2024-03-07  7:29     ` Greg Kroah-Hartman
2024-03-07  8:38       ` Uwe Kleine-König
2024-03-08 21:20         ` [PULL] siox changes for 6.9 Uwe Kleine-König
2024-03-16  7:37           ` Uwe Kleine-König [this message]
2024-03-22  7:22             ` Uwe Kleine-König
2024-03-22  7:31               ` Greg Kroah-Hartman
2024-03-23  9:21                 ` Uwe Kleine-König
2024-02-19  7:46 ` [PATCH 3/4] siox: Provide a devm variant of siox_master_register() Uwe Kleine-König
2024-02-19  7:46 ` [PATCH 4/4] siox: bus-gpio: Simplify using devm_siox_* functions Uwe Kleine-König
2024-02-27 10:21 ` [PATCH 0/4] siox: Move some complexity into the core Thorsten Scherer
2024-03-06 18:24   ` siox patches for next development cycle [Re: [PATCH 0/4] siox: Move some complexity into the core] Uwe Kleine-König
2024-03-06 21:34     ` Stephen Rothwell
2024-03-06 22:46     ` Greg Kroah-Hartman
2024-03-07  7:08       ` Uwe Kleine-König

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=k7pd3oar3e3mogaokjl7mykqy3w3cifl4dgbukmnsynyqgk5ze@ch5mn5xln2j7 \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.scherer@eckelmann.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).