linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL REQUEST] at24 updates for 4.16
Date: Thu, 4 Jan 2018 10:04:57 +0100	[thread overview]
Message-ID: <CAMRc=MfNKbykgAvhRpuk=x8PFM2JvgK6rwpPvhc+tjRbzA=f_g@mail.gmail.com> (raw)
In-Reply-To: <20180103215433.n5lmyzzgc5auub2m@ninjato>

2018-01-03 22:54 GMT+01:00 Wolfram Sang <wsa@the-dreams.de>:
> On Wed, Jan 03, 2018 at 05:01:13PM +0100, Bartosz Golaszewski wrote:
>> Hi Wolfram,
>>
>> The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d:
>>
>>   Linux 4.15-rc6 (2017-12-31 14:47:43 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/at24-4.16-updates-for-wolfram
>
> Thanks, pulled!
>
> Note: patchwork still doesn't recognize your pull requests, but I don't
> understand why :( So, please ping me if I don't pull within a few days.
>

Strange indeed. Is feeding the output of 'git request-pull' to 'mail'
the correct way of sending pull requests?

While we're at it - if you'll choose to pick up the series from
Heiner[1] for 4.16, you can take all three patches in, I'll leave my
Reviewed-by in patch 3/3.

Best regards,
Bartosz Golaszewski

[1] http://patchwork.ozlabs.org/project/linux-i2c/list/?series=19586

  reply	other threads:[~2018-01-04  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 16:01 [GIT PULL REQUEST] at24 updates for 4.16 Bartosz Golaszewski
2018-01-03 21:54 ` Wolfram Sang
2018-01-04  9:04   ` Bartosz Golaszewski [this message]
2018-02-21  9:12     ` Wolfram Sang

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='CAMRc=MfNKbykgAvhRpuk=x8PFM2JvgK6rwpPvhc+tjRbzA=f_g@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).