From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: sr1500: Remove USB_GADGET
Date: Mon, 11 Apr 2016 18:01:57 +0200 [thread overview]
Message-ID: <570BCA75.5090803@denx.de> (raw)
In-Reply-To: <CAKaJLVtQqdfqyhKqf6DX5C+_tKL8gDtBZxO9XyN_DvE1dxcDvg@mail.gmail.com>
On 04/11/2016 05:47 PM, Sam Protsenko wrote:
> On Mon, Apr 11, 2016 at 6:41 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>> On 04/11/2016 05:09 PM, Sam Protsenko wrote:
>>> On Sun, Apr 3, 2016 at 5:34 PM, Stefan Roese <sr@denx.de> wrote:
>>>> On 01.04.2016 20:27, Semen Protsenko wrote:
>>>>>
>>>>> From: Sam Protsenko <semen.protsenko@linaro.org>
>>>>>
>>>>> "buildman" tool revealed that USB_GADGET was enabled by mistake for this
>>>>> board in process of moving that option to Kconfig. Remove it to bring
>>>>> things back to correct state.
>>>>>
>>>>> Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
>>>>
>>>>
>>>> Acked-by: Stefan Roese <sr@denx.de>
>>>>
>>>> Thanks,
>>>> Stefan
>>>>
>>>
>>> Tom,
>>>
>>> Can you please take a look and merge this patch?
>>
>> It would be fantastic if you kept me on CC. Such patches should go
>> through the socfpga tree. But it would be easier for Tom to pick it
>> this time so I dont have to roll another PR before rc1.
>
> Sure thing. I guess "get_maintainer.pl" didn't show you for this
> patch, because it only affects configs/. But it's indeed socfpga
> related, so I'll be more careful next time.
Thanks. All socfpga stuff goes to/through Dinh, Chin and me.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-11 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 18:27 [U-Boot] [PATCH] arm: socfpga: sr1500: Remove USB_GADGET Semen Protsenko
2016-04-03 14:34 ` Stefan Roese
2016-04-11 15:09 ` Sam Protsenko
2016-04-11 15:41 ` Marek Vasut
2016-04-11 15:47 ` Sam Protsenko
2016-04-11 16:01 ` Marek Vasut [this message]
2016-04-12 2:28 ` [U-Boot] " Tom Rini
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=570BCA75.5090803@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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