From: Greg KH <greg@kroah.com>
To: "Gomonovych, Vasyl" <gomonovych@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
sudeep.dutt@intel.com, ashutosh.dixit@intel.com,
dan.carpenter@oracle.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH v2] misc: mic: Use memdup_user() as a cleanup
Date: Wed, 13 Dec 2017 10:30:27 +0100 [thread overview]
Message-ID: <20171213093027.GA13194@kroah.com> (raw)
In-Reply-To: <CAHYXAnJw78JRqBj9LBr5-e0PffO=xXeRDJvs9cHCYjR0Wcw3tg@mail.gmail.com>
On Tue, Dec 12, 2017 at 02:22:41PM +0100, Gomonovych, Vasyl wrote:
> Hi,
> Thanks.
> Should I prepare fix patch only for missed label?
I have no context here at all, sorry...
next prev parent reply other threads:[~2017-12-13 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 3:39 linux-next: build warning after merge of the char-misc tree Stephen Rothwell
2017-12-12 10:40 ` [PATCH v2] misc: mic: Use memdup_user() as a cleanup Vasyl Gomonovych
2017-12-12 11:49 ` Greg KH
2017-12-12 13:22 ` Gomonovych, Vasyl
2017-12-13 9:30 ` Greg KH [this message]
2017-12-13 22:01 ` [PATCH v3] " Vasyl Gomonovych
2017-12-19 9:17 ` Greg KH
2017-12-12 11:49 ` linux-next: build warning after merge of the char-misc tree Greg KH
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=20171213093027.GA13194@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=gomonovych@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudeep.dutt@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.