public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] kconfig: introduce kconfig for UBI
Date: Wed, 21 Sep 2016 07:41:34 +0200	[thread overview]
Message-ID: <57E21D8E.100@denx.de> (raw)
In-Reply-To: <20160920150221.GV29602@bill-the-cat>

Hello Andrew,

Am 20.09.2016 um 17:02 schrieb Tom Rini:
> On Tue, Sep 20, 2016 at 09:26:15AM -0500, Andrew F. Davis wrote:
>> On 09/20/2016 12:50 AM, Heiko Schocher wrote:
>>> Hello Andrew,
>>>
>>> Am 19.09.2016 um 18:03 schrieb Andrew F. Davis:
>>>> BTW, the following addresses that bounce should be removed from wherever
>>>> you found them or added to .get_maintainer.ignore if they are part of
>>>> old commits:
>>>>
>>>> Bo Shen <voice.shen@atmel.com>
>>>> Albert ARIBAUD <albert-u-boot@aribaud.net>
>>>> Gerald Kerma <dreagle@doukki.net>
>>>> Karl Beldan <kbeldan@baylibre.com>
>>>> Vaibhav Hiremath <hvaibhav@ti.com>
>>>> Sudhakar Rajashekhara <sudhakar.raj@ti.com>
>>>>
>>>
>>> Hmm.. I used patman for creating the patch and so patman created with
>>> the help of scripts/get_maintainer.pl creates the cc list ...
>>>
>>
>> It seems most of these are from MAINTAINER files, these names need to be
>> removed and their subsystem status changed to unmaintained until new
>> maintainers can step up.
>>
>>> I just tried to create such a ".get_maintainer.ignore" file, but
>>> doesn;t work ... ah, I see, the get_maintainer.pl from U-Boot does
>>> not support the ".get_maintainer.ignore" file
>>>
>>> Hmm.. looked into it, not easy (for me) to fix this "fast" ...
>>>
>>
>> Looks like the scripts/get_maintainer.pl needs to be synced with the
>> Linux version, something like:
>>
>> ---
>>
>>  From b9a032c6e33cfe59f9d2cd6d0901bf588aad3b5f Mon Sep 17 00:00:00 2001
>> From: "Andrew F. Davis" <afd@ti.com>
>> Date: Tue, 20 Sep 2016 07:59:58 -0500
>> Subject: [PATCH] get_maintainer.pl: Sync with latest version from Linux
>
> Yes, a re-sync with special attention paid to the few intentional
> differences is once again in order :)  Please submit as a formal patch
> after checking that we didn't lose those (I think it's an easy one and
> checkpatch.pl is where it's a tiny bit harder, we never finished
> convincing upstream to take one change we had, iirc).

Yes, that would be great, just tried your patch proposal, it seems
to work :-)

Please add also in your commit description, the linux commit ID, which
is your base, thanks!

bye,
Heeiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2016-09-21  5:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  5:03 [U-Boot] [RFC PATCH] kconfig: introduce kconfig for UBI Heiko Schocher
2016-09-19  0:58 ` Simon Glass
2016-09-19 15:38 ` Andrew F. Davis
2016-09-20  5:26   ` Heiko Schocher
2016-09-20 14:21     ` Andrew F. Davis
2016-09-19 16:03 ` Andrew F. Davis
2016-09-20  5:50   ` Heiko Schocher
2016-09-20 14:26     ` Andrew F. Davis
2016-09-20 15:02       ` Tom Rini
2016-09-21  5:41         ` Heiko Schocher [this message]
2016-09-20 20:59 ` Evgeni Dobrev

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=57E21D8E.100@denx.de \
    --to=hs@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