On Thu, Nov 30, 2017 at 07:38:41PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> don't know, wether that's best option.
What is?
> With that procedure, it will be very hard, to integrate large patches, if
> the owner of the patch isn't dealing with kernel source in his daily
> business and thus
Hi Greg,
don't know, wether that's best option.
With that procedure, it will be very hard, to integrate large patches,
if the owner of the patch isn't dealing with kernel source in his daily
business and thus isn't able to react on new releases within no time.
I've seen the release of
On Thu, Nov 30, 2017 at 06:01:46PM +0100, Marcin Ciupak wrote:
> On Sat, Nov 11, 2017 at 01:51:10PM +0200, Marcus Wolf wrote:
> Hi Marcus,
>
> since 4.15-rc1 is out I would like to ask if you are going to provide
> your changes anytime soon?
>
> I would like to send a few patches as well and do
On Sat, Nov 11, 2017 at 01:51:10PM +0200, Marcus Wolf wrote:
Hi Marcus,
since 4.15-rc1 is out I would like to ask if you are going to provide
your changes anytime soon?
I would like to send a few patches as well and do not want to block your
work.
Thanks,
Marcin
> Hi Greg,
>
> ok.
>
> I'll
On Fri, 2017-11-10 at 18:23 +0100, Marcus Wolf wrote:
> Hi everybody!
>
> Just comparing the master of Gregs statging of pi433 with my local SVN
> to review all changes, that were done the last monthes.
>
> I am not sure, but maybe we imported a bug in rf69.c lines 378 and
> following:
>
>
Hi Joe,
thank you for your suggestion.
The enums are necessary for the (old fashioned) ioctl interface, too.
So the user space uses these enums in order to configure the driver.
If we want to completely remove rf69_enum.h, we need to find a solution
for that, too.
From the optics/readability,
On Sat, Nov 11, 2017 at 01:51:10PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> ok.
>
> I'll postpone all my work until then. Give me a hook, when I can start :-)
I am not going to remember, sorry, I deal with over 1000 patches a week.
Just watch kernel.org for when the new kernel is released.
On Sat, Nov 11, 2017 at 11:42:09AM +0200, Marcus Wolf wrote:
> But I still need to know when to use staging and when to use linux-next.
> I don't want to prepare patches for the wrong tree.
Ah, I see now that the confusion is Al's patch. Al is a law unto
himself so I don't know the answer.
Hi Greg,
ok.
I'll postpone all my work until then. Give me a hook, when I can start :-)
Thanks,
Marcus
Am 11.11.2017 um 13:49 schrieb Greg Kroah-Hartman:
On Sat, Nov 11, 2017 at 01:42:27PM +0200, Marcus Wolf wrote:
Hi Greg,
that's fine.
Is this the right URL:
On Sat, Nov 11, 2017 at 01:42:27PM +0200, Marcus Wolf wrote:
> Hi Greg,
>
> that's fine.
>
> Is this the right URL:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
Yes.
> Is there already an aprox. date, when 4.15rc1 will be out and
> backintegration will be done?
Should
Hi Greg,
that's fine.
Is this the right URL:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
Is there already an aprox. date, when 4.15rc1 will be out and
backintegration will be done?
Thx,
Marcus
Am 11.11.2017 um 13:18 schrieb Greg Kroah-Hartman:
On Sat, Nov 11, 2017
On Sat, Nov 11, 2017 at 11:42:09AM +0200, Marcus Wolf wrote:
> Hi Dan,
>
> thanks fot the link. I can't remeber, why and what I wanted to redo. Maybe
> there was a complaint about the format of the patch...
>
> In that patch, we also have the topic with the '>> 3', we were discussing a
> few
Hi Dan,
thanks fot the link. I can't remeber, why and what I wanted to redo.
Maybe there was a complaint about the format of the patch...
In that patch, we also have the topic with the '>> 3', we were
discussing a few days ago!
I'd suggest, not to invest the history any more. I'm ok with
On Sat, Nov 11, 2017 at 08:55:30AM +0100, Marcus Wolf wrote:
> Hi Dan,
>
> I checked it on my local SVN. You are right. I submitted the code with '&'.
> Accodring to a check-in message on my SVN, there was a bugreport end of
> July and most probably a patch - either from me, you, Joseph Wright,
>
On Sat, Nov 11, 2017 at 08:55:30AM +0100, Marcus Wolf wrote:
> Shortly befor I fell ill, you proposed me to use Gregs staging for my
> further development. But Colin yesterday was working on a repo, called
> linux-next.
>
> Can you (or anyone else) please tell me, when (or for which kind of
>
Hi Dan,
I checked it on my local SVN. You are right. I submitted the code with '&'.
Accodring to a check-in message on my SVN, there was a bugreport end of
July and most probably a patch - either from me, you, Joseph Wright,
Colin King or Julia Lawall, changing '&' to '|'. I guess the patch for
On Fri, Nov 10, 2017 at 06:23:32PM +0100, Marcus Wolf wrote:
> Hi everybody!
>
> Just comparing the master of Gregs statging of pi433 with my local SVN
> to review all changes, that were done the last monthes.
>
> I am not sure, but maybe we imported a bug in rf69.c lines 378 and
> following:
>
Hi everybody!
Just comparing the master of Gregs statging of pi433 with my local SVN
to review all changes, that were done the last monthes.
I am not sure, but maybe we imported a bug in rf69.c lines 378 and
following:
Gregs repo:
case automatic: return WRITE_REG(REG_LNA, (
18 matches
Mail list logo
