All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian.Birsan@microchip.com (m91496)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH linux-next v3 2/4] usb: gadget: udc: atmel: Minor code cleanup
Date: Fri, 7 Apr 2017 19:05:07 +0300	[thread overview]
Message-ID: <d736c194-e827-8d48-2e10-900dc33c6808@microchip.com> (raw)
In-Reply-To: <87efx7ghkz.fsf@linux.intel.com>

Hi,

The patch 2 does not apply because it's already on testing/next.

I'll send a new patch series version that will apply clean on top of testing branch.

Regards,
Cristi

On 05.04.2017 15:33, Felipe Balbi wrote:
> 
> Hi,
> 
> cristian.birsan at microchip.com writes:
>> From: Cristian Birsan <cristian.birsan@microchip.com>
>>
>> Minor code cleanup based on feedback received on mailinglist.
>>
>> Signed-off-by: Cristian Birsan <cristian.birsan@microchip.com>
>> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> 
> patch 1 applied fine, patch 2 didn't. Please rebase on testing/next
> 

WARNING: multiple messages have this Message-ID (diff)
From: m91496 <Cristian.Birsan@microchip.com>
To: Felipe Balbi <balbi@kernel.org>, <nicolas.ferre@atmel.com>,
	<gregkh@linuxfoundation.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <ludovic.desroches@atmel.com>,
	<alexandre.belloni@free-electrons.com>,
	<boris.brezillon@free-electrons.com>
Subject: Re: [PATCH linux-next v3 2/4] usb: gadget: udc: atmel: Minor code cleanup
Date: Fri, 7 Apr 2017 19:05:07 +0300	[thread overview]
Message-ID: <d736c194-e827-8d48-2e10-900dc33c6808@microchip.com> (raw)
In-Reply-To: <87efx7ghkz.fsf@linux.intel.com>

Hi,

The patch 2 does not apply because it's already on testing/next.

I'll send a new patch series version that will apply clean on top of testing branch.

Regards,
Cristi

On 05.04.2017 15:33, Felipe Balbi wrote:
> 
> Hi,
> 
> cristian.birsan@microchip.com writes:
>> From: Cristian Birsan <cristian.birsan@microchip.com>
>>
>> Minor code cleanup based on feedback received on mailinglist.
>>
>> Signed-off-by: Cristian Birsan <cristian.birsan@microchip.com>
>> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> 
> patch 1 applied fine, patch 2 didn't. Please rebase on testing/next
> 

  reply	other threads:[~2017-04-07 16:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  7:19 [PATCH linux-next v3 0/4] usb: gadget: udc: atmel: Endpoint allocation scheme fixes cristian.birsan at microchip.com
2017-04-03  7:19 ` cristian.birsan
2017-04-03  7:19 ` [PATCH linux-next v3 1/4] usb: gadget: udc: atmel: Check fifo configuration values against device tree cristian.birsan at microchip.com
2017-04-03  7:19   ` cristian.birsan
2017-04-03  7:19 ` [PATCH linux-next v3 2/4] usb: gadget: udc: atmel: Minor code cleanup cristian.birsan at microchip.com
2017-04-03  7:19   ` cristian.birsan
2017-04-05 12:33   ` Felipe Balbi
2017-04-05 12:33     ` Felipe Balbi
2017-04-07 16:05     ` m91496 [this message]
2017-04-07 16:05       ` m91496
2017-04-03  7:19 ` [PATCH linux-next v3 3/4] usb: gadget: udc: atmel: Use dev_err() to display EP configuration error cristian.birsan at microchip.com
2017-04-03  7:19   ` cristian.birsan
2017-04-03  7:19 ` [PATCH linux-next v3 4/4] usb: gadget: udc: atmel: Update Kconfig help for fifo_mode = 0 cristian.birsan at microchip.com
2017-04-03  7:19   ` cristian.birsan

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=d736c194-e827-8d48-2e10-900dc33c6808@microchip.com \
    --to=cristian.birsan@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.