mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcus Wolf <marcus.wolf@smarthome-wolf.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: staging: pi433: Possible bug in rf69.c
Date: Sat, 11 Nov 2017 13:42:27 +0200	[thread overview]
Message-ID: <5279c977-d62c-cbf4-a764-149ddc80e37a@smarthome-wolf.de> (raw)
In-Reply-To: <20171111111819.GA14436@kroah.com>

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 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 days ago!
>>
>> I'd suggest, not to invest the history any more. I'm ok with preparing a new
>> patch/new patches, so we can import the fixes.
>>
>> I also have several improvements for the rf69.c, I'd like to offer.
>>
>> 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.
> 
> I recommend waiting for 4.15-rc1 to come out, all of the different trees
> will be merged, and then you can just work off of the staging-next tree
> and I can take the patches.
> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2017-11-11 11:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 17:23 Marcus Wolf
2017-11-10 19:32 ` Dan Carpenter
2017-11-11  7:55   ` Marcus Wolf
2017-11-11  8:40     ` Dan Carpenter
2017-11-11  8:45     ` Dan Carpenter
2017-11-11  9:42       ` Marcus Wolf
2017-11-11 11:18         ` Greg Kroah-Hartman
2017-11-11 11:42           ` Marcus Wolf [this message]
2017-11-11 11:49             ` Greg Kroah-Hartman
2017-11-11 11:51               ` Marcus Wolf
2017-11-11 12:33                 ` Greg Kroah-Hartman
2017-11-11 12:10         ` Dan Carpenter
2017-11-11 16:02 ` Joe Perches
2017-11-11 16:40   ` Marcus Wolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5279c977-d62c-cbf4-a764-149ddc80e37a@smarthome-wolf.de \
    --to=marcus.wolf@smarthome-wolf.de \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®