On Sun, 2013-06-09 at 14:33 -0700, Linus Torvalds wrote:
On Sun, Jun 9, 2013 at 12:56 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
Here are a few more powerpc changes for 3.10. I've merged your
tree in at some point (which I generally avoid) in order to get
the compat
Hi Linus !
Here's the previous pull request with a couple of commits removed,
this is purely regressions (though not all recent ones) or stable
material.
Cheers,
Ben.
The following changes since commit 1612e111e4e565422242727efb59499cce8738e4:
Merge
Hi Linus,
Is Jeremy the patchwork maintainer?
Yep, that's me.
and it turns out that apparently 'patchwork' is just making up random
times, because when you download the email as an mbox, it will turn
this into that corrupt and incorrect
Date: Thu, 06 Jun 2013 19:42:54 -
thing
On Sun, Jun 9, 2013 at 7:44 PM, Jeremy Kerr j...@ozlabs.org wrote:
We keep all patch dates in UTC, but were generating the Date header
incorrectly. Now fixed:
No, not fixed.
Keeping patch dates in UTC *corrupts* the date.
I'll ask people to stop using patchworks if it cannot keep track of
On Sun, Jun 9, 2013 at 8:06 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
And it does matter.
.. the rationale for this is that the work pattern of people is
actually interesting information. You can do things like this:
git log --pretty=%aD --author=Torvalds
to see what my work
On Sun, Jun 9, 2013 at 8:20 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
.. the rationale for this is that the work pattern of people is
actually interesting information. You can do things like this:
git log --pretty=%aD --author=Torvalds
Final side note: for me, and other git
Hi Linus,
No. The date from the email was
Date: Fri, 7 Jun 2013 15:42:54 +1000
and we want *that* date.
Ah, gotchya.
So, we now use the original date header (if present) in the mbox views:
$ wget -qO - http://patchwork.ozlabs.org/patch/249598/mbox/ | grep ^Date
Date: Fri, 7 Jun 2013
On Sun, Jun 9, 2013 at 9:20 PM, Jeremy Kerr j...@ozlabs.org wrote:
So, we now use the original date header (if present) in the mbox views:
$ wget -qO - http://patchwork.ozlabs.org/patch/249598/mbox/ | grep ^Date
Date: Fri, 7 Jun 2013 15:42:54 +1000
... for all your data-mining needs.
On Sat, 2013-06-01 at 09:22 +1000, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> Here are a few more fixes for powerpc 3.10. It's a bit more than I would
> have liked this late in the game but I suppose that's what happens with
> a brand new chip generation coming out.
>
> A few regression
Hi Linus !
Here are a few more fixes for powerpc 3.10. It's a bit more than I would
have liked this late in the game but I suppose that's what happens with
a brand new chip generation coming out.
A few regression fixes, some last minute fixes for new P8 features such
as transactional memory,...
Hi Linus !
Here are a few more fixes for powerpc 3.10. It's a bit more than I would
have liked this late in the game but I suppose that's what happens with
a brand new chip generation coming out.
A few regression fixes, some last minute fixes for new P8 features such
as transactional memory,...
On Sat, 2013-06-01 at 09:22 +1000, Benjamin Herrenschmidt wrote:
Hi Linus !
Here are a few more fixes for powerpc 3.10. It's a bit more than I would
have liked this late in the game but I suppose that's what happens with
a brand new chip generation coming out.
A few regression fixes, some
Hi Linus !
Here are a few more powerpc fixes for 3.10. Some more P8 related
bits, a bunch of fixes for our P7+/P8 HW crypto drivers, some added
workarounds for those radeons that don't do proper 64-bit MSIs and
a couple of other trivialities by myself.
Cheers,
Ben.
The following changes since
Hi Linus !
Here are a few more powerpc fixes for 3.10. Some more P8 related
bits, a bunch of fixes for our P7+/P8 HW crypto drivers, some added
workarounds for those radeons that don't do proper 64-bit MSIs and
a couple of other trivialities by myself.
Cheers,
Ben.
The following changes since
Hi Linus !
Here are some more powerpc fixes to apply to 3.10. This is mostly bug
fixes (some of them regressions, some of them I deemed worth merging
now) along with some patches from Li Zhong hooking up the new
context tracking stuff (for the new full NO_HZ)
Cheers,
Ben.
The following changes
Hi Linus !
Here are some more powerpc fixes to apply to 3.10. This is mostly bug
fixes (some of them regressions, some of them I deemed worth merging
now) along with some patches from Li Zhong hooking up the new
context tracking stuff (for the new full NO_HZ)
Cheers,
Ben.
The following changes
Hi Linus !
Here are a few more powerpc bits that I would like in 3.10. Mostly
remaining bolts & screw tightening of power8 support such as actually
exposing the new features via the previously added AT_HWCAP2, and a
few fixes, some of them for problems exposed recently like irqdomain
warnings or
Hi Linus !
Here are a few more powerpc bits that I would like in 3.10. Mostly
remaining bolts screw tightening of power8 support such as actually
exposing the new features via the previously added AT_HWCAP2, and a
few fixes, some of them for problems exposed recently like irqdomain
warnings or
Hi Linus !
Here's a few powerpc fixes for 3.9, mostly regressions (though not all
from 3.9 merge window) that we've been hammering into shape over the
last couple of weeks. They fix booting on Cell and G5 among other
things (yes, we've been a bit sloppy with older machines this time
around).
Hi Linus !
Here's a few powerpc fixes for 3.9, mostly regressions (though not all
from 3.9 merge window) that we've been hammering into shape over the
last couple of weeks. They fix booting on Cell and G5 among other
things (yes, we've been a bit sloppy with older machines this time
around).
Hi Linus !
Here are a few powerpc bits & fixes for rc1. A couple of str*cpy fixes,
some fixes in handling the FSCR register on Power8 (controls the
enabling of processor features), a 32-bit build fix and a couple more
nits.
Cheers,
Ben.
The following changes since commit
Hi Linus !
Here are a few powerpc bits fixes for rc1. A couple of str*cpy fixes,
some fixes in handling the FSCR register on Power8 (controls the
enabling of processor features), a 32-bit build fix and a couple more
nits.
Cheers,
Ben.
The following changes since commit
Hi Linus !
Just so that you don't get too bored on your Island here's a patch for
3.8 fixing a nasty bug that affects the new 64T support that was merged
in 3.7. Please apply whenever you have a chance (and an internet
connection !)
Cheers,
Ben.
The following changes since commit
Hi Linus !
Just so that you don't get too bored on your Island here's a patch for
3.8 fixing a nasty bug that affects the new 64T support that was merged
in 3.7. Please apply whenever you have a chance (and an internet
connection !)
Cheers,
Ben.
The following changes since commit
On Tue, Jan 29, 2013 at 1:09 AM, Benjamin Herrenschmidt
wrote:
> On Mon, 2013-01-28 at 16:03 -0800, Linus Torvalds wrote:
>> I'll have you know that I haven't quite even left for Au yet, and I
>> have LCA before diving. So no snarky "in between dives" comments,
>> please.
>
> It wasn't meant to
On Tue, Jan 29, 2013 at 1:09 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Mon, 2013-01-28 at 16:03 -0800, Linus Torvalds wrote:
I'll have you know that I haven't quite even left for Au yet, and I
have LCA before diving. So no snarky in between dives comments,
please.
It
On Mon, 2013-01-28 at 16:03 -0800, Linus Torvalds wrote:
> I'll have you know that I haven't quite even left for Au yet, and I
> have LCA before diving. So no snarky "in between dives" comments,
> please.
It wasn't meant to be "snarky", sorry about that...
> At least not for a few days.
>
> >
On Mon, Jan 28, 2013 at 3:42 PM, Benjamin Herrenschmidt
wrote:
>
> Whenever you have a chance between two dives, you might want to consider
> pulling my merge branch to pickup a few fixes for 3.8 that have been
> accumulating for the last couple of weeks (I was myself travelling
> then on
Hi Linus !
Whenever you have a chance between two dives, you might want to consider
pulling my merge branch to pickup a few fixes for 3.8 that have been
accumulating for the last couple of weeks (I was myself travelling
then on vacation). Nothing major, just a handful of powerpc bug fixes
that I
Hi Linus !
Whenever you have a chance between two dives, you might want to consider
pulling my merge branch to pickup a few fixes for 3.8 that have been
accumulating for the last couple of weeks (I was myself travelling
then on vacation). Nothing major, just a handful of powerpc bug fixes
that I
On Mon, Jan 28, 2013 at 3:42 PM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
Whenever you have a chance between two dives, you might want to consider
pulling my merge branch to pickup a few fixes for 3.8 that have been
accumulating for the last couple of weeks (I was myself
On Mon, 2013-01-28 at 16:03 -0800, Linus Torvalds wrote:
I'll have you know that I haven't quite even left for Au yet, and I
have LCA before diving. So no snarky in between dives comments,
please.
It wasn't meant to be snarky, sorry about that...
At least not for a few days.
On Thu, 2013-01-03 at 17:13 +1100, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> Here are a couple of small powerpc fixes. They aren't new bugs (and
> they are both CCed to stable) but I didn't see the point of sitting
> on the fixes any longer.
Looks like I still need to fix my script to get
Hi Linus !
Here are a couple of small powerpc fixes. They aren't new bugs (and
they are both CCed to stable) but I didn't see the point of sitting
on the fixes any longer.
Oh and happy new year !
Cheers,
Ben.
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linux
Hi Linus !
Here are a couple of small powerpc fixes. They aren't new bugs (and
they are both CCed to stable) but I didn't see the point of sitting
on the fixes any longer.
Oh and happy new year !
Cheers,
Ben.
The following changes since commit d1c3ed669a2d452cacfb48c2d171a1f364dae2ed:
Linux
On Thu, 2013-01-03 at 17:13 +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Here are a couple of small powerpc fixes. They aren't new bugs (and
they are both CCed to stable) but I didn't see the point of sitting
on the fixes any longer.
Looks like I still need to fix my script to get the
On Mon, 2012-11-26 at 09:07 +1100, Benjamin Herrenschmidt wrote:
> Hi Linus !
>
> Here's a patch that would be good to still have in 3.7. It's a one liner
> fixing
> a regression introduced by the new EEH code in .37 (potential oops on some
> PCI setups when configuring MSIs).
>
> Cheers,
>
On Mon, 2012-11-26 at 09:08 +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2012-11-26 at 09:07 +1100, Benjamin Herrenschmidt wrote:
> > Hi Linus !
> >
> > Here's a patch that would be good to still have in 3.7. It's a one liner
> > fixing
> > a regression introduced by the new EEH code in .37
Hi Linus !
Here's a patch that would be good to still have in 3.7. It's a one liner fixing
a regression introduced by the new EEH code in .37 (potential oops on some
PCI setups when configuring MSIs).
Cheers,
Ben.
The following changes since commit d6dc24613c222f9057131ccbd5264a10bcba9f97:
Hi Linus !
Here's a patch that would be good to still have in 3.7. It's a one liner fixing
a regression introduced by the new EEH code in .37 (potential oops on some
PCI setups when configuring MSIs).
Cheers,
Ben.
The following changes since commit d6dc24613c222f9057131ccbd5264a10bcba9f97:
On Mon, 2012-11-26 at 09:08 +1100, Benjamin Herrenschmidt wrote:
On Mon, 2012-11-26 at 09:07 +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Here's a patch that would be good to still have in 3.7. It's a one liner
fixing
a regression introduced by the new EEH code in .37 (potential
On Mon, 2012-11-26 at 09:07 +1100, Benjamin Herrenschmidt wrote:
Hi Linus !
Here's a patch that would be good to still have in 3.7. It's a one liner
fixing
a regression introduced by the new EEH code in .37 (potential oops on some
PCI setups when configuring MSIs).
Cheers,
Ben.
The
Hi Linus !
Here are small 52xx fixes that Anatolij asked me to pull a while back
and that I completely missed. The stuff is local to that platform code,
and was in next for a while, so it should still go into 3.7.
Thanks,
Ben.
The following changes since commit
Hi Linus !
Here are small 52xx fixes that Anatolij asked me to pull a while back
and that I completely missed. The stuff is local to that platform code,
and was in next for a while, so it should still go into 3.7.
Thanks,
Ben.
The following changes since commit
Hi Linus !
Here are a handful of powerpc related fixes for you to pull.
Cheers,
Ben.
The following changes since commit 18673533256a2953ccefded52df2679de8640685:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2012-10-17
12:41:18 -0700)
are available in the git repository
Hi Linus !
Here are a handful of powerpc related fixes for you to pull.
Cheers,
Ben.
The following changes since commit 18673533256a2953ccefded52df2679de8640685:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2012-10-17
12:41:18 -0700)
are available in the git repository
On Thu, 2012-10-04 at 09:02 -0700, Linus Torvalds wrote:
> Hmm. There's nothing there.
>
> Did you mean for me to pull some branch/tag you didn't mention?
Heh, yeah, the mirrors hadn't updated yet so git request-pull didn't put
the branch name in. It's common but I usually fix it up by hand.
On Thu, 2012-10-04 at 09:00 -0700, Linus Torvalds wrote:
> So this happens if you have "reverse merges" (ie you've pulled my
> tree, or some other tree I've pulled), and there is no longer a single
> clear common point that you started from. In that case, there is no
> simple diff for the "what
On Thu, Oct 4, 2012 at 1:38 AM, Benjamin Herrenschmidt
wrote:
>
> The following changes since commit 271fd03a3013b106ccc178d54219c1be0c9759b7:
>
> powerpc/powernv: I/O and memory alignment for P2P bridges (2012-09-11
> 16:59:47 -0600)
>
> are available in the git repository at:
>
>
On Thu, Oct 4, 2012 at 1:38 AM, Benjamin Herrenschmidt
wrote:
>
> First, however, a note about the pull request details ... the diffstat looks
> completely on crack, any idea what's up ? It sees piles of files modified
> in various other archs & generic code but I see no patch in that branch
>
On Thu, Oct 4, 2012 at 1:38 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
First, however, a note about the pull request details ... the diffstat looks
completely on crack, any idea what's up ? It sees piles of files modified
in various other archs generic code but I see no patch
On Thu, Oct 4, 2012 at 1:38 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
The following changes since commit 271fd03a3013b106ccc178d54219c1be0c9759b7:
powerpc/powernv: I/O and memory alignment for P2P bridges (2012-09-11
16:59:47 -0600)
are available in the git repository
On Thu, 2012-10-04 at 09:00 -0700, Linus Torvalds wrote:
So this happens if you have reverse merges (ie you've pulled my
tree, or some other tree I've pulled), and there is no longer a single
clear common point that you started from. In that case, there is no
simple diff for the what has
On Thu, 2012-10-04 at 09:02 -0700, Linus Torvalds wrote:
Hmm. There's nothing there.
Did you mean for me to pull some branch/tag you didn't mention?
Heh, yeah, the mirrors hadn't updated yet so git request-pull didn't put
the branch name in. It's common but I usually fix it up by hand. Since
On Wed, 2012-09-05 at 16:12 +1000, Benjamin Herrenschmidt wrote:
> The following changes since commit
> 5b716ac728bcc01b1f2a7ed6e437196602237c27:
>
> Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6
> (2012-09-02 11:30:10 -0700)
>
> are available in the git repository at:
>
>
Hi Linus !
Here are a few fixes for 3.6 that were piling up while I was away or
busy (I was mostly MIA a week or two before San Diego). Some fixes from
Anton fixing up issues with our relatively new DSCR control feature,
and a few other fixes that are either regressions or bugs nasty enough
to
Hi Linus !
Here are a few fixes for 3.6 that were piling up while I was away or
busy (I was mostly MIA a week or two before San Diego). Some fixes from
Anton fixing up issues with our relatively new DSCR control feature,
and a few other fixes that are either regressions or bugs nasty enough
to
On Wed, 2012-09-05 at 16:12 +1000, Benjamin Herrenschmidt wrote:
The following changes since commit
5b716ac728bcc01b1f2a7ed6e437196602237c27:
Merge branch 'for-next' of git://git.samba.org/sfrench/cifs-2.6
(2012-09-02 11:30:10 -0700)
are available in the git repository at:
Hi Linus !
I meant to sent that earlier but got swamped with other things, so here
are some powerpc fixes for 3.6. A few regression fixes and some bug
fixes that I deemed should still make it.
There's a FSL update from Kumar with a bunch of defconfig updates along
with a few embedded fixes.
I
Hi Linus !
I meant to sent that earlier but got swamped with other things, so here
are some powerpc fixes for 3.6. A few regression fixes and some bug
fixes that I deemed should still make it.
There's a FSL update from Kumar with a bunch of defconfig updates along
with a few embedded fixes.
I
Hi Linus !
Kumar sent me a handful of Freescale related fixes and I added
another regression fix to the pile.
Cheers,
Ben.
PS. I -will- eventually learn about that signed tag business :-)
The following changes since commit 1fad1e9a747687a7399bf58e87974f9b1bbcae06:
Merge tag 'nfs-for-3.6-1'
Hi Linus !
Kumar sent me a handful of Freescale related fixes and I added
another regression fix to the pile.
Cheers,
Ben.
PS. I -will- eventually learn about that signed tag business :-)
The following changes since commit 1fad1e9a747687a7399bf58e87974f9b1bbcae06:
Merge tag 'nfs-for-3.6-1'
Hi Linus !
Here's a handful of powerpc patches, a couple of regression fixes
for problems introduced in the main batch in this merge window,
a couple of defconfig updates, and some trivials. The radeonfb
one is something that was long standing in SLES which I forgot
to pickup earlier.
Cheers,
Hi Linus !
Here's a handful of powerpc patches, a couple of regression fixes
for problems introduced in the main batch in this merge window,
a couple of defconfig updates, and some trivials. The radeonfb
one is something that was long standing in SLES which I forgot
to pickup earlier.
Cheers,
Hi Linus !
It looks like my rewrite of our lazy irq scheme is still exposing
"interesting" issues left and right. The previous fixes are now
causing an occasional BUG_ON to trigger (which this patch turns
into a WARN_ON while at it), due to another issue of disconnect
of the lazy irq state vs.
Hi Linus !
It looks like my rewrite of our lazy irq scheme is still exposing
interesting issues left and right. The previous fixes are now
causing an occasional BUG_ON to trigger (which this patch turns
into a WARN_ON while at it), due to another issue of disconnect
of the lazy irq state vs. the
101 - 166 of 166 matches
Mail list logo
