Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-26 Thread PrasannaKumar Muralidharan
Hi Dan, On 26 November 2017 at 02:10, Dan Carpenter wrote: > Paul's original patch should have been separated into two patches to > begin with. The patch does two different things and one part goes > through the MIPS tree and one part goes through Andrew, probably.

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-26 Thread PrasannaKumar Muralidharan
Hi Dan, On 26 November 2017 at 02:10, Dan Carpenter wrote: > Paul's original patch should have been separated into two patches to > begin with. The patch does two different things and one part goes > through the MIPS tree and one part goes through Andrew, probably. Okay. I will split his patch

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-25 Thread Dan Carpenter
Paul's original patch should have been separated into two patches to begin with. The patch does two different things and one part goes through the MIPS tree and one part goes through Andrew, probably. On Sat, Nov 25, 2017 at 10:52:04PM +0530, PrasannaKumar Muralidharan wrote: > Hi, > > On 4

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-25 Thread Dan Carpenter
Paul's original patch should have been separated into two patches to begin with. The patch does two different things and one part goes through the MIPS tree and one part goes through Andrew, probably. On Sat, Nov 25, 2017 at 10:52:04PM +0530, PrasannaKumar Muralidharan wrote: > Hi, > > On 4

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-25 Thread PrasannaKumar Muralidharan
Hi, On 4 October 2017 at 22:26, PrasannaKumar Muralidharan wrote: > When there is no overlap between src and dst use optimised memcpy if it > is available. > > Signed-off-by: Paul Burton > Signed-off-by: PrasannaKumar Muralidharan

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-11-25 Thread PrasannaKumar Muralidharan
Hi, On 4 October 2017 at 22:26, PrasannaKumar Muralidharan wrote: > When there is no overlap between src and dst use optimised memcpy if it > is available. > > Signed-off-by: Paul Burton > Signed-off-by: PrasannaKumar Muralidharan > --- > This change is a small part of a patch [1] from Paul

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-10-21 Thread PrasannaKumar Muralidharan
On 4 October 2017 at 22:26, PrasannaKumar Muralidharan wrote: > When there is no overlap between src and dst use optimised memcpy if it > is available. > > Signed-off-by: Paul Burton > Signed-off-by: PrasannaKumar Muralidharan

Re: [PATCH] lib: memmove: Use optimised memcpy if possible

2017-10-21 Thread PrasannaKumar Muralidharan
On 4 October 2017 at 22:26, PrasannaKumar Muralidharan wrote: > When there is no overlap between src and dst use optimised memcpy if it > is available. > > Signed-off-by: Paul Burton > Signed-off-by: PrasannaKumar Muralidharan > --- > This change is a small part of a patch [1] from Paul Burton.

[PATCH] lib: memmove: Use optimised memcpy if possible

2017-10-04 Thread PrasannaKumar Muralidharan
When there is no overlap between src and dst use optimised memcpy if it is available. Signed-off-by: Paul Burton Signed-off-by: PrasannaKumar Muralidharan --- This change is a small part of a patch [1] from Paul Burton. I have added his

[PATCH] lib: memmove: Use optimised memcpy if possible

2017-10-04 Thread PrasannaKumar Muralidharan
When there is no overlap between src and dst use optimised memcpy if it is available. Signed-off-by: Paul Burton Signed-off-by: PrasannaKumar Muralidharan --- This change is a small part of a patch [1] from Paul Burton. I have added his Signed-off by. I do not know whether it is correct. Please