linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: [PATCH] depmod: fix errorpath memleaks in report cycles logic
Date: Mon, 8 May 2017 23:48:55 -0700	[thread overview]
Message-ID: <CAKi4VA+yFRHxENG0s6SF1REcf+5k6Q2G4Rp0g+iaJPStejjQ2Q@mail.gmail.com> (raw)
In-Reply-To: <xunyk27kgs3j.fsf@redhat.com>

On Mon, Mar 20, 2017 at 3:28 AM, Yauheni Kaliuta
<yauheni.kaliuta@redhat.com> wrote:
> Hi!
>
>>>>>> On Mon, 20 Mar 2017 12:09:51 +0200, Yauheni Kaliuta  wrote:
>
>  > From: Yauheni Kaliuta <y.kaliuta@gmail.com>
>
> Ooops. Could you please remove the line? ;)

Yep. Applied, thanks.

Lucas De Marchi

      reply	other threads:[~2017-05-09  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 10:09 [PATCH] depmod: fix errorpath memleaks in report cycles logic Yauheni Kaliuta
2017-03-20 10:28 ` Yauheni Kaliuta
2017-05-09  6:48   ` Lucas De Marchi [this message]

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=CAKi4VA+yFRHxENG0s6SF1REcf+5k6Q2G4Rp0g+iaJPStejjQ2Q@mail.gmail.com \
    --to=lucas.de.marchi@gmail.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=yauheni.kaliuta@redhat.com \
    /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).