All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: sameo@linux.intel.com, davem@davemloft.net, netdev@vger.kernel.org
Cc: allen.pais@oracle.com, keescook@chromium.org, surenb@google.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 0/2] NFC fixes for 4.19-final
Date: Mon, 17 Sep 2018 15:51:39 +0200	[thread overview]
Message-ID: <20180917135141.28328-1-gregkh@linuxfoundation.org> (raw)

For some reason, these two NFC patches fell through the cracks.  It
looks like sometimes NFC patches go through the wireless tree, and
other times, through the networking tree directly.

I don't care which way they go, but they should get merged through some
way, or, I can take them in my device tree, but that feels a bit odd to
me.

thanks,

greg k-h

Suren Baghdasaryan (2):
  NFC: Fix possible memory corruption when handling SHDLC I-Frame
    commands
  NFC: Fix the number of pipes

 include/net/nfc/hci.h |  2 +-
 net/nfc/hci/core.c    | 10 ++++++++++
 2 files changed, 11 insertions(+), 1 deletion(-)

-- 
2.19.0

             reply	other threads:[~2018-09-17 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:51 Greg Kroah-Hartman [this message]
2018-09-17 13:51 ` [PATCH 1/2] NFC: Fix possible memory corruption when handling SHDLC I-Frame commands Greg Kroah-Hartman
2018-09-17 13:51 ` [PATCH 2/2] NFC: Fix the number of pipes Greg Kroah-Hartman
2018-09-19  2:54 ` [PATCH 0/2] NFC fixes for 4.19-final David Miller

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=20180917135141.28328-1-gregkh@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=allen.pais@oracle.com \
    --cc=davem@davemloft.net \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=surenb@google.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.