From: Dan Priamo <danp@adiengineering.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Steve Douthit <stephend@adiengineering.com>,
"seth.heasley@intel.com" <seth.heasley@intel.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/2] i2c: ismt: Fix length handling for SMBus block reads
Date: Tue, 29 Aug 2017 20:10:48 +0000 [thread overview]
Message-ID: <VI1PR0401MB2303FCB4B465FC147AC55A71BB9F0@VI1PR0401MB2303.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20170829200830.op73cdkwjmhrht3k@ninjato>
Thank you!
-----Original Message-----
From: Wolfram Sang [mailto:wsa@the-dreams.de]
Sent: Tuesday, August 29, 2017 4:09 PM
To: Dan Priamo <danp@adiengineering.com>
Cc: Neil Horman <nhorman@tuxdriver.com>; Steve Douthit <stephend@adiengineering.com>; seth.heasley@intel.com; linux-i2c@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: ismt: Fix length handling for SMBus block reads
> We are using Linux stable kernel version 4.4.y and would like to see
> these changes included in that version. So once these patches are
> merged in, can they be tagged for other Linux stable kernel releases
> to pick up these changes?
Okay, since I haven't pushed out yet, I can re-apply the bugfix to for-current and add the stable tag to it.
prev parent reply other threads:[~2017-08-29 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 21:10 [PATCH 0/2] i2c: ismt: Fix length handling for SMBus block reads Stephen Douthit
2017-08-07 21:10 ` [PATCH 1/2] i2c: ismt: Don't duplicate the receive length for " Stephen Douthit
2017-08-07 21:11 ` [PATCH 2/2] i2c: ismt: Return EMSGSIZE for block reads with bogus length Stephen Douthit
2017-08-14 19:31 ` [PATCH 0/2] i2c: ismt: Fix length handling for SMBus block reads Wolfram Sang
2017-08-28 13:50 ` Stephen Douthit
2017-08-29 10:22 ` Wolfram Sang
2017-08-29 11:35 ` Neil Horman
2017-08-29 11:49 ` Wolfram Sang
2017-08-29 18:12 ` Dan Priamo
2017-08-29 20:08 ` Wolfram Sang
2017-08-29 20:10 ` Dan Priamo [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=VI1PR0401MB2303FCB4B465FC147AC55A71BB9F0@VI1PR0401MB2303.eurprd04.prod.outlook.com \
--to=danp@adiengineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=seth.heasley@intel.com \
--cc=stephend@adiengineering.com \
--cc=wsa@the-dreams.de \
/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.