Re: [GIT PULL] Keyrings patches

2013-09-27 Thread David Howells
James Morris wrote: > > Hi James, > > > > Could you pull these patches into the security tree? They're based on your > > next branch. > > > > Thanks, pulled. Nagyon köszönöm! David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord.

Re: [GIT PULL] Keyrings patches

2013-09-27 Thread James Morris
On Wed, 25 Sep 2013, David Howells wrote: > > Hi James, > > Could you pull these patches into the security tree? They're based on your > next branch. > Thanks, pulled. > The patches can be viewed as a number of sets: > > (1) KEYS: Skip key state checks when checking for possession > >

[GIT PULL] Keyrings patches

2013-09-25 Thread David Howells
Hi James, Could you pull these patches into the security tree? They're based on your next branch. The patches can be viewed as a number of sets: (1) KEYS: Skip key state checks when checking for possession This is a fix for determining the possessed status of keys that have been in

Re: [GIT PULL] Keyrings patches

2013-09-24 Thread David Howells
James Morris wrote: > > There's a slight change upstream that means that my patchset needs > > regenerating (the initconst changes). Can you bring your -next branch up to > > date with linus/master so that I can rebase on top of it? > > I've merged my tree to -rc2 so you can rebase or merge (pr

Re: [GIT PULL] Keyrings patches

2013-09-23 Thread James Morris
On Tue, 17 Sep 2013, David Howells wrote: > > There's a slight change upstream that means that my patchset needs > regenerating (the initconst changes). Can you bring your -next branch up to > date with linus/master so that I can rebase on top of it? I've merged my tree to -rc2 so you can rebas

Re: [GIT PULL] Keyrings patches

2013-09-18 Thread Mimi Zohar
On Wed, 2013-09-18 at 12:53 +0100, David Howells wrote: > Stephen Rothwell wrote: > > > Is there some reason that those fixups cannot be done in a merge commit? > > i.e. are they more than simple text updates? Hi Stephen, the issue is that the patches were created against a newer kernel (eg. nex

Re: [GIT PULL] Keyrings patches

2013-09-18 Thread David Howells
Stephen Rothwell wrote: > Is there some reason that those fixups cannot be done in a merge commit? > i.e. are they more than simple text updates? That's somewhat up to James. *He* would be the person doing the merge, not me. I'm changing the lines in my patches also. > /me thinks that most re

Re: [GIT PULL] Keyrings patches

2013-09-17 Thread Mimi Zohar
On Tue, 2013-09-17 at 14:55 +0100, David Howells wrote: > There's a slight change upstream that means that my patchset needs > regenerating (the initconst changes). Can you bring your -next branch up to > date with linus/master so that I can rebase on top of it? Once -rc1 is out, James normally r

Re: [GIT PULL] Keyrings patches

2013-09-17 Thread Stephen Rothwell
Hi Dave, On Tue, 17 Sep 2013 14:55:49 +0100 David Howells wrote: > > There's a slight change upstream that means that my patchset needs > regenerating (the initconst changes). Can you bring your -next branch up to > date with linus/master so that I can rebase on top of it? Is there some reason

Re: [GIT PULL] Keyrings patches

2013-09-17 Thread David Howells
There's a slight change upstream that means that my patchset needs regenerating (the initconst changes). Can you bring your -next branch up to date with linus/master so that I can rebase on top of it? Thanks, David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the

Re: [GIT PULL] Keyrings patches

2013-09-11 Thread James Morris
On Tue, 10 Sep 2013, David Howells wrote: > James Morris wrote: > > > > > This missed the merge for 3.12. Do you want me to queue the changes > > > > up, > > > > or do you want to send a pull request again after -rc1 ? > > > > > > Can you queue them up now in your 'next' branch? > > > > Nop

Re: [GIT PULL] Keyrings patches

2013-09-10 Thread David Howells
James Morris wrote: > > > This missed the merge for 3.12. Do you want me to queue the changes up, > > > or do you want to send a pull request again after -rc1 ? > > > > Can you queue them up now in your 'next' branch? > > Nope, new patches can't go into -next until -rc1. I think I misunderst

Re: [GIT PULL] Keyrings patches

2013-09-06 Thread James Morris
On Fri, 6 Sep 2013, David Howells wrote: > James Morris wrote: > > > > Could you pull these patches into the security tree? They're based on > > > your > > > next branch. > > > > This missed the merge for 3.12. Do you want me to queue the changes up, > > or do you want to send a pull reques

Re: [GIT PULL] Keyrings patches

2013-09-06 Thread David Howells
James Morris wrote: > > Could you pull these patches into the security tree? They're based on your > > next branch. > > This missed the merge for 3.12. Do you want me to queue the changes up, > or do you want to send a pull request again after -rc1 ? Can you queue them up now in your 'next'

Re: [GIT PULL] Keyrings patches

2013-09-06 Thread James Morris
On Thu, 5 Sep 2013, David Howells wrote: > > Hi James, > > Could you pull these patches into the security tree? They're based on your > next branch. This missed the merge for 3.12. Do you want me to queue the changes up, or do you want to send a pull request again after -rc1 ? > > The pat

[GIT PULL] Keyrings patches

2013-09-04 Thread David Howells
Hi James, Could you pull these patches into the security tree? They're based on your next branch. The patches can be viewed as a number of sets: (1) KEYS: Skip key state checks when checking for possession This is a fix for determining the possessed status of keys that have been in