linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thorsten Scherer <t.scherer@eckelmann.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PULL] siox changes for 6.9
Date: Fri, 22 Mar 2024 08:31:15 +0100	[thread overview]
Message-ID: <2024032240-yield-tycoon-f5a4@gregkh> (raw)
In-Reply-To: <mryuydqd7pqxwkvylp24fped57tsys4me4pazdg4ujwkwtthhp@26rnjgzjesrx>

On Fri, Mar 22, 2024 at 08:22:16AM +0100, Uwe Kleine-König wrote:
> Hello Greg,
> 
> On Sat, Mar 16, 2024 at 08:37:04AM +0100, Uwe Kleine-König wrote:
> > 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.)
> 
> You probably saw me being impatient and sending the PR to Linus
> directly. If not: These changes are already in the mainline now
> (00453419575d6b4f5ce0f370da9421cf5253f103) and this is the thread you
> can drop from your todo list. I removed the above tag from my repository
> to (hopefully) prevent future confusion.

No worries, I see this is all in Linus's tree.  Sorry for the delay, I
was actually on vacation for once and didn't have the chance to do all
of this (and to be fair, you asked for the pull request way too late...)

thanks,

greg k-h

  reply	other threads:[~2024-03-22  7:31 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
2024-03-22  7:22             ` Uwe Kleine-König
2024-03-22  7:31               ` Greg Kroah-Hartman [this message]
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=2024032240-yield-tycoon-f5a4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.scherer@eckelmann.de \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).