On Tue, Oct 30, 2012 at 10:27:55PM +, Arnd Bergmann wrote:
> On Monday 29 October 2012, Richard Cochran wrote:
> > On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
> > >
> > > Don't get me wrong. If I had time for this it could be different.
> > > Unfortunately IXP4xx is a
On Monday 29 October 2012, Richard Cochran wrote:
> On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
> >
> > Don't get me wrong. If I had time for this it could be different.
> > Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
> > this point. Given the
On Monday 29 October 2012, Richard Cochran wrote:
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
Don't get me wrong. If I had time for this it could be different.
Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
this point. Given the raised
On Tue, Oct 30, 2012 at 10:27:55PM +, Arnd Bergmann wrote:
On Monday 29 October 2012, Richard Cochran wrote:
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
Don't get me wrong. If I had time for this it could be different.
Unfortunately IXP4xx is a legacy arch,
On 18/10/12 09:01, Krzysztof Halasa wrote:
> Hi,
>
>
> Unfortunately, as I already explained to you in
> https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
> limited (and this isn't a paid job) and I'm in no way able to do what
> you require. This, coupled with my inability
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
> Hi,
>
> Arnd Bergmann writes:
> > Also, never rebase your tree immediately before sending a pull
> > request.
>
> I did not, of course. My mail stated:
> "Build-tested for now. This is based on your current tree tip because it
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
>
> Don't get me wrong. If I had time for this it could be different.
> Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
> this point. Given the raised barriers to participate, probably aimed at
> paid
On 18/10/12 09:01, Krzysztof Halasa wrote:
Hi,
snip
Unfortunately, as I already explained to you in
https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
limited (and this isn't a paid job) and I'm in no way able to do what
you require. This, coupled with my inability to
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
Don't get me wrong. If I had time for this it could be different.
Unfortunately IXP4xx is a legacy arch, and for me it's simply a hobby at
this point. Given the raised barriers to participate, probably aimed at
paid
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
Hi,
Arnd Bergmann a...@arndb.de writes:
Also, never rebase your tree immediately before sending a pull
request.
I did not, of course. My mail stated:
Build-tested for now. This is based on your current tree tip because
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
...
> Unfortunately, as I already explained to you in
> https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
> limited (and this isn't a paid job) and I'm in no way able to do what
> you require. This, coupled with
On Thu, Oct 18, 2012 at 12:01:17AM +0200, Krzysztof Halasa wrote:
...
Unfortunately, as I already explained to you in
https://lkml.org/lkml/2012/9/29/37, my resources for IXP4xx are very
limited (and this isn't a paid job) and I'm in no way able to do what
you require. This, coupled with my
Hi,
Arnd Bergmann writes:
> as mentioned before, all arch/arm/mach-* patches should go through the
> arm-soc tree or get an Ack from the arm-soc maintainers. The same thing
> is true for the char-misc and the crypto trees.
You've seen the changes. They were trivial fixes, touched only
Hi,
Arnd Bergmann a...@arndb.de writes:
as mentioned before, all arch/arm/mach-* patches should go through the
arm-soc tree or get an Ack from the arm-soc maintainers. The same thing
is true for the char-misc and the crypto trees.
You've seen the changes. They were trivial fixes, touched
On Saturday 13 October 2012, Krzysztof Halasa wrote:
> Linus,
>
> please pull my ARM IXP4xx changes for 3.7:
>
> The following changes since commit 4d7127dace8cf4b05eb7c8c8531fc204fbb195f4:
>
> "Merge branch 'for-linus' of git://git.kernel.org/.../jmorris/linux-security"
> (2012-10-13 11:29:00
On Saturday 13 October 2012, Krzysztof Halasa wrote:
Linus,
please pull my ARM IXP4xx changes for 3.7:
The following changes since commit 4d7127dace8cf4b05eb7c8c8531fc204fbb195f4:
Merge branch 'for-linus' of git://git.kernel.org/.../jmorris/linux-security
(2012-10-13 11:29:00 +0900)
Linus,
please pull my ARM IXP4xx changes for 3.7:
The following changes since commit 4d7127dace8cf4b05eb7c8c8531fc204fbb195f4:
"Merge branch 'for-linus' of git://git.kernel.org/.../jmorris/linux-security"
(2012-10-13 11:29:00 +0900)
are available in the git repository at:
Linus,
please pull my ARM IXP4xx changes for 3.7:
The following changes since commit 4d7127dace8cf4b05eb7c8c8531fc204fbb195f4:
Merge branch 'for-linus' of git://git.kernel.org/.../jmorris/linux-security
(2012-10-13 11:29:00 +0900)
are available in the git repository at:
18 matches
Mail list logo