* linux-next: bad commit in the luto-misc tree
@ 2015-01-04 23:35 Stephen Rothwell
2015-01-04 23:42 ` Andy Lutomirski
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2015-01-04 23:35 UTC (permalink / raw)
To: Andy Lutomirski; +Cc: linux-next, linux-kernel, Paul E. McKenney
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Hi Andy,
I noticed commit 7d032e5b1042 ("[TEST ONLY] Force RCU NMI nesting") has
no Signed-off-by ... I understand that this is for testing, but that
is *not* what linux-next is really for. Especially given that that
commit is x86 only, it should be used for unit testing. not a wider
audience like this.
I am also not sure about 9f29ed3365cd ("[DO NOT APPLY] rcu: Make
rcu_nmi_enter() handle nesting") ... (it is, in particular, not
Signed-off-by the committer, you).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: bad commit in the luto-misc tree
2015-01-04 23:35 linux-next: bad commit in the luto-misc tree Stephen Rothwell
@ 2015-01-04 23:42 ` Andy Lutomirski
2015-01-04 23:48 ` Stephen Rothwell
0 siblings, 1 reply; 3+ messages in thread
From: Andy Lutomirski @ 2015-01-04 23:42 UTC (permalink / raw)
To: Stephen Rothwell
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Paul E. McKenney
On Sun, Jan 4, 2015 at 3:35 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi Andy,
>
> I noticed commit 7d032e5b1042 ("[TEST ONLY] Force RCU NMI nesting") has
> no Signed-off-by ... I understand that this is for testing, but that
> is *not* what linux-next is really for. Especially given that that
> commit is x86 only, it should be used for unit testing. not a wider
> audience like this.
Sorry. I totally failed here. I swear I rebased onto the latest RCU
tree, double-checked it, and pushed that exact revision to luto/next.
Somehow I pushed a much older development commit. I have no idea how
I did that. I didn't even know I still had that commit around at all.
Fixed now, I think. Next time I will push to luto/next and
double-check that I pushed the commit I thought I pushed.
Sorry for causing trouble.
--Andy
>
> I am also not sure about 9f29ed3365cd ("[DO NOT APPLY] rcu: Make
> rcu_nmi_enter() handle nesting") ... (it is, in particular, not
> Signed-off-by the committer, you).
>
> --
> Cheers,
> Stephen Rothwell sfr@canb•auug.org.au
--
Andy Lutomirski
AMA Capital Management, LLC
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: bad commit in the luto-misc tree
2015-01-04 23:42 ` Andy Lutomirski
@ 2015-01-04 23:48 ` Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2015-01-04 23:48 UTC (permalink / raw)
To: Andy Lutomirski
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Paul E. McKenney
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hi Andy,
On Sun, 4 Jan 2015 15:42:31 -0800 Andy Lutomirski <luto@amacapital•net> wrote:
>
> Sorry. I totally failed here. I swear I rebased onto the latest RCU
> tree, double-checked it, and pushed that exact revision to luto/next.
> Somehow I pushed a much older development commit. I have no idea how
> I did that. I didn't even know I still had that commit around at all.
OK, I have refetched your tree for today and it looks fine.
> Fixed now, I think. Next time I will push to luto/next and
> double-check that I pushed the commit I thought I pushed.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-01-04 23:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-04 23:35 linux-next: bad commit in the luto-misc tree Stephen Rothwell
2015-01-04 23:42 ` Andy Lutomirski
2015-01-04 23:48 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox