mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, soc@kernel.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [GIT PULL] SOC FSL for 6.20
Date: Tue, 14 Apr 2026 17:02:25 +0200	[thread overview]
Message-ID: <a7d13f9e-7a95-4464-abe8-c095354f9908@kernel.org> (raw)
In-Reply-To: <f48af0d1-0980-46dd-b2e9-081b019381e2@app.fastmail.com>



Le 14/04/2026 à 16:55, Arnd Bergmann a écrit :
> On Tue, Apr 14, 2026, at 16:08, Christophe Leroy (CS GROUP) wrote:
>> Hi Arnd,
>>
>> Please pull the following Freescale Soc Drivers changes for 7.1
>>
>> Changes to fsl-mc bus are reviewed or acked by Ioana Ciornei.
> 
> Hi Christophe,
> 
> This is really too late for 7.1: the merge window is
> already open, and I see that all the commits have a committer
> date of today, though some appear to be freshly rebased
> and had an earlier version in linux-next.
> 
> I don't think any of these are urgent bugfixes, so I'd
> suggest you rebase onto 7.1-rc1 and send these again for
> 7.2.

Uhm .... Maybe I made it wrong. All those changes have spent quite some 
time in linux-next but the branch was based on the tag soc_fsl-7.0-2 
that you merged into 7.0-rc5.
This morning I fetched soc tree and saw that the soc/driver branch was 
based on rc1, so to avoid pulling 7.0-rc5 I rebased the changes on 7.0-rc1.

Should I restore the original branch as it was in Linux-next until this 
morning and send a new pull request ?

Christophe

  reply	other threads:[~2026-04-14 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 14:08 Christophe Leroy (CS GROUP)
2026-04-14 14:55 ` Arnd Bergmann
2026-04-14 15:02   ` Christophe Leroy (CS GROUP) [this message]
2026-04-14 15:13     ` Christophe Leroy (CS GROUP)
  -- strict thread matches above, loose matches on Subject: below --
2026-01-31  7:38 Christophe Leroy (CS GROUP)

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=a7d13f9e-7a95-4464-abe8-c095354f9908@kernel.org \
    --to=chleroy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®