From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "arnd@arndb.de" <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [char-misc-next 2/3] mei: fix reading large reposnes
Date: Fri, 19 Apr 2013 18:59:49 +0000 [thread overview]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B01F022F4@HASMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <20130419182543.GA30807@kroah.com>
>
> On Fri, Apr 19, 2013 at 09:16:54PM +0300, Tomas Winkler wrote:
> > While writting to device is limitted to max_msg_length advertized in
> > client properites the read can be much longer delivered consequiting
> chunks.
> >
> > We use krealloc to enlarge the buffer when needed.
> >
> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
>
> Patch 1/3 had some fuzz in interrupt.c, so I fixed that up by hand, but this
> one just fails to apply at all:
> checking file drivers/misc/mei/bus.c
> checking file drivers/misc/mei/client.c
> checking file drivers/misc/mei/client.h
> checking file drivers/misc/mei/interrupt.c
> Hunk #1 FAILED at 145.
> 1 out of 1 hunk FAILED
> checking file drivers/misc/mei/main.c
>
> So something is out of sync between us.
>
> Care to refresh this patch based on my latest tree, and 3/3, and resend
> them?
Grrr, I sent you one patch less, I've rebased this new spelling fix and missed to count it in.
I'm resending the missing patches.
Tomas
next prev parent reply other threads:[~2013-04-19 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 18:16 [char-misc-next 1/3] mei: revamp mei_amthif_irq_read_message Tomas Winkler
2013-04-19 18:16 ` [char-misc-next 2/3] mei: fix reading large reposnes Tomas Winkler
2013-04-19 18:25 ` Greg KH
2013-04-19 18:59 ` Winkler, Tomas [this message]
2013-04-19 18:16 ` [char-misc-next 3/3 V2] mei: reseting -> resetting Tomas Winkler
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=5B8DA87D05A7694D9FA63FD143655C1B01F022F4@HASMSX106.ger.corp.intel.com \
--to=tomas.winkler@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®