Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>
Subject: Re: [PATCH 2/5 V2] b43: N-PHY: implement and add multi-dimensional table writing
Date: Mon, 18 Jan 2010 16:24:51 +0100	[thread overview]
Message-ID: <69e28c911001180724q58ff24eas8b6c72e834a6f818@mail.gmail.com> (raw)
In-Reply-To: <b170af451001180616w5d79411fka3835e8da04e2bcf@mail.gmail.com>

You don't even need to mention it, as Git handles offset/fuzzy patches
automatically.

2010/1/18 Rafał Miłecki <zajec5@gmail.com>:
> W dniu 18 stycznia 2010 01:28 użytkownik Gábor Stefanik
> <netrolller.3d@gmail.com> napisał:
>> 2010/1/18 Rafał Miłecki <zajec5@gmail.com>:
>>> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
>>> ---
>>> V2: updated to apply without fuzz
>>
>> Actually, you do not need to do that - offset or fuzzy patches will
>> still be applied cleanly AFAIK, without any intervention.
>> (John, correct me if I'm wrong here...)
>
> That's right, it actually did. I just wanted to don't bother John with
> wondering if everything gone correctly. I guess I could just mention
> it instead of sending patch :)
>
> --
> Rafał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

      reply	other threads:[~2010-01-18 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 23:21 [PATCH 2/5 V2] b43: N-PHY: implement and add multi-dimensional table writing Rafał Miłecki
2010-01-18  0:28 ` Gábor Stefanik
2010-01-18 14:16   ` Rafał Miłecki
2010-01-18 15:24     ` Gábor Stefanik [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=69e28c911001180724q58ff24eas8b6c72e834a6f818@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=zajec5@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