public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel•org>
To: Waiman Long <longman@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the cgroup tree
Date: Wed, 4 Sep 2024 10:48:40 -1000	[thread overview]
Message-ID: <ZtjHqB32gzZGyZGd@slm.duckdns.org> (raw)
In-Reply-To: <c4c802fb-90d7-4971-9bb6-a37a3f799d59@redhat.com>

On Sun, Sep 01, 2024 at 08:52:13PM -0400, Waiman Long wrote:
> On 9/1/24 18:11, Stephen Rothwell wrote:
...
> Commit dd46bd00ab4c does exist in the cgroup tree, but it is missing Tejun's
> Signed-off. So it is probably in a dead branch. Commit 047b83097448 should

Hmm... I probably force pushed to fix up something?

> be the right hash for the for-6.12 branch. I don't know how I got the other
> commit hash though.
> 
> Tejun, could you update the commit hash in my patch?

Anyways, fixed up.

Thanks.

-- 
tejun

  parent reply	other threads:[~2024-09-04 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01 22:11 linux-next: Fixes tag needs some work in the cgroup tree Stephen Rothwell
     [not found] ` <c4c802fb-90d7-4971-9bb6-a37a3f799d59@redhat.com>
2024-09-04 20:48   ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-15 22:32 Stephen Rothwell
2022-08-15 22:34 ` Tejun Heo
2021-08-09 22:51 Stephen Rothwell
2021-08-09 22:54 ` Tejun Heo
2021-06-06 22:48 Stephen Rothwell
2019-10-24 20:13 Stephen Rothwell

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=ZtjHqB32gzZGyZGd@slm.duckdns.org \
    --to=tj@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=longman@redhat$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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