From: Ivajlo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Ivajlo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Ivaylo Dimitrov <freemangordon@abv.bg>,
pavel@ucw.cz, pali.rohar@gmail.com
Subject: Re: [PATCH] Staging: TIDSPBRIDGE: Remove UUID helper
Date: Fri, 06 Dec 2013 09:41:40 +0200 [thread overview]
Message-ID: <52A17FB4.9000301@gmail.com> (raw)
In-Reply-To: <20131206073225.GD28413@mwanda>
My other patch (the one that fixes the security issue) was already
applied, albeit it was sent after this one, see
https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/commit/?h=staging-linus&id=559c71fe5dc3bf2ecc55afb336145db7f0abf810
, that is why I think there is some problem with the mail itself.
Sure I will wait :)
regards,
Ivo
On 06.12.2013 09:32, Dan Carpenter wrote:
> On Fri, Dec 06, 2013 at 08:05:38AM +0200, Ivajlo Dimitrov wrote:
>> Hi Greg,
>>
>> On 01.12.2013 19:07, Ivaylo DImitrov wrote:
>>> From: Ivaylo Dimitrov <freemangordon@abv.bg>
>>>
>>> Custom uuid helper function is needed only in rmgr/dbdcd.c and doesn't
>>> need to be exported. It can also be made way simpler by using sscanf.
>>>
>>> Signed-off-by: Ivaylo Dimitrov <freemangordon@abv.bg>
>>> ---
>>> drivers/staging/tidspbridge/Makefile | 2 +-
>>> drivers/staging/tidspbridge/gen/uuidutil.c | 85 --------------------
>>> .../tidspbridge/include/dspbridge/uuidutil.h | 18 ----
>>> drivers/staging/tidspbridge/rmgr/dbdcd.c | 42 +++++++++-
>>> 4 files changed, 39 insertions(+), 108 deletions(-)
>>> delete mode 100644 drivers/staging/tidspbridge/gen/uuidutil.c
>>>
>> I guess the initial mail somehow didn't make it through your spam filter:
>> https://lkml.org/lkml/2013/12/1/70
>>
> It's too early to start resending. Wait for another week at least.
>
> regards,
> dan carpenter
>
next prev parent reply other threads:[~2013-12-06 7:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 17:07 [PATCH] Staging: TIDSPBRIDGE: Remove UUID helper Ivaylo DImitrov
2013-12-01 19:06 ` Joe Perches
2013-12-01 23:26 ` Ivajlo Dimitrov
2013-12-06 6:05 ` Ivajlo Dimitrov
2013-12-06 7:32 ` Dan Carpenter
2013-12-06 7:41 ` Ivajlo Dimitrov [this message]
2013-12-06 15:10 ` gregkh
2013-12-07 8:41 ` Ivajlo Dimitrov
2013-12-08 7:18 ` gregkh
2013-12-08 12:32 ` Pavel Machek
2013-12-09 10:13 ` [PATCH v2] " Ivaylo DImitrov
2013-12-09 14:40 ` Pavel Machek
2013-12-09 18:34 ` Joe Perches
2013-12-10 22:03 ` [PATCH v3] " Ivaylo DImitrov
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=52A17FB4.9000301@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=freemangordon@abv.bg \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
/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