From: "Paul E. McKenney" <paulmck@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the rcu tree
Date: Mon, 28 Oct 2019 17:36:44 -0700 [thread overview]
Message-ID: <20191029003644.GE20975@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20191029080116.1ba4849f@canb.auug.org.au>
On Tue, Oct 29, 2019 at 08:01:16AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> [Resending with correct address syntax]
>
> On Tue, 29 Oct 2019 07:50:41 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > [Resent with Paul's new (working) address]
> >
> > In commit
> >
> > 292d1bb21aba ("rcu: Several rcu_segcblist functions can be static")
> >
> > Fixes tag
> >
> > Fixes: ab2ef5c7b4d1 ("rcu/nocb: Atomic ->len field in rcu_segcblist structure")
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Did you mean
> >
> > Fixes: eda669a6a2c5 ("rcu/nocb: Atomic ->len field in rcu_segcblist structure")
Indeed I did, thank you, Stephen!
Thanx, Paul
next prev parent reply other threads:[~2019-10-29 0:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191029075041.7bf3f723@canb.auug.org.au>
2019-10-28 21:01 ` linux-next: Fixes tag needs some work in the rcu tree Stephen Rothwell
2019-10-29 0:36 ` Paul E. McKenney [this message]
2024-04-08 23:14 Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-04-03 21:39 Stephen Rothwell
2024-04-04 12:14 ` Uladzislau Rezki
2024-04-04 14:35 ` Paul E. McKenney
2024-04-05 17:17 ` Uladzislau Rezki
2024-04-01 21:03 Stephen Rothwell
2023-04-05 22:36 Stephen Rothwell
2023-04-05 22:59 ` Paul E. McKenney
2020-10-05 11:53 Stephen Rothwell
2020-10-05 14:07 ` Paul E. McKenney
2020-02-12 22:26 Stephen Rothwell
2020-02-13 10:35 ` Paul E. McKenney
2019-12-11 20:44 Stephen Rothwell
2019-12-11 22:52 ` Paul E. McKenney
2019-10-28 20:48 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=20191029003644.GE20975@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.