lkml.org 
[lkml]   [2015]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH V2] drivers: CCI: fix used_mask init in validate_group()
    From
    Date
    On Thu, 2015-04-30 at 15:38 +0100, Mark Rutland wrote:
    > On Thu, Apr 30, 2015 at 03:03:07PM +0100, Mark Salter wrote:
    > > On Thu, 2015-04-30 at 14:33 +0100, Mark Rutland wrote:
    > > > > > Could you please send this to arm-soc as suggested by Will, with the
    > > > > > relevant acks/reviews ?
    > > > > >
    > > > >
    > > > > I sent it on Tuesday. Did it not show up? Is arm@kernel.org the correct
    > > > > address? I got the cc:
    > > > >
    > > > > From: Mark Salter <msalter@redhat.com>
    > > > > To: arm@kernel.org
    > > > > Cc: Mark Salter <msalter@redhat.com>
    > > > > Subject: [PATCH V2] drivers: CCI: fix used_mask init in validate_group()
    > > > > Date: Tue, 28 Apr 2015 13:09:32 -0400
    > > > > Message-Id: <1430240972-16386-1-git-send-email-msalter@redhat.com>
    > > >
    > > > That's the right address, but that only goes to the maintainers, and
    > > > doesn't get copied to any list. In future, please Cc linux-arm-kernel in
    > > > addition.
    > >
    > > That's where I sent it originally.
    >
    > Sure, but it's good to Cc when sending to arm-soc so as to make it
    > visible that the patches have been sent. Doing so avoids the necessity
    > of queries like Suzuki's, and makes it possible for others to reply to
    > the version sent to arm@kernel.org in the case of conflicts or other
    > issues.

    But why did it need to be sent to a private maintainer's list in the
    first place? I think that the destination addresses of the original
    posting was perfectly reasonable given output from get_maintainer.pl
    and that sending me to a private list was an unnecessary hoop to
    jump through.




    \
     
     \ /
      Last update: 2015-04-30 17:21    [W:3.691 / U:0.052 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site