mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Lee Jones <lee.jones@linaro.org>, Morris Ku <saumah@gmail.com>
Cc: linux-kernel@vger.kernel.org, morris_ku@sunix.com
Subject: Re: [PATCH 1/4] Add support for SUNIX Multi-I/O board
Date: Fri, 5 Apr 2019 10:46:07 +0200	[thread overview]
Message-ID: <377340b0-1860-6672-ebee-5e73dc1db722@metux.net> (raw)
In-Reply-To: <20190402061925.GU4187@dell>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

On 02.04.19 08:19, Lee Jones wrote:

> Please use `git format-patch` and `git send-email` to create and
> submit your patches.  Use the following flags; --annotate, --compose
> and --thread to ensure the patches are sent a) pinned to each other so
> they do not become spread throughout people's inboxes and b) a cover
> letter is provided which should contain a summary of what you are
> trying to achieve.

here's a little script which helps w/ that: it automatically picks
the corresponding maintainers/maillists, you can also pass the usual
git-send-email flags.


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

[-- Attachment #2: git-send-patch --]
[-- Type: text/plain, Size: 1634 bytes --]

#!/bin/bash
# SPDX-License-Identifier: GPL-2.0

[ -x "$GIT" ]       || export GIT=git
[ -d "$KERNELSRC" ] || export KERNELSRC=.

LKML="linux-kernel@vger.kernel.org"

check_ksrc() {
    if [ -d $KERNELSRC/arch ] && \
       [ -d $KERNELSRC/block ] && \
       [ -d $KERNELSRC/init ] && \
       [ -d $KERNELSRC/kernel ] && \
       [ -d $KERNELSRC/sound ] && \
       [ -d $KERNELSRC/drivers ] && \
       [ -d $KERNELSRC/net ] && \
       [ -d $KERNELSRC/include ] && \
       [ -f $KERNELSRC/COPYING ] && \
       [ -f $KERNELSRC/MAINTAINERS ] && \
       [ -f $KERNELSRC/CREDITS ] && \
       [ -f $KERNELSRC/Kconfig ] && \
       [ -f $KERNELSRC/Makefile ]; then
        return 0
    else
        echo "$0: cant find the kernel source tree. please call me from the topdir" >&2
        exit 1
    fi
}

check_ksrc

get_files() {
    $GIT diff --name-only "$REF"
}

get_maintainers() {
    $KERNELSRC/scripts/get_maintainer.pl --m --l --remove-duplicates `get_files` |
        grep -v "$LKML" | \
        grep -E "(maintainer|reviewer|open list)" | \
        grep -o '[[:alnum:]+\.\_\-]*@[[:alnum:]+\.\_\-]*'
}

construct_params() {
    echo -n "--to=$LKML "
    for a in $MAINTAINERS; do
        echo -n "--cc=$a "
    done
}

if [ ! "$1" ]; then
    echo "$0: missing git revision to send out" >&2
    echo "" >&2
    echo "for example: 'HEAD^' for sending just the last patch" >&2
    echo >&2
    echo "$0 <git-ref> [<extra params for git-send-mail>]"
    exit 1
fi

REF="$1"
shift

echo "scanning for maintainers ..." >&2
MAINTAINERS=`get_maintainers`

echo "sending mail ..." >&2
$GIT send-email `construct_params` "$REF" "$@"

      reply	other threads:[~2019-04-05  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 12:07 Morris Ku
2019-04-02  6:19 ` Lee Jones
2019-04-05  8:46   ` Enrico Weigelt, metux IT consult [this message]

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=377340b0-1860-6672-ebee-5e73dc1db722@metux.net \
    --to=lkml@metux.net \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morris_ku@sunix.com \
    --cc=saumah@gmail.com \
    /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

all inboxes | Powered by JetHome®