[PATCH v2 3/6] staging: most: aim-cdev: make syscall write accept buffers of arbitrary size

[Christian Gromm]

On Fri, 23 Sep 2016 15:20:33 +0200
Greg KH <gregkh at linuxfoundation.org> wrote:

> On Fri, Sep 23, 2016 at 02:49:28PM +0200, Christian Gromm wrote:
> > On Fri, 23 Sep 2016 14:08:51 +0200
> > Greg KH <gregkh at linuxfoundation.org> wrote:
> > 
> > > On Thu, Sep 22, 2016 at 11:37:07AM +0200, Christian Gromm wrote:
> > > > This patch allows to call the write() function for synchronous
> > > > and isochronous channels with buffers of any size. The AIM
> > > > simply waits for data to fill up the MOST buffer object
> > > > according to the network interface controller specification for
> > > > streaming channels, before it submits the buffer to the HDM.
> > > > 
> > > > The new behavior is backward compatible to the old applications,
> > > > since all known applications needed to fill the buffer
> > > > completely anyway.
> > > > 
> > > > Signed-off-by: Christian Gromm <christian.gromm at microchip.com>
> > > > ---
> > > > 
> > > > v2: Since the previous patch of this series has beed dropped,
> > > > this patch needed some adaptation work to match the source tree
> > > > again.
> > > 
> > > Where are the 5 other patches in this series?
> > 
> > You dropped one and added four of them. This is the remaining one
> > that couldn't be applied.
> > 
> > Why would I resend patches that have already been added?
> 
> You shouldn't, but why would you resend a patch and claim it is the
> middle of a series of patches that are not sent at the same time?

Got your point and almost did it that way.

Then I thought the community would want the second version of a
patch to have the very same "subject" (except for v2) as the
original one to pull them together.

> 
> Remember, I have the short-term memory of a squirrel, I have no idea
> what was previously sent.  You wouldn't either if you dealt with as
> many patches as I get...

I see. :) But why do I need a v2 then anyway? If your process doesn't
track that there's been a first version around.

all the best,
Chris 

> 
> thanks,
> 
> greg k-h



-- 
Regards
Chris

Microchip Technology Germany II GmbH & Co. KG

Dipl.-Ing. (FH) Christian Gromm
Principal Software Engineer, AIS Engineering

Emmy-Noether-Straße 14, 76131 Karlsruhe | Germany
Tel: +49 721 62537 466 | Fax: +49 721 62537 119

christian.gromm at microchip.com | www.microchip.com

Firmensitz: Ismaning
Registergericht: Amtsgericht München HRA 98692
Haftender Gesellschafter: Microchip Technology Germany GmbH, Gilching
Geschäftsführer: Mohammed Nawaz Sharif, James Eric Bjornholt, Ulrich
Hallerberg

Diese E-Mail kann vertrauliche Informationen enthalten. Sie darf nicht
durch andere als die ursprünglich genannten Adressaten genutzt, kopiert
oder weitergeleitet werden. This e-mail may contain confidential
information and should not be used, copied or disclosed by anyone who
is not the original intended recipient.