linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Biwen Li <biwen.li@nxp.com>
Cc: "Biwen Li (OSS)" <biwen.li@oss.nxp.com>,
	Leo Li <leoyang.li@nxp.com>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"wsa@the-dreams.de" <wsa@the-dreams.de>,
	Jiafei Pan <jiafei.pan@nxp.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: slave: support I2C_SLAVE_STOP event for the read transactions
Date: Mon, 30 Mar 2020 13:12:31 +0200	[thread overview]
Message-ID: <20200330111231.x2a57acoy57ycyo6@pengutronix.de> (raw)
In-Reply-To: <DB6PR0401MB24389E2570C242FB9036EC968FCB0@DB6PR0401MB2438.eurprd04.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Hi,

On Mon, Mar 30, 2020 at 10:56:28AM +0000, Biwen Li wrote:
> Hi All,
> 
> The patch based on https://patchwork.ozlabs.org/patch/1203640/
> and it is not accepted, so it(https://patchwork.ozlabs.org/patch/1203640/) is needed before apply the new patch. 

I'm not sure what should I do with this information. This links are to
the patch which needed to be update by you, before it can be reviewed
and then hopefully accepted. Why do you sending one more patch for
review for a patch which is not accepted? 

> Best Regards,
> Biwen Li
> > Support I2C_SLAVE_STOP event for the read transactions(master read from
> > slave)
> > 
> > Signed-off-by: Biwen Li <biwen.li@nxp.com>
> > ---
> >  drivers/i2c/busses/i2c-imx.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c index
> > 62517a41b32d..1fd0d87885d5 100644
> > --- a/drivers/i2c/busses/i2c-imx.c
> > +++ b/drivers/i2c/busses/i2c-imx.c
> > @@ -1464,6 +1464,7 @@ static irqreturn_t i2c_imx_slave_isr(struct
> > imx_i2c_struct *i2c_imx)
> >  		ctl &= ~I2CR_MTX;
> >  		imx_i2c_write_reg(ctl, i2c_imx, IMX_I2C_I2CR);
> >  		imx_i2c_read_reg(i2c_imx, IMX_I2C_I2DR);
> > +		i2c_slave_event(i2c_imx->slave, I2C_SLAVE_STOP, &value);
> >  	}
> >  	return IRQ_HANDLED;
> >  }
> > --
> > 2.17.1

Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-30 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 10:50 [PATCH] i2c: slave: support I2C_SLAVE_STOP event for the read transactions Biwen Li
2020-03-30 10:56 ` Biwen Li
2020-03-30 11:12   ` Oleksij Rempel [this message]
2020-03-31  8:48     ` Biwen Li (OSS)
2020-04-01  5:18       ` Oleksij Rempel
2020-04-13  1:47         ` Biwen Li (OSS)

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=20200330111231.x2a57acoy57ycyo6@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=biwen.li@nxp.com \
    --cc=biwen.li@oss.nxp.com \
    --cc=jiafei.pan@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).