From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Tom Li <tomli@tomli.me>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Teddy Wang <teddy.wang@siliconmotion.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
LFBDEV <linux-fbdev@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2 7/7] MAINTAINERS: sm712fb: list myself as one maintainer.
Date: Tue, 2 Apr 2019 22:09:31 +0100 [thread overview]
Message-ID: <CADVatmPtQAfSC=UkYWHKUx98JK=PMcSZB29ULeQKTBLD9iPnkw@mail.gmail.com> (raw)
In-Reply-To: <20190401174103.GF15736@localhost.localdomain>
On Mon, Apr 1, 2019 at 6:41 PM Tom Li <tomli@tomli.me> wrote:
>
> On Sun, Mar 31, 2019 at 08:08:01PM +0100, Sudip Mukherjee wrote:
> > Technically I donot have any problem with this, you seem to know more
> > about SM712 than I know. But Teddy Wang is also an existing maintainer
> > and I think there should be an ack from him before this is accepted.
>
> Okay, I'll write a personal mail to Teddy. I think it could be a separate
> patch to allow more time for communication, but the problem is that, if
> the MAINTAINERS and the new changes are not merged at the same time, users
> who have problems may unable to see my name and E-mail address for reporting
> problems.
git will not forget that you have done the changes. :)
So anyone who has a problem only needs to do a "git blame" to see who
has done it and the user will get your name and email to contact you.
If that is the only reason you think your name is added as a
maintainer then I guess that is not a valid concern and then in that
case I am not seeing any need to add your name in maintainer.
Bartlomiej can you advise please.
--
Regards
Sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Tom Li <tomli@tomli.me>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: LFBDEV <linux-fbdev@vger.kernel.org>,
Teddy Wang <teddy.wang@siliconmotion.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 7/7] MAINTAINERS: sm712fb: list myself as one maintainer.
Date: Tue, 02 Apr 2019 21:09:31 +0000 [thread overview]
Message-ID: <CADVatmPtQAfSC=UkYWHKUx98JK=PMcSZB29ULeQKTBLD9iPnkw@mail.gmail.com> (raw)
In-Reply-To: <20190401174103.GF15736@localhost.localdomain>
On Mon, Apr 1, 2019 at 6:41 PM Tom Li <tomli@tomli.me> wrote:
>
> On Sun, Mar 31, 2019 at 08:08:01PM +0100, Sudip Mukherjee wrote:
> > Technically I donot have any problem with this, you seem to know more
> > about SM712 than I know. But Teddy Wang is also an existing maintainer
> > and I think there should be an ack from him before this is accepted.
>
> Okay, I'll write a personal mail to Teddy. I think it could be a separate
> patch to allow more time for communication, but the problem is that, if
> the MAINTAINERS and the new changes are not merged at the same time, users
> who have problems may unable to see my name and E-mail address for reporting
> problems.
git will not forget that you have done the changes. :)
So anyone who has a problem only needs to do a "git blame" to see who
has done it and the user will get your name and email to contact you.
If that is the only reason you think your name is added as a
maintainer then I guess that is not a valid concern and then in that
case I am not seeing any need to add your name in maintainer.
Bartlomiej can you advise please.
--
Regards
Sudip
WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Tom Li <tomli@tomli.me>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: LFBDEV <linux-fbdev@vger.kernel.org>,
Teddy Wang <teddy.wang@siliconmotion.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 7/7] MAINTAINERS: sm712fb: list myself as one maintainer.
Date: Tue, 2 Apr 2019 22:09:31 +0100 [thread overview]
Message-ID: <CADVatmPtQAfSC=UkYWHKUx98JK=PMcSZB29ULeQKTBLD9iPnkw@mail.gmail.com> (raw)
In-Reply-To: <20190401174103.GF15736@localhost.localdomain>
On Mon, Apr 1, 2019 at 6:41 PM Tom Li <tomli@tomli.me> wrote:
>
> On Sun, Mar 31, 2019 at 08:08:01PM +0100, Sudip Mukherjee wrote:
> > Technically I donot have any problem with this, you seem to know more
> > about SM712 than I know. But Teddy Wang is also an existing maintainer
> > and I think there should be an ack from him before this is accepted.
>
> Okay, I'll write a personal mail to Teddy. I think it could be a separate
> patch to allow more time for communication, but the problem is that, if
> the MAINTAINERS and the new changes are not merged at the same time, users
> who have problems may unable to see my name and E-mail address for reporting
> problems.
git will not forget that you have done the changes. :)
So anyone who has a problem only needs to do a "git blame" to see who
has done it and the user will get your name and email to contact you.
If that is the only reason you think your name is added as a
maintainer then I guess that is not a valid concern and then in that
case I am not seeing any need to add your name in maintainer.
Bartlomiej can you advise please.
--
Regards
Sudip
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-02 21:10 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 5:17 [PATCH v2 0/7] implement 2D acceleration, minor cleanups, doc updates Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-22 5:17 ` [PATCH v2 1/7] fbdev: sm712fb: use type "u8" for 8-bit I/O Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 17:16 ` Sudip Mukherjee
2019-03-31 17:16 ` Sudip Mukherjee
2019-03-31 17:16 ` Sudip Mukherjee
2019-03-22 5:17 ` [PATCH v2 2/7] fbdev: sm712fb: add 2D-related I/O headers and functions Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 17:25 ` Sudip Mukherjee
2019-03-31 17:25 ` Sudip Mukherjee
2019-04-01 16:04 ` Tom Li
2019-04-01 16:04 ` Tom Li
2019-03-22 5:17 ` [PATCH v2 3/7] fbdev: sm712fb: support 2D acceleration on SM712 w/ Little-Endian CPU Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 18:09 ` Sudip Mukherjee
2019-03-31 18:09 ` Sudip Mukherjee
2019-04-01 16:26 ` Tom Li
2019-04-01 16:26 ` Tom Li
2019-04-02 20:53 ` Sudip Mukherjee
2019-04-02 20:53 ` Sudip Mukherjee
2019-03-22 5:17 ` [PATCH v2 4/7] fbdev: sm712fb: add 32-bit color modes, drops some other modes Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 18:33 ` Sudip Mukherjee
2019-03-31 18:33 ` Sudip Mukherjee
2019-04-01 16:41 ` Tom Li
2019-04-01 16:41 ` Tom Li
2019-04-02 20:59 ` Sudip Mukherjee
2019-04-02 20:59 ` Sudip Mukherjee
2019-03-22 5:17 ` [PATCH v2 5/7] Documentation: fb: sm712fb: add information mainly about 2D Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 18:54 ` Sudip Mukherjee
2019-03-31 18:54 ` Sudip Mukherjee
2019-03-31 18:54 ` Sudip Mukherjee
2019-04-01 17:30 ` Tom Li
2019-04-01 17:30 ` Tom Li
2019-04-02 21:03 ` Sudip Mukherjee
2019-04-02 21:03 ` Sudip Mukherjee
2019-04-02 21:03 ` Sudip Mukherjee
2019-03-22 5:17 ` [PATCH v2 6/7] fbdev: sm712fb: Kconfig: add information about docs Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 19:01 ` Sudip Mukherjee
2019-03-31 19:01 ` Sudip Mukherjee
2019-04-01 17:33 ` Tom Li
2019-04-01 17:33 ` Tom Li
2019-03-22 5:17 ` [PATCH v2 7/7] MAINTAINERS: sm712fb: list myself as one maintainer Yifeng Li
2019-03-22 5:17 ` Yifeng Li
2019-03-31 19:08 ` Sudip Mukherjee
2019-03-31 19:08 ` Sudip Mukherjee
2019-03-31 19:08 ` Sudip Mukherjee
2019-04-01 17:41 ` Tom Li
2019-04-01 17:41 ` Tom Li
2019-04-02 21:09 ` Sudip Mukherjee [this message]
2019-04-02 21:09 ` Sudip Mukherjee
2019-04-02 21:09 ` Sudip Mukherjee
2019-04-03 13:53 ` Bartlomiej Zolnierkiewicz
2019-04-03 13:53 ` Bartlomiej Zolnierkiewicz
2019-04-05 22:11 ` Sudip Mukherjee
2019-04-05 22:11 ` Sudip Mukherjee
2019-04-05 22:11 ` Sudip Mukherjee
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='CADVatmPtQAfSC=UkYWHKUx98JK=PMcSZB29ULeQKTBLD9iPnkw@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=teddy.wang@siliconmotion.com \
--cc=tomli@tomli.me \
/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.