* powerpc -next rebase WARNING
@ 2012-05-22 1:51 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2012-05-22 1:51 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Linux Kernel list
Folks, bad news ... my fault.
I accidentally forgot a --signoff on a git am command last week, meaning
that a pair of patches are in -next and not signed off by me.
For various (legal) reasons that cannot go into Linus tree as-is, so I
have to rebase the tree to fix it.
Sorry about that ...
Cheers,
Ben.
^ permalink raw reply [flat|nested] 6+ messages in thread
* powerpc -next rebase WARNING
@ 2012-05-22 1:51 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2012-05-22 1:51 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Linux Kernel list, Kumar Gala, Josh Boyer
Folks, bad news ... my fault.
I accidentally forgot a --signoff on a git am command last week, meaning
that a pair of patches are in -next and not signed off by me.
For various (legal) reasons that cannot go into Linus tree as-is, so I
have to rebase the tree to fix it.
Sorry about that ...
Cheers,
Ben.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: powerpc -next rebase WARNING
2012-05-22 1:51 ` Benjamin Herrenschmidt
@ 2012-05-22 4:40 ` Benjamin Herrenschmidt
-1 siblings, 0 replies; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2012-05-22 4:40 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Linux Kernel list
On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:
> Folks, bad news ... my fault.
>
> I accidentally forgot a --signoff on a git am command last week, meaning
> that a pair of patches are in -next and not signed off by me.
>
> For various (legal) reasons that cannot go into Linus tree as-is, so I
> have to rebase the tree to fix it.
>
> Sorry about that ...
Note that the rebase only affects the top 3 commits, so if your
tree is based on something older you're fine (Kumar, you seem to
be ok, I haven't checked Josh).
Cheers,
Ben.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: powerpc -next rebase WARNING
@ 2012-05-22 4:40 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2012-05-22 4:40 UTC (permalink / raw)
To: linuxppc-dev; +Cc: Linux Kernel list, Kumar Gala, Josh Boyer
On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:
> Folks, bad news ... my fault.
>
> I accidentally forgot a --signoff on a git am command last week, meaning
> that a pair of patches are in -next and not signed off by me.
>
> For various (legal) reasons that cannot go into Linus tree as-is, so I
> have to rebase the tree to fix it.
>
> Sorry about that ...
Note that the rebase only affects the top 3 commits, so if your
tree is based on something older you're fine (Kumar, you seem to
be ok, I haven't checked Josh).
Cheers,
Ben.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: powerpc -next rebase WARNING
2012-05-22 4:40 ` Benjamin Herrenschmidt
@ 2012-05-22 11:03 ` Josh Boyer
-1 siblings, 0 replies; 6+ messages in thread
From: Josh Boyer @ 2012-05-22 11:03 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev, Linux Kernel list
On Tue, May 22, 2012 at 12:40 AM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:
>> Folks, bad news ... my fault.
>>
>> I accidentally forgot a --signoff on a git am command last week, meaning
>> that a pair of patches are in -next and not signed off by me.
>>
>> For various (legal) reasons that cannot go into Linus tree as-is, so I
>> have to rebase the tree to fix it.
>>
>> Sorry about that ...
>
> Note that the rebase only affects the top 3 commits, so if your
> tree is based on something older you're fine (Kumar, you seem to
> be ok, I haven't checked Josh).
Should be fine. Even if not, all 4 of its users will manage to cope.
josh
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: powerpc -next rebase WARNING
@ 2012-05-22 11:03 ` Josh Boyer
0 siblings, 0 replies; 6+ messages in thread
From: Josh Boyer @ 2012-05-22 11:03 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc-dev, Linux Kernel list, Kumar Gala
On Tue, May 22, 2012 at 12:40 AM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote:
>> Folks, bad news ... my fault.
>>
>> I accidentally forgot a --signoff on a git am command last week, meaning
>> that a pair of patches are in -next and not signed off by me.
>>
>> For various (legal) reasons that cannot go into Linus tree as-is, so I
>> have to rebase the tree to fix it.
>>
>> Sorry about that ...
>
> Note that the rebase only affects the top 3 commits, so if your
> tree is based on something older you're fine (Kumar, you seem to
> be ok, I haven't checked Josh).
Should be fine. Even if not, all 4 of its users will manage to cope.
josh
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-05-22 11:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-22 1:51 powerpc -next rebase WARNING Benjamin Herrenschmidt
2012-05-22 1:51 ` Benjamin Herrenschmidt
2012-05-22 4:40 ` Benjamin Herrenschmidt
2012-05-22 4:40 ` Benjamin Herrenschmidt
2012-05-22 11:03 ` Josh Boyer
2012-05-22 11:03 ` Josh Boyer
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.