From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] gnss: fixes for char-misc-next
Date: Mon, 16 Jul 2018 12:48:45 +0200 [thread overview]
Message-ID: <20180716104845.GA18483@kroah.com> (raw)
In-Reply-To: <20180716104203.28440-1-johan@kernel.org>
On Mon, Jul 16, 2018 at 12:42:01PM +0200, Johan Hovold wrote:
> Hi Greg,
>
> Here's a resend of two gnss fixes for char-misc-next which I noted you
> haven't picked up directly (I'll continue picking these up an forwarding
> to you in batches if that's alright).
That's fine, I didn't see them myself, which is why I didn't pick them
up. I'll just wait for you to forward patches on for this subsystem, as
that makes things a lot easier for me.
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-16 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 10:42 [PATCH 0/2] gnss: fixes for char-misc-next Johan Hovold
2018-07-16 10:42 ` [PATCH 1/2] gnss: ubx: make struct ubx_gserial_ops static Johan Hovold
2018-07-16 10:42 ` [PATCH 2/2] gnss: fix potential error pointer dereference Johan Hovold
2018-07-16 10:48 ` Greg Kroah-Hartman [this message]
2018-07-16 12:16 ` [PATCH 0/2] gnss: fixes for char-misc-next Johan Hovold
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=20180716104845.GA18483@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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