linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Harry Wentland <harry.wentland@amd.com>,
	Leo Li <sunpeng.li@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Balbir Singh <bsingharora@gmail.com>,
	Daniel Axtens <dja@axtens.net>,
	Paul Mackerras <paulus@ozlabs.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: Linux 5.19-rc6
Date: Thu, 14 Jul 2022 13:20:36 +0100	[thread overview]
Message-ID: <YtAKFNgeC1vXjHYI@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAHk-=wh-SE=s+bJq_jwuQ6zfnifaAwYdXikpXo8iZ4JbbNph4Q@mail.gmail.com>

On Wed, Jul 13, 2022 at 01:42:15PM -0700, Linus Torvalds wrote:
> On Wed, Jul 13, 2022 at 1:40 PM Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > That patch is (and has been) in linux-next for a long time,
> > as commit d2ca1fd2bc70, and with the following tags.
> >
> >      Fixes: 7719a68b2fa4 ("ARM: 9192/1: amba: fix memory leak in amba_device_try_add()")
> >      Reported-by: Guenter Roeck <linux@roeck-us.net>
> >      Tested-by: Guenter Roeck <linux@roeck-us.net>
> >      Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> >      Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> >
> > So, yes, it fixes the problem. I don't know where it is pulled from, though.
> > I thought that it is from Russell's tree, given his Signed-off-by:,
> > but I never really checked.
> 
> Heh. Yeah, with that sign-off, I bet it's in Russell's queue, bit it
> just ended up in the "for next release" branch. Russell?

Oh, I see, I never rebased my "misc" branch from the last cycle, so it
looks to me like 9192/1 was due for _this_ merge window - so I merged
the fix for it into that same branch, rather than the "fixes" branch.
I've moved it over to the correct branch now.

Looks like there's another fix that's in that very same state as well.

Expect a pull request shortly.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2022-07-14 12:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 21:54 Linux 5.19-rc6 Linus Torvalds
2022-07-11  6:44 ` Build regressions/improvements in v5.19-rc6 Geert Uytterhoeven
2022-07-13  5:07 ` Linux 5.19-rc6 Guenter Roeck
2022-07-13 19:36   ` Linus Torvalds
2022-07-13 19:48     ` Russell King (Oracle)
2022-07-13 20:21       ` Linus Torvalds
2022-07-13 20:40         ` Guenter Roeck
2022-07-13 20:42           ` Linus Torvalds
2022-07-14 12:20             ` Russell King (Oracle) [this message]
2022-07-14 12:14           ` Russell King (Oracle)
2022-07-13 21:36         ` Sudip Mukherjee
2022-07-13 21:45           ` Linus Torvalds
2022-07-13 21:50             ` Sudip Mukherjee
2022-07-13 22:56               ` Guenter Roeck
2022-07-13 23:09                 ` Sudip Mukherjee
2022-07-13 23:12                   ` Guenter Roeck
2022-07-13 23:26                     ` Sudip Mukherjee
2022-07-13 23:44                       ` Guenter Roeck
2022-07-13 23:02               ` Guenter Roeck
2022-07-14  1:30       ` Kefeng Wang
2022-07-13 19:53     ` Alex Deucher
2022-07-13 20:22       ` Linus Torvalds
2022-07-13 20:45         ` Guenter Roeck
2022-07-13 20:46     ` Guenter Roeck
2022-07-13 20:50       ` Linus Torvalds
2022-07-13 21:00       ` Alex Deucher
2022-07-13 21:32         ` Linus Torvalds
2022-07-14  7:23           ` Geert Uytterhoeven
2022-07-14 13:20             ` Guenter Roeck
2022-07-14 13:56               ` Geert Uytterhoeven
2022-07-14 16:48             ` Linus Torvalds
2022-07-14 17:24               ` Guenter Roeck
2022-07-14 17:37                 ` Linus Torvalds
2022-07-15  7:26                 ` Geert Uytterhoeven
2022-07-14 16:52           ` Alex Deucher
2022-07-14 23:16           ` Russell Currey
2022-07-15  9:33             ` Sudip Mukherjee

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=YtAKFNgeC1vXjHYI@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bsingharora@gmail.com \
    --cc=dja@axtens.net \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@ozlabs.org \
    --cc=sunpeng.li@amd.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).