linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcus Wolf <marcus.wolf@smarthome-wolf.de>
Cc: devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: staging: pi433: Possible bug in rf69.c
Date: Sat, 11 Nov 2017 11:45:01 +0300	[thread overview]
Message-ID: <20171111084501.chwx5ku2senlgdza@mwanda> (raw)
In-Reply-To: <a8d75f3c-b7b1-19eb-4ecb-54b9a003d34c@smarthome-wolf.de>

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,
> Colin King or Julia Lawall, changing '&' to '|'. I guess the patch for
> some reason wasn't accepted, but fortunatley I introduced the change to
> my SVN.

You sent the patch, but then talked about sending a new version so
that's why it wasn't merged.  Greg probably would have merged it as-is
if it hadn't sounded like you were going to redo it.

http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2017-July/108821.html

regards,
dan carpenter

  parent reply	other threads:[~2017-11-11  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 17:23 staging: pi433: Possible bug in rf69.c 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 [this message]
2017-11-11  9:42       ` Marcus Wolf
2017-11-11 11:18         ` Greg Kroah-Hartman
2017-11-11 11:42           ` Marcus Wolf
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=20171111084501.chwx5ku2senlgdza@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus.wolf@smarthome-wolf.de \
    /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;
as well as URLs for NNTP newsgroup(s).