From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Samuel Iglesias Gonsálvez" <siglesias@igalia.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
industrypack-devel@lists.sourceforge.net,
Jens Taprogge <jens.taprogge@taprogge.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] ipack: Improve a size determination in ipack_bus_register()
Date: Mon, 15 May 2017 07:56:53 +0200 [thread overview]
Message-ID: <20170515055653.GA5658@kroah.com> (raw)
In-Reply-To: <1494823967.2172.1.camel@igalia.com>
On Mon, May 15, 2017 at 06:52:47AM +0200, Samuel Iglesias Gonsálvez wrote:
> Hello Markus,
>
> Thanks for the patches!
>
> Series is,
>
> Acked-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
>
> Greg, Would you mind picking this patch series through your char-misc
> tree?
I'm sorry, but this person is in my blacklist and I don't have any of
their emails, so I don't have these patches anywhere. If you wish to
have them applied, please resend them with your acked-by, or just ignore
them, it's up to you.
good luck!
greg k-h
next prev parent reply other threads:[~2017-05-15 5:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 8:54 [PATCH 0/2] Industry-pack bus: Adjustments for two function implementations SF Markus Elfring
2017-05-13 8:55 ` [PATCH 1/2] ipack: Delete an error message for a failed memory allocation in ipack_device_read_id() SF Markus Elfring
2017-05-13 8:56 ` [PATCH 2/2] ipack: Improve a size determination in ipack_bus_register() SF Markus Elfring
2017-05-15 4:52 ` Samuel Iglesias Gonsálvez
2017-05-15 5:56 ` Greg Kroah-Hartman [this message]
2017-05-15 6:40 ` SF Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2017-05-15 9:08 [PATCH 1/2] ipack: Delete an error message for a failed memory allocation in ipack_device_read_id() Samuel Iglesias Gonsálvez
2017-05-15 9:08 ` [PATCH 2/2] ipack: Improve a size determination in ipack_bus_register() Samuel Iglesias Gonsálvez
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=20170515055653.GA5658@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=elfring@users.sourceforge.net \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siglesias@igalia.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